Sprint Contract System
Pre-work contracts co-signed by builder and evaluator. Eliminates close-enough shipping. 48 contracts shipped.
DisciplineRead
Take the method with you.
Working templates, operating disciplines, and reusable tools. Open a playbook to see the method, examples, and available files.
Postmortem Discipline
Blameless postmortems with structural action items. The discipline that makes the same mistake stop happening twice.
DisciplineRead
CLAUDE.md Template
The annotated skeleton every Claude Code operator needs before their second week. Three worked examples, one framing essay, and the advice everyone skips: what NOT to put in.
TemplateRead
Agent Routing Template
The chief-of-staff + N-specialists scaffold. Routing table, authority levels, and an escalation protocol — the piece everyone skips until it bites them.
TemplateRead
Vault Structure
13-folder Obsidian template that scales across multiple ventures. The operating system around your AI agents.
ArchitectureRead
Memory Architecture
The MEMORY.md index pattern. Four memory types, a staleness protocol, and the one rule that stops memory systems from becoming archives.
ArchitectureRead
Agent Hierarchies
Authority levels, the mothership pattern, generation/evaluation separation. The structural decisions most multi-agent setups skip until they break.
ArchitectureRead
Token Discipline
Context window hygiene. What belongs in CLAUDE.md vs memory vs code. The compaction strategy that keeps sessions fast after month 3.
DisciplineRead
TruPath Stack
The assembled picture — how agents, hooks, memory, sprint contracts, kanban, and the Telegram bridge connect into a single operating system for a multi-venture portfolio.
ArchitectureRead
Hooks Bundle
Five production-tested Claude Code hooks — session loading, config protection, eval auditing, decision logging, anchor-check cadence. The mechanical enforcement layer your CLAUDE.md rules have been promising.
ToolkitRead
The Security & IP Discipline Playbook
Five gates that keep a fast-moving AI shop from leaking its secrets, its source license, or its patent rights. Written the day I pasted my session tokens into a chat.
DisciplineRead
The CV-for-Physical-Sports Wedge Playbook
Don't build computer vision for sports. Build it for one sport — the one with the most constrained geometry and the simplest rules — get it referee-grade, then generalize. Three filters and the trust-bar framework.
DisciplineRead
Why run a parallel research arm
A small operator can run a parallel research project alongside two startups without it cannibalizing them — but only under specific conditions, and Parley is the worked example.
DisciplineRead
How to run one without it cannibalizing the startup
Four discipline levers that let a side research arm survive contact with the main work — scope rails, monthly cadence, public publishing, and decision logs, with kill criteria written down in advance.
DisciplineRead
The Honest Sign-Language Research Playbook
The discipline behind Parley's notebooks: question-first contracts, signer-holdout splits, multi-seed floors, failure-modes-first, and a Deaf-community honesty checklist. The rules that make a 45% you can trust beat an 85% you can't.
DisciplineRead
Pre-register the recipe before you rank architectures
A shared training recipe across architectures does not control for the recipe. It bakes it into the result and disguises it as an architecture finding. Four cheap controls keep the ranking honest.
DisciplineRead
Run a falsification session before you trust your own asset
Operators accumulate load-bearing assets that were built under deadline and never adversarially examined. A one-evening AI falsification session is the cheapest insurance that exists, and the discipline is scheduling it before the asset feeds a decision.
DisciplineRead
The five-phase audit: a science agent's working method
An agent audit of a Quantum Caddy simulator ran five phases in a fixed order — reproduce the as-built model, rebuild it from first principles, map the divergence, budget the uncertainty, ship a ranked measurement list. What each phase produced, what breaks it, and how to run it on a demand model or a game economy.
ToolkitRead