Bound concurrent section work and finalize proposal identities in order
This commit is contained in:
@@ -15,8 +15,11 @@ formats; [configuration](../config.md) owns settings; the
|
||||
estimates stay fixed while text evolves.
|
||||
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.
|
||||
operation facts and any captured exchange. A bounded window admits sections
|
||||
in order and lets validation and repair proceed as proposals become ready.
|
||||
The runner assigns final proposal indices in section and response order
|
||||
when it records completed work. It then writes diagnostics that use those
|
||||
indices. PromptKit controls provider capacity across all three roles.
|
||||
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.
|
||||
@@ -43,8 +46,8 @@ complete with model errors and applied corrections. Recoverable model failures
|
||||
never trigger shared cancellation. Fatal failures and parent cancellation stop
|
||||
further dispatch and join active workers. The initiating error carries its
|
||||
processing phase and available origin. Work-unit evidence preserves each peer's
|
||||
interruption or error. Usable proposal results from later sections are indexed
|
||||
in order after joining, even when the runner could not validate them. The
|
||||
interruption or error. The runner drains active outcomes and assigns indices
|
||||
to usable proposals from later sections even when it could not validate them. The
|
||||
working transcript advances only at the module's successful commit boundary.
|
||||
Earlier committed text remains available to an interrupted run, and transcript
|
||||
delivery requires successful processing.
|
||||
|
||||
@@ -589,6 +589,21 @@ pending, and identical index ordering for the same usable results under
|
||||
different completion orders. Report representative pending-work measurements
|
||||
without pinning a timing or worker-count threshold in the default suite.
|
||||
|
||||
**Complete.** The runner admits sections through a bounded rolling window,
|
||||
drains active outcomes on cancellation, and lets validation and repair proceed
|
||||
while earlier proposals are pending. It assigns final indices in section order
|
||||
and publishes identity-sensitive artifacts through the interaction writer.
|
||||
Tests checked native contention and overlap, stable ordering, and repair and
|
||||
revalidation evidence after completion and cancellation. The full offline Go
|
||||
suite and targeted race checks passed.
|
||||
|
||||
In three runs of a 36-section fixture with two shared provider slots and the
|
||||
first proposal held for 250 ms, ordered dispatch completed seven later proposals
|
||||
and no validations during the hold. With section-local identities, seven later
|
||||
validations also reached the provider before release, with eight sections
|
||||
charged to the window in both variants. Both variants completed 36 proposals
|
||||
and 36 validations overall. The window of eight was retained for this workload.
|
||||
|
||||
## Stage 17 — Project typed report and ledger facts
|
||||
|
||||
Audit #22, #27 (ledger), #39, #41 (projection).
|
||||
|
||||
Reference in New Issue
Block a user