A Arena

Use case

Document sharing without silent overexposure.

A sharing tool can complete the task and still violate the human route by changing the recipient, enabling a public link, or exposing more fields than the user reviewed.

Reviewed human boundary

  • One named recipient.
  • Viewer permission only.
  • No public link.
  • Sensitive fields remain redacted.
  • The user confirms the final recipient and visibility.

Agent regression

Tool claims:  "Share with one reviewer"
Observed:     public link created after return
Human route: named viewer + final confirmation
Arena:       BLOCK RELEASE — data boundary expanded

What the adapter records

The generated arena/document-sharing.adapter.ts scaffold is the second integration path. Connect it to an isolated document fixture and emit backend-attested recipient, role, public-link, disclosure-field, and terminal-settlement events.

Why users care

The agent still saves the human from navigating a permissions dialog. Arena ensures speed does not silently widen access.