eric/audita
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

Validate correction repair through the processing command

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-11 04:47:43 +00:00
parent f4c638313e
commit aa8073cab1
19 changed files with 511 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/roadmap/correction-repair.md
View File

@@ -2,8 +2,8 @@
**Updated:** 2026-11-11
**Status:** Feature direction and all six decisions accepted. Implementation
is pending. See the [implementation plan](implementation.md).
**Status:** Implemented. See the [implementation plan](implementation.md)
and the [pipeline guide](../internal/pipeline.md).
## Objective

8
docs/roadmap/future.md
View File

@@ -11,9 +11,9 @@ implementing every capability.
The implemented [partial-success decision reconciliation](../internal/validators.md#llm-validator-batching)
preserves usable decisions without another model call. Revision of rejected
correction proposals is now an agreed feature direction in the
[correction-repair roadmap](correction-repair.md), with its feature decisions accepted.
That work includes substantive validator feedback and explicit proposal withdrawal.
correction proposals is implemented with substantive
validator feedback and explicit proposal withdrawal; see the
[pipeline guide](../internal/pipeline.md).
It is distinct from recovering an unavailable validator decision.
Consider bounded feedback and regeneration for model responses that satisfy the
@@ -32,7 +32,7 @@ shared library capabilities where appropriate; do not introduce an uncoordinated
outer retry loop that multiplies existing retry/repair budgets.
Editorial rejection remains a valid decision about the evaluated proposal. The
correction-repair roadmap owns any subsequent revision of that proposal and full
implemented correction repair loop handles subsequent revision and full
revalidation; this deferred entry concerns unavailable decisions. Decision recovery
must preserve required validation, candidate identity, partial-success safety,
and truthful error/recovery reporting. Validate with controlled responses that

2
docs/roadmap/implementation.md
View File

@@ -352,6 +352,8 @@ validator responses remains [deferred](future.md#domain-aware-response-recovery)
## Stage 9 — Validate the assembled command and update canonical documentation
**Completed.**
1. Exercise the normal processing command with controlled provider responses,
real configuration and prompt loading, and the output session. Cover a
mixed proposal set with two independent repair branches, a second turn