Release And Governance

Current implementation evidence: docs/release.html,

docs/release-compat.html, docs/documentation.html, and docs/safe-public-docs-gates.html.

Release Evidence

0x0 release docs track source, compiler, stage output, ABI, runtime, linker,

optimizer, independent compiler, memory, and compatibility evidence.

Public site releases add a separate layer:

• site source;
• generated static output;
• checksums;
• remote dry run;
• rollback plan;
• public smoke checks.

Documentation Discipline

Public docs must describe implemented behavior. Future work belongs in planned

or deferred sections.

Safe Gates

For public documentation work, use bounded gates first:

make public-docs-milestone-0-check
make public-site-link-check
make public-site-build-check

Broader compiler and release gates remain important for source and artifact

changes, but they are not the default quick path for static site edits.

Practical Rule

If a release claim depends on an artifact, link the artifact, manifest, hash, or

gate that proves it.