Request-bound human approval

The Java durable profile demonstrates human-in-the-loop approval for an exact simulated request. Its trusted reviewer context requires an authenticated, authorized human in the same tenant. Self-approval is rejected. Approval binds the subject, actor/lineage, event, action hash, policy, tool, resource, and expiry; PostgreSQL atomically consumes it with the execution claim before simulator dispatch.

Agent proposes fixed simulated deletion
          ↓
Policy requires approval → pending durable request
          ↓
Separate trusted reviewer approves exact request
          ↓
Atomic approval + permit claim → simulator execution

Atomic claim and approval boundary

The POC does not expose an authenticated remote approval API, editable console control, or Slack/Teams notification workflow. The React console is read-only. Scenario 3 and Scenario 8 exercise the approval boundary with safe simulators and disposable state.