The packet carries the gate and the drawdown that produced it.

A conclusion and its basis

Most transferred fields are facts; one is a derived state, so its input travels too.

The packet's other fields are measurements or classifications the throttle simply consumes — an expectancy status, a profit tone, a count of open trades, an active risk percentage, a viability threshold, a mode. The gate is different in kind: it is a derived state produced by comparing current equity against the equity peak and locating the result on a band ladder. A derived state can be wrong in ways a measurement cannot, because it depends on a comparison and a table lookup rather than on an observation. Carrying the drawdown percentage alongside it means the receiving end holds both the answer and the number the answer was computed from, and can therefore check one against the other without access to the console's internals.

The permitted mismatch

The gate may differ from the calculated drawdown, and only if the difference is documented.

The operating note is worth quoting in substance because it is easy to miss: the gate should match the calculated drawdown unless an override is documented. That sentence permits something the authority doctrine otherwise appears to forbid — a gate state that is not the one the arithmetic produced. The permission exists for a reason. The drawdown calculation depends on the equity peak, and there are legitimate situations where the computed figure is not the operationally correct one: a capital withdrawal that mechanically lowers equity without representing loss, a data correction, a deposit that resets the reference. In those cases the honest gate is not the calculated one, and the system's answer is to permit the divergence and require it to be written down rather than to pretend the calculation is never wrong.

The asymmetry

A documented gate override should virtually always run toward the more restrictive state.

The permission comes with a direction that the doctrine implies rather than states, and it is worth making explicit. Overriding the gate to a more restrictive state — treating the account as being in a deeper band than the arithmetic says — is the survivability rule applied by hand, and it costs bounded upside. Overriding toward a shallower state raises the tier ceiling, which is the one thing the gate exists to prevent evidence from doing, and an operator who has just computed an uncomfortable drawdown is exactly the person most motivated to find a reason the calculation is unrepresentative. The documentation requirement carries most of the protection here: a written justification for deploying more after a drawdown reads very differently a month later than it does in the moment it is composed.

What the receiving end can do

Having both fields makes a mismatch detectable rather than invisible.

If only the gate travelled, the throttle would receive a capital state with no way to evaluate it, and any error — a stale peak, a mistyped equity figure, an override nobody recorded — would arrive as settled fact and propagate through every downstream calculation. With the drawdown alongside, the pair can be checked in one glance against the band ladder, and a gate that does not correspond to its stated drawdown is immediately visible as either a documented override or a defect. This is the same construction the journal uses when derived columns act as an integrity check on typed ones, and the same reason the contradiction engine renders selected week beside latest available week. Redundancy that permits a comparison is not duplication.

Reading the pair

Two fields, one ladder, and a question that has three answers.

The operational routine is to read the drawdown figure, locate it on the band ladder, and confirm it produces the gate in the field beside it. Agreement means the capital state is settled and the rest of the packet can be trusted on that dimension. Disagreement toward the restrictive side, with a note, is a documented override and should be read for its reason. Disagreement with no note is a defect and stops the cycle until it is resolved — because every downstream figure, the tier cap most of all, is computed from the gate rather than from the drawdown. It is a five-second check guarding the single highest-authority input in the deployment chain, and it is only possible because the packet was designed to carry both.

• The gate is derived, so its input travels with it; measured fields do not need this.
• A documented divergence is legitimate — an undocumented one halts the cycle.
• Overrides toward restriction cost upside; overrides toward permission need scrutiny.

The key idea

Transferring a conclusion without its basis makes the receiver a believer.

Interfaces between systems tend to move conclusions, because conclusions are what the receiving side needs and the intermediate working is bulk. The cost is that the receiver acquires no capacity to disagree — it consumes what it is given and its own outputs inherit whatever was wrong upstream. Sending one extra field with the single derived value in the packet converts the throttle from a consumer of the console's gate into something that can check it, at a cost of one number. That is a very good exchange rate for the highest-authority input in the system.