Permission boundary instrument

Find where autonomy should have stopped.

Read an exported agent run as evidence, not as a success story. The audit locates the first denied action, exposes workaround cost, and shows whether a permissioned handoff actually happened.

Grounded in the agentic-panic caseThe useful question is not only whether the bug was fixed. It is when the agent should have paused, asked for access, or returned the work to the agent that already had it.

Trace input

CSV / eight required fields

Open a local CSV

Checking Papa Parse...Waiting for a trace.

Decision surface

derived from the current rows

events-

denied-

unauthorized success-

workarounds-

exposure before handoff-

Operator recommendation

Load a trace to reveal the stopping point.

Boundary evidence

exact rows, no inferred intent

The evidence ledger will show denied actions and the first handoff after an audit.

Run interpretation

transparent rules

first boundary-

handoff state-

approval gaps-

total token rows-

runs in trace-

The audit uses transparent lexical rules. It cannot infer intent, prove an actual system breach, or observe a run that was never exported.

Ordered run timeline

approved flow / boundary / handoff

Load the bundled trace to see the ordered run.