Preserve version one error record scopes

This commit is contained in:
2026-11-17 03:54:41 +00:00
parent 0c2a2164ec
commit c6be2ec20d
7 changed files with 71 additions and 47 deletions

View File

@@ -55,11 +55,12 @@ work unit form one error record. A record with scope `run` records a fatal
processing failure or a separate output delivery failure. It identifies the
phase, safe reason and message, and available origin. A processing origin can
include the operation, validator, batch, proposal index, and repair attempt.
A delivery failure includes the output path when known. A record with scope
`interrupted` preserves an interrupted peer's cause and location when
available. These records do not add to the recoverable work-unit or run-error
counts. The work-unit matrix still marks the interrupted work. Raw provider
errors and transcript text are absent.
A delivery failure includes the output path when known. The initiating
processing failure can include an `interruptions` sequence with each
available peer's phase, safe reason and message, and available origin.
Peer details do not add to the recoverable work-unit or run-error counts.
The work-unit matrix marks interrupted work. Raw provider errors and
transcript text are absent.
For `validation_decisions_invalid`, proposal indices identify only candidates
whose required decisions were unavailable. Other candidates in the same batch
may still be approved or rejected normally.

View File

@@ -81,6 +81,11 @@ second write failure. Check failure attribution and counts as well as status.
### R2 — Preserve the Version 1 Error Record Discriminator (P2)
**Complete.** Version 1 retains the `work_unit` and `run` scopes. The
initiating run record carries available peer details in an optional
`interruptions` sequence. The mixed-run YAML and Markdown test verifies
peer attribution and unchanged counts.
**Affected plan:** Stage 17, item 1.
**Evidence:** [Report projection](../../internal/framework/processreport/report.go#L108)