Toolkit/lens
Scope Charter
Deep alignment artifact for cross-functional initiatives.
scoperiskcontractselection
The Scope Charter is the definitive, cross-functional contract generated by the Governance OS. It eliminates ambiguity before delivery begins.
The Structure of the Charter
The Charter is not a blank Word document. It is a compiled export generated by the OS based on your inputs across the Outcome, DoR, DoD, and Assembler tabs.
- ☐Executive Summary & Problem Statement: The 'Why'.
- ☐Success Signals: Binary, testable criteria.
- ☐Team Resourcing: The Capital Envelope ($) and Capacity Envelope (FTE).
- ☐Stakeholders & Allowed Signers: The named accountability matrix.
The Assembler & Architecture Map
Unlike a standard project brief, the Scope Charter forces architectural reality into the contract via the Assembler:
- Macro Gantt / Milestones: Explicit target dates, separated by Gates, Dependencies, and Releases.
- Upstream Integrations: Databases, APIs, or teams providing data to the project.
- Downstream Integrations: Systems, platforms, or consumers relying on the project's output.
The AI Sanity Check
Before a Charter can be signed and locked, it is submitted to the AI Governance Auditor. The Auditor reads the entire contract and flags structural anomalies:
- ☐Systemic Risk Level (Low/Medium/High)
- ☐Financial Sanity (Does the timeline fit the Capital Envelope?)
- ☐Bottlenecks (e.g., '4 milestones squeezed into 1 week')
The Lock Mechanism
Charters require explicit cryptographic sign-off. Silence is not consent. By clicking "Sign Now", approvers accept the Scope Contract, the Auto-Selected Accelerator Path, and the AI Audit findings.