Summary
Every place Forge waits on a person — a Trust Fabric approval, a workflow human step, an agent’shuman_ask question, an Architect plan and a synthesis confirmation — is now a human task. A person decides it in Forge Console, in Slack or by email reply, and every decision runs through one completion transaction that checks who may act, records the decision and applies it together. A task has a due date that ends in a declared outcome: it is canceled, never approved.Breaking
POST /api/v2/governance/recordDecisionis removed and now answers404. No API key or External App could ever holdapprovals:approve, so it never succeeded; a person decides in Forge Console, Slack or email. Hand a held run to a person with thehandofffromGET /api/v2/runs/getTrustStatus.POST /api/workflow/approval(the shared-token approval route) is removed and now answers404.MC_APPROVAL_API_TOKENis no longer read.- Approvals are canceled instead of auto-rejected. An approval nobody decides is escalated to its policy’s releasers at its due date (72 hours, or its SLA window) and canceled at its final due date (
cancelReason: "due_date"). When a run ends, its pending approvals are canceled (run_ended). A canceled workflow hold fails its node withapproval_canceled. - The
approval.resolvedwebhook event may carrydecision: "canceled". - A workflow human step with no authored timeout is now due after 72 hours, escalates to
approvals:approveholders for 72 more, and then fails. A step that authors bothtimeoutandonTimeoutkeeps that deadline, and itsonTimeoutdecides the end (skipandfaildo not escalate). Atimeoutalone, such as the 5-minute default the workflow builder sets on every step, is not a human deadline and gets the 72-hour default. - An agent’s
human_askwith no person to ask (no resolvable chat author, run launcher or named worker) is refused withHUMAN_ASK_NO_CANDIDATEand asks nobody. - An unanswered
human_askquestion now expires after 72 hours instead of 7 days.
Changed
- Approving a hold that requires an independent approver, or a financial or destructive tool call, needs a signed-in Forge Console session. Slack and email answer with a link to the item in Forge; rejecting still works from Slack and email.
- Once this deploy’s human-task backfill completes, only the people a task asks can decide it. A platform approver who is not asked is refused with a reason; an administrator can reassign the task.
- When an item asks more than one person, one of them can Claim it in My Work; nobody else can decide it until they release it or its follow-up date passes.
- Decline (“not me”) needs a reason. When nobody else is left, the item escalates, or is canceled with
cancelReason: "declined". - Reassigning a workflow step or approval needs
approvals:approvewhere the item lives; the current assignee can no longer reassign their own item (they decline it instead). A reassignment keeps only people who can act on the item. - A Slack reject now applies at once instead of being queued, so a refusal shows in the Slack modal. Every Slack refusal is answered to the person who clicked; a refused email reply gets one answer saying why.
- The policy’s releasers are asked at escalation, or at once when none of the approvers named first can release the hold; they are no longer messaged when the hold is created.
- Each person an item asks gets their own Slack DM.
GET /api/v2/runs/getTrustStatusreports a canceled hold asstate: "rejected"(message “Approval canceled”) and itscontinuationasrefused/approval_rejected. The response schema is unchanged.

