DOMAIN / 02 — RESEARCH
8 ENTRIES · 4 VERIFIED · 2 ONGOING
I investigate how markets, quantitative methods, data and software systems interact. Every entry follows the same spine — question, hypothesis, method, evidence, result, limitation and conclusion — including the ones still in progress and the ones whose answer is a limitation rather than a finding.
GAUSSIAN PROBABILITY MANIFOLD · 3D DENSITY DISTRIBUTION
FEATURED INVESTIGATION
Lookahead Bias as an Engineering Failure, Not a Statistical One
Where does lookahead bias actually enter quantitative pipelines — and can it be prevented structurally?
METHOD CHAIN — VERIFIED AT THE TERMINAL NODE
EVIDENCE SOURCE — DATA REPLAY
METHOD
Audit of ingestion, normalization, resampling and join paths; adversarial tests that attempt to extract future information through every access pattern.
EVIDENCE
Adversarial test suite in quant-market-data-replay — deliberate future-information extraction attempts fail against point-in-time reads.
RESULT
Point-in-time safe reads enforced in the data layer prevent lookahead by construction. Consumers cannot opt out.
LIMITATION
Consumer code can still misuse resampled windows above the data layer; the guarantee covers access, not strategy logic.
CONCLUSION
Information-flow correctness belongs in infrastructure. Researcher discipline is a fragile control; structural guarantees are not.
HOW ENTRIES ARE STRUCTURED
Each entry carries one of three statuses. VERIFIED — reproduced against the artifact. DOCUMENTED — written up from real work, with limits stated. ONGOING — the question is registered and the answer does not exist yet.
Every entry states its question, method, evidence, result and limitation — including entries still in progress, which are marked as such and published alongside completed work. The visual beside each entry is a generative diagram of its category, labelled illustrative.
THE ARCHIVE
EXPAND ANY ENTRY TO READ THE FULL CHAIN
TOPIC INDEX
8 OF 8 ENTRIES
01Lookahead Bias as an Engineering Failure, Not a Statistical OneDATA INTEGRITYVERIFIED
QUESTION
Where does lookahead bias actually enter quantitative pipelines — and can it be prevented structurally?
HYPOTHESIS
Lookahead bias enters through data-layer engineering decisions, not strategy logic, and can be eliminated by point-in-time access semantics.
METHOD
Audit of ingestion, normalization, resampling and join paths; adversarial tests that attempt to extract future information through every access pattern.
EVIDENCE
Adversarial test suite in quant-market-data-replay — deliberate future-information extraction attempts fail against point-in-time reads.
RESULT
Point-in-time safe reads enforced in the data layer prevent lookahead by construction. Consumers cannot opt out.
LIMITATION
Consumer code can still misuse resampled windows above the data layer; the guarantee covers access, not strategy logic.
CONCLUSION
Information-flow correctness belongs in infrastructure. Researcher discipline is a fragile control; structural guarantees are not.
ILLUSTRATIVE — GENERATIVE DIAGRAM FOR DATA INTEGRITY. NOT A MEASUREMENT.
02Reproducibility as an Overfitting DefenseBACKTESTINGDOCUMENTED
QUESTION
Does determinism in the backtest harness measurably reduce false-positive strategies?
HYPOTHESIS
If identical inputs produce identical outputs, parameters tuned to noise become identifiable as unstable rather than performant.
METHOD
Deterministic replay of the same strategy configuration across repeated runs; comparison of results under perturbed data ordering with fixed tie-breaking rules.
EVIDENCE
Apex Quant Engine backtests reproduce byte-identically from raw bars to equity curve; 5,867-trade master-fund runs regenerate exactly.
RESULT
Deterministic harnesses make an entire class of irreproducible 'results' impossible to mistake for findings.
LIMITATION
Determinism addresses reproducibility, not statistical overfitting to a single historical window — that requires out-of-sample discipline.
CONCLUSION
Determinism is necessary but not sufficient: it removes accidental false positives so real statistical work can begin.
ILLUSTRATIVE — GENERATIVE DIAGRAM FOR BACKTESTING. NOT A MEASUREMENT.
EVIDENCE SOURCE — APEX
COVERED IN CAPABILITIES — QUANTITATIVE RESEARCH · BACKTESTING · ALGORITHMS & DATA STRUCTURES
OPEN FULL ENTRY →03Exact Decimal Arithmetic in Market DataQUANTITATIVE METHODSVERIFIED
QUESTION
Where does binary floating-point representation corrupt market data, and does it matter?
HYPOTHESIS
Float representation of prices and monetary values accumulates representation error that surfaces in aggregates, joins and risk calculations.
METHOD
Comparison of ingestion-storage-replay paths under exact decimal arithmetic versus IEEE-754 floats, tracking divergence through aggregation.
EVIDENCE
quant-market-data-replay stores and replays with exact decimal arithmetic across the full pipeline.
RESULT
Representation drift is eliminated as a failure mode; joins and aggregates behave identically across runs.
LIMITATION
Exact arithmetic trades throughput for correctness — appropriate at research speeds, costly at HFT scale.
CONCLUSION
In research infrastructure, correctness of representation is cheap insurance against an invisible failure class.
ILLUSTRATIVE — GENERATIVE DIAGRAM FOR QUANTITATIVE METHODS. NOT A MEASUREMENT.
EVIDENCE SOURCE — DATA REPLAY
COVERED IN CAPABILITIES — MARKET DATA · DATA INFRASTRUCTURE · SYSTEMS PROGRAMMING & MEMORY
OPEN FULL ENTRY →04Position Sizing Before AdmissionRISKDOCUMENTED
QUESTION
What changes when risk controls run before order construction rather than as post-trade reconciliation?
HYPOTHESIS
Structural pre-trade controls — risk cap, R:R floor, cost-budget filter — change the population of admitted trades, not just their outcomes.
METHOD
Pipeline architecture with controls as gates: position size derives from stop distance and risk cap; setups failing the 1:4 R:R floor or cost budget never reach execution.
EVIDENCE
automated_trading_os implements 1% per-trade risk cap, minimum 1:4 R:R, fee/slippage modelling, cost-budget filtering, profit lock and giveback limit.
RESULT
The admitted-trade population is defined by rules rather than discretion; every admitted trade satisfies all structural constraints by construction.
LIMITATION
Ablation studies quantifying each control's individual contribution are ongoing.
CONCLUSION
Order-of-operations matters: controls applied after sizing are advice; controls applied before are physics.
ILLUSTRATIVE — GENERATIVE DIAGRAM FOR RISK. NOT A MEASUREMENT.
05Multi-Timeframe Agreement WindowsSTRATEGY RESEARCHONGOING
QUESTION
What is the character of windows where higher, mid and lower timeframes agree?
HYPOTHESIS
One-way information flow — LTF triggers inside MTF structure within HTF direction — produces a distinct, analyzable population of setups.
METHOD
Layered pipeline analysis: HTF establishes directional context, MTF maps structure, LTF times entries; agreement windows extracted and studied.
EVIDENCE
automated_trading_os pipeline with explicit stage contracts; timeframe explorer instrument in development.
RESULT
In progress — agreement-window extraction across instrument history under construction.
LIMITATION
Results not yet published; the pipeline exists, the study is ongoing.
CONCLUSION
Preliminary: enforcing one-way flow eliminates a class of contradictory signals by construction.
ILLUSTRATIVE — GENERATIVE DIAGRAM FOR STRATEGY RESEARCH. NOT A MEASUREMENT.
06Regime Dependence in Strategy PopulationsMARKET STRUCTUREONGOING
QUESTION
How much of a multi-strategy portfolio's simulated performance is regime selection rather than strategy skill?
HYPOTHESIS
Strategy performance clusters by market regime more strongly than by strategy family — allocation across regimes matters more than strategy count.
METHOD
Decomposition of master-fund backtest results by regime classification across the 11.9M+ bar history.
EVIDENCE
Apex master-fund backtest artifacts: +570.18% net simulated ROI across 5,867 completed backtest trades.
RESULT
In progress — regime attribution analysis under construction.
LIMITATION
Regime classification itself is a modeling choice; attribution results will depend on the classifier.
CONCLUSION
Pending — the question is registered and the data exists; the attribution study is next.
ILLUSTRATIVE — GENERATIVE DIAGRAM FOR MARKET STRUCTURE. NOT A MEASUREMENT.
07Deterministic Tie-Breaking Under Nanosecond ClocksDATA INTEGRITYVERIFIED
QUESTION
How should equal-timestamp market events be ordered so replay is reproducible?
HYPOTHESIS
Without deterministic tie-breaking, equal-timestamp events order arbitrarily across runs, making replay irreproducible.
METHOD
Reorder stage with explicit deterministic tie-breaking rules; repeated replay verification that output is byte-identical.
EVIDENCE
quant-market-data-replay determinism verification: identical replays across runs including tie-breaking.
RESULT
Replay determinism holds under nanosecond timestamps with equal-timestamp events.
LIMITATION
Tie-breaking rules encode an ordering assumption — an approximation of true within-timestamp causality.
CONCLUSION
Determinism requires explicit choices at every ambiguity. Defaulting to insertion order is a choice; making it deliberate is the difference.
ILLUSTRATIVE — GENERATIVE DIAGRAM FOR DATA INTEGRITY. NOT A MEASUREMENT.
EVIDENCE SOURCE — DATA REPLAY
OPEN FULL ENTRY →08Promotion Gates for Strategy ResearchCOMPUTATIONAL FINANCEVERIFIED
QUESTION
What evidence threshold should graduate a strategy from research to deployment consideration?
HYPOTHESIS
A governance gate — verified artifacts, reproducible runs, documented limitations — raises the evidentiary floor of everything promoted.
METHOD
QRSIP workflow: hypothesis → experiment → verification → artifact → report → promotion, with 352 tests on deterministic fixtures and CI security validation.
EVIDENCE
QRSIP test suite and promotion-gate integrity tests; alpha-stage platform operational for the core workflow.
RESULT
Strategies cannot pass promotion without verified evidence; the gate is structural.
LIMITATION
The gate verifies process integrity, not edge — a well-governed strategy can still be unprofitable.
CONCLUSION
Governance converts research from anecdote to evidence. It is the floor, not the ceiling.
ILLUSTRATIVE — GENERATIVE DIAGRAM FOR COMPUTATIONAL FINANCE. NOT A MEASUREMENT.
EVIDENCE SOURCE — QRSIP
OPEN FULL ENTRY →WHERE THE EVIDENCE COMES FROM
BUILT SYSTEMS
Most entries here exist because a system was built that could answer the question. The builds are the evidence source; the research is what the evidence turned out to mean.
NEXT
READ THE WRITING OR RUN THE INSTRUMENTS