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

Verify partial validator decisions through CLI workflows

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-25 11:34:26 +00:00
parent 22f0932389
commit b8089f4a50
6 changed files with 361 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/roadmap/decision-set-reconciliation.md
View File

@@ -2,8 +2,7 @@
**Last updated:** 2026-09-25
**Status:** Accepted feature direction; implementation not started. Intended for
consideration before v2.0.0. This document owns the target behavior and user intent.
**Status:** Implemented. This document owns the target behavior and user intent.
[implementation.md](implementation.md) owns concrete decisions, ordered work,
and verification.
@@ -19,7 +18,7 @@ Missing validation must never authorize applying a correction, but neither shoul
it invalidate a different candidate's unambiguous approval or editorial rejection.
The existing [resilience design](resilience.md) remains the foundation.
## Current Baseline
## Historical Baseline
The reviewed application baseline is `d2a6fcf`:

22
docs/roadmap/future.md
View File

@@ -9,22 +9,20 @@ intent; inclusion does not commit us to implementing every capability.
## Domain-Aware Response Recovery
First implement [partial success for validator decision sets](decision-set-reconciliation.md),
preserving usable decisions without another model call. Reconsider guided recovery
after that simpler change, based on the failures that remain. General per-entry
The [partial-success decision reconciliation](decision-set-reconciliation.md)
preserves usable decisions without another model call. Guided recovery remains
deferred pending evidence from failures that remain. General per-entry
salvage from structurally invalid responses is also a separate design question;
the accepted reconciliation feature retains whole-response structural validation.
Add bounded feedback and regeneration for model responses that satisfy the
structural schema but violate Audita's domain response contract, such as missing,
duplicate, or unexpected validator decision indices. The goal is to recover more
usable work before excluding affected candidates, reducing the impact of an
isolated malformed decision set.
Consider bounded feedback and regeneration for model responses that satisfy the
structural schema but leave requested decisions unavailable after reconciliation.
The goal would be to recover more usable work before excluding affected
candidates, when doing so materially improves outcomes.
This capability is desired but explicitly deferred from the current resilience
work. That work retains existing PromptKit structural repair and safe filtering;
unresolved domain-invalid decision sets produce errors and exclude their affected
candidates while other candidates can succeed.
This capability is explicitly deferred. Current behavior retains PromptKit
structural repair and per-candidate reconciliation; unavailable requested
decisions produce errors while other candidates can succeed.
Before implementation, define the Audita/PromptKit ownership boundary, which
checks are eligible for feedback, how feedback identifies defects without exposing

10
docs/roadmap/implementation.md
View File

@@ -2,7 +2,7 @@
**Last updated:** 2026-09-25
**Status:** Ready for implementation; no stages implemented by this planning pass.
**Status:** Implemented; all stages completed.
**Source baseline:** `60e2fe7`.
**Audience:** gpt-5.6-terra coding agent.
@@ -230,6 +230,14 @@ success and handled extras through existing reporting mechanisms.
## Stage 3 — Verify the Assembled Workflow and Finalize Documentation
**Completed:** 2026-09-25. Controlled subprocess runs covered a mixed decision
response and an extra-only response through the CLI, transcript, YAML, Markdown,
debug ledger, and interaction evidence. Fixture execution facts showed one
provider attempt and zero structural repairs per logical call. `go test
./cmd/audita` and `go test ./...` passed. Canonical validator guidance and
roadmap status were updated; the two span-deletion plan links now target the
historical plan at `60e2fe7`.
**Work**
1. Extend the existing local-provider subprocess fixtures in

12
docs/roadmap/span-deletion.md
View File

@@ -2,9 +2,10 @@
**Last updated:** 2026-09-25
**Status:** Implemented. This document owns the desired
behavior and user intent. [implementation.md](implementation.md) owns the concrete
steps, selected implementation details, and completion evidence.
**Status:** Implemented. This document owns the desired behavior and user intent.
The [historical implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/60e2fe7/docs/roadmap/implementation.md)
records the concrete steps, selected implementation details, and completion
evidence.
## Purpose and User Intent
@@ -197,5 +198,6 @@ in [future.md](future.md). This feature changes neither retry budgets nor the
Audita/PromptKit ownership boundary and requires no upstream library feature.
Implementation sequencing and concrete names belong to the
[implementation plan](implementation.md). The target remains consistent deletion
of spans within surviving segments, with no new operator controls or report types.
[historical implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/60e2fe7/docs/roadmap/implementation.md).
The target remains consistent deletion of spans within surviving segments, with
no new operator controls or report types.