Bounded request
One action and one context
Show the exact action, resource, amount or constraint, policy outcome, and evidence gap under review.
Accountable intervention
Human Review gives authorized operators a bounded request, the policy reasons behind it, the supporting evidence state, and a clear expiry. The agent cannot approve its own action.
THE OPERATING MODEL
A review request is linked to one tenant, resource, action, Decision Receipt, and policy context. Reviewer authorization is checked independently from the authority claimed by the agent.
Approve, reject, expire, and comment-free structured dispositions remain separate immutable facts. The original receipt and origin request never change.
WHAT THE RECORD MUST SHOW
Bounded request
Show the exact action, resource, amount or constraint, policy outcome, and evidence gap under review.
Authorized reviewer
Verify that the responding account has the required tenant role and cannot act across workspace boundaries.
Immutable result
Record approval, rejection, or expiry as a new auditable fact without rewriting the triggering evidence.
EVIDENCE FLOW
CLEAR PRODUCT BOUNDARY
Agents cannot satisfy their own review request. A reviewer decision does not prove payment, delivery, or outcome, and in the current OBSERVE milestone it does not execute the customer action.
COMMON QUESTIONS
No. Review actions require an authorized human account in the applicable tenant and resource context.
The request reaches its deterministic expiry state. It is not silently converted into approval.
No. The disposition is a separate immutable event linked to the original record.
START WITH EVIDENCE