Causal Forensics

DECISION TRACES

Cross-system context recording with threaded trace views. See exactly what data an agent gathered, what it decided, and why — with full input provenance.

InputsSource Tracking
ThreadedParent-Child Trees
HashData Integrity

See it in action

custodex.vercel.app
DECISION TRACES — Custodex Dashboard

Every input. Every source. Every data hash.

Record the exact inputs an agent consumed before making a decision: Salesforce records, PagerDuty alerts, Slack messages, database queries. Each input captures source, source type, query, summary, and a SHA-256 data hash for integrity verification — without storing the sensitive data itself.

POST /api/decision-traces
{
  "traceId": "tr_abc123",
  "action": "crm.update",
  "scope": "crm:write",
  "decision": "allowed",
  "intent": "Update customer status based on support ticket",
  "inputs": [
    {
      "source": "salesforce",
      "sourceType": "crm",
      "query": "GET /contacts/C-1234",
      "summary": "Customer record with open ticket",
      "dataHash": "sha256:a1b2c3..."
    },
    {
      "source": "pagerduty",
      "sourceType": "incident",
      "query": "GET /incidents/INC-567",
      "summary": "P2 incident, 4h old",
      "dataHash": "sha256:d4e5f6..."
    }
  ],
  "rationale": "Customer has open P2 incident requiring status update"
}

Parent-child trace trees for orchestration chains.

Traces link via parentTraceId to form trees. A parent agent delegates to sub-agents, each recording their own trace. The threaded view shows the full decision tree from root orchestrator to leaf executors. Collapse or expand any branch.

Reconstruct any decision. Months later.

Filter traces by agent, session, decision type, or input source. Every trace links to its telemetry event and approval (if any). Data hashes allow post-hoc verification that inputs haven't been tampered with. Export trace chains for compliance evidence.

What's included in
decision traces

01

Cross-system input recording with source provenance

02

SHA-256 data hashing for integrity verification

03

Parent-child trace threading for orchestration chains

04

Filter by agent, session, decision, or source

05

Links to telemetry events and approval records

06

Export trace chains for compliance evidence packages