python-math #35: feat(delphi): certify battery speedup — engine-scoped py cache + parallel entries (Phase 0) - #2664
Draft
jucor wants to merge 1 commit into
Draft
python-math #35: feat(delphi): certify battery speedup — engine-scoped py cache + parallel entries (Phase 0)#2664jucor wants to merge 1 commit into
jucor wants to merge 1 commit into
Conversation
This was referenced Jul 27, 2026
Draft
Draft
Draft
Draft
Draft
Draft
Draft
Draft
This was referenced Jul 27, 2026
Draft
Draft
python-math #43: docs(delphi): s7 goal state + journal — mode collapse executed, battery 20/20
#2672
Draft
Draft
Draft
This was referenced Jul 28, 2026
Draft
jucor
changed the title
…d py cache + parallel entries (Phase 0) ## Why `GOAL_CUTOVER_READY.md` Phase 0 (Julien ruling 2026-07-27): the certification battery re-ran the full ~36-minute Python re-replay after ANY `polismath` edit, blocking every code change. ## What - The Python recording cache key is now the ENGINE-scoped tree hash: pure-harness files (`certify.py`, `poller_equiv.py`, `prodclone.py`, `shard_bench.py`, `poller/**`) are excluded from the hash — none is reachable from the replay subprocess import graph (`scripts/replay_driver.py` -> driver/schedule/real_data/store/stepcompare/types -> engine). Manifest key renamed `py_tree_sha256` -> `engine_tree_sha256`; the resulting one-time invalidation of all 20 Python recordings doubled as the timed A/B run. - `run_battery(workers=N)` fans the per-entry heavy work (driver subprocesses + hash-first compare) across threads; the ledger fold stays strictly serial in battery order, so report + ledger are bit-identical to `workers=1` (pinned by test). Step-verdict cache writes are atomic (tmp + `os.replace`). CLI `--workers` defaults to 6. ## Measured A/B on the 10-core host - First pass: 19m17s wall vs ~36m serial (the long pole: `pakistan:uniform8` alone is ~18m). - Cached pass: 22s. - Harness-only edit: 2m9s with ZERO re-replays (previously: the full 36-minute re-replay). ## Testing TDD: 7 RED -> GREEN; replay_harness 464 passed / 5 skipped (baseline 456/5 plus exactly the 8 new tests). Battery on this tree: 20/20 MATCH x2 (post-invalidation re-record + cached pass). The Phase 1 `engine_mode` inventory (18 branch sites classified DELETE/PARK/KEEP) is journaled. commit-id:31c19ea5
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
1 participant
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.
Why
GOAL_CUTOVER_READY.mdPhase 0 (Julien ruling 2026-07-27): the certification battery re-ran the full ~36-minute Python re-replay after ANYpolismathedit, blocking every code change.What
certify.py,poller_equiv.py,prodclone.py,shard_bench.py,poller/**) are excluded from the hash — none is reachable from the replay subprocess import graph (scripts/replay_driver.py-> driver/schedule/real_data/store/stepcompare/types -> engine). Manifest key renamedpy_tree_sha256->engine_tree_sha256; the resulting one-time invalidation of all 20 Python recordings doubled as the timed A/B run.run_battery(workers=N)fans the per-entry heavy work (driver subprocesses + hash-first compare) across threads; the ledger fold stays strictly serial in battery order, so report + ledger are bit-identical toworkers=1(pinned by test). Step-verdict cache writes are atomic (tmp +os.replace). CLI--workersdefaults to 6.Measured A/B on the 10-core host
pakistan:uniform8alone is ~18m).Testing
TDD: 7 RED -> GREEN; replay_harness 464 passed / 5 skipped (baseline 456/5 plus exactly the 8 new tests). Battery on this tree: 20/20 MATCH x2 (post-invalidation re-record + cached pass). The Phase 1
engine_modeinventory (18 branch sites classified DELETE/PARK/KEEP) is journaled.commit-id:31c19ea5
Stack: