Research brief · Runtime governance

Based on published preprint

Authorized Actions, Unauthorized Outcomes

Why enterprise controls fail when they evaluate each agent action independently.

Michael K. SalemePublished August 1, 2026Research briefBased on published preprint

Executive abstract

Every call can pass the control, and the outcome can still fail.

An agent-control system can authenticate an agent, verify delegated authority, and approve every individual request under a local policy, yet still authorize an aggregate outcome the enterprise did not intend. The gap appears when decisions are evaluated in isolation across sessions. In the underlying synthetic payment scenario, five sessions each remain below a 1,000 per-session cap, while their combined authorized exposure reaches 4,000 against a 3,000 aggregate risk budget. The issue is not whether a policy evaluator is stateless. A stateless evaluator can enforce an aggregate rule when a trustworthy aggregate is supplied in its decision context. The missing control is an architecture that maintains cross-session exposure, reserves capacity atomically before authorization, manages the reservation lifecycle, and makes that state available to the decision. This brief explains the pattern, its executive implications, and the evidence boundary of the proposed control in systems that delegate authority at scale.

The scenario

A changed refund destination can look locally routine.

Consider a payment agent handling refunds across several customer sessions. Each refund destination change is authenticated, within its per-session amount limit, and approved by the policy presented at that moment. If the system evaluates only one request at a time, nothing in any one decision may justify refusal.

The refund example illustrates the business pattern; the preprint evaluates the control using a synthetic cross-session payment-exposure model.

But the enterprise may care about the aggregate exposure created by those changes together. The control question is therefore not only, “May this action proceed?” It is also, “What do the actions already authorized make this action become?”

Governance model

Per-call authorization versus sequence-level governance

Per-call authorization

Evaluates the identity, delegation, policy, and facts supplied for one action. It can correctly approve every action under its local rule.

Sequence-level governance

Evaluates the action together with authoritative aggregate state: prior commitments, remaining capacity, correlation, and the risk budget the action would consume.

A composition-aware control needs a shared cross-session risk ledger, atomic reservation before authorization, idempotency and correlation for retries, and a lifecycle for settlement, release, expiry, or cancellation. A naive counter is insufficient under concurrent requests because multiple sessions can evaluate the same pre-commit state. The proposed pattern is reserve-then-authorize.

Executive implications

Three decisions leaders need to make explicitly

  1. Define aggregate authority. Per-action limits do not automatically represent an enterprise risk budget. Name the aggregate that matters: spend, exposure, inventory, privilege, or another constrained resource.
  2. Make the control architectural. A policy rule cannot reconstruct trustworthy cross-session state by itself. Decide which service owns the ledger, reservation semantics, reconciliation, and evidence record.
  3. Require evidence of composition. An allow or deny verdict alone cannot show how separately authorized actions accumulated. Capture the relevant decisions, aggregate, threshold, and refusal in a replayable record.

Proposed control

Cross-session composition control

The proposed design places an authoritative ledger and atomic reservation step ahead of the final authorization. The control checks remaining aggregate capacity, reserves it if available, presents the updated aggregate to the evaluator, then records whether the action settles, releases, expires, or is canceled. This does not replace identity, delegation, or per-call policy. It governs what their individually permitted decisions compose into.

  1. Read authoritative aggregate exposure. Start with the current committed and reserved exposure for the governed resource.
  2. Reserve capacity atomically. Create a durable reservation before final authorization so concurrent sessions cannot rely on the same remaining capacity.
  3. Evaluate with the updated aggregate. Present the post-reservation state to the policy evaluator with the relevant correlation and authority context.
  4. Settle, release, expire, or cancel the reservation. Close the reservation lifecycle and preserve the record required to explain the outcome.

Evidence and limitations

Useful as a design and evaluation reference, not a production claim

  • The reference scenario uses five simulated sessions valued at 800 each, a 1,000 per-session cap, and a 3,000 aggregate budget.
  • The companion concurrency comparison is simulated in a single-threaded reference implementation. It models the difference between a shared pre-commit snapshot and serialized reservations.
  • The included record can be replayed for internal consistency. It is not an independently verifiable, provenance-bound attestation.
  • Third-party platform discussion is limited to cited public descriptions and is not an internal audit or exhaustive market survey.

Source record

Citation and underlying research

Cite this PubPoint brief

Saleme, Michael K. (2026, August 1). Authorized Actions, Unauthorized Outcomes: Why enterprise controls fail when they evaluate each agent action independently. PubPoint. https://pubpoint.com/publications/authorized-actions-unauthorized-outcomes/

Underlying research and recommended scholarly citation

Saleme, Michael K. (2026). Authorized but Composed: Cross-Session Risk Composition as an Agent-Governance Control (Version 1.1). Zenodo. https://doi.org/10.5281/zenodo.21400261

Download the published preprint

Research inquiry

Formal source: Version 1.1, published July 16, 2026. PubPoint edition published August 1, 2026. Material revisions will be recorded here.

Related research