Skip to content

Disambiguate recall spans with session context - #7

Merged
Sahith59 merged 2 commits into
mainfrom
codex/recall-entity-order
Sep 12, 2026
Merged

Sahith59 merged 2 commits into
mainfrom
codex/recall-entity-order

Conversation

@Sahith59

Copy link
Copy Markdown
Owner

The final English QA isolated one development control where generic recall wording selected an unrelated session even though the correct source session was present. This change adds complete scoped-session similarity to span reranking while preserving the existing turn-level admission boundary, so 561fabcd and d596882b move to their annotated gold sessions without admitting any new query.

Validation:

  • 35 focused retrieval tests pass
  • frozen all54 screen passes with the exact prior 49-case admission set, 49/49 selected annotated gold sessions, zero annotated-session loss, and 49/54→54/54 lexical answer recoverability
  • final110 composition changes only those two packets versus the paid candidate; the other108 are byte-identical and independent verification passes

@Sahith59
Sahith59 merged commit 63114d6 into main Sep 12, 2026
1 check passed
@Sahith59
Sahith59 deleted the codex/recall-entity-order branch September 12, 2026 17:15
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