Method
AI to build, AI to decide — always from a written brief
AI-assisted development fails when nothing is written down. Every project here runs on the same discipline: the context, the plan, and the mistakes all live in documents the next session — human or AI — can pick up cold.
The artifacts
What every project carries
A project constitution
Every repo has a CLAUDE.md: architecture, conventions, and guard rails the AI must follow. Cross-project rules live in a shared map, so no session works blind.
Agent briefs
Features start as written briefs — the trading coach began as a 300-line specification covering endpoints, schema, and the full system prompt before any code existed.
Plan documents
Multi-step work gets a reviewed plan with tasks and verification steps. One driver per working tree; hand-offs happen through task documents at the target repo, not by reaching across projects.
Custom skills
Repeatable judgment gets encoded: a design-system skill keeps every AI edit on-brand; a rubric-interview skill lets a non-programmer teach an agent a scorecard in fifteen minutes.
Bug ledgers
Mistakes get written down, not buried
Two examples from these projects. A vector-search configuration bug silently broke memory recall for every agent and every coding session — found, traced to an upstream issue, fixed, and documented. And in the backtest lab, a subtle bar-labeling bug was leaking about a minute of hindsight into every simulated trade: the fix went in the ledger, and every previously computed statistic was declared invalid and purged.
That second one matters. The system was reporting profitable results. The ledger is why those numbers didn't survive.
Human gates
Autonomy with a spine
Agents act on their own inside boundaries that are enforced by infrastructure, not vibes: hard spend ceilings on data purchases, model routing by cost tier, approval gates that block a pipeline until a human rules, and memory governance that stops credentials and transcripts at the door. The human decision point is a first-class part of every design on this site — it's the orange in every diagram.
Say hello
Curious about any of this?
No pitch — the work is the pitch. If something here sparked an idea, or you'd like a closer look at how a piece of it fits together, I'd genuinely love to talk about it.
Say hello