Lineage Explorer | Developer Docs

Lineage Explorer is the execution investigation workspace at /trace-explorer. Route access requires trace:read unless a full-access role applies.

What it owns

Run search and disposition filters over Lineage Records.
An ordered run story built from the execution's spans. Consecutive spans with the same signature collapse into one step.
Per-step operation name, duration, clock time, agent, service, rule identifier, decision, and reason.
Policy outcomes, masked payloads with justification-gated unmasking, and a raw record view.
Signature and timestamp proof checks against the record's Sealed Evidence Bundle.
Contextual handoffs to Decision Desk and Evidence Room.

The page refreshes on request. It holds no live subscription.

A Lineage Record is the trace for one governed execution. It keeps execution, Release, Rollout, Process version, policy, Decision Request, and source-event identifiers when those records exist.

Evidence handoff

flowchart LR
  E["Execution"] --> L["Lineage Record"]
  L --> S["Selected records and chronology"]
  S --> F["Evidence Factory Job"]
  F --> B["Sealed Evidence Bundle"]

Lineage Explorer supplies selectors and chronology to the shared Evidence Factory contract. Evidence Room owns job status, bundle inventory, download, sharing, and verification.

Cross-tenant, stale, and inaccessible direct links fail closed. Redaction occurs before stored attributes are presented.