Back to work

Causal systems

TraceAI

Explains a failed execution by tracing typed dataflow evidence back to the upstream producer.

Year
2026
Status
Built

01 / failure

A downstream process fails.

The visible error belongs to consume_and_process. The cause may not.

TraceAI causal replayA failed consumer is connected to an upstream producer by artifact:corrupted.bin.artifact:corrupted.bin
produce_fileartifact:corrupted.binconsume_and_process

02 / dependency

The failure is downstream. The evidence is not.

consume_and_process fails after accepting artifact:corrupted.bin.

The artifact is the relevant dependency: a typed dataflow edge, not an inferred story about the logs.

03 / judgment

The graph points to the producer.

root cause
step1
failure type
upstream_data_error
confidence
0.82
reason
strong dataflow evidence

produce_file emitted the invalid artifact. The consumer used that same artifact and failed. The judgment stays attached to a causal path engineers can inspect.

04 / boundary

Certainty is not a feature.

root causenone

Tied or weak evidence returns no root cause. The system preserves the ambiguity instead of manufacturing an answer.

05 / system surface

A narrow boundary. A real system.

execution spans
typed graph
causal analysis

POST /v1/tracesGET /graphGET /analysis

Python SDK · TypeScript SDK · FastAPI · PostgreSQL