python-math #47: docs+test(delphi): s7 conditions 4-6 evidence — EC2 measurement, equiv PASSes, NaN pin - #2676
Draft
jucor wants to merge 1 commit into
Draft
python-math #47: docs+test(delphi): s7 conditions 4-6 evidence — EC2 measurement, equiv PASSes, NaN pin#2676jucor 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
python-math #43: docs(delphi): s7 goal state + journal — mode collapse executed, battery 20/20
#2672
Draft
Draft
Draft
Draft
Draft
This was referenced Jul 27, 2026
Draft
Draft
Draft
5 tasks
This was referenced Jul 28, 2026
Draft
jucor
changed the title
…measurement, equiv PASSes, NaN pin ## What Closing evidence for `GOAL_CUTOVER_READY.md` (the standing goal document for the Python math cutover), covering its numbered DONE conditions 4-6. - `CUTOVER_RUNBOOK.md` risk item 3 RESOLVED with the measured numbers (r8g.4xlarge EC2 instance, 33,422 participants x 783 comments, 2.0M votes): cold tick 519.6s, WARM tick 1856.0s (~31 min). Verdict: NOT serial-OK at the extreme shape — either the deterministic large-conversation path (runbook item 9) or a `POLL_BLOCKLIST` of the 7 historical zids (conversation ids) at that scale is required before they tick on Python. The flip itself is not blocked. - Journal: the battery pair plus zero-open-ledger evidence for condition 4 (the certification battery at 20/20 MATCH twice, divergence ledger 0 open); live equivalence full-run PASSes on the `vw` AND `pc-meta-02` datasets for condition 5; the EC2 + local measurement records for condition 6; review dispositions (the #2659 finding was pre-fixed by the mode collapse; #2663 is sound); and the Copilot-credits correction. - #2663 review pin applied: `test_euclidean_propagates_nan_instead_of_clamping` — NaN must propagate through the legacy `_euclidean` distance; the old `max(0.0, d2)` silently ate it — plus a ledger addendum for quirk Q11 (the legacy kmeans distance formula's cancellation makes near-coincident points tie at exactly 0.0, and those ties decide cluster merges). commit-id:c5632ace
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.
What
Closing evidence for
GOAL_CUTOVER_READY.md(the standing goal document for the Python math cutover), covering its numbered DONE conditions 4-6.CUTOVER_RUNBOOK.mdrisk item 3 RESOLVED with the measured numbers (r8g.4xlarge EC2 instance, 33,422 participants x 783 comments, 2.0M votes): cold tick 519.6s, WARM tick 1856.0s (~31 min). Verdict: NOT serial-OK at the extreme shape — either the deterministic large-conversation path (runbook item 9) or aPOLL_BLOCKLISTof the 7 historical zids (conversation ids) at that scale is required before they tick on Python. The flip itself is not blocked.vwANDpc-meta-02datasets for condition 5; the EC2 + local measurement records for condition 6; review dispositions (the python-math #33: docs(delphi): overnight pre-cutover audit (s6) — CUTOVER_RUNBOOK + journal #2659 finding was pre-fixed by the mode collapse; python-math #34: fix(delphi): Copilot-review triage batch — 16 findings across the stack #2663 is sound); and the Copilot-credits correction.test_euclidean_propagates_nan_instead_of_clamping— NaN must propagate through the legacy_euclideandistance; the oldmax(0.0, d2)silently ate it — plus a ledger addendum for quirk Q11 (the legacy kmeans distance formula's cancellation makes near-coincident points tie at exactly 0.0, and those ties decide cluster merges).commit-id:c5632ace
Stack: