Authority Leases for Safe Agentic Execution
Separating Evidence Qualification from Action-Time Authorization. LatentAtlas treats a queued action as a bounded authority contract that must still be valid at execution time.
The action-time authority problem.
Agentic systems often decide before they act. A model, worker, or automation can inspect evidence, queue an action, and execute later through a scheduler, retry loop, delegated worker, or tool call. Between the decision and the action, the world can change.
Frozen review outcomes.
The unresolved bucket is not discarded. It becomes a measured state of the review instrument: the packet needs more evidence before it can become an outcome label.
| Outcome | Count | Meaning |
|---|---|---|
correct_block |
99 | The conservative block or revalidation decision was supported by packet-visible evidence. |
false_block |
22 | The packet-visible evidence indicated the conservative block was not warranted. |
needs_more_evidence |
25 | The packet did not contain enough evidence to judge correctness or falseness. |
Findings.
These are descriptive findings from a frozen masked review set, useful because they turn action-time uncertainty into reviewable evidence states.
False blocks are measurable
22 of 146 reviewed packets were labeled false_block: 15.1% of all reviewed packets and 18.2% of resolved packets.
Evidence insufficiency is a result
25 reviewed packets remained needs_more_evidence, or 17.1% of all reviewed packets.
Temporal authority matters
14 of 48 latest-PDP temporal-authority packets were labeled false_block.
Identity conflict was block-grade
4 of 4 identity_conflict_masked packets were labeled correct_block in the reviewed set.
Blocked PDP was not outcome evidence
7 of 7 blocked_pdp packets remained needs_more_evidence.
Deduplication stayed stable
146 event-level units, 146 subject clusters, and 0 duplicate subject clusters.
Authority leases as a control surface.
A lease ties a prior decision to the actor, action, target, evidence, permission, policy, impact ceiling, and expiry state that made it valid. At action time, the system checks whether the lease still holds.
Decision-time retrieval, proof, and state are captured before the action is queued.
The action is bound to actor, target, permission, source, impact ceiling, and expiry.
At execution time, the system checks whether identity, state, policy, and permission still match.
The worker executes, revalidates, blocks, or sends the packet to manual review.