Overview — the forex shared data layer

A central, reusable definition of the slice-rotation mechanism the forex orthogonal-feature campaign reads from — the forex-side sibling of the crypto shared_data hub. One byte-identical engine lives in both repos, invoked with --asset forex here and --asset crypto there.

In plain English. The same "shared pantry" idea as the crypto side, for forex. Instead of every forex study re-defining and re-fetching its own slices of EURUSD/GBPUSD/XAGUSD/XAUUSD data, this folder defines the data scope and the testing mechanism once — read-only, real bars only — so every forex orthogonality study draws from the identical foundation.

What this folder is

The forex shared data layer holds the rotation engine (the canonical, reusable probe that reads each stratum directly from ClickHouse and measures orthogonality + cross-candidate redundancy), the mechanism spoke (the rotation contract + flowchart), and a machine-readable manifest. It is non-audit: it holds the substrate + provenance, never the per-campaign verdicts.

PITSLARP. The rotation engine advances no future data, no silent drift, no unexplained divergence: kernels only ever see causal trailing windows; coverage is provable from the ledger (not hoped-for from random draws); infeasible strata carry an explicit reason. See the rotation mechanism.

Current scope

substrate	symbols	thresholds (dbps)	(symbol, threshold) cells
Forex — `fxview_cache.forex_bars`	EURUSD, GBPUSD, XAGUSD, XAUUSD	EUR 1–50; others 5–50	19
Crypto — `opendeviationbar_cache.open_deviation_bars` (sibling hub)	16-symbol panel	100–750 (750 = spearman-only)	62

Read-only ClickHouse · real data only · no fixtures. Every bar a kernel sees is a real production bar.
Kernel registry SSoT: mql5/findings/audits/2026-06-03-forex-parameterless-orthogonal-candidate-discovery/multislice_orthogonality_probe.py (the 47 campaign kernels), resolved via KERNEL_PROBE_DIR — the engine imports these kernels rather than duplicating them, so the same 47 candidate kernels run on both forex and crypto.

What's in the folder

file	purpose
README.md (this page)	Hub — start here.
ROTATION-MECHANISM.md	The rotation contract: stratum grid, value-row stratification, coverage ledger, fused ρ+ξ, cross-candidate LOO-R², flowchart, validation evidence.
probe scripts	The engine + the three-axis gate probes (agnostic / parameterless / orthogonality), vendored byte-for-byte from the crypto sibling.
`manifest.json`	Machine-readable index: engine path, asset configs, kernel-registry SSoT, run recipes.

Why a separate forex folder (not moving the campaign probe)

The campaign's multislice_orthogonality_probe.py stays in its discovery-campaign audit folder — it is the kernel-registry SSoT referenced by the harness, queue, and merged PRs. The rotation engine imports those kernels (via KERNEL_PROBE_DIR) rather than duplicating them, so the same 47 candidate kernels run on both forex and crypto without drift.

Forex Shared Artifacts · finding · source: mql5/findings/forex_shared_data/README.md · ← back to Shared Artifacts