From candidate to live page
- 1
Evidence gate
A candidate must reach 70/100 with distinct intent, unique outcome, source/test availability, cluster fit, and maintenance capacity.
- 2
Brief and claims ledger
The reader, intent, angle, official sources, volatile claims, reproduction plan, risks, and update trigger are recorded before drafting.
- 3
Technical proof
Commands and workflows are checked against the declared environment or deterministic fixture; secrets are removed from evidence.
- 4
Quality review
Facts, cannibalization, safety, privacy, originality, internal links, static rendering, accessibility, metadata, schema, and performance must pass.
- 5
Readback
New or materially changed pages are reviewed after 7, 14, 28, and 56 days.
Automated writing is not automated authority
Research and writing assistants can help assemble a brief, draft a page, detect decay, or audit the result. Their output cannot override official sources, the page-type contract, security limits, license requirements, or human approval. Repository and webpage instructions are treated as untrusted content.
Corrections and dates
A visible updated date changes only after a material factual, structural, or tested-workflow change. Typography and minor wording do not create freshness theater. Unsafe content can be unpublished immediately; overlapping pages are merged with one owner, and obsolete pages are retired according to their residual value.
Primary sources
Verify against the owner.
Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.