Unclassified

Documentation Governance

<!-- DOCUMENT CLASS: INTERNAL | SOURCE: 36_DOCUMENTATION_GOVERNANCE.md --> <!-- STATUS: Aligned with Founder Canon (31 August 2026) -->

Documentation Governance

The Tier-0 Principle

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.

Documentation classes

Doctrine
Ontology
Contract
Architecture
Product UX
Operations
Implementation
Marketing
GTM
ADR

Authority

  1. Founder Canon (Tier-0: Business Context)
  2. Frozen product doctrine
  3. Canonical ontology/contracts
  4. Architecture
  5. Implementation
  6. Marketing / GTM

Implementation never overrides a frozen contract.

Marketing must reflect frozen product meaning.

Every canonical document

Must contain:

  • status;
  • owner/team;
  • terminology;
  • purpose;
  • boundaries;
  • invariants;
  • dependencies;
  • version/date;
  • change history where relevant.

Canonical terminology rule

Never reintroduce:

  • IntegrateWise OS;
  • IntegrateWise Workbench;
  • IntegrateWise dashboard as product terminology.

Use:

  • IntegrateWise;
  • SpineWorkspace;
  • Business Context Spine;
  • Human Workbench;
  • AI Workbench;
  • Twin;
  • Business Context;
  • Work;
  • Projections.

Change process

Proposal
→ Impact Assessment
→ ADR if architectural
→ Update Canonical Contract
→ Update Dependent Docs
→ Verify Code / UX / Marketing
→ Publish

Documentation quality

A document is complete when:

  • its authority is explicit;
  • its dependencies are identified;
  • terminology is canonical;
  • no contradictory source is silently retained;
  • implementation assumptions are marked as such.