Boundary note: this is a public validation asset, not production deployment and not evidence of a deployed customer workflow.
Route decision
- What work item is being routed?
- Which lanes were considered?
- Which lane was selected?
- What reason was recorded for the route?
- What confidence or uncertainty should a reviewer see?
Delegation boundary
- What may the AI or tool do without further approval?
- What actions are blocked?
- What actions are allowed only after approval?
- What data or context is excluded from the delegated path?
- What side effects are out of scope?
Human checkpoint
- Who reviews the decision before risk increases?
- What condition sends the work to a human?
- What does the reviewer approve, reject, or escalate?
- Is the checkpoint visible in the record?
Blocked actions
- Are irreversible or high-impact actions listed explicitly?
- Are customer-impacting, security-impacting, or data-changing steps blocked by default?
- Is there a clear reason for each blocked action?
Approval / escalation
- What approval is required before a risky step?
- Who owns escalation?
- What happens if confidence is low or context is incomplete?
- Is the escalation path recorded?
Replayable receipt
- Can a reviewer reconstruct the route, boundary, checkpoint, and outcome?
- Does the receipt show what was allowed, blocked, and gated?
- Does it preserve the reason for the decision?
- Can it be reviewed without depending on hidden runtime state?
What should remain after the work
- A bounded work item.
- A route decision.
- A delegation boundary.
- A human checkpoint or reason it was not required.
- A list of blocked and gated actions.
- A replayable receipt.
What this checklist does not claim
- It is not evidence of a deployed customer workflow.
- It does not prove operational outcomes.
- It does not make an autonomous incident-response claim.
- It does not describe an open participation system.
- It does not require public source access.