Skip to content

fix(live): model carried weights and recovery evidence - #47

Merged
hobbyistz merged 2 commits into
mainfrom
com-1497-live-record-red
Sep 3, 2026
Merged

fix(live): model carried weights and recovery evidence#47
hobbyistz merged 2 commits into
mainfrom
com-1497-live-record-red

Conversation

@hobbyistz

@hobbyistz hobbyistz commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Align the public live-record re-derivation check with the producer's current-allocation domain, excluding historical collection-failure carries while retaining current no-price carries.
  • Assert the intended pre-observation exclusion behavior: no weight or vote, with a fresh accepted recovery price retained as evidence for next-observation readmission.
  • Document both semantics in the public methodology.

References COM-1497.

Diagnosis

The current producer re-casts a prior accepted vote, band, and booked weight when collection fails. That historical carry is intentionally outside the newly allocated weight vector. Fresh recovery observations during a hard-cutoff exclusion are intentionally visible as evidence, but receive neither weight nor vote until the next scheduled observation.

Test Coverage

All changed live-record branches are exercised by the live suite.

Pre-Landing Review

No issues found.

Design Review

No frontend files changed — design review skipped.

Eval Results

No prompt-related files changed — evals skipped.

Greptile Review

Requested once in first-round-only mode. The repository integration returned no review or comments during the normal review window; no second round was triggered.

Scope Drift

Scope Check: CLEAN.

Plan Completion

  • Current allocation excludes historical collection-failure carries using shared panel constants.
  • Excluded recovery evidence must be fresh and accepted while weight and vote dispersion remain null.
  • Historical booked weights and pre-advance recovery are documented.
  • Historical carry replay coverage remains present.
  • Targeted live tests pass.
  • Methodology and public-safety checks pass.
  • The full unit suite, Ruff, and complete live suite pass.

Verification Results

  • 1,611 unit tests pass
  • 22 live tests pass against the published records
  • Ruff passes across the repository
  • Public-safety and credential-redaction sweeps pass

Automode Review Mode

  • Mode: first-round-only
  • Why: default one-round budget; no explicit Greploop request
  • Task diff: 59 lines across 2 files
  • Risk triggers: migrations=no; money-path-state-machine=no

Documentation

  • METHODOLOGY.md now clarifies historical collection-failure weights and evidence-only hard-cutoff recovery.
  • All other tracked documentation remains accurate.
  • Coverage: no public-surface gaps or architecture diagram drift.

COM-1497 distinguishes historical collection-failure carries from the current allocation vector and documents fresh recovery-price evidence during exclusion.

Signed-off-by: hobbyistz <293619914+hobbyistz@users.noreply.github.com>
@hobbyistz
hobbyistz marked this pull request as ready for review September 3, 2026 21:30
…d; attendance marking text matches the engine

The rewritten excluded-seat test required every priced excluded receipt
to be an accepted print. The engine publishes two other legitimate
shapes for a fresh recovery print on a seat that carries no weight and
no vote: one held out by the sigma fence and one quarantined by the
jump screen. The test now asserts what must hold (no weight, no vote
dispersion, a fresh upstream print with a verdict) and not which verdict.

Section 8.6 said a price rejected by the outlier check counts as absent
for attendance; the engine counts a fenced print as present (the fence
keeps a print out of the index, not out of the attendance record). The
collection-failure bullet is reworded in the document's own terms.

Signed-off-by: hobbyistz <293619914+hobbyistz@users.noreply.github.com>
@hobbyistz
hobbyistz merged commit 412415c into main Sep 3, 2026
5 checks passed
@hobbyistz
hobbyistz deleted the com-1497-live-record-red branch September 3, 2026 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant