›Navigation
Closing reconciliation

This is not a campaign. It is the single read-only pantry every orthogonality probe reads from, holding the locked data scope, the intake registries and the slice-rotation engine for crypto and forex side by side.

What it measured
QuantityValueMeaning
Artifact pages18 (14 crypto + 4 forex)the whole substrate, split by asset class
Addressable cells62 crypto / 19 forex (symbol x threshold)the measurement grid
Symbol panels16 crypto / 4 forex (EURUSD, GBPUSD, XAGUSD, XAUUSD)scope of the locked substrate
Robustness map441 cellsthe published slicing-robustness grid
Iterations0no firings — it is read substrate, not a campaign
What it produced
Carries forward

Nothing pending. It is terminal by construction, not by conclusion: it holds substrate, never verdicts. It changes only when a campaign extends the scope, via the documented scope-expansion path in pre-spec.md.

Why it is closed

Substrate, not a loop — kept in the accounting anyway so it cannot sit outside it. No iteration pages, no contract, no stop rule. Settled here means stable and nothing pending, NOT that a campaign concluded.

Lifecycle status is process state, not a judgement of the findings. Results are stated as numbers with their uncertainty. Generated between CLOSING-RECONCILIATION markers — regenerate rather than edit.

Dashboard › Three-Axis Probes › Shared Artifacts

substrate · one folder · crypto + forex

🗄 Shared Artifacts

The single substrate folder every orthogonality probe reads from — the locked data scope, the registries, and the rotation engine — now consolidated in one place and split by asset class so you never have to look in two folders.

In plain English. One shared pantry for the research. The crypto and forex campaigns each have their own shelf, but it's the same pantry: one read-only data scope, one rotation engine (byte-identical across both), and one set of intake/quality rules. Pick your asset class below.

🪙 Crypto Shared Artifacts

The crypto-side substrate (BTCUSD + the multi-symbol panel), read-only against opendeviationbar_cache.open_deviation_bars. Source: findings/evolution/shared_data/.

Overview — the central data layer every test reads from Why the shared data pool exists Locked data scope — the pre-registration of what the probes may read How the data is sliced — and why The 441-cell robustness map The regime-slicing robustness fix — test in the storms, not the calm The auto-rotation coverage engine — every market condition The orthogonality probe — does a new feature tell us anything new? The S1 pin-invariant spec (GCM + O-information) The candidate intake standard — one ledger, one preflight Per-cell data-quality findings manifest.json — the catalogue card for every slice The forex data-availability probe (crypto-side check) Scope-expansion options for the future

💱 Forex Shared Artifacts

The forex-side substrate (EURUSD / GBPUSD / XAGUSD / XAUUSD), read-only against fxview_cache.forex_bars. Source: mql5/findings/forex_shared_data/ — the byte-identical sibling of the crypto rotation engine, invoked with --asset forex.

Overview — the forex shared data layer The slice rotation mechanism — coverage-ledger orthogonality engine The three-axis gate probes (forex) — agnostic · parameterless · orthogonality The Forex candidate intake standard — one ledger, one preflight

The locked substrate (shared by both)

dimensioncryptoforex
Database · tableopendeviationbar_cache · open_deviation_barsfxview_cache · forex_bars
Symbols16-symbol panel (BTC/ETH/…)EURUSD · GBPUSD · XAGUSD · XAUUSD
Thresholds (dbps)100 / 250 / 500 / 750 (750 = spearman-only)EUR 1–50; others 5–50
(symbol, threshold) cells6219
Enginerotating_slice_orthogonality_probe.py — one byte-identical engine, --asset crypto / --asset forex
Access contractREAD-ONLY ClickHouse · real data only · no fixtures · runs on bigblack
Non-verdict. This folder holds the substrate (the data scope + the mechanism), never the per-campaign verdicts. Each campaign's conclusions live in its own dated folder under the crypto- or forex-candidates hub.