Arxi Basics
Systems are reliable when you can replay their history and verify its integrity. Automation is powerful, but its execution trails are fragile and hard to prove. Arxi recreates those guarantees for any system that crosses trust boundaries without slowing the system down.
It does this through three concepts that build on each other: Envelopes define what happened, Chains prove the sequence, and Bundles make the evidence portable.
Three Core Concepts
Envelopes (How Events Are Recorded)
Every boundary event is captured as an evidence envelope. Each envelope carries the event type, actor identity, timestamps, correlation IDs, a typed payload, and optional attachments. Envelopes are the atomic unit of evidence—structured enough to query, complete enough to verify.
{
"envelope_id": "env-a7f3",
"event_type": "tool.call",
"actor_id": "agent:planner",
"capture_time": "2025-01-15T10:30:00Z",
"payload": { "tool": "run_tests", "exit_code": 0 },
"prev_hash": "sha256:9c1e..."
}
An evidence envelope: who did what, when, with a cryptographic link to the chain.
Why this matters: you stop guessing what happened and start proving it. Envelopes turn “the agent ran something” into structured, queryable evidence with provenance.
Chains (How Integrity Is Maintained)
Envelopes don’t float—they’re linked into hash chains. Each envelope references the hash of its predecessor, so the sequence is tamper-evident. Chains are organized into segments that can be sealed (made immutable). Once sealed, a segment’s integrity can be verified from chain head to first envelope.
{
"segment_id": "seg-001",
"status": "sealed",
"envelope_count": 42,
"chain_head": "sha256:d4e5...",
"seal_time": "2025-01-15T11:00:00Z"
}
A sealed segment: 42 envelopes, integrity verifiable by walking the hash chain.
Why this matters: chains turn a collection of events into a tamper-evident sequence. If any envelope is altered, removed, or reordered, the chain breaks—and verification catches it.
Bundles (How Evidence Is Exchanged)
Bundles are immutable, portable snapshots of evidence. They contain selected envelope chains, required attachments, and a verification manifest with hashes. Bundles are the unit of exchange—hand one to a decision system, an auditor, or an archival store and it can be verified independently.
{
"bundle_id": "bun-001",
"segments": ["seg-001"],
"attachment_count": 3,
"manifest_hash": "sha256:f8a1...",
"verification": { "phases_passed": 7, "verdict": "valid" }
}
An evidence bundle: self-contained, verifiable offline, and portable across systems.
Why this matters: bundles turn internal records into external proof. They can be verified offline, shared across trust boundaries, and archived for compliance—without trusting the source system.
Next, see how these concepts appear in real workflows in Arxi Examples.
Learn More
- Arxi CLI Reference — Recording, querying, and bundle operations
- Evidence Envelope Model — Full envelope specification
- Bundle Verification — 7-phase offline verification pipeline
- Integration with Decision Gate — Closed-loop governance