{"slug":"architecture/10_GOVERNANCE","title":"10 · Governance","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/10_GOVERNANCE.mdx","bytes":2895,"description":"The hard gate between intent and execution — authority, policy, risk, approval, evidence, and audit","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n\n**May This Be Done?**\n\nGovernance is the hard gate between intent and execution. Nothing executes without passing through governance. It is not a suggestion layer — it is a hard stop.\n\n---\n\n## Governance Model\n\n```text\nIntent / Action\n      ↓\nPolicy Evaluation\n      ↓\nAuthorization Check\n      ↓\nRisk Assessment\n      ↓\nApproval Workflow\n      ↓\nExecution Token\n      ↓\nExecution\n```\n\n---\n\n## Governance Components\n\n| Component | Purpose |\n|-----------|---------|\n| **Policy Evaluation** | Checks against organizational policies |\n| **Authorization** | Verifies permissions and roles |\n| **Risk Assessment** | Evaluates risk level of the action |\n| **Approval Workflow** | Routes to human approvers when required |\n| **Limits & Guardrails** | Enforces spending, rate, and scope limits |\n| **Evidence Collection** | Gathers supporting evidence for the decision |\n| **Audit Trail** | Records who did what, when, and why |\n\n---\n\n## Governance Rules\n\n| Rule | Description |\n|------|-------------|\n| **No token = no execution** | Every execution requires a governance token |\n| **Every action is auditable** | Full traceability from intent to outcome |\n| **Human approval for high-risk** | High-risk actions require explicit human approval |\n| **Twin never acts without approval** | Twin proposals go through governance |\n| **Policies are enforceable** | Organizational policies are hard gates |\n\n---\n\n## Governance Gates\n\n### Composition Gate (Before Work Is Created)\n\nEvaluates whether work should be created:\n- Does this align with organizational goals?\n- Is this within the scope of the requesting role?\n- Are there policy conflicts?\n\n### Execution Gate (Before Work Is Executed)\n\nEvaluates whether approved work can be executed:\n- Is the execution within authorized scope?\n- Are there rate limits or budget constraints?\n- Is the target system healthy?\n- Is governance approval current?\n\n---\n\n## Authority Law\n\n> The Twin NEVER acts without approval. The user ALWAYS has control.\n\nThis is the fundamental governance invariant:\n- No chat required\n- No prompt required\n- No context explaining required\n- Just the Four Buttons: Store, Ask, Assign, Approve\n\n---\n\n## Governance Connects to\n\n| Layer | Relationship |\n|-------|-------------|\n| [Business Context](/architecture/01_BUSINESS_CONTEXT) | Policies derived from business context |\n| [Work Allocation](/architecture/09_WORK_ALLOCATION) | Evaluates allocation decisions |\n| [Twin Workbench](/architecture/07_TWIN_WORKBENCH) | Gates Twin actions |\n| [Agents](/architecture/12_AGENTS) | Gates agent execution |\n| [Execution](/architecture/13_EXECUTION) | Issues execution tokens |\n| [Reconciliation](/architecture/15_RECONCILIATION) | Records governance decisions |\n"}