Persistence vs. Authority
Persistence vs. Authority is the AI governance rule that runtime duration must be decoupled from state-altering permission scope.
“The real test of an autonomous agent is not how long it can work without you. It is how much authority you are willing to give it when you are not there.”
Extending agent runtime without strict write boundaries creates silent distributed failures. While terminal-interactive tools (Claude Code) contain blast radius through human presence, unattended background agents require mechanical write allowlists and deterministic rollbacks.
Multi-Hop Causal Traversal Engine
Explore how concepts dynamically feed into each other across 1-hop, 2-hop, and 3-hop transitive relationships. Click any node to navigate the causal highway.
Persistence vs. Authority
Persistence vs. Authority is the AI governance rule that runtime duration must be decoupled from state-altering permission scope.
Direct Relationships (4)
Transitive Neighbors (Connected via Hop 1)
Extended Causal Ripple Effects
Richard Ewing’s Research Thesis
Runtime persistence and operational authority are separate engineering decisions; unattended background agents must be restricted to read-heavy triggers and bounded execution.
Why This Specification Exists
Organizations deploy persistent background agents into office applications assuming that uptime and persistence equate to autonomous reliability.
Generic OAuth scopes and superficial payment confirmation dialogs.
No framework addressing silent state corruption, accumulated context drift, and cross-application recoverability.
Persistence vs. Authority framework enforcing decoupled write allowlists and deterministic recovery boundaries.
What Changes If You Believe This?
Teams isolate background agent execution in read-only sandboxes and require cryptographic human sign-off on all state-mutating writes.
Prevents unauthorized financial discounts, premature invoicing, and unvetted procurement commitments initiated by automated scripts.
Defines bounded operational workflows with explicit error recovery paths rather than open-ended autonomous mandates.
Eliminates persistent write tokens on service accounts used by background AI workers.
Recommended Action by Role
Enforce Scoped Ephemeral Tokens and zero default write permissions for all persistent background agents connecting via MCP.
Choose interactive terminal workflows (Claude Code) for exploratory problem solving and reserve background persistence (Gemini Spark) for bounded, read-only coordination.
Agentic Drift Risk Matrix
Quantify state drift risk and authority decay thresholds across multi-turn autonomous agent loops.
Latest Publications & Research Activity
Claude Code vs. Gemini Spark: How Do They Compare?
AI Agents Are Creating New Enterprise Governance Risks
Who’s Actually Responsible for Your AI Agents?
Frequently Asked Questions
Q:What is the core distinction between persistence and authority?
Persistence is runtime duration (executing unattended across hours or days). Authority is permission to alter business state, modify databases, or commit corporate capital.
Q:Why is explainability not recoverability?
Knowing why an agent corrupted a spreadsheet or database record does not undo the damage. Without automated cross-app rollback, operators become forensic auditors.
Canonical Specification Origin
Persistence is not authority. Operating without continuous supervision requires strict boundaries around what software can change independently.
Corpus Interconnections
Richard Ewing artifacts developed around this canonical framework, including publications, execution tools, and diagnostic models.
External Adoption & Peer Citations
Documented instances where independent researchers, engineering teams, and publications have cited, implemented, or referenced this concept outside Richard Ewing’s ecosystem.
External Evidence: No independently verified references recorded yet.
This concept is part of Richard Ewing’s original baseline canon. External citations and implementations are added only upon rigorous empirical verification.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
Recommended Citation
Ewing, R. (2026). "Persistence vs. Authority." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/persistence-vs-authority
@article{ewing_persistence_vs_authority,
author = {Ewing, Richard},
title = {Persistence vs. Authority},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/persistence-vs-authority}
}