Agent Sovereignty Zones
Platform Overview
ASZ Trust Operations Platform
Operate cross-zone agent trust with signed assertions, deterministic failure explanations, tamper-evident audit history, and local enforcement handoff visibility.
Command Rule
Verified ≠ Authorized
ASZ provides verified handoff context. Sentinel/OPA remains the receiving-zone decision authority.
Trust operations rule
Verified ≠ Authorized
Trust posture summary
Executive Trust Posture
A compact operations view of trust registry state, evidence volume, audit integrity, rejection proof, tamper evidence, and local enforcement posture.
Trusted Zones
Trust registry entries currently marked trusted.
Live Events
Cross-zone records loaded from the backend evidence stream.
Audit Chain
Waiting for audit data or backend verification.
Rejected Handoffs
Derived from rejected, invalid, deny, signature, and replay evidence.
Tamper Proof
Safe simulation has not returned tamper evidence yet.
K8s Correlation
Correlation is evidence-only. ASZ does not authorize Kubernetes execution.
Handshake simulator
Run Cross-Zone Handshake
Create a signed outbound assertion, submit it to the inbound verifier, then refresh the live evidence panels without clearing audit history.
Handshake Result
Local OPA RequiredLive backend visibility
Trust Evidence Command Center
Operational evidence from the Agent Sovereignty Zones backend: registry posture, cross-zone events, hash-linked audit proof, DDR explanations, safe tamper simulation, deterministic failure evidence, and Kubernetes/Sentinel correlation.
Registry
Zone Registry
Activity
Cross-Zone Events
Audit integrity
Dual-Zone Audit Chain
0 audit records
Deterministic decision record
DDR Explanations
Kubernetes/Sentinel Handoff
Live Correlation View
ASZ assertion verified
Pending evidence
No ASZ correlation record loaded
ASZ handoff context
Pending
No asz_handoff_id in current evidence
Sentinel evidence
Pending / unavailable
pending_sentinel_evidence
OPA authority preserved
TrueSentinel/OPA remains the local decision authority.
ASZ authorization bypass
FalseThe correlation proof keeps bypass false.
ASZ authorization granted
FalseASZ evidence is not an execution approval.
Redis authorization source
FalseRedis is persistence, not authorization authority.
Runtime artifacts emitted
FalseCorrelation does not issue tokens, sessions, or runtime grants.
Correlation records
0 correlations
Tamper-Evident Audit Demo
Safe simulation: ASZ creates a temporary copy of the audit chain, changes one field in that copy, and verifies that the copied chain breaks. The real Redis-backed audit chain remains unchanged and verified.
Real Audit Chain
Unverified
Simulated Tampered Copy
Pending
Field Changed in Copy
—
Cloned event tested: —
Only the cloned audit event was modified for this demo. The persisted Redis audit chain was not changed.
Refresh behavior: Refresh re-runs the safe simulation against the latest persisted audit chain. It does not clear audit history.
Cross-Zone Failure Scenarios
Valid assertions can cross zones. Invalid assertions fail closed before local OPA. ASZ records the rejection, explains the reason, and produces no runtime grant.
Invalid Signature
Simulates a modified assertion payload. CIPHER integrity rejects it before local OPA.
Replay Attempt
Simulates reusing the same assertion ID. Replay protection rejects the duplicate handoff.
Preview
Evidence Export
Future evidence bundles will package assertion details, DDR explanations, audit anchors, failure evidence, and handoff correlation without exposing secrets, tokens, or private keys.
Handoff Resolver Evidence
Read-only resolver evidence
Resolver evidence is read-only. Resolver output is evidence-only. Resolved does not mean authorized. Safe context available does not mean authorized. ASZ does not authorize Kubernetes execution. Sentinel/OPA remains local decision authority. Redis is persistence, not authorization.
Resolver evidence unavailable. No authorization decision is inferred.
Trust Operations for Cross-Zone Agent Governance
Use this command center to demonstrate live handshakes, rejection proof, deterministic explanations, audit integrity, and local enforcement handoff visibility without changing backend behavior.