1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
//! Structured evaluation traces for FEL.
//!
//! A [`Trace`] is an ordered sequence of [`TraceStep`]s that records what the
//! evaluator did while producing a result. Traces are opt-in: the hot-path
//! [`crate::evaluate`] function does not allocate or emit any steps. Use
//! [`crate::evaluate_with`] with [`crate::EvaluatorOptions::trace`] set (and optionally [`crate::EvaluatorOptions::extensions`] when host
//! extensions must appear in the trace) to capture one.
//!
//! Traces are designed for human and LLM consumption, not for re-evaluation.
//! Values are projected to `serde_json::Value` — losing FEL type fidelity
//! (money, date) but gaining universal readability. Add new variants as the
//! need arises; this v0 set covers field resolution, function calls, binary
//! ops, conditional branches, and short-circuit skips.
use Serialize;
/// A single recorded event during FEL evaluation.
///
/// The variant set is intentionally narrow: only events that help explain
/// *why* an expression produced its result. Non-covered AST nodes omit steps
/// rather than emitting noise — correctness over completeness.
/// An ordered record of everything the evaluator emitted during one run.
///
/// Steps are appended in evaluation order. A consumer (linter, MCP tool,
/// error-explainer) can render the sequence top-to-bottom to reconstruct
/// *why* the expression produced its result.