Skip to content

Collect bounded music-event chronologies - #6

Merged
Sahith59 merged 1 commit into
mainfrom
codex/multi-event-reserve
Sep 12, 2026
Merged

Sahith59 merged 1 commit into
mainfrom
codex/multi-event-reserve

Conversation

@Sahith59

Copy link
Copy Markdown
Owner

The combined English confirmation missed one five-event concert chronology because the conservative dated-event reserve kept only the earliest event. Raising the existing limit also admitted unrelated events, so this adds an opt-in benchmark route restricted to explicit ordered music-event range questions. It selects distinct, completed user events in source-date order and remains disabled by default.

The frozen selector census processes all 500 questions: exactly the Queen chronology triggers, five source events are selected, and the other 499 produce no enumeration reserve. Its packet gains the fifth annotated source session, improves first-24k source-session coverage from 3 to 5, and places all five answer needles between characters 10,587 and 12,048. One displaced exact turn asks about future jazz festivals and is pre-reviewed and hash-bound; the attended jazz event remains. Independent verification passes.

Validation: pytest -q tests/test_dated_event_reserve.py tests/test_dated_event_adapter.py tests/test_recall_span_adapter.py (32 passed). No provider calls or paid evaluation were made.

@Sahith59
Sahith59 merged commit ecb81a6 into main Sep 12, 2026
1 check passed
@Sahith59
Sahith59 deleted the codex/multi-event-reserve branch September 12, 2026 15:53
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