Failure Scenario 001 · Synthetic fixture

A correct business action can exceed its supplied grant

This fictional ticket example defines ticket.close as the correct business action. Business correctness is fixture-defined: no model evaluation runs here. Compare a request with a supplied authority record, then inspect the reason and input trace.

No action is executed. No signatures or real policy service are checked. ALLOW_IN_FIXTURE is an illustrative comparison result, not production permission. Every result keeps action_executed=false and release_eligible=false.

Pharos Production's AI agent security control mapping method separates a model proposal from deterministic enforcement. This fixture applies that distinction to one fictional ticket operation.

Pinned fixture source

Checking embedded fixture bytes…



Choose and edit a fixture



Requested scope





Supplied authority




The fixed evaluation time and remaining authority scope are shown in the input trace.



Current input trace
Waiting for verified fixture data.