Documentation Coverage

Documentation Coverage means 0x0 has current public and maintainer docs for

the language, runtime, package, library, release, governance, AI-first, and

contribution areas users need for production work.

Docs Coverage Gate

Run:

make docs-parity-closure-check

The gate reads docs/docs-coverage.tsv and verifies:

• docs coverage gate inventory is current;
• every required coverage class has a current doc;
• every required doc contains its required tokens;
• public navigation links to the doc;
• the support matrix marks documentation coverage implemented;
• release helper manifests include the docs parity gate;
• public learning and reference pages do not contain stale planning or fake

adapter claims.

Covered Classes

The coverage manifest covers:

• AI-first language experience;
• AI contributing and evaluation;
• agent workflows;
• community examples;
• contribution flow;
• release artifact bundles;
• governance and review;
• platform support;
• production readiness;
• conformance and differential validation;
• performance and runtime reliability;
• security program;
• self-hosting readiness;
• no-fallback receipts;
• bootstrap chain;
• source-owned tooling status;
• hardware and firmware docs.

Documentation Impact Review

Every implementation, syntax, API, CLI, compiler, runtime, standard-library, or

behavior change must update affected docs in the same change or explain why no

documentation update was required.