feat: add SessionBank checkpoint replay telemetry - #4
Merged
PhilipJohnBasile merged 1 commit intoAug 11, 2026
Conversation
Owner
Author
|
Publication receipt for
Workflow: https://github.com/PhilipJohnBasile/MTPLX/actions/runs/31515511225 |
PhilipJohnBasile
marked this pull request as ready for review
August 11, 2026 17:04
PhilipJohnBasile
changed the base branch from
codex/sparse-complete-state-checkpoints-20260811
to
codex/moe-dflash-integration-20260730
August 11, 2026 17:05
Owner
Author
|
Final merged-state receipt:
Final workflow: https://github.com/PhilipJohnBasile/MTPLX/actions/runs/31515841020 |
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
This is a stacked draft PR on #3. It adds a default-off, bounded, content-free SessionBank overlap trace and a CPU-only offline checkpoint-placement replay/falsifier.
put_snapshotrecurrence provenance to recurrent/fail-closedContract
This does not activate a runtime placement policy and cannot emit a deployable GO.
runtime_goremains false and the CLI exits nonzero even when the CPU counterfactual clears its numeric threshold.The two replay arms are deliberately limited:
observed_fittedmay select successfully captured snapshots whose payloads were later discarded, so it is counterfactual-only.future_known_upperuses event-specific future knowledge and is only a no-go oracle.Only complete, quiescent traces with no drops, pending probes, or candidate truncation are eligible for favorable evidence. Request ordering is server probe/admission chronology, not client-observed HTTP start time. The trace excludes prompt/token/session/model content, but includes prompt lengths, bounded duration counters, epochs, and process-local ordinals.
Runtime promotion still requires implementable retention/rematerialization, exact continuation, measured M5 cost, quality, regression, and physical-memory gates.
Verification
Exact reviewed commit:
cce784be70da96320e05db2565581bcdd55e6000py_compilepassedgit diff --checkpassedNo GPU/model load, M5 timing, quality, physical-memory, or production-speed claim is included.