Identify pipeline entries in reports and diagnostics
This commit is contained in:
@@ -545,6 +545,11 @@ failure before outputs/model work and a valid no-stage normalization run.
|
||||
|
||||
## Stage 13: Carry stage identity through ordinary and debug evidence
|
||||
|
||||
**Completed.** Machine records carry execution position and optional operator ID;
|
||||
human labels include position, module, and the ID when supplied. Controlled
|
||||
processing and focused report checks cover repeated and unnamed entries, escaped
|
||||
labels, debug evidence, recoveries, failures, and unavailable candidates.
|
||||
|
||||
Own `internal/framework/outcomes`, `processreport`, `structuredoutput` call
|
||||
context, and `internal/core/reporting`. Use the [stage attribution contract](glossary-stages.md#stage-identity-and-attribution--resolved).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user