A11 / Release Gate
Ready means more than compiled.
A release gate keeps local validation, runtime readiness, external integrations, and owner authority as separate questions with separate evidence.
Pass the
check.
Then decide.
A status is only as strong as its source.
The following release vocabulary is intentionally conservative. It describes what can be supported by the current repository and local validation boundary; it does not claim an external deployment.
Source and tracked configuration are present in the repository.
Type generation, typechecking, and relevant local checks have passed.
Architecture and release documentation are available for review.
Hosting identity, target project, secrets, health, and rollback evidence remain to be established.
Observed workflow startup failures prevent a successful hosted execution claim.
Decision boundary
A green check is not a release authorisation.
Verification supplies evidence. The owner still decides whether the evidence is sufficient for the next environment or consequence.
- Local evidence is not hosted evidence.
- Configured is not connected.
- Proposed is not executed.
- Pending remains pending until directly verified.
Continue