Arxi Decision Gate Asset Core
Docs

Arxi Examples

Arxi takes envelopes, chains, and bundles and turns them into verifiable evidence trails. Every workflow here is append-only, tamper-evident, and independently verifiable.

Agent Execution Trail

What This Solves

When an agent completes a task, you need more than logs—you need a verifiable record of every tool call, every input, and every result. This example shows how Arxi captures an agent’s execution trail as chained evidence.

Workflow

  1. Agent executes a task, calling tools along the way
  2. Each tool call is recorded as an envelope with actor, payload, and correlation ID
  3. When the task completes, the segment is sealed
  4. A bundle is exported for audit or Decision Gate evaluation

Spec Snippet (Envelope Recording)

{
  "event_type": "tool.call",
  "actor_id": "agent:planner",
  "trace_id": "trace-7a2b",
  "payload": { "tool": "run_tests", "exit_code": 0, "coverage": 92.4 }
}

Each tool call becomes an envelope with provenance and a chain link.

Key takeaway

This pattern turns ephemeral agent activity into a permanent, verifiable record. It applies anywhere automation crosses trust boundaries—tool calls, API requests, file operations, or external system interactions. The record isn’t a claim; it’s chained, hashable proof.

Pipeline Evidence Capture

What This Solves

CI/CD pipelines produce artifacts—test results, coverage reports, security scans—but the evidence is scattered across logs and rarely verifiable after the fact. This example shows how Arxi chains pipeline outputs into a single verifiable bundle.

Workflow

  1. Each pipeline step records its result as an envelope with attachments
  2. Arxi chains all envelopes in sequence, maintaining integrity
  3. On pipeline completion, the segment is sealed
  4. A bundle is exported and handed to Decision Gate for evaluation

Spec Snippet (Bundle Selector)

{
  "selector": {
    "And": [
      { "BySegment": "seg-pipeline-42" },
      { "ByEventType": "pipeline.*" }
    ]
  }
}

Bundle selector algebra: combine segment, event type, time range, or trace filters.

Key takeaway

This pattern turns scattered pipeline artifacts into a single verifiable evidence package. The same bundle feeds decision systems, compliance archives, and post-incident reviews. Evidence is chained at capture time—not reconstructed after the fact.

Compliance Audit Export

What This Solves

When regulators or auditors ask “what happened?”, you need evidence that is complete, tamper-evident, and independently verifiable. This example shows how Arxi produces an audit-grade evidence export without requiring live system access.

Workflow

  1. Operations generate envelopes continuously as boundary events occur
  2. Segment lifecycle policies auto-seal segments at thresholds
  3. Auditor requests evidence for a time range or trace
  4. Arxi builds a bundle using selector algebra
  5. 7-phase offline verification confirms integrity, signatures, and completeness

Spec Snippet (Verification Verdict)

{
  "verdict": "valid",
  "phases": [
    { "phase": "manifest", "status": "pass" },
    { "phase": "attachments", "status": "pass" },
    { "phase": "content", "status": "pass" },
    { "phase": "chain", "status": "pass" },
    { "phase": "cross_segment", "status": "pass" },
    { "phase": "signatures", "status": "pass" },
    { "phase": "verdict", "status": "pass" }
  ]
}

7-phase bundle verification: integrity proven without access to the live system.

Key takeaway

Compliance stops being a reconstruction exercise and becomes a bundle export. The evidence is self-contained, the verification is deterministic, and the auditor doesn’t need access to your live system. The same pattern serves regulatory audits, incident review, and archival preservation.

Learn More

That completes the introduction to Arxi. Compare editions in Arxi Features, or go straight to the docs for specs, math, and guarantees.