Draft
Documentation and policy governance
Important project claims need an owner, source, review date, status, and visible change path.
Change classes
- Editorial: clarifies wording without changing behavior or policy.
- Operational: changes installation, recovery, compatibility, or integration guidance.
- Policy: changes rights, responsibilities, fees, governance, privacy, or security expectations.
- Protocol: changes interoperable behavior, state transitions, or machine contracts.
Review expectation
Operational, policy, and protocol changes require review by the owning repository and must update affected documentation, machine-readable indexes, tests where applicable, and release notes. The docs site is a publication surface, not an authority that silently overrides source owners.
Documentation publication workflow
- Wave 0 inventories authorities, public sources, lifecycle states, and stable URLs.
- Wave 1 keeps the portal, compatibility routes, source mapping, link checks, and deployment healthy.
- Wave 2 turns implementation and public contracts into task-first user, operator, and developer guidance.
- Wave 3 publishes reviewed trust, security, economic, governance, ADR, RFC, and whitepaper material.
- Wave 4 evaluates Agent answers, adds maintained translations, and measures freshness and support outcomes.