Decision Trace Reconstructor makes agent decisions auditable after the fact: it shows whether the available traces are enough to reconstruct what happened, and names every missing or opaque decision fact.
Instead of generating another narrative, it produces a per-property reconstructability matrix: which decision-event fields are evidenced, partial, structurally absent, or opaque. No synthetic rationale is invented.
Full adapter documentation lives in docs/adapters/. Each adapter supports offline file ingest; vendor-backed adapters also support live/network ingest when the optional extra and credentials are available.
| # | Adapter | Extra | Covers |
|---|---|---|---|
| 01 | langsmith |
[langsmith] |
LangChain / LangGraph ecosystem |
| 02 | otlp |
[otlp] |
OpenTelemetry GenAI — one adapter, many backends |
| 03 | bedrock |
[bedrock] |
AWS Bedrock AgentCore |
| 04 | openai-agents |
[openai-agents] |
OpenAI Agents SDK + Traces dashboard exports |
| 05 | anthropic |
[anthropic] |
Anthropic Messages API + Computer Use |
| 06 | mcp |
[mcp] |
Model Context Protocol transcripts |
| 07 | crewai |
[crewai] |
CrewAI multi-agent telemetry |
| 08 | agentframework |
[agentframework] |
Microsoft Agent Framework / AutoGen v0.4 |
| 09 | pydantic-ai |
[pydantic-ai] |
Pydantic AI run records |
| 10 | generic-jsonl |
none | Custom JSONL logs via mapping config |
Unsupported source systems should use generic-jsonl first. If OpenTelemetry GenAI spans are available, otlp is usually the better long-term integration path.
# 1. Install with the relevant adapter extra
pip install -e '.[langsmith]' # or [otlp], [bedrock], [openai-agents], ...
# 2. Ingest a trace into a fragments manifest
decision-trace ingest langsmith --from-file traces/agent_run.json \
--architecture single_agent --stack-tier within_stack \
--state-mutation-tools "(write|exec|drop|delete|update)" \
--out fragments.json
# 3. Reconstruct and emit evidence reports
decision-trace reconstruct fragments.json --out report/ --jsonldOutput:
report/feasibility.json: per-property reconstructability categories, gap descriptions, and completeness percentagereport/trace.jsonld: W3C PROV-O graph, queryable via SPARQL
Ingest can also be piped directly into reconstruction:
decision-trace ingest langsmith --from-file traces/run.json --out - | \
decision-trace reconstruct /dev/stdin --out report/ --jsonldThe report is intentionally diagnostic, not narrative:
| Property | Category | Gap |
|---|---|---|
inputs |
fully_fillable |
none |
policy_basis |
structurally_unfillable |
active policy was not recorded |
reasoning_trace |
opaque |
model reasoning is not externally observable |
- Installation
- Adapter documentation
- Reports and output artifacts
- Reconstruction architecture
- v0.2.0 release notes and migration
- Development
- Roadmap
Worked examples live under examples/<adapter>_basic_agent/ and are pinned by integration tests for bit-identical reproduction. The named incident example examples/replit_drop_database/ shows reconstruction from a public-record fragment manifest.
- Companion papers for the Decision Evidence Maturity Model and related evidence-regime concepts are in preparation. They are intentionally not cited as publications until public identifiers exist.
- Conceptual dependencies: the Decision Event Schema, the upstream Evidence Collector SDK, and the downstream Governance Benchmark Dataset.
CITATION.cff, codemeta.json, and ro-crate-metadata.json ship with the package.
Version v0.1.0 is archived on Zenodo at https://doi.org/10.5281/zenodo.19851574. That deposit identifies the original fixture evaluation, including the retained results/ files. Version v0.2.0 was published on 11 October 2026 and is archived at https://doi.org/10.5281/zenodo.23297502. It contains the typed-contract implementation and replay tools. The later live-model packets, frozen assessments and replay results require a separate replication deposit; neither software DOI identifies that study dataset.
Apache-2.0. See LICENSE.
The mapper separates topology from evidence visibility and record producers from action issuers. Existing manifests report structural coverage (fragment-coverage-v2). The opt-in decision-evidence-v1 contract checks structured scope, request/receipt binding and independent state observations; it is not a general semantic or authentication verifier. See the contract and examples. Historical v0.1.0 results and frozen V5 assessments remain tied to their preserved instruments.
See the replication guide for the immutable run inventory, portable offline reproduction command and local package preparation. Study data are delivered separately from the runtime wheel. The source distribution includes the experiment tools, but cannot recreate frozen model responses unless the replication data are supplied.