Project typed failure origins and join correction evidence by identity

This commit is contained in:
2026-11-16 15:00:05 +00:00
parent b98d463958
commit 5167154a1c
16 changed files with 473 additions and 363 deletions

View File

@@ -51,10 +51,15 @@ count, and a `failures` sequence. Each failure identifies the operation
(`proposal`, `validation`, `validation_input`, or `correction_repair`), optional validator and
zero-based batch index, safe reason/message, sorted proposal indices when
known, and execution counts when available. Multiple failed batches in one
work unit form one error record. `scope: run` instead records phase, safe reason
and message, optional origin, and output path where relevant. It can describe
a fatal error or secondary output-write failure without inventing a failed
model work unit. Raw provider errors and transcript text are absent.
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.
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

@@ -72,3 +72,10 @@ Useful tests: `internal/core/reporting/*_test.go`,
`internal/core/diagnostics/*_test.go`,
`internal/framework/processreport/*_test.go`, and
`cmd/audita/main_integration_test.go`.
Report projection uses typed operation and delivery results. Recoverable
operations count toward work-unit errors. A fatal processing cause retains its
own phase and available operation coordinates, and peer interruptions and later
file failures preserve their own attribution. The correction ledger joins one
candidate row by module instance and proposal index, preserving repair lineage
and the recorded validator execution class.

View File

@@ -629,6 +629,15 @@ specified mixed run, including partial decisions, repair/filter interaction,
later failure, and an overridden validator class. Update the
[output contract](../integrations/output-files.md) and diagnostics internals.
**Complete.** Reports project typed operation, processing, and delivery
facts, with separate attribution for the primary failure, interrupted peers,
and file failures. The ledger joins each candidate's evidence once, uses
recorded validator classes, and preserves literal empty replacements and
repair lineage. Apply-time filtering reuses original section lookups and
groups skip evidence by its originating operation. The full offline Go suite
passed, including mixed YAML and Markdown counts, ledger class overrides,
and the repair/filter/later-failure subprocess fixture.
## Stage 18 — Retain evidence according to selected outputs
Audit #32 and supporting work for #30, #33, and #44.