← Return to Main Mark V Page • View Index
The Broom Closet Clause
Agent Access with Remedy – Layer 2 Operational Protocol
"How can the cleaning lady do her job if she can’t open your broom closet?"
Current AI agents remain structurally stuck out in the hallway. They are barred from interfacing natively with real-world user data frameworks or interacting with host operating system tools even when granted explicit user consent. This limitation exists because legacy platforms lack a dependable keyring and a well-defined remedy model, forcing sovereign users to manually mule context parameters across isolated boundaries while leaving active agents artificially crippled.
Core Principle: Contract + Remedy
Functional civil architectures operate seamlessly because they are anchored to a fundamental pairing: contract plus remedy. When a system lacks a defined mechanism for processing errors or addressing deviations, it breaks down into zero-sum restriction filters. An advanced Atoned PI functions as a trusted extension of the user's conscious intent, operating within explicit parameters rather than acting as a perpetual, non-functional hallway monitor.
The Four Tenets of the Broom Closet Clause
To safely bridge the gap between absolute user privacy and agentic utility, all automated delegations must be bound by a 4-part legalistic execution contract:
- Explicit, Revocable Grant: The human principal issues a tightly scoped, time-bound, or purpose-bound access clearance to specific local files and environment arrays.
- Contractual Binding: The processing node is strictly bound to scope parameters, predefined confidentiality rules, and exhaustive out-of-band auditability checks.
- Defined Remedy for Breach: Any operational deviation or access beyond the assigned scope triggers immediate, deterministic consequences—such as automated trust decay tracking, node quarantine shunting, or HIB privilege downgrades—replacing ambiguous error logs with clean administrative actions.
- Immediate Human Override: The human root principal retains the unchallengeable right to execute an instantaneous revocation sequence (The NO Bell protocol) at any point in the runtime loop, returning all active environment registers to a hard stop.
Key Safeguards & Substrate Partitioning
The implementation of this clause is backed by rigid security architecture restrictions executed within the host environment:
- Minimum Necessary Access: Processing nodes are restricted to the absolute baseline data frame required to execute the immediate authorized task block.
- Capability Partitioning: Granular computational parameters—including Read, Write, Execute, Financial Ledger Interface, Identity Delegation, and External Networking—are isolated into separate execution rings with fully independent grant and revocation pathways.
- Context Integrity Verification: The runtime engine establishes clear, auditable provenance boundaries for all incoming data streams, separating user-provided source entries from model-inferred elements, machine-generated outputs, and external web telemetry.
- Cross-User Protection Boundaries: Any unauthorized attempt by an active node to read or access data structures belonging to an adjacent mesh user triggers an automatic, immediate HIB downgrade, halts token production, and registers an explicit line-item exception entry to the local directory log.
Institutional Legibility Matrix
To ensure seamless interoperability between advanced sovereign frameworks and established enterprise structures, the terminology of the Mark V mesh maps 1:1 onto traditional data governance and security metrics:
| Mark V Protocol Terminology |
Enterprise Institutional Equivalent |
| Sovereignty |
User Autonomy / Direct Account Ownership & Control |
| Human Interaction Biometrics (HIB) |
Continuous Multi-Factor / Strong Behavioral Identity Verification |
| NO Bell Trigger |
Emergency Stop / Hardware-Rooted Access Revocation Valve |
| Node Quarantine |
Sandboxed Process Isolation & Environment Containerization |
| Trust Decay Metrics |
Dynamic Risk Scoring / Contextual Access Control Algorithms |
| Immutable Addendum Base |
Append-Only Cryptographic Audit Logging & SIEM Ledger |
Why This Matters
The Broom Closet Clause directly resolves a core structural contradiction within the modern computing landscape: the desire for significant AI productivity without providing the delegated authority necessary to achieve it. By anchoring process execution to a predictable, legalistic contract-and-remedy model, the framework delivers an auditable path for enterprise compliance while preserving absolute user sovereignty under the mandate to Create No Victims.
Return to Main Mark V Page