Nothing in the gate ladder fires for duration — which is why dwell is measured.

The blind spot

Depth triggers cannot see duration, by construction.

The gate ladder routes on drawdown depth: a defined percentage takes the system from Growth to Recovery, a deeper one to Buffer, then Floor, Deep-Floor, Ground-Floor, and System Lock. This is the correct design for the thing it protects against, because depth is what threatens the account. It also means that a drawdown which stabilises just above a threshold and stays there indefinitely will never advance the gate — the system remains in one state, the ladder reports it accurately, and nothing escalates. A shallow drawdown lasting a quarter and a shallow drawdown lasting three days present identically to every depth trigger in the system.

Why the slow bleed is dangerous

It costs capital and it costs the operator, in different currencies.

The extended shallow drawdown does two kinds of damage. The capital cost is straightforward and modest — that is what makes it shallow. The operator cost is not. Depth threatens the account; duration threatens the person operating it, and a system that grinds sideways for eleven weeks tests conviction in a way a sharp, deep, quickly-recovered drawdown does not. The failure that follows is rarely a gate breach. It is abandonment of the plan out of fatigue: a rule loosened because it has not paid in months, a branch dropped because it has not worked recently, a size increase taken to accelerate a recovery that patience would have delivered. None of those register as capital events and all of them are structural.

• Depth is an account problem with an automatic response. Duration is an operator problem with none.
• The gate cannot escalate for fatigue, so the escalation has to come from the review.
• Long dwell in a stress gate is the signal that persistent damage is present, not a one-day event.

What dwell does about it

It makes duration a recorded fact rather than a feeling.

Dwell does not fire anything, and it is important to be clear that it is not a hidden time-based gate. It records how long the account has remained in its current state, which converts a subjective sense of grinding into a number that appears in the weekly and monthly rollups and feeds the pressure score. That is a smaller intervention than a trigger and it is the right size for the problem: a time-based automatic gate would have to pick a duration threshold, and there is no non-arbitrary one — the point at which a long drawdown becomes dangerous depends on the operator, not the arithmetic. Recording it puts the escalation decision in the monthly review where the judgement belongs, with a fact rather than an impression to work from.

Reading dwell in context

The same dwell figure means opposite things at opposite ends of the ladder.

Dwell is unusual among the diagnostics in that its interpretation reverses depending on where the system sits. Long dwell in Growth is the healthiest possible reading — the account has held a strong capital state without interruption. Long dwell in Floor is among the most serious, because it says the system has been unable to climb out and the constraint has become the normal operating condition rather than a temporary response. A dwell figure quoted without its gate state is therefore not a partial reading; it is an uninterpretable one. This is the clearest case in the diagnostic layer where a number genuinely requires its context to have a sign at all.

The key idea

Measure the failure shape your triggers are structurally unable to catch.

The gate ladder is not deficient — depth routing is the right mechanism for capital protection, and adding a duration trigger would mean picking an arbitrary threshold for a problem that varies by operator. What the system does instead is name the gap honestly and instrument it, so that the failure the automation cannot catch is at least one the operator cannot miss.