Approval Model

Approval modes

readonly
  inspect state only.

proposal
  generate plans, artifacts, handoff packs, and evidence drafts.

operator
  submit approved Fleet template jobs and create Lenses records.

sandboxed_implementation
  perform bounded implementation work in a controlled workspace.

Approval lifecycle

requested -> approved -> executed -> evidence_ready -> decision
requested -> rejected
requested -> deferred
requested -> expired

ApprovalRequest must include

• approval_id,
• forge_run_id,
• requested action,
• risk level,
• required role,
• constraints,
• evidence refs,
• expiration or revocation rules when applicable.

Rule

Approval is not chat memory. Approval is a record in the Forge Run Spine, visible in Lenses.

For Self-Host Alpha, scripts/selfhost_runner.py requires an on-disk forge.approval_request.v1 in approved state whose action field gates the allowlisted action_id (for example local_runner:check_foundation). Chat transcripts are never sufficient approval for execution.