The console refuses to produce an expectancy status for an unfinished cycle.

Two statuses, not one

The tab computes what closed trades imply and what the throttle is allowed to use.

The primary output block carries a closed-only expectancy status alongside the status fed to the throttle, and they answer different questions. The first grades the closed trades on their own terms and will happily return a favourable reading from two closed winners. The second applies the completeness filter and returns Insufficient Sample unless the expected cycle is fully resolved. Keeping both means the operator can see what the partial evidence suggests without that suggestion acquiring deployment authority. It is the same separation the system applies everywhere: an observation is permitted to exist and is not permitted to travel. What crosses into the throttle packet is the filtered one, and the unfiltered one stays on the console as context for the person reading it.

Why completeness

The trades that remain open are not a random subset of the cycle.

The reason a partial cycle cannot be treated as a small complete one is selection, not sample size. Trades close for reasons connected to their outcomes: losers reach their stops and finish, winners that keep running stay open, and positions managed to break-even may sit unresolved for days. So at any moment inside an unfinished cycle, the closed subset is systematically unrepresentative of the whole, and the direction of the bias depends on which management rules are in force rather than being noise that averages out. Grading two closed trades and reporting the result as the cycle's expectancy therefore does not produce a noisy estimate of the eventual figure — it produces a figure with a built-in tilt that no amount of caution about small samples corrects for.

The mode that relaxes it

A second mode allows closed-only context, and its warning is specific.

The behaviour is controlled rather than hard-wired. The default mode requires a complete cycle and is described as the safest live default, precisely because it prevents incomplete samples from promoting risk. The alternative permits closed trades to supply contextual evidence while others remain open, and its stated use is monitoring or end-of-day review — with the explicit caution that it should not be used casually for promotion. Notice what the two modes actually change: not the arithmetic, which is identical, but whether a partial reading is permitted to leave the console. The mode is therefore a statement about what the operator intends to do with the number, made before the number is read, which is the only order in which such a statement means anything.

The parallel status

Profit direction has its own unresolved value, and it is not neutral.

Cycle profit direction runs the same discipline through a different vocabulary. It classifies a resolved cycle into a tone — strongly positive through severely negative — and when trades remain open it returns Pending rather than defaulting to flat or mixed. The distinction matters because flat is a claim about the cycle and pending is a claim about the reading. A throttle receiving flat would treat it as neutral tactical evidence and weigh it accordingly; a throttle receiving pending knows the cycle has not concluded. The same principle governs the open exposure warning, which exists specifically to prevent unresolved trades being read as clean proof. Three different fields, one behaviour: when the answer is not yet available, say so in a way that survives the transfer.

What it costs

Mid-week cycles frequently produce no promotable evidence at all, by design.

The honest consequence is that an operator running trades that regularly carry over will spend much of the week with a daily expectancy status that cannot support promotion. That feels like the instrument failing to deliver, and it is the instrument working. The tactical layer is the fastest and weakest input in the whole stack, permitted to select inside a ceiling that structural evidence established rather than to raise one, so a week in which it abstains is a week in which deployment is governed by the weekly and gate layers alone — which is close to the intended resting state. The status is not withholding something the operator would otherwise have. It is declining to manufacture something that was never there.

• Open trades are not a random subset — the closed ones carry a management-driven tilt.
• The default mode blocks partial readings from leaving; the alternative is for review.
• Pending is a claim about the reading; flat would be a claim about the cycle.

The key idea

A refusal that survives the handoff is worth more than one that does not.

Many systems know when their evidence is thin and lose that knowledge at the boundary, because what gets exported is a number and the caveat stayed behind as a note or a colour. The console exports the refusal itself: the field the throttle reads contains Insufficient Sample, not a value accompanied by a warning somewhere else. That is what makes the discipline durable across two workbooks and two operators' attention spans. Uncertainty that travels as data is respected; uncertainty that travels as commentary is discarded at the first convenient moment.