Carry one proposal result from generation to the runner

This commit is contained in:
2026-11-16 14:30:57 +00:00
parent c2c8050bc8
commit a0c70e8dce
9 changed files with 153 additions and 314 deletions

View File

@@ -43,7 +43,9 @@ rendered by ConfigKit, the correction ledger, LLM execution observations, and
model interactions. Candidate capture includes proposals later
rejected or interrupted. Repair and revalidation artifacts use section, proposal,
attempt, validator, and batch coordinates as applicable. Request metadata records
these coordinates with the interaction role. Each interaction retains its available
these coordinates with the interaction role. Proposal request metadata carries
the zero-based response origin (`start_index`) and the ordered `segment_ids`
used to interpret response references. Each interaction retains its available
prepared request, response, and failure evidence. Ledger mapping preserves empty
proposed and applied replacements and distinguishes unavailable candidates from
interrupted work.

View File

@@ -13,8 +13,10 @@ formats; [configuration](../config.md) owns settings; the
3. The runner partitions the normalized transcript exactly once before its
module loop. Initial section identity, segment membership, and token
estimates stay fixed while text evolves.
4. Module instances execute in configured order. Sections may propose
concurrently, but proposal indices follow section order and response order.
4. Module instances execute in configured order. Each section hands its decoded
proposals and original local segment references to the runner along with
operation facts and any captured exchange. Sections may propose concurrently.
The runner assigns indices in section order and response order.
5. Deterministic validators precede LLM-backed validators. Every submitted
candidate receives one decision per validator on a normal return. Fatal returns
may preserve a checked subset of completed decisions as diagnostic evidence.

View File

@@ -472,6 +472,14 @@ Audit #46.
verify indices and original references. Keep model response and reference
coverage in the generator's owning tests.
**Complete.** The generator and runner share one decoded proposal result with
raw local references, operation facts, and the optional native exchange. The
runner assigns indices in section and response order. A production-module
fixture observed the later response first and verified applied indices,
operation associations, and raw references. Proposal diagnostics retain
the response-local `start_index`. The full offline suite and repeated
ordering checks under the race detector passed.
## Stage 14 — Own each correction repair branch explicitly
Audit #34, #45, #48, #64 (branch integration).