{"slug":"internal/operations/documentation-governance","title":"Documentation Governance","section":"internal","sectionLabel":"Internal","status":"unclassified","type":"document","path":"internal/operations/documentation-governance.md","bytes":1754,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: INTERNAL | SOURCE: 36_DOCUMENTATION_GOVERNANCE.md -->\n<!-- STATUS: Aligned with Founder Canon (31 August 2026) -->\n\n# Documentation Governance\n\n## The Tier-0 Principle\n\n> **Business Context is the semantic foundation of SpineWorkspace.** Documentation must explain how the product establishes, maintains, and serves Business Context. Without Business Context, documentation has nothing to document.\n\n## Documentation classes\n\n```text\nDoctrine\nOntology\nContract\nArchitecture\nProduct UX\nOperations\nImplementation\nMarketing\nGTM\nADR\n```\n\n## Authority\n\n1. **Founder Canon** (Tier-0: Business Context)\n2. Frozen product doctrine\n3. Canonical ontology/contracts\n4. Architecture\n5. Implementation\n6. Marketing / GTM\n\nImplementation never overrides a frozen contract.\n\nMarketing must reflect frozen product meaning.\n\n## Every canonical document\n\nMust contain:\n\n- status;\n- owner/team;\n- terminology;\n- purpose;\n- boundaries;\n- invariants;\n- dependencies;\n- version/date;\n- change history where relevant.\n\n## Canonical terminology rule\n\nNever reintroduce:\n\n- IntegrateWise OS;\n- IntegrateWise Workbench;\n- IntegrateWise dashboard as product terminology.\n\nUse:\n\n- IntegrateWise;\n- SpineWorkspace;\n- Business Context Spine;\n- Human Workbench;\n- AI Workbench;\n- Twin;\n- Business Context;\n- Work;\n- Projections.\n\n## Change process\n\n```text\nProposal\n→ Impact Assessment\n→ ADR if architectural\n→ Update Canonical Contract\n→ Update Dependent Docs\n→ Verify Code / UX / Marketing\n→ Publish\n```\n\n## Documentation quality\n\nA document is complete when:\n\n- its authority is explicit;\n- its dependencies are identified;\n- terminology is canonical;\n- no contradictory source is silently retained;\n- implementation assumptions are marked as such.\n"}