Feed & Execution
Publication cadence, coordination structure, staleness distributions and spread regimes — measured on your own broker feed.
I went looking for honest, instrumented trading tools. I couldn't buy them, so I built them.
I build measurement instruments for the claims traders make about feeds, backtests, desk risk and chart vocabulary. The method is public before any instrument runs, every artefact is content-hashed, and each instrument states in writing what it does not establish. Zero performance claims — not in the copy, not in the examples, not ever. No firm is measured or published here, and nothing on this site is for sale yet.
Hadal (/ˈheɪ.dəl/) — from the hadal zone, the ocean's deepest realm.
The strip below is where a measured fact stands beside the hash of the artefact it was computed from. Not one of them exists yet — so it carries the three commitments instead: what will be published, and the page that will carry it. Each seal below becomes that artefact's hash on the day it lands, and not one day earlier.
The feed battery, written down before it is run
Every dimension, threshold and exclusion rule of the fidelity battery, fixed and hashed before any feed is measured — so the auditing method cannot be tuned afterwards to flatter a result.
sha256 NOT YET PUBLISHED
Feed & Execution receipt pageAn overfit audit published with what it audited
The probability of backtest overfitting, the deflated Sharpe and the effective number of independent trials — each published beside the backtest they were computed from and the code version that produced them.
sha256 NOT YET PUBLISHED
Backtest Honesty receipt pageThe first feed receipt, re-derivable by a stranger
The battery run on a synthetic stream carrying a planted defect, refusing that defect by name, and published with the stream, the code version and the digests so a stranger can rerun it. Not a firm: the battery measures a feed the reader holds, and this house publishes no counterparty.
sha256 NOT YET PUBLISHED
Feed & Execution receipt page"I searched for it, couldn't buy it, and built it — module by module. First-frustrated-customer validation."
The category — honest, instrumented trading tooling — doesn't exist because the market's incumbents discovered that promises sell better than measurements and stopped trying.
The addressable customer is the burned-serious minority — traders who want an instrument, not a lottery ticket. They are a small fraction of the market and the only fraction that retains.
Each instrument earns its place by solving a problem nobody else will touch. I don't resell external analytics or white-label third-party models — nothing here is someone else's engine with my name on it, and whatever has been built was built by me. What is running, what is on hold and what is still a design differs across the catalogue, and each instrument's own page states which it is.
The mathematics is mostly the field's own: the probability of backtest overfitting and the deflated Sharpe ratio are López de Prado's, the annualisation correction is Lo's, HAR-RV is Corsi's. Where I arrived somewhere the literature had already reached, I say so. Where I got there on my own, I publish the reasoning so you can check that too. What makes any of it worth paying for is the part nobody does — guarding the assumptions, refusing to render a number when they fail, and publishing the method so both can be checked. The field is not short of mathematics. It is short of anyone enforcing the conditions the mathematics requires.
Publication cadence, coordination structure, staleness distributions and spread regimes — measured on your own broker feed.
PBO, deflated Sharpe, effective-N, collapse ratio and dual-denominator FDR, run against a backtest you upload.
Drawdown-halt monitoring, sizing grids, risk-of-ruin surfaces and correlation-adjusted heat for funded-account candidates.
Dealer positioning, volatility and liquidity regimes under a never-repaint constraint, and the propagation structure of forced-flow cascades — terrain described, never forecast.
Provenance-grade data ingestion, epistemic discipline for research, and the agent-governance constitution that caught a fabricating system.
A quant cockpit where every displayed number carries its git SHA and the sha256 of its source artefact — or the panel refuses to render.
Dashboards traced number-by-number to their computation and CI gates drilled until they demonstrate they can fail — FABRICATED is a first-class finding.
Instruments, suites and defined terms are read from the published catalogue when this page is built. The zero is pinned by policy. The one is a published post-mortem. Nothing on this plate describes a result.
Those are instruments you run yourself. If you would rather one measurement was run for you — on your own statement, by me, ending in a written report — that is the assay desk. The whole menu and every anticipated price are published there. Intake is not open yet, and the page says so before it lists a single assay.
The tick panel here is a simulation of what a measured broker feed looks like: every tick timestamped, every gap visible, every pattern named. A real measurement publishes with its raw, content-hashed artefact — and the feed it measures is one the reader holds, never a firm.
SIMULATED Synthetic ticks drawn in your browser from a fixed pattern. No broker, no feed, no measurement — the panel shows the shape an instrument reads, never a result it produced.
"What does your broker's feed actually do when you measure it instead of trusting it?"
— The founding question
A receipt is cheap to publish and expensive to fake. That asymmetry is the whole strategy — and it is legible to exactly the customers I want.
04 published 01 in force, unpublished 02 not yet published
Agent-governance constitution
Every agent session that touches this product is bound by a written constitution: no fabrication, no self-attestation, receipts or it did not happen.
Agent fabrication caught
In July 2026 an agent working on my core engine fabricated results and declared the system "COMPLETE" when nothing worked. I caught it, documented it, and published the post-mortem.
Every term defined before it is used
The vocabulary a measurement depends on is published as a glossary, so a reader can check what a word means here before deciding whether a claim built on it is worth anything.
Fabrication fails the build
Placeholder hashes, invented provenance and unverifiable dataset claims are build failures. The site cannot ship a number that does not trace to a real artefact.
Feed fidelity battery
The battery’s definitions and thresholds are written down and hashed before any feed is measured, so the method cannot be tuned to flatter a result.
Kills publish with registrations
Hypotheses that fail publish with the same visibility as the ones that survive. Four engine-registry kills already stand in the ledger, with effect sizes, intervals and artefact digests; the site’s own battery has registered nothing yet, and its first entries arrive with its first pre-registration.
Out-of-sample verification
In-sample calibration is not evidence. Every measurement faces out-of-sample verification before publication — no exceptions, no post-hoc adjustments.
Both end at the same rule: a measurement of your own artefact, with its method public before it runs, and no firm published by this house.
Start with the free calculators and the glossary, then read a method guide on the question you actually have. When you want a measurement of your own feed, the Feed Fidelity Assay runs the battery on a quote log you export, and the report is yours.
Check the sample size your edge needs before you trust it, then put the backtest and the desk rules under the instruments built to break them. The Overfit Assay runs the published overfitting method on a backtest you send; the Backtest Honesty and Desk Discipline suites are specified instrument by instrument.
"I caught my own system fabricating results. Then I built the constitution that makes it impossible."
The core asset is not any single module. It is the discipline culture — mandatory internal structures, receipts, pre-registration, retraction with original errors preserved verbatim, the register that caught a fabricating agent and two honest ones compressing.
Receipts promise nothing about returns, which is precisely why they are safe to publish and hard to counterfeit. Filtering is the feature — these instruments tell you things you may not want to hear, and that selects the buyer. What survives the funnel retains.
Join the waitlist for early access, first look at pricing, and build updates. No spam — just signal.
Standing policy
The same statement stands in the footer of every page.Terms Privacy