module · research·lab notebook · falsifiable·we retract in public
Hypotheses, with falsifiers attached.
Short, dated notes from the desk. Each one comes with the specific observation that would force us to walk it back. Some get shipped into tools and playbooks. Some get retracted — and we keep those visible too.
// methodology · how a note moves through the pipe
Four states. No quiet deletes.
Every research note starts as a draft and ends in one of three places: shipped into a tool or chapter, kept active with a live falsifier, or retracted in public.
step 01
Pose a hypothesis
Frame the edge as a specific, dated claim. “X happens Y% of the time when Z.” Vague claims don’t make it onto the notebook.
step 02
Attach a falsifier
Define the observation that would force us to walk it back. If we can’t name one, the note is rejected on intake.
step 03
Walk-forward, in public
Promote a draft to active once the in-sample work is done. Active notes run live for a defined window with the falsifier on the wall.
step 04
Ship, hold, or retract
Notes that survive get shipped into a tool, playbook, or chapter. Notes that fail get marked retracted and stay visible — we don’t quietly delete.
// index · all notes · status × track
The whole notebook. Newest first.
Filter by status or track. Retracted notes stay in the index — we don't quietly delete what didn't hold up.
status
track
shippedtooling·rn-008
Tool latency under 250ms changes user behavior, not just satisfaction
On the desk, dropping decision-surface latency below ~250ms shifted users from re-pulling charts to acting on first-render data. Above ~400ms, users second-guess the tool. Below ~150ms, returns flatten — diminishing utility.
falsifier
If session telemetry shows no behavior shift across the 150–400ms band over a 4-week sample, the engineering target gets relaxed.
activerisk·rn-007
Regime-aware sizing beats fixed-fractional in walk-forward
A simple regime classifier (VIX bucket × value-area context) feeding a multiplier into fixed-fractional sizing beat the unmodified 1% rule on Sharpe across an 18-month walk-forward, primarily by under-sizing during chop.
falsifier
If forward Sharpe improvement compresses to < 0.10 over 60 sessions, the multiplier gets shipped as opt-in only, not default.
draftexecution·rn-006
VWAP+1σ band as overshoot filter for mean-reversion entries
Adding a 1-sigma VWAP band as a hard filter on counter-trend entries cut sample size by ~40% and lifted average expectancy meaningfully across two ticker baskets. Tradeoff: fewer trades, fatter average outcome.
falsifier
If forward sample expectancy regresses to within 0.05R of the unfiltered version over 200 trades, the filter is dropped.
activepsychology·rn-005
Journaling within 90 minutes of close correlates with faster mistake correction
Members who journal within 90 minutes of session close show measurable mistake-class drop-off in 3–4 weeks. Members who batch-journal weekly take 8–10 weeks to reach the same delta. Same template, same prompts.
falsifier
If a 12-week cohort shows no statistically meaningful difference at p < 0.10, the recommendation gets softened to optional cadence.
activemicrostructure·rn-004
TTM Squeeze release direction follows higher-timeframe trend ~70% of the time
On 5-minute charts, when the daily trend is up and a TTM Squeeze release occurs, the resolution prints upward in ~7 of 10 cases over a 90-day rolling window. The asymmetry collapses near macro events and inside the 60 minutes pre-FOMC.
falsifier
If the alignment falls below 60% for 30 consecutive sessions outside event windows, demote to confirmation-only signal.
shippedrisk·rn-003
Daily loss caps reduce week-over-week variance more than position sizing tweaks
Replaying 2024–2025 trades with a hard 3% daily loss cap and an unchanged position-sizing model cut weekly P&L variance more than halving size with no cap. Caps win on tail control; sizing wins on average return.
falsifier
If a regime appears where the cap clips materially profitable revenge-trade recoveries (top decile day > +6R after a -3% morning), revisit.
shippedexecution·rn-002
Opening-range breakout R:R degrades after 09:55 ET
Opening-range breakouts entered between 09:30 and 09:50 ET hit a 2R target ~38% of the time. Breakouts entered after 09:55 ET hit 2R ~21% of the time across the same sample, even when triggers look mechanically similar.
falsifier
If the post-09:55 cohort recovers to ≥ 30% 2R hit-rate over 60 sessions, the cutoff is widened or removed.
shippedmicrostructure·rn-001
Volume Profile POC reverts in balanced regimes; trends in imbalanced
Across two years of intraday ES data, retests of the developing POC mean-revert ~63% of the time when VIX < 18 and the prior session closed inside its value area, and trend-continue at a similar rate when VIX ≥ 22 and price closes outside value.
falsifier
If 12 weeks of forward data show < 55% directional bias in either regime bucket, the heuristic gets demoted to discretionary input only.
retractedregime·rn-009
Earnings drift no longer pays in single-name large caps for our cohort
Post-earnings drift trades on large-cap names underperformed expectations by a wide margin in the 2024–2025 sample. We retracted this as a primary edge in member playbooks; remaining mentions are explicitly historical.
falsifier
Re-instate as an active edge only if 2 consecutive 6-month windows show ≥ 0.30R median drift on filtered candidates.
// open questions · what we don’t know yet
What we’re still not sure about.
A short list of questions the desk hasn't answered. If you have data, opinions, or a way to falsify these faster, we'd like to hear about it.
open · q01
Does TTM-Squeeze direction-alignment hold outside event windows?
Current sample is 90 days. We want 240 sessions and explicit pre-FOMC / pre-CPI carve-outs before promoting to a primary signal.
open · q02
Is journaling cadence a cause or a correlate?
Members who journal within 90 minutes of close also tend to size smaller. We need to disentangle which lever is doing the work.
open · q03
Where does VWAP+1σ filtering break down?
The lift looks real on two ticker baskets. The honest answer is we haven’t stress-tested it on low-liquidity names where VWAP itself is noisy.
open · q04
Latency → behavior — is the threshold platform-dependent?
We saw the 250ms inflection on the desk web client. Mobile and desktop NinjaTrader users may have a different sweet spot. Open.
// next · contribute or read on
Got data? Got a falsifier?
If you've replicated, broken, or extended one of these notes, we want to see it. If you'd rather just keep reading, the long-form blog and the open primitives are next door.