Bound concurrent section work and finalize proposal identities in order

This commit is contained in:
2026-11-16 14:53:14 +00:00
parent 1c43264f6f
commit b98d463958
11 changed files with 739 additions and 240 deletions

View File

@@ -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).