Context requests and exit discipline

2 min readReferenceUpdated 2026-05-19

What you'll find here

Two contracts that bound how agents stop: craik.context_request for structured asks before continuing, and craik.exit_discipline_check for what every agent exit must produce.

Blocked exits must explain why.

Complete exits require every checklist field and no blockers. Blocked exits must explain blocking reasons so the next agent can recover without guessing.

Contracts

Contract

Records

Fields

craik.context_request

structured ask

Requester · kind · status · question · why the context is needed · fulfillment details when available. Can link to handoffs, recovery sessions, and unresolved unknowns.

craik.exit_discipline_check

exit checklist

Validation · handoff · residual risk state · next steps · context request links · unresolved unknown links.

What's next

GuideWriting handoffsThe handoff that exit discipline verifies.ReferenceSchema referenceThe shapes of both contracts.ReferenceFailure modesHow blocked exits compose with the wider failure posture.