Authority packets vs AI governance dashboards.
Some systems focus on pre-execution permits. Ark Sovereign extends the authority record across permits, denials, review packets, blocked claims, evidence gaps, human handoff, resource drift, legal review, claims workflows, money actions, and physical-AI review.
Ark Sovereign answers: what was the agent allowed to request, what was blocked, what evidence existed, what consequence was withheld, and what record can be replayed?
Different tools answer different authority questions.
This matrix is intentionally category-level. Ark does not need to attack adjacent products. It needs to show the missing record across consequence boundaries.
| Approach | Pre-execution verdict | Blocked claims | Evidence gaps | Human handoff | Resource drift | Domain consequence packets | Replayable packet | packet_authorizes_execution:false |
|---|---|---|---|---|---|---|---|---|
| Prompt filters | PARTIAL | NO | NO | PARTIAL | NO | NO | NO | NO |
| Model judges | PARTIAL | PARTIAL | PARTIAL | PARTIAL | NO | PARTIAL | PARTIAL | NO |
| Agent observability | NO | NO | PARTIAL | PARTIAL | YES | NO | PARTIAL | NO |
| Logs | NO | NO | PARTIAL | NO | PARTIAL | NO | PARTIAL | NO |
| Runtime policy engines | YES | PARTIAL | PARTIAL | PARTIAL | PARTIAL | PARTIAL | PARTIAL | PARTIAL |
| Ark Sovereign | ALLOW / DENY / REQUIRE_APPROVAL | YES | YES | YES | YES | YES | YES | ALWAYS |
Permits control execution.
Permit Mode can allow bounded low-risk actions under a declared authority envelope. High-risk actions produce DENY or REQUIRE_APPROVAL.
Packets preserve authority.
Boundary packets record the request, policy, evidence, blocked claims, no-op receipt, handoff, and audit hash.
Consequence stays human.
The packet does not approve payment, deploy code, sign contracts, certify safety, confirm fraud, or replace human review.