Skip to main content

Module trace

Module trace 

Source
Expand description

Explanation traces for policy decisions.

Every PolicyDecision returned by the engine carries an optional DecisionTrace so audit consumers and the dashboard can answer “why was this denied / approved” without re-running the engine.

The trace is additive metadata — existing API contracts continue to work unchanged. Consumers that don’t care about explanations can ignore the field; consumers that do care receive the full conflict-resolution record produced by crate::precedence::resolve_conflicts.

Structs§

DecisionTrace
Audit-grade explanation of how a policy decision was reached.