A Trading System in Three Layers: Measure, Decide, Accounteric

In the last post I argued that indicator, strategy, and alpha are not three words for the same thing but three different layers with three different jobs: indicators measure, strategies decide, alpha is what survives honest accounting. Several readers asked the natural follow-up: fine as a taxonomy — but what does a trading system built that way actually look like?

This post is the answer. The claim is stronger than "layers are a nice way to think." The claim is that the layering is an architecture, that each layer has a concrete set of components and a rule it must never break, and that the rate at which your whole operation finds real edges depends less on the brilliance of any one idea than on how cleanly the layers are separated. Edges are not found; they are farmed — and the three layers are the farm.

Layer 1: the measurement layer

What it consists of: the data pipeline (bars at every timeframe you consult, gap-checked and freshness-checked), and the indicator library — every instrument computed on every bar of every series, all the time, whether or not anything downstream is listening. Moving averages, bands, oscillators, trailing stops, plus whatever house instruments you have built. In our system this layer runs from the 15-minute series up through hourly, daily, weekly and monthly, for every symbol, continuously.

Its function: report events. Never judge them.

The rule it must never break: an indicator is not allowed to know whether its event worked out. The moment you let outcome-awareness leak into an instrument — tuning it to "avoid false signals," suppressing a crossover because the last three lost — you have destroyed the layer boundary, and everything downstream is now measuring a mixture of the market and your opinions. The false signals are not a defect. They are the raw material the next layer exists to judge, and the layer after that exists to count.

Because the components are boring, the failure modes at this layer are boring too — and that is exactly what makes them dangerous. Two dominate:

• Silently wrong. An indicator implementation that drifts from its canonical definition still draws a plausible line on the chart. The last post covered this one: verify each instrument against the reference once, like calibrating a thermometer, then leave it alone.
• Silently stale. This is the system-level version, and it bites harder. We recently discovered that a monthly-timeframe series on one of our servers had quietly stopped updating almost a year earlier. Nothing crashed. Nothing warned. Every policy that consulted the monthly level was voting with a ten-month-old opinion — and one class of policies that required monthly agreement had been silently dead the whole time, because the frozen bar happened to read "trending," a state those policies could never align with. A measurement layer needs freshness monitoring the way a lab needs calibration stickers: every series carries an implicit "last verified current" date, and a policy consulting a stale series should be told, not humoured.

Where a trader should focus here: correctness and coverage, once each, plus a standing freshness check. This layer rewards diligence, not creativity. If you find yourself spending your evenings retuning indicator parameters, you are farming the wrong field.

Layer 2: the decision layer

What it consists of: a portfolio of small policies — strategies — each one a single hypothesis about how to map measurements to actions. Each policy owns its entry conditions, its exit doctrine, its stop placement, and its right of refusal. Critically, each policy is small: one idea, one file, one name in the ledger.

Its function: judgment. This is the only layer where an opinion about the market is allowed to exist.

The rule it must never break: a policy consumes measurements; it never re-measures, and it never grades its own homework. Timeframes have a contract — the higher timeframes decide direction and regime, the lower timeframes time the entry — and a policy that lets a 15-minute signal overrule a daily trend has broken it.

The payoff of keeping policies small and separate is that the same instruments can serve contradictory hypotheses simultaneously, and the system does not have to pick a winner in advance. A worked example from our own book, using nothing more exotic than Bollinger Bands and Parabolic SAR:

Our workhorse band policy trades the cycle a band system sees: expansion, trend, exhaustion, reversion. It is structurally good at that shape — and structurally blind to one specific, expensive shape: the failed breakdown that V-reverses and melts up. Price breaks the lower band, looks like a crash, snaps back through the middle band within a few bars, and then trends for months without ever offering the pullback the policy waits for. We measured thousands of these events, and the numbers were blunt: at the moment the band policy would first consider the recovered trend tradeable, price sat a couple of ATRs beyond anything it would chase, and a quarter of the resulting runs never revisited the middle band at all. No parameter setting fixes that. It is not a tuning problem; it is the wrong hypothesis for that shape.

The instructive part is what the fix was not. We did not touch the bands, and we did not bolt a "melt-up exception" onto the band policy — that would have been two hypotheses wearing one name, unjudgeable at the accounting layer. Instead: a different instrument already in the measurement layer (Parabolic SAR, which flips on the recovery bar essentially every time, precisely because it judges nothing) and a new, separate policy that consumes the same measurements at higher timeframes and rides the calm drift the band cycle reads as "nothing happening." Two policies, one instrument bench, each individually accountable.

And the tempting shortcut — skip the policy, just buy every failed breakdown, since the pattern looks so obviously bullish on a chart? We measured that too, across nine hundred-plus events: 24% win rate, zero expectancy under every conditioning we tried. The pattern is real; the naive trade on it is worthless. Which brings us to the layer that told us so.

Where a trader should focus here: this is where creative effort belongs — but creativity expressed as separable hypotheses, not as features accreted onto one ever-growing strategy. The question "what would a policy for this market shape look like?" is productive. The question "how do I make my main strategy also handle this?" usually is not.

Layer 3: the accounting layer

What it consists of: four components, in escalating order of realism.

• The backtest through the live code path. Not a separate vectorized approximation of your strategy — the actual policy code, fed historical bars the way live bars arrive. Any divergence between "backtest logic" and "live logic" is a fraud you are committing against yourself, and it will be discovered at the worst possible price.
• A probation tier: signal-only deployment. Every new policy in our system carries a flag that lets it run fully live — consuming real-time measurements, forming real decisions, logging real signals — while trading nothing. It is the single highest-value feature in the codebase. Backtests answer "would it have worked?"; probation answers "does it actually fire, on live data, when the code, the data feed, and the market are all being themselves?" The new drift policy above went out signal-only; it will earn capital or it will not, and either way the answer will be data.
• Ground-truth labels. For recurring patterns, a store of hand-labelled or rule-labelled outcomes ("was this breakout real?") that candidate policies can be scored against without waiting months of wall-clock time.
• The negative-results ledger. When an idea fails measurement, the result gets recorded where the code lives. The cheapest experiment is the one you do not re-run, and the most expensive opinion is the one you re-believe six months later.

Its function: decide what survives — and, just as importantly, notice what has stopped surviving. Edges decay. A layer that can only admit policies and never expel them is a museum, not an accounting department.

The rule it must never break: it must be able to kill your favourite idea, and it must apply the same test to every candidate. The moment a beloved policy gets a friendlier backtest window or a waived probation period, the layer stops producing information.

Where a trader should focus here: skepticism. Not the performative kind — the procedural kind, where the test is fixed before the idea is loved.

Why the separation is what finds the edges

Here is the part that took me longest to internalise. The layering is usually sold as hygiene — nice, clean engineering. But the real payoff is economic: separation collapses the cost of running experiments, and edge-finding is an experiment-count game.

• Fixed layer 1 + uniform layer 3 = cheap layer 2. When measurement is shared and accounting is standardised, a new hypothesis costs one small policy file — not a new system. This is precisely the WorldQuant lesson from the last post, scaled to a retail codebase: they froze the policy contract so that thousands of alpha expressions could be measured on an assembly line. You freeze the instrument bench and the courtroom so that dozens of policies can be.
• Failures become attributable. When a layered system loses, you can say which layer failed: a stale series (measurement), a broken thesis (policy), or a correct decision that lost anyway (variance — the only acceptable kind of loss). An unlayered system offers only "the strategy lost," which is unactionable, so the trader responds the only way the architecture allows: retuning indicator parameters. That is the indicator graveyard, explained structurally.
• Probation converts opinion into data at zero risk. A signal-only tier means the gap between "I believe this" and "the ledger says this" is a few weeks of patience instead of a few percent of the account.
• The edge becomes a portfolio property. No single policy has to be brilliant. A shelf of small, separately-accountable policies, each with a modest measured edge and each individually killable, is more robust than one grand unified strategy — because when the market changes shape, you retire a policy, not a system.

Where the effort goes

Most traders allocate effort in almost exactly the wrong proportions: the vast majority at layer 1 (cycling indicators and settings), a little at layer 2 (rules copied from the indicator's folklore), and none at layer 3. A working allocation is closer to the inverse — measurement verified once and then trusted, decisions where the imagination goes, accounting where most of the discipline and a surprising amount of the time goes.

The edge, when it comes, will not look like a secret indicator. It will look like a small, slightly boring policy — sitting on instruments everyone has, judged by a court you built yourself — that keeps surviving the count while its siblings get retired around it. The system that can notice that, cheaply and repeatedly, is the edge.

Next in this series: what the probation tier looks like in practice — how a signal-only policy earns its way to real capital, and the graduation criteria we actually use.