Skip to main content
Trust Fabric: every refusal or hold says what happened, who decides, by when, and where.

Refusals name the decision they recorded

  • A refused or held governed tool call’s result includes decisionId.
  • An external inference block or hold includes decision_id in its error body, beside approval_request_id and human_handoff.
  • A chat turn blocked or held by governance links to its decision.

Every API refusal names its decision

Every 403 refusal from the Platform API records a Trust Fabric decision and returns its id on error.decisionId; the Forge MCP server ends the refusal with Reference: <id>. Before this, pod reads and writes, assignment history, memory writes and other record-level refusals recorded nothing. A refusal that one grant does not fix, such as a platform agent’s read-only memory, names no requiredPermission. Two kinds of 403 still record no decision: one about the credential itself (the wrong credential kind or token type, or an External App with no owning org unit or organization), and the refusal while an operator has stopped Forge.

Ingress, the agent gateway and the procedures API name their decision

Three more refusals record a Trust Fabric decision and name it:
  • POST /api/v2/ingress/<token>: a 403 because the trigger’s principal does not hold a key the trigger declares adds decisionId to the body. The error and message do not change and still name no key.
  • The coding-agent gateway (/api/inference/* and /api/agent-gateway/v1/*): a 401, 402 or 403 to a run whose token verified adds decision_id to the error object, on both the Anthropic and the OpenAI wire. A missing or invalid run token, a malformed request and the kill switch’s 503 record nothing.
  • The procedures API (invokeCapability, putFile, getFile, agentCallback, workflowDebugEgress, sandboxEffect): an authorization 403 to a verified session token adds decisionId beside error and message. INVOCATION_NOT_LIVE and STEP_NOT_LIVE record nothing: they mean the session outlived its invocation or step. Neither does a debug egress transport or response fault (a timeout, a redirect, an oversized response).

Governance webhook events name their decision

governance.denied, governance.sensitive_data and governance.run_cost_cap_exceeded carry data.decisionId, so a webhook or SIEM subscriber can join the event to its recorded decision. Forge records the decision before it emits governance.denied or governance.sensitive_data. See Webhooks.

A stopped door gives the operator’s reason

When an operator stops people, API key or agent access, every surface now says so in one sentence and gives the operator’s reason, for example “An operator has stopped people access to Forge: incident drill”. The surfaces are:
  • Slack slash commands, buttons, modals and shortcuts;
  • email replies, which are answered once and can be sent again after access resumes;
  • the HTTP 503s;
  • agent refusals.
Before this, Slack told the person to ask an admin for a permission that no grant could fix.

Authoring decisions stay with their creator

A Builder or Architect refusal is listed only for the person who started that authoring conversation. This applies to the decision lists and the logs feed as well as the evidence views. Gate tallies and rollups still count it.

Breaking (Console functions): file URLs come from recording actions

Every read of a stored file is now audited. A query cannot write, so no query returns a file URL any more. A list returns file metadata, and an action records the read and then returns the URL. A read that cannot be recorded is refused.
  • runArtifacts.listByRun and chatAttachments.listByChannel no longer return url. Call runArtifacts.getRunArtifactUrl or chatAttachments.getChatAttachmentUrl with the file’s fileId.
  • api.workflowV2.humanNodeFiles.getHumanNodeInputFiles no longer returns url. Call getHumanNodeInputFileUrl in the same module.
  • workflowsInternal.getDocumentFileUrl is removed. A run’s input file opens through workflowsInternal.getRunInputFileUrl. No function returns a workflow document’s source file.
  • opsInternal.getConversationLogUrl is removed, with no replacement.
  • workflowsInternal.getDocument and listDocuments no longer return extractedText.
  • api.traceSnapshots.getTraceContentUrls is an action, not a query. Call it with useAction, not useQuery.
See File operations.
Human tasks, Increment 2 hardening: the edges now match the design.

Summary

This release closes the gaps a validation of Increments 1 and 2 found. It adds no new kind of task. Tasks close for the reason that is true, every door tells the person why it refused, and Slack, email and Forge Console agree on what a task asks.

Changed

  • Decided elsewhere. When a task’s subject (the approval, workflow step or plan it asks about) was already decided through another path, its due date or last decline closes it as superseded, not due_date or declined, and does not run the expiry effect a second time. The audit row records decidedElsewhere and the reason that was asked for.
  • Which door. A completed task records the door it was answered through (resolvedBy.door), and the completed audit row carries it too.
  • Workflow steps. A step whose declared outputs do not make a valid form fails its run with “This step’s form cannot be shown: …” instead of creating a task nobody can answer. A door that tries to answer such a step returns that sentence as its refusal; nothing is completed. A step’s answer is read against the form pinned when it was asked, so renaming the node’s outputs later no longer changes how an open step’s answer is mapped.
  • Escalation. A workflow step past its due date escalates to the approvals:approve holders at the run’s org unit and its ancestors, not to every holder on the platform. The Slack notice for a step or a hold past its due date is a pointer to the task with no decision buttons (event human_task.escalated, not a webhook event). approval.sla_breached keeps its webhook and audit row and no longer posts to Slack.
  • Email. approval.requested no longer sends its own email; the human task’s email presents the approval. A reply to a hold that is already closed, or from a verified sender who may not decide it, now gets one reply saying so instead of silence.
  • Slack. /forge approvals lists your open human tasks from the same source as the Home tab and renders them the same way: an approve that needs a signed-in Console session is an “Approve in Forge” link, never a button. A click on a pre-task workflow card (human_node_complete, or its reject dialog) is told the task is closed and completes nothing.
  • Chat. An answer that resumes a chat agent is delivered when the turn ahead of it ends, including fan-out turns and turns released by the stalled-turn sweeper. A canceled chat hold is marked in the agent’s thread.
  • Synthesis batches expire through their task’s due date only; the synthesis-confirmation-expiry cron is removed.

Deprecated aliases

These Console mutations are deprecated aliases of workersMyWork.completeMyHumanTask. They join the 2026-10-11 alias list and are removed next release. Each keeps its arguments, returns and checks until then.
  • trust_fabric/approvals/approvalResolution.resolve
  • workflowArchitect/architectProposals.confirmProposal, editAndConfirmProposal and rejectProposal
  • workflowArchitect/synthesisConfirmation.confirmSynthesisBatch, confirmSynthesisSubset, rejectSynthesisBatch and requestChangesOnSynthesisBatch

Deploy note

No data migration runs. The repair for tasks closed before this release with the wrong reason ships unrun.
Human tasks, hardening 2: approve only what you can see.

Summary

Slack and email approve in place only when they show what is being approved, task text in Slack is shown exactly as written, and a refusal on the Slack Home tab is answered there.

Changed

  • What you approve in place. A tool hold’s Slack card and email show the arguments the tool marks safe to show, and approve it in place. Slack Home and /forge approvals do not show them, so they offer “Approve in Forge” and an inline Reject. A hold that sends something outside Forge is approved only in Forge Console, from any surface. A task with extra detail is approved from its card, email or Forge; Home links to Forge. An approve from an older card for a hold that now needs Forge is refused with a link.
  • Slack text. Task titles, details, names and answers appear in Slack exactly as written: <, > and & are escaped once and links or mentions inside task text are not expanded.
  • Slack Home. A click on Home that cannot be taken (already closed, claimed by someone else, or not yours) refreshes Home with the reason at the top and an “Open in Forge” button. Home lists your 10 newest open tasks out of the 50 newest rows it reads. A click on a pre-task workflow card (runId|nodeId) is told the task is closed and completes nothing.
  • Escalation. The human_task.escalated Slack pointer says why: past its due date, or everyone first asked declined. A hold escalated at creation because nobody could permit it is no longer reported as an SLA breach. A task whose every candidate declined, with nobody new to ask, closes as declined.
  • Chat. A rejected chat approval is noted in the chat and in the agent’s thread, as a canceled one already was.
  • Claim. Claiming a task when you are the only person asked is refused with “Only you are asked, so there is nothing to claim.”
  • Dashboards. The governance.pendingApprovals widget source is removed (it returns no data), and governance.attentionItems items read “Pending approval” instead of the item’s title.
  • Removed. The internal httpHelpers.markStepCompleted mutation.

Deploy note

No data migration runs. Holds created before this release keep their form; their approve links to Forge when the approval carries arguments to show or a send binding.