Correctness / Tracing
Boundary Tracing
Tracing captures what happened at the boundary, why it failed, and what correction path succeeded.
What Tracing Records
- attempt number and model metadata
- failure class and message
- repair transform that ran
- retry decision and final outcome
Example Trace
Attempt 1 PARSE_ERROR repair: strip markdown Attempt 2 VALIDATION_ERROR repair: regenerate Attempt 3 SUCCESS
This turns probabilistic generation into a sequence of observable boundary decisions.
Operational Value
Boundary traces let teams compare model versions, isolate regression classes, and route failures with context instead of generic error strings.