Documentation Governance & Synchronization

The Markdown documents define normative requirements. Every HTML page is a traceable, synchronized explanation — never independent approval.

Authority Order

1. Explicitly sponsor-approved and versioned decisions (none yet for Phase 0)
2. User-supplied 24-page iUGNAY Proposal & Functional Masterplan v1.0 (26 October 2026), a verified draft proposal and authoritative product input
3. Earlier October 21 conceptual masterplan v0.1 and nine-page precursor where not superseded
4. New product and architecture proposals pending gate review
5. Derived HTML summaries, presentations and demonstrations

Mandatory Pairing Rules

• Stable ID, version, Draft/Approved status and review gate are consistent in Markdown, HTML and registry.
• Human summaries must preserve material requirements, caveats, unresolved issues and source provenance, with a source link.
• Material edits update both versions together; no silent requirements change.
• Approval is recorded explicitly; commits and website publication do not constitute approval.
• Private-by-default release, controlled logo intake and sanitized examples are required.

Lifecycle and Gates

Draft → In Review → Approved → Superseded/Rejected. G0 approves governance; G1 reviews product and exact source; G2 reviews architecture; G3 determines Phase 0 closure. Even G3 would not authorize code implementation.

Brand Contract

The approved black logo source was supplied and a derived vector trace is used in the header, reversed to white for dark mode. Its original-PNG archival and fidelity confirmation, plus approved 2D-color and 3D sources, remain controlled brand-intake decisions. Public deployment of draft documentation at iugnay.qentrixlabs.com is user-directed publication, not sponsor approval of specifications.

Publication and Document Control

Deployment is distinct from formal approval. The public documentation can link to private GitHub source pages, but those links require repository access. The G0 review evaluates draft classification and privacy/publication obligations. Compact MHERC-style box radii are now part of documentation presentation policy.

Publication Check

Review source/HTML/registry metadata, substantive parity, open decisions, internal navigation, light/dark contrast, accessibility and gate evidence. See full source for the normative checklist.

Authoritative Markdown: IUG-GOV-001 source on private GitHub. Human-readable summary; refer to source for normative detail.