checkpoints

Answer a held checkpoint (approve / revise / abandon)

The A1 review grammar: one decision for the gate, optionally carrying anchored comments ({beatId} or {timecodeMs} anchors; per-anchor verdict approve|revise|lock — lock freezes the element contractually) and/or edits (your revised stage artifact). revise loops IN-JOB: the director revises and re-presents this same gate with a new packet (version+1); the brief quote states the included revision cycles — beyond them, revise is refused 402 with the path forward. abandon ends the run. Approve-with-comments is legal: the notes record without gating.

post/v1/checkpoints/{id}/resume

Request

  • Base URL: https://api.cueframe.ai
  • URL: https://api.cueframe.ai/v1/checkpoints/{id}/resume
  • Auth: one of:
    • HTTP bearer
    • OAuth 2 (authorization code, authorization URL https://api.cueframe.ai/api/auth/mcp/authorize, token URL https://api.cueframe.ai/api/auth/mcp/token, scopes: projects:write)
    • API key in header PAYMENT-SIGNATURE

Path parameters

idstring required

Request body

decision'approve' | 'revise' | 'abandon' required

The ONE verdict for this gate (GitHub review grammar). approve = proceed (comments allowed — they record as taste signal without gating); revise = the director revises per comments/edits and RE-PRESENTS this same gate (in-job, no re-meter); abandon = end the run.

editsunknown
globalNotestring

Example request

{
  "decision": "approve"
}

Response

Decision recorded; the run resumes.

oktrue required

Changes

No recorded changes to this operation across all 1 revision of this API.