Closeout section
Passed proof
evidence stateRecord only checks that have direct evidence from the approved session and can be tied to source, runtime, account, provider, or interaction proof.
Fields to capture
- Requirement or lane name
- Approved scope reference
- Observed result
- Evidence artifact or route
- Timestamp and operator alias
Stop condition
Do not mark an item passed from intent, old screenshots, unrelated tests, HTTP 200 alone, or a broad inference.
Closeout section
Failed or contradicted proof
evidence stateCapture checks that failed, contradicted an expected behavior, returned missing data, or exposed a launch-risk gap.
Fields to capture
- Requirement or lane name
- Expected behavior
- Observed failure
- Impact on launch readiness
- Owner-visible follow-up
Stop condition
Do not hide failed checks inside partial-success summaries or mutate production to make the evidence pass.
Closeout section
Still gated
evidence statePreserve every item that still needs owner approval, credentials, real records, provider mutation, money movement, protected media, alert channels, or role-account QA.
Fields to capture
- Gated lane
- Missing approval or artifact
- Why source/live public checks are insufficient
- Required owner action
- Do-not-cross boundary
Stop condition
Do not convert a gated item into done because another adjacent route, packet, test, or checklist exists.
Closeout section
Rollback and evidence ledger
evidence stateRecord rollback readiness, deployed revision context, archive location, and next action without claiming launch-complete status.
Fields to capture
- Current revision and image
- Rollback target and traffic plan
- Ledger checkpoint
- Archive note
- Next bounded slice or owner gate
Stop condition
Do not leave a session without naming what remains unproven and what must not be claimed complete.