Wiki / 5 of 7
A release and its evidence
The historical fifteen gates described the state on 26 August. Today the site follows a shorter, verifiable route from commit to live page.
Historical snapshot
On 26 August the release review distinguished nine machine gates and six human decisions. That was a dated model for a broader release, not the current list of gates for publishing this site.
Human decision
A machine can check conditions, but it cannot accept residual risk or grant publication authority by itself. Human authority remains a separate fact.
A decision made for one version does not carry automatically to the next. A new commit needs its own checks and proper permission.
Current site route
The public site goes directly from the repository to Cloudflare Workers. A push to main starts npm run check, deployment and an independent check of the live page.
After deployment, the check matches the live build-ref to the commit that passed the gates. A separate private release verifier and a SHA-256 receipt per publication are no longer requirements of this route.
What closes publication
A successful local build does not show that visitors see the new text. Publication is closed only when the live build-ref matches the checked commit.
This rule concerns delivery of the site. It does not turn the illustrative EolSpace scenario into an available production workflow.