Atomic Decision Boundaries: Why Split Governance Fails at Runtime
Autonomous systems need decisions and state changes fused into one indivisible step; separation creates an architectural gap no policy can close.
Autonomous systems must couple policy decisions and state transitions atomically; split evaluation architectures cannot guarantee execution-time safety.
- — Atomic decision boundaries fuse evaluation and state transition into one LTS step.
- — Split systems separate decision from transition, allowing environment changes between them.
- — The architectural gap in split systems cannot be closed by any policy alone.
- — Existing systems (RBAC, ABAC, OPA, Cedar, AWS IAM) are split; only ACP is atomic.
- — Escalate outcomes transfer rather than eliminate the atomicity requirement.
- — Admissibility is an execution-time property, not an evaluation-time one.
- — Concurrent environments expose split systems to race conditions and state drift.
Astrobobo tool mapping
- Knowledge Capture Record the decision-to-transition latency in your governance system. Capture the specific LTS steps your system executes when granting and enforcing access.
- Focus Brief Summarize whether your system is atomic (decision + transition in one step) or split (separate steps). Note which external systems can change state between evaluation and execution.
- Daily Log Log one instance where a permission was evaluated, then the system state changed before the action executed. This is your concrete evidence of split-system risk.
Frequently asked
- An atomic decision boundary is an architectural property where a permission decision and the resulting state transition occur as a single indivisible step in the system's execution model. This ensures that the system state at the moment the decision is made is the same state in which the action executes, eliminating race conditions and guaranteeing admissibility.
cite ▸
APA
Marcelo Fernandez (TraslaIA). (2026, April 23). Atomic Decision Boundaries: Why Split Governance Fails at Runtime. Astrobobo Content Engine (rewrite of arxiv/cs.AI). https://astrobobo-content-engine.vercel.app/article/atomic-decision-boundaries-why-split-governance-fails-at-runtime-f018a1
MLA
Marcelo Fernandez (TraslaIA). "Atomic Decision Boundaries: Why Split Governance Fails at Runtime." Astrobobo Content Engine, 23 Apr 2026, https://astrobobo-content-engine.vercel.app/article/atomic-decision-boundaries-why-split-governance-fails-at-runtime-f018a1. Based on "arxiv/cs.AI", https://arxiv.org/abs/2604.17511.
BibTeX
@misc{astrobobo_atomic-decision-boundaries-why-split-governance-fails-at-runtime-f018a1_2026,
author = {Marcelo Fernandez (TraslaIA)},
title = {Atomic Decision Boundaries: Why Split Governance Fails at Runtime},
year = {2026},
url = {https://astrobobo-content-engine.vercel.app/article/atomic-decision-boundaries-why-split-governance-fails-at-runtime-f018a1},
note = {Astrobobo rewrite of arxiv/cs.AI, https://arxiv.org/abs/2604.17511},
}