← Root Zero Vault
Architecture
An action is born scoped.
Authority, permission, target enforcement and evidence stay connected to the same action.
RSBIS · AUTHORITY TO ACTION TO EVIDENCE Existing systems Action request AI agent Named identity Application Defined operation Workflow Scoped credentials Integrations SDKs · APIs · gateways Qualified per action Who authorized this? Can you prove it? What actually happened? The Governed Action Path CONSTITUTIONAL BOUNDS · LOCAL POLICY · EXACT ACTION A. IDENTITY AND GOVERNING AUTHORITY Deed · trust history Delegated authority Identity · scope · lineage Resolve who may authorize this action and under which bounds. ↓ B. POLICY — WHICH RULES APPLY? Action · target · context Local timing · see live demo Applicable policy Explicit exceptions Constitutional bounds Evaluate the exact request before the target performs it. ↓ C. PERMISSION FOR THE EXACT ACTION PERMIT · bounds DENY · reason Action + target + expiry ↓ D. RECORD DECISION AND OBSERVED RESULT Journal evidence Hash-linked history Registry anchor Published commitments Components and qualification depend on the integrated action path Target Enforcement Check exact permission Execute within bounds Record observed result Action Refused No valid permission Retain refusal evidence Independent Review Recheck decision + history Inspect recorded outcome Request · scope · context Authority → exact permission → enforcement → evidence Preserve · recheck

Permission alone does not establish that an action occurred. The target must enforce it and record the observed result.
Evidence is designed to support legal and audit review. The browser demonstrations exercise selected components of this architecture.