Action approval manifest

Technical contract, ownership boundaries, source files, and acceptance checks for this workflow kit.

Schema version 1 · kit version 0.1.0 · recipe

Initial: pending. Terminal: rejected executed Values: pending, approved, rejected, executed, failed.

Confirmation, DiffViewer, ToolCall

Kit provides

  • Canonical payload snapshot
  • Version fingerprint check
  • Decision command mapping

Host provides

  • Authenticated approver
  • Durable signed approval
  • Idempotent action executor
  • Action audit and retention

External validation boundary: The host authorizes the approver and rechecks the frozen payload immediately before executing the action.

cd examples/workflows
node --experimental-strip-types action-approval/example.ts

Run from a source checkout. The browser example uses supplied local fixtures; follow these commands for the standalone reference or recipe.

  • Payload changes invalidate approval
  • A decision targets the reviewed revision
  • Execution remains host-owned and idempotent
  • The recipe does not execute actions
  • The non-cryptographic fixture fingerprint is a version marker, not an approval signature
  • Use the assistant's persisted signed approval path for its live task writes