Markets are the same class of problem as the systems I build everywhere else: noisy, adversarial, latency-bound, full of feedback loops and regime changes. The mistake most people make is judging themselves by outcomes. But a single outcome tells you almost nothing, because a good decision can lose and a bad one can win. The only thing worth optimizing is the quality of the decision and whether it survives under pressure.
So I built tooling around that idea instead of around PnL.
The thesis
Insight is not enough. A system is only real when it stays executable under pressure. Recognizing a pattern is the easy part. Executing it the same way at size, on a bad day, after three losses, is the actual skill, and that is a systems problem, not a willpower problem.
What it does
- Market-structure research. Liquidity, ICT and Smart Money Concepts, and regime classification across MNQ and MES futures, used to define what a valid setup even is.
- Execution analytics. Every trade is categorized by setup, conviction, and error type, so I can separate "good process, bad luck" from "bad process." The dashboard prioritizes decision quality over raw returns.
- Risk as system rules. Position and risk constraints are enforced as rules the system applies, not as intentions I have to remember mid-trade.
- Pine Script tooling. Indicators and alerts that detect setups and track process, so the discipline is in the tools, not in my mood.
- Decision journal. Structured logging of context, thesis, and outcome for every trade, which is the raw data the whole feedback loop runs on.
Why this connects to the rest of my work
This is the same instinct as KOTA and Archon: take an environment full of uncertainty and build the structure that makes good behavior the default. A voice agent that must hold up at peak hour, an agent framework that must stay inspectable, and a trading process that must stay executable under stress are the same problem wearing different clothes.
I am not going to post return figures here. That is not the point, and unverified performance claims are noise. The point is the architecture of deciding well when you cannot remove the uncertainty.
[If you want specifics on the regime classification or the execution-scoring model, ask.]