Claude Code, subagents, and persistent memory aren't an accessory to the work — they're the toolchain that lets one person ship like a team. But the interesting part isn't that AI writes code; it's the discipline wrapped around it so that moving fast doesn't mean moving carelessly.
I build features with subagent-driven TDD: a spec, a plan, then implementation reviewed by independent spec- and code-quality passes. Risky claims go to adversarial verification panels — multiple agents whose job is to refute, not agree. They've caught real, verdict-changing bugs: a pairing flaw that could have promoted the strictly-worse strategy, a lookahead leak in a feature builder, a prompt-injection bypass — each killed before it merged. That discipline is now open source as refute — a skeptic-panel CLI + GitHub Action on npm, with a published eval that's honest about where the panel wins (100% recall on hard flawed claims a single reviewer missed) and where it doesn't (it over-flags, so CI mode defaults to comment-only).
Durable context is the other half. Two dozen operating playbooks hold the manual for each system; a 1.7 GB memory store keeps hard-won lessons across sessions; and a custom MCP server lets an agent touch a live exchange only through a hash-verified preview-then-execute gate — the gate, not a string scrub, is the trust boundary.
Promotion discipline
paper → shadow → canary → live, each step gated on out-of-sample evidence. Strategies die on data, not on a story.
Preregistration
Hypothesis, endpoints, kill thresholds — plus the RNG seed and a code+config hash — fixed before any run, so fast iteration can't become optional-stopping.
Adversarial review
Multi-agent red-teams as a merge gate — two security audits hardened the live arcade; an 8-agent panel guards the LLM-trader's invariants.
Honest by construction
No fabricated numbers — live surfaces show a dash when a bot is offline; triggers are verified against a clean readback before any outward action.
Fleet ops & cost
46 services on one self-managed host across promotion tiers, fed by 16 collectors into PostgreSQL — with spend caps and RPC retry budgets throughout.