How it gets organised — one page
How an experiment becomes a working system with contracts, proof and continuity.
Something in this artifact failed to run
The content below is still readable, but an interactive control may not respond.
One page / From experiment to working system
Keep the creature’s identity; make its promises travel
A roadmap holds the image of the whole. Each slice removes one uncertainty and leaves a reviewable result; the cold handoff carries the image and next cut to someone who was not in the room.
| Stage | Artifact that travels | Workshop example |
|---|---|---|
| Purpose | Brief and visible non-goals. | A bird’s sound path; a rider’s identity constraints. |
| Intermediate model | Graph, schema, proxy, rig or beat sheet. | Vantara legal intent; MOLT song/plate association. |
| Receiving contract | Small interface and a real consumer. | TALON StageBeat; AV-core vectors/emitted copies. |
| Proof boundary | Measured check plus exact human review. | Editor import; owner watches the named cut. |
| Cold handoff | State, exact version/checks, decisions and one next slice. | A fresh session can pick up without the previous chat. |
Can a fresh session pick it up?
From the canonical record and linked files, locate the branch and local-only state, reproduce a relevant check, then restate the next slice before editing. This is a proposed pickup test, not a completed fleet-wide drill.
Principles: purpose before surface; facts separate from suggestions; rules before improvisation; one useful slice; the real receiving surface; a cold-ready handoff.
Ranks are context, not value. The recorded owner-scope registry has 2 Apex, 17 emerging and 1 unranked repo. It is not a fresh audit, an IP score or a reason to start seventeen roadmaps.
Registry snapshot 13 October 2026; excludes Apollo and school analytics. Principles are editorial synthesis; operational adoption requires evidence.