feat: add exact sparse checkpoint placement planner - #3
Merged
PhilipJohnBasile merged 1 commit intoAug 11, 2026
Conversation
Owner
Author
|
Exact-head public build receipt: release run 31492969642 passed on |
PhilipJohnBasile
marked this pull request as ready for review
August 11, 2026 17:04
PhilipJohnBasile
merged commit Aug 11, 2026
5df9af9
into
codex/moe-dflash-integration-20260730
2 checks passed
7 tasks
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.
Summary
Scope
This is phase 1 only: planner and oracle infrastructure. It does not change SessionBank capture, restore, placement, SSD, cache ownership, or runtime defaults, and it makes no M5 speed claim.
The architecture audit found that MTPLX already has hybrid snapshots and geometric recurrent boundaries. Runtime integration should therefore modify the existing SessionBank path only after real overlap traces show that an optimal oracle beats the incumbent policy. Separate pre-existing exactness/identity/lifecycle gaps must be fixed before any complete-state release claim.
Follow-up GO gate: equal-byte-budget trace replay must beat the incumbent geometric policy by at least 10%, with a paired 95% lower bound above zero and wins in at least two non-append overlap buckets. Only then should an opt-in M5 runtime experiment begin.
Verification
python -m pytest tests/test_checkpoint_placement.py— 28 passed(10**16, 10**16, 1), budget 1 →(2,)(2, 3, 2), budget 2 →(1, 2)py_compileandgit diff --check— passedmtplx/checkpoint_placement.pyRelationship
Follow-up implementation work from #2. Kept separate so the evidence-only research PR remains unchanged.