Decision trace

What it contains

A trace is not a log line. It records the evidence an agent or person consulted, the version of the policy in force, the reasoning that connected the two, and the outcome. Because it is captured at execution time rather than reconstructed afterwards, it reflects what was actually known when the decision was taken rather than what could be pieced together later.

Why it is different from a log

Audit logs answer the question "what happened". A decision trace answers "why was this allowed". That distinction is what regulators, auditors, and courts actually probe, and it is the part that conventional systems discard because the reasoning lived in a person or a model rather than in a field.

Why traces compound

Once decisions carry their reasoning, they become precedent. An agent facing a similar case can inherit how comparable situations were handled rather than starting from the raw data, which is why a system that records traces improves over time instead of merely repeating itself.

In practice

A customs agent clears a shipment at 02:14. The trace records the three supplier attestations it read, the tariff policy at revision 14, the origin exception it applied because a tier-two supplier was newly certified, the two comparable shipments whose handling it inherited, and the compliance officer whose standing authorized that class of exception. Nine months later a regulator asks why that shipment cleared, and the answer is retrieved in seconds rather than rebuilt from email.

Common questions about decision trace.

Read next.