Same pipeline. Now it watches itself.
The spec-to-ship loop didn't change in v3 — skills encode how, three contracts per repo define what, four gates block every commit. What changed is what happens after a commit lands: escapes are detected, doctrine is audited, and every closed goal carries its cost.
What changed in v3: in v2 the factory shipped work and reported completion. In v3 three instruments close the feedback gap — an escape detector, a weekly doctrine audit, and cost-per-outcome accounting.
Skills are short markdown procedures the agents load when needed — "how Michael wants this done", encoded once, reused across products. Small, composable, version-controlled. A few in active use:
Skills follow the open agentskills.io standard, so the same skill is portable across agent tools. A skill loads only when its trigger fires — it doesn't clutter the agent's context the rest of the time.
Where skills are cross-project capabilities, these three contracts ship inside each repo — what THIS product is, what its rules are, what it should look like. Without them, a worker has nowhere to anchor.
Skills define how, contracts define what, the loop is when they meet — five stages that turn an idea into a shipped commit.
Nothing ships without passing four checks. The rule that drives them: a test passing isn't the same as a feature working.
An idea in.
A deployed product out.
The pipeline that turns specs into shipped software. Skills encode how. The loop runs on every job the resident fleet picks up. Four quality gates on every commit, then an independent review before anything merges. Three contracts at every project root. Same factory, every product.
What v2 changed: same loop, same gates — but it now runs on the resident fleet instead of a per-task scheduled job, and every product ships with three short contract files so a worker always knows the rules before it touches the code.
Skills are short markdown procedures the agents load when needed. They encode "how Michael wants this done" into something the fleet can reuse across products. A skill is small (a few KB), composable, and version-controlled. A few in active use:
Skills follow the open agentskills.io standard, so the same skill is portable across different agent tools. A skill loads only when its trigger fires — it doesn't clutter the agent's context the rest of the time.
Where Skills are cross-project capabilities the fleet brings to any codebase, the three contracts below are the per-project files that ship inside each repo. They tell the factory what THIS product is, what its rules are, what it should look like. Without them, a worker has nowhere to anchor.
Skills define how the agents work. The three contracts define what the product is. The Loop is when they meet — five stages that turn an idea into a shipped commit. Every job the resident fleet picks up runs through this loop end-to-end.
Nothing ships without passing four checks. The rule that drives them: a test passing isn't the same as a feature working.
An idea in.
A deployed product out.
The agentic engineering pipeline that turns specs into shipped software. Skills encode how. The loop runs on every resident-fleet dispatch. Four blocking quality gates on every commit, then a fresh-context review before anything reaches master. Three contracts at every project root. Same factory, every product.
Skills are markdown procedures the agents auto-load when needed. They encode "how Michael wants this done" into something the fleet can reuse across products. A skill is small (a few KB), composable, and version-controlled. A few examples in active use:
Skills follow the open agentskills.io standard, so the same skill works across Claude Code, Codex, Cursor, OpenCode and other agent harnesses. Skills are loaded only when their trigger fires — they don't pollute the agent's context the rest of the time.
Where Skills are cross-project capabilities the fleet brings to any codebase, the three contracts below are the per-project artifacts that ship inside each repo. They tell the factory what THIS product is, what its rules are, what it should look like. Without them a dispatched worker has nowhere to anchor.
Skills define how the agents work. The three contracts define what the product is. The Loop is when they meet — five stages that turn an idea into a shipped commit. Every resident-fleet dispatch runs one work-item through this loop end-to-end.
any, no implicit, no escapes.