{"slug":"strategy/business-strategy/GOVERNANCE","title":"GOVERNANCE","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/GOVERNANCE.mdx","bytes":2889,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **Tier C — Historical.** This document is a point-in-time snapshot preserved for reference. For current architecture, see [CANONICAL_PLATFORM_ARCHITECTURE.md](../architecture/CANONICAL_PLATFORM_ARCHITECTURE.md).\n\nStatus: CURRENT\nScope: Governance policy, HITL, semantic stages, runtime identity classification\nCanonical Owner: Governance\nLast Verified: 2026-07-11\nEvidence Basis: docs/CANON.md, docs/platform-specs/09-governance-engine.md, docs/architecture/WORKBENCH_DOCTRINE.md, docs/platform-specs/10-signal-engine.md, wrangler manifests, Option B branch evidence\nSupersedes: none\nSuperseded By: none\n\n---\n\n## 1. WHAT GOVERNANCE IS\n\nGovernance owns policy and approval semantics.\n\nIt is the operational control plane that decides whether inferred state, proposed actions, or execution candidates may advance.\n\nGovernance is not a chat window. Governance is not modal UI for its own sake. Governance appears when policy requires it.\n\n```text\nUNDERSTAND\n→ PROPOSE\n→ GOVERN WHEN REQUIRED\n→ EXECUTE\n→ CONTINUE\n```\n\nThis is the canonical product-level loop.\n\nHistorical architectural expression:\n\n```text\nTHINK\n→ ACT\n→ GOVERN\n→ REPEAT\n```\n\nThis historical model may represent semantic stages rather than independent runtime services.\n\n```text\nSEMANTIC STAGE\n≠\nRUNTIME SERVICE IDENTITY\n```\n\n---\n\n## 2. CURRENT RUNTIME EVIDENCE\n\nCurrent wrangler manifests show:\n\n- services/govern/wrangler.toml name = integratewise-govern\n\nTarget runtime identity is `governance`.\n\nDocument current runtime ownership separately from target ownership. Do not declare the migration complete unless Git and runtime evidence prove it.\n\n---\n\n## 3. GOVERNANCE OWNERSHIP\n\nGovernance must not be documented as a domain user experience unless covered by the CUSTOMER_ZERO and product verification path.\n\nGovernance is:\n\n- approval gating\n- request/response policy\n- evidence retention\n- confidence threshold\n- escalation rules\n- audit\n- HITL behavior\n\nProduct expression of governance must be emitted through L1 Workbench grammar:\n\n- contextual intelligence surface\n- action governance gate\n- execution state update\n\nGovernance is not:\n\n- backend chat\n- backend report panel\n- standalone admin product unless explicitly frozen\n\n---\n\n## 4. HITL CLASSIFICATION\n\nHuman-in-the-loop is governance behavior.\n\nOperators may act as reviewers, approvers, escallators, or exception handlers.\n\nHuman involvement does not make a feature a separate product boundary.\n\nHuman involvement does not bypass canonical write authority.\n\n---\n\n## 5. DOCUMENTS THAT PRECEDE THIS\n\n- docs/platform-specs/09-governance-engine.md\n- docs/architecture/WORKBENCH_DOCTRINE.md\n- docs/platform-specs/10-signal-engine.md\n- docs/archive/GOVERNANCE_AND_CONTINUITY.md\n- docs/ip/tech/MCP_ADK_ROUTING_SPINE_MEMORY_ARCHITECTURE.md\n\nWhen conflict arises between this document and those documents, this document is canonical.\n"}