Preserve decision sequence in recall spans - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 passed561fabcdchanges from candidate002