Nine plans that ran. One per kind of work.
These are plans from our own use of the system, run between August 5 and September 12, 2026: phases, gates, and the specialists each step was assigned to. They are examples of what it produced for our goals, not templates that ship with it. We publish the structure, never the contents: the shape is the proof, and the contents belong to whoever the work was for.
One badly typed sentence, five phases, a document and a dashboard.
Its prompt is verbatim; nobody tidied it up before sending. Phase five carries the only gate: nothing leaves the workspace until a person signs.
INTELLIGENCE SWEEP · SIGNED · 5 PHASES · 8 STEPS · 4 CALLSIGNSphase 1 · intelligence sweep · 3 steps, parallel · MARKET_INTEL ✓ complete phase 2 · capability-to-value · 2 steps, parallel · LIFECYCLE +1 ✓ complete phase 3 · strategic synthesis · 1 step · GTM_STRATEGIST ✓ complete phase 4 · peer review · 1 step · VALUE_ARCHITECT ✓ complete phase 5 · final deliverable · 1 step · GTM_STRATEGIST · GATE ● awaitingledger 0x3f9a…c21e · prev 0x8b04…77d1 · 09/03/2026 7:06 PM ET
Phases, step counts, line-ups and the gate position are read from the plan record. A gate is a property of a phase, not a phase of its own. Ledger hashes are illustrative; we do not publish a live chain.
“Based on these past sessions what are business outcomes that can be achieved. Be very detailed, search the web and any other intel gathering that can help you find a market fit for this system”
| What the signature binds | Why it is here |
|---|---|
| The plan body: 5 phases, 8 steps, 1 gate | Change a step, a phase or the gate and the signature no longer verifies. |
| Four specialists: MARKET_INTEL, LIFECYCLE, VALUE_ARCHITECT, GTM_STRATEGIST | MARKET_INTEL did not exist when the plan was written. The foundry forged it, and the plan was signed against the hash of what came out. |
| The operator | A person, named, at a time, not a service account. |
One per kind of work.
Same system, different work. The team changes; nothing underneath it does.
| Work | Plan | Phases | Steps | Gates | The team it was staffed with |
|---|---|---|---|---|---|
| Security | Attack Surface Mapping mapping → hunt wave 1 → hunt wave 2 → adversarial verification → cross-verification → executive report | 6 | 16 | 2 | RED_LEAD and seven forged hunters |
| Financial | Filing Retrieval retrieval → deep analysis → pair review → executive report · market-data integration | 4 | 8 | 2 | SEC_REG, FUNDAMENTALS, VALUATION, SECTOR, RISK_COUNSEL, SYNTHESIS |
| Deliverables | Investor Content Assembly assembly → build deliverables → cross-review and validation | 3 | 7 | 2 | SAAS_STRAT, VENTURE, TECHIND, SCRIBE |
| Audit | Source Code Audit audit → end-game synthesis → technical validation → deliverable · repository integration | 4 | 6 | 2 | SRC_ARCH, LIFECYCLE, BRIDGE |
| Extraction | Pattern Analysis analysis → peer review → synthesis | 3 | 6 | 1 | VERTICAL_ANALYST, WORKFLOW_ARCH, VALUE_ARCHITECT |
| Brand | Content Strategy & Copy strategy and copy → visual production → social card assembly → brand compliance review | 4 | 5 | 0 | CONTENT, BRAND, LOGO_DESIGNER, ADTECH, BRIDGE |
| Build | Corporate Website Build single phase, four parallel steps | 1 | 4 | 0 | BRAND, ADVOCATE, BRIDGE |
| Staffing | Specialist Creation one signed step: a domain brief in, a forged specialist out | 1 | 1 | 1 | ALPHA_ED |
Our own runs, August 5 – September 12, 2026. Callsigns are specialist roles the system created, not people.
Six to one.
A security engagement takes six phases and eight specialists. Staffing a new domain takes one signed step. The same machine sized both.
Seven of nine review themselves.
Peer review, pair review, cross-verification, compliance review: a checking phase the operator did not have to ask for.
Eleven places a person signed.
Across nine plans. The gates sit where the work becomes irreversible, not at the end as a formality.
The tenth plan should be yours.
Bring a goal and we will plan it in front of you: phases, line-up, ceiling and gates, before anything runs.