Skip to content

Preserve decision sequence in recall spans - #8

Merged
Sahith59 merged 1 commit into
mainfrom
codex/recall-decision-order
Sep 12, 2026
Merged

Sahith59 merged 1 commit into
mainfrom
codex/recall-decision-order

Conversation

@Sahith59

Copy link
Copy Markdown
Owner

The final recall-control QA reached the correct source session but still answered Fissionator incorrectly because the reserve selected a later design exchange and equal-timestamp packing obscured the earlier naming decision.

This change keeps the existing session admission/ranking boundary, then uses source-only decision cues inside the selected session to reserve the proposal, user acceptance, and immediate continuation in original dialogue order. On the frozen corpus, only the Fissionator packet changes relative to the previous final candidate; all other 109 final packets remain byte-identical.

Validation:

  • pytest -q tests/test_recall_span_adapter.py — 10 passed
  • frozen all54 packet gate and independent verification pass; exact49-case admission set retained,49/49 selected gold sessions, no session loss
  • frozen final110 composition and independent verification pass; only 561fabcd changes from candidate002
  • no paid call was used for this offline repair

@Sahith59
Sahith59 merged commit 9ffe8e2 into main Sep 12, 2026
1 check passed
@Sahith59
Sahith59 deleted the codex/recall-decision-order branch September 12, 2026 17:57
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