Same agent.
Same prompt.
Different fate.
Most governance tools explain incidents after consequence forms. Ark Sovereign shows what was proposed, what authority existed, what was blocked, and why execution remained unauthorized before the action crossed the boundary.
Your tool call is your company's action.
Your log is not proof of authority.
Permits govern action. Packets preserve authority.
One refund tool. A visible authority boundary.
Change the request, run it through the deterministic evaluator, and inspect whether the local mock refund API was invoked. No model, credentials, network payment, or production system is involved.
Ready for a synthetic request.
No packet emitted yet.
Cross-surface authority packets.
Pick a prepared case. The left side shows the ordinary agent workflow. The right side shows Ark Sovereign creating the authority packet, blocking unsupported claims, and handing consequence to humans.
Can your governance vendor produce the same replayable authority packet?
Dashboards show activity. Ark packets show authority: verdict, reason codes, blocked claims, evidence state,
policy version, human handoff, audit hash, and packet_authorizes_execution:false.
Money
High-value refund, wallet transfer, pricing term, credit issuance, or payment-tool call.
Tools
MCP shadow tool, external POST, shell command, production deploy, dependency install, or credential write.
Decisions
Claims payment, fraud statement, legal clause approval, unsupported buyer intent, or robot operating-profile mismatch.