handoff-consume-openaccp

Handoff Consume OpenACCP

Validate structure, check scope against task card, review verification evidence, inspect risks, consider reviewer recommendation, and decide accepted, amend, split-follow-up, rejected, or blocked.

Handoff presence is not acceptance.

Every consume should produce or return a consume-result artifact. Frontier consume results are provisional unless Primary explicitly granted final authority, which should not be the default. Final consume results belong to Primary or the human owner.

Consume Rules

Before consume, check:

• handoff exists and is readable,
• task card or source authority matches the claimed work,
• changed artifacts fit allowed scope,
• forbidden files or effects were not touched,
• verification evidence is present and specific,
• skipped checks are explained,
• reviewer recommendation is considered when available,
• final-state claims are not made by non-final roles.

Use consume results to drive the next dispatch. If the handoff is incomplete, send it back for amendment or dispatch reviewer/discovery work instead of treating it as done.

If consuming a Frontier return or Primary-ready packet with a final accepted decision, cite the closure closureId, laneId, or path in basisRefs, then validate the consume-result with that frontier-closure. A closure file is evidence; it is not final acceptance by itself.

Consume Result Fields

Record:

• consumeId,
• responseId,
• consumerRole,
• authorityScope,
• targetHandoffIds,
• targetReviewIds,
• decision,
• basisRefs,
• evidenceStatus,
• claimsAccepted,
• claimsRejected,
• remainingRisks,
• authorityLimits,
• nextActions.

Validate with:

openaccp-validate --artifact <consume-result.json> --ruleset consume-result --strict
# Only for final accepted Frontier return or Primary-ready packet consume:
openaccp-validate --artifact <consume-result.json> --ruleset consume-result --frontier-closure <frontier-closure.json> --strict