Every gate produces a number and a name, and they govern different things.

Two outputs

The band produces a ceiling and a description, in parallel.

Reading the gate table across rather than down makes the structure visible. Each drawdown range maps to a state name, a brake meaning and a throttle interpretation. The brake meaning is not a restatement of the tier cap in words — Expansion, Stability Brake, Defense Brake, Containment Brake, Suppression Brake, Seizure Brake and Lock describe a stance, and they were chosen to be distinguishable from each other rather than to be ordinal. A stability brake and a defense brake both compress the ladder; they name different reasons for compressing and different behaviours that follow. The number tells the operator how much capital is available. The name tells them what kind of operating period they are in.

What the tone reaches

The posture constrains behaviour that no pool percentage can express.

A tier ceiling is a quantity and can only govern quantities. The brake tone governs the qualitative side of the operating period: which management variants are appropriate, how much latitude discretion has within the plan, and what the review cadence should be paying attention to. An account under a containment brake is not simply an account deploying less capital — it is an account whose mission has changed from growth to preservation, and that changes what a good week looks like, what counts as a reason to take a marginal setup, and whether an unusual structure is worth experimenting with. None of that is derivable from a pool percentage, which is why the tone exists as a separate output rather than as commentary on the number.

The two can be read against each other

Adjacent states can carry similar ceilings and quite different postures.

Because the two outputs are produced independently from the band, they do not have to move in lockstep, and reading them together is more informative than reading either alone. The stability brake and the defense brake sit next to each other on the ladder and their deployment ceilings are not dramatically different — but one is described as normal operating defense and the other as controlled exposure and early defense, which is a genuine shift in stance rather than a step down in size. An operator tracking only the pool would experience the transition as a modest reduction. An operator reading the tone would recognise that the account has moved from operating normally under mild contraction to actively defending, which is the more consequential of the two facts.

The terminal name

Lock is the one state whose tone has no corresponding number.

The bottom of the ladder makes the separation unmistakable. Six of the seven states produce a tier ceiling and a pool; the seventh produces neither, because it does not authorise trading at all. Its tone — lock, with a structural audit required — is doing all of the work, and there is no deployment figure for it to accompany. That asymmetry is worth noticing precisely because it demonstrates the tone is not decoration on the number: at the one state where the number ceases to exist, the name is still there and is the entire content of the state. A system in which the brake tone were merely a description of the tier would have nothing to say at the point it most needs to.

In practice

Carry the tone into the review, not just the pool into the sizing.

The operational habit worth building is to record and repeat the brake tone rather than only the tier and pool. The decision log stores the gate, so the tone is recoverable, and the weekly review benefits from being framed by it: a week traded under a defense brake should be read differently from one traded under expansion, and the same result under each has different implications. This is the same discipline that governs reading a week's results after the gate state rather than before. The number tells you what you were allowed to deploy. The name tells you what the period was for, and a review that only recovers the first has lost the frame that makes the second interpretable.

• Ceiling and tone are parallel outputs of the band, not a number and its label.
• The tone governs management latitude and review focus — things a percentage cannot express.
• Lock has a tone and no pool, which proves the tone is not derived from the number.

The key idea

Naming a state is what lets a doctrine attach to it.

A ladder of pool percentages would be sufficient to govern deployment and would leave the system unable to say anything about what an operator should be doing differently. Names carry doctrine: containment means something, and once it means something, rules and habits and review questions can be written against it that would have nowhere to attach if the state were merely twenty percent. This is why the gate table has a meaning column at all. The number governs the account, and the name governs the operator.