Repository navigation
v2.2.5: window result, parity cpus tolerance, Query A/B (G5 D3b + DR byte compare), certificate PASS - #48
Merged
Conversation
…S under P1, release notes - scripts/kn_versioned_compose.py parity: compare cpus within 1e-6 vCPU (compose passes cpus through float32: 2.25 -> NanoCpus 2249999872); tests in test_kn_stable_compose. R2 re-run read-only against live 2026-10-20T03:00:55Z: PASS, 863 checks, 0 problems. - Window 2026-10-20 receipts (non-secret byte copies + SHA256SUMS) under upgrade/evidence/releases/v2.2.5/window-20261020T0128Z. - Drafts moved to final files; packet section 10 records the window result. - CERTIFICATE.md / certificate.json / endpoint-report.json: status PASS under P1 (POST_HOC_PACKAGING_DECISION, owner confirmation required): the predeclared G5 item "concurrent hot-read latency" was not measured; gates_without_p1 keeps G5 NOT_MEASURED. Other gates inherited from v2.2.4 with delta proofs; SDK 2.4.1 wheel unchanged. - CERTIFICATION_LEDGER.md and the plan journal updated.
…armup bursts + warmup byte compare) scripts/v225_query_hot_read_ab.py: old Query 3e9e4d3a vs new 753604f8 on one private read-only copy of the market cache; open-loop TS EXECUTION snapshot reads at 10/s during 12 x 64-warmup bursts (incl. memory-maintenance runs), and an A/B/A' warmup byte comparison of every TS r11 requirement. Pass rules HR1-HR5 and BC are fixed in PREREG before the run.
…a foreign correctness lock, interleaved A1 B1 A2 B2, paired-delta rules, foreign activity sampling Changed before any run; v1 (7d28d9c) was never executed.
…pec (new-generation client CA bundle) Attempt 1 (2026-10-20 04:50Z) dropped /consumer-realms/query-client-ca-bundle.crt, so the isolated replicas refused the new TS client certificate; nothing was measured. Rules unchanged.
…ery spec (/session-liveness) Attempt 2 (05:02Z) bound the stable_state volume root, so every latest read was DATA_STALE (SESSION_STATE) on both images; stopped after 3 requirements, not scored. Rules unchanged.
…are-only rerun mode Attempt 3's BC driver could not write its raw record (/out not writable for the capped root driver); the per-requirement statuses survive in cmp/driver.out, the bodies by sha. The BC phase is re-run in the same session dir after the arms. The analysis now masks the raw token at each volatile path exactly, as the pre-registered BC rule states (the driver skipped small integers such as per-request ages). Rules unchanged.
…compare; certificate PASS without P1 - Session query-ab-20261020c (2026-10-20 05:04-05:50Z, owner "Đo luôn rồi tag", run beside other agents' jobs by owner instruction, arms interleaved A1 B1 A2 B2): verdict PASS. Hot reads (TS EXECUTION QUOTE/TRADE snapshots, 10/s) during 64-warmup bursts: paired mean d_p95 -41.9 ms, d_p99 -19.5 ms; maintenance runs 131/147 ms covered; non-200 equal. - Warmup byte compare old 3e9e4d3a vs new 753604f8, 65 TS r11 requirements x 2 passes: byte-identical outside per-request paths (byte-compare.json 41ebcc3c). - Certificate, endpoint report, release notes, scope header, ledger and plan updated; P1 superseded (never used). Harness analysis compacted; unit tests for masking/percentiles.
BobbyAxerol
changed the title
…d shapes, alpha-binance r16 + alpha-okx r15 BAR 1m) Same BC rule; --alpha re-runs only the compare phase in the session dir; analyze-alpha writes byte-compare-alpha.json.
…dence updated 24 alpha read shapes (alpha-binance r16 + alpha-okx r15 BAR 1m) x 2 passes on old 3e9e4d3a vs new 753604f8: statuses equal (44 x 200, 4 x 400), bodies byte-identical outside per-request paths (byte-compare-alpha.json c884e495). Certificate, endpoint report, ledger and plan.
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.
Data Layer v2.2.5 release packaging after the 2026-10-20 production maintenance window (coordinator-run, owner GO).
Certificate status: PASS. No post-hoc decision is used. The earlier P1 proposal is superseded: the owner chose to measure instead.
G5 D3 (b): concurrent hot-read latency
scripts/v225_query_hot_read_ab.py, PREREG v20bba6385).DR warmup byte compare
upgrade/evidence/releases/v2.2.5/query-ab-20261020/byte-compare.json, sha25641ebcc3c575e3fb1cb37ee069cd5eff156bb0ed7ef0dd4b0b5becc51e22ae7e4.Run conditions
foreign.jsonl.Also in this PR
kn_versioned_compose.pyparity now has a cpus tolerance. R2 re-run PASS: 863 checks, 0 problems.SHA256SUMS).SDK 2.4.1 wheel
9f79e032is unchanged. The release.yml checks were simulated locally and pass. Rust digests and writer 2deb90b0 are unchanged. This PR makes no runtime change.