Toolkit/lens

Governance RACI

Standardized accountability model for Governance OS.

rolesownershippeople

Accountability is singular. Contribution is plural. In the Governance OS, roles are not just HR titles—they are cryptographic keys to the Phase Gates.

🎭Tone:Quick-Memory Rule: Sponsor = Why, Delivery = What, Engineering = How.

Cryptographic Signers (The Core RACI)

These roles are explicitly named in the Allowed Signers block. Without their signatures, the platform will mathematically block the project from going Live.

Sponsor

Holds the Capital Envelope and the mandate. Signs the Charter and the Architecture. Accountable for whether the investment pays off.

Delivery Owner (PM/PO)

Guardian of the Scope. Signs every artifact. Ensures the work delivered matches the baseline. Owns the Change Forum triggers.

Engineering Lead

Owns the technical execution path and Capacity Envelope (FTE). Signs the Architecture and the Plan.

Risk Owner

A dynamic liability handle. If the AI recommends a Charter and you force a Scope Card, the Risk Owner must explicitly sign the Deviation Record.

Contributors (Consulted & Informed)

These roles are critical to the Assembler and Team Resourcing, but they do not hold cryptographic sign-off power for the baseline lock.

  • Architect: Consulted on domain boundaries and upstream/downstream integrations.
  • System-of-Record Owner: Decides what data means and who can change it.
  • Subject Matter Experts (SMEs): Provide domain context, test cases, and problem validation.
The Unambiguous Rule
If accountability is not explicitly assigned in the OS, the platform assumes the project is not ready to start.