// 18 DEEP DIVES · FOUR READING LANES
Find the method for the problem in front of you.
Start with the job: operate, verify, ship, or explore. Every path returns to evidence and an explicit next move.
01 / OPERATE
Direct the work
Tools, settings, voice, control surfaces, and the contracts that keep agent work bounded.
The four-agent toolbenchClaude, Codex, Droid and Cursor — what each is best at, how to route work between them, and the one mirrored context file that keeps them in sync.
Tuning the knobs: models & settingsReasoning effort, model tier, temperature, tool-use — and separate saved profiles for coding speed versus agentic work, with copy-usable configs.
Voice-driven developmentDriving a fleet of agents by talking — handling transcription artifacts, and the shorthand that expands one spoken phrase into a whole workflow.
Hermes on Telegram: a pocket control planeHow a Telegram-facing agent routes questions, monitoring, digests, diagnostics, bounded workflows, evidence, and human approvals without exposing the underlying systems.
Designing skills and loops for certain and uncertain outcomesHow to package agent skills as explicit contracts, use deterministic loops for exact predicates, and bound non-deterministic work with rubrics, budgets, reviewers, and human gates.
02 / VERIFY
Protect the truth
Source-of-truth checks, evidence loops, privacy boundaries, and failures that looked successful.
The verification loopA practical evidence ladder for turning ‘looks right’ into a result another person or agent can trust.
Context without oversharingHow to give agents enough context to work well while keeping private systems, personal details, credentials, and non-public facts out of public artifacts.
Before the AI edits: find the live truthA source-of-truth protocol for checking production, deploy state, repositories and generated artifacts before an agent changes the wrong version.
When ‘success’ is still brokenWhy a 200 response, green check, or finished-looking agent answer can still hide a failed user outcome—and what evidence closes the gap.
The stale worktree that passed every checkA postmortem pattern for the dangerous case where tests are green because they ran against the wrong source of truth.
03 / SHIP
Make the work compound
Recipes, publishing, handoffs, coordination, and memory that improve the next run.
The cookbookSeven copy-usable recipes — cache-bust blast radius, CSP hash recompute, adversarial verify, config recovery from live headers — each with the reasoning.
From rough brief to published pageHow a loose idea becomes a structured, visual, connected page—and leaves the seed for what to publish next.
Handoff packets that do not lose the plotA copy-usable transfer format for current state, decisions, evidence, stop conditions, and the smallest safe continuation.
Parallel agents without branch collisionsA practical ownership and integration method for running agents in parallel without colliding on shared files, generated artifacts, cache versions, or release state.
Decision ledgers for long-running agent workA practical way to preserve why an agent rule exists, append evidence that confirms or changes it, and name the trigger for its next review.
04 / EXPLORE
Test the frontier carefully
Local models, open weights, and risk ideas that remain useful when the tools change.
Local & uncensored modelsRunning open-weight models on your own machine — the stack, why privacy and cost make it worth it, and a plain, responsible explanation of what abliteration is.
Local model field notesA living test format for LM Studio, Gemma-family models, context limits, privacy, latency, failure modes, and honest cloud comparisons.
Position sizing for agent autonomyWhat derivatives, portfolio construction, and surviving volatility teach about permissions, stop conditions, and bounded agent action.