No feature is ported yet. Bootstrap reuses the heavy infrastructure prior runs already shipped (the frozen real fixture, the SOTA harness, the cohort-registry pattern) and adds only the pieces unique to this run: a freshly minted v3 cohort, a numpy-pinned SSoT/tolerance doc for the gap-aware substrate, and the three dashboard placeholders. PR1 is the base of the stack.
Status: PR1 #124 OPEN ยท feat/odb-ext/rqw-crex-bootstrap ยท base=main โ first in the squash-merge order.
orthogonal_extension_cohort_v3.rs +
forex_orthogonal_extension_v3_ordered_names_list.json โ a brand-new sibling registry, kept strictly separate from v2..sha256 sidecar.
4 anchor-pin tests recompute the SHA + HARD-HALT on drift. The anchor was re-locked after the #7 witness correction (โ0.605 โ โ0.5838646869163802).None-stubs โ so test_schema_contract stays green; no BarRow /
COLUMN_NAMES / schema.sql change until the feature PRs land.multislice_orthogonality_probe.py with the pin numpy 2.5.0 / scipy 1.18.0 (uv --python 3.14);
tolerance is VALUE-within-1e-9.HYGIENE_DEBT.md): clippy 1.95, git-hooks worktree-compat, meta-test GIT_DIR.Both features measure the shape of the recent returns, so they must agree on exactly which returns to look at.
The recipe is transcribed from multislice_orthogonality_probe.py (the k_crex / k_rqw paths) โ
not the discovery harness, whose sign-dropped, no-gap-null variant would diverge silently.
logret = diff(log(close)).NULL for that bar.This is the no-silent-drift discipline: we port the pinned convention exactly rather than "improve" it.
Parity is verified VALUE-within-1e-9 against a pinned numpy oracle (numpy 2.5.0 / scipy 1.18.0), not a byte-sha of a frozen blob.
1/std.
A reviewer who z-scores the returns "to normalize" would silently break parity. The witness asserts that z-scoring FAILS โ locking the raw-input convention.XAUUSD@25, open_time_us = 1768179397541000 โ RQW = โ0.5838646869163802 (binding, frozen fixture).
Any sign-drop regresses this. Note: the contract's โ0.605 was a stale full-production figure that no numpy quantile method reproduces โ the anchor was re-locked to the binding value.
The kernel reuses the already-shipped RollingPercentile HF7 primitive rather than re-implementing octile interpolation.Both features cleared the KEEP test on 2026-06-12-xi-batch34-crossed-verdict.md and are not re-run here:
#38 ฮพ 0.160 / 0.395 (close) โ independent; #7 ฮพ 0.135 / 0.260 โ independent.
This run is production wiring, not discovery.
โ back to the running dashboard ยท next: #38 cumulative_residual_extropy