Every capability is a governance record
Nothing below is aspirational. Each module maps to a manual chapter.
The Accelerator rail moving from POC to Pilot to MVP, each gate approved by a named role.
No Lens output, no work starts.
Scores a request across six readiness axes and forces the choice between a Scope Card and a Scope Charter. The output is mathematical, not a vote.
- Six readiness axes scored 0 to 5
- Forces a Scope Card or a Scope Charter
- DoR and DoD evidence at every gate
The Lens record view scoring six readiness axes, one axis marked blocking, ending on an Above threshold verdict.
You may skip a phase. You may not skip the risk.
Four phases, four gates, four named approvers.
Gates and forumsPOC
Feasibility gate. Arch lead
Pilot
Behaviour gate. Product owner
MVP
Value gate. Sponsor
V1
Operational gate. Platform lead
Scope frozen. Not scope forgotten.
Freezes scope during execution and halts work when a boundary moves without a trade-off, an owner, or a signature.
- 5 stop-work triggers
A frozen charter's risk axis rescored below threshold, firing a stop-work trigger and writing a revision.
Liability is never shared.
Binds the three into a closed loop with four permanent roles whose liability is never shared.
Intake
Work enters the OS as an idea, not a ticket.
Lens
Intent becomes a Scope of Work with evidence and named ownership.
Accelerator
Delivery executes through deliberate phases and signed gates.
Shield
Focus, people and scope integrity are protected throughout.
Audit exhaust
Produced as a default output, not assembled after the fact.
Change
Every deviation is governed through the Change Forum, or rejected.
What every run produces
| Artifact | What it proves | When it is produced |
|---|---|---|
| Scope Charter | Scored intent, with owners named and boundaries and dependencies mapped. | Before the Accelerator will accept the work. |
| DoR / DoD record | Evidence, not opinion, that a scope was ready to start and complete to finish. | At Lens entry and at every phase exit. |
| Accelerator gate log | Every phase transition (POC, Pilot, MVP, V1) and who approved it. | At each Feasibility, Behaviour, Value and Operational gate. |
| Change Forum decision | The zero-sum trade-off behind a scope change: what was added, what was dropped, and who owns it. | Whenever scope, timeline, boundary or risk shifts mid-delivery. |
| Stop-work record | Why delivery paused, which condition failed, and who cleared it before work resumed. | The moment a governance condition is no longer satisfied. |
| Audit exhaust | A reconstructable record of what happened, produced as a byproduct, not filed after the fact. | Continuously, across every artifact above. |
What the record turns into
Once a scope is signed, these capabilities carry it into delivery. Each one starts from the signed record, not from a copy of it.
Master Dossier
The signed project as one PDF: problem statement and resourcing, charter scope, architecture and integrations, the project plan, governance protocols, sign-offs and every contract amendment.
Pro and above
Agent Manifest
Compiles the locked architecture into a Markdown manifest, with the phased prompts an AI coding agent needs to build inside the signed scope.
Pro and above
Executive Digest
A personalized portfolio digest by email, sent on demand: to yourself, to every executive, or to named people.
Every paid plan (a digest to yourself is free)
Reality Checker
Upload a CSV or JSON export from Azure DevOps, Jira or Linear. It is mapped against the signed milestones and reports progress, blockers, and work assigned to people outside the governance team.
Pro and above
Jira and Azure DevOps export
Turns the locked scope, architecture and milestones into a backlog import file for Azure DevOps or Jira, with optional instructions for how the work is split.
Pro and above
Made for the lead who owns the consequence.
Engineering leads sign feasibility. Sponsors sign value. The record names both.
