The gate row is read first because every result below it is conditional.

The conditional

A result is not interpretable until the state it occurred in is known.

Nine R gained under Growth was produced at full deployment authority against an account at its peak: it is expansion evidence and can reasonably inform confidence in the method. The identical nine R clawed back under a compressed gate was produced at a reduced tier against a damaged account: it is recovery, which is encouraging and is not licence. Neither reading is available from the number. Both require the state, and the state is not something the operator can supply from memory reliably because the gate may have moved during the week being reviewed. Recollection of one's own capital state is unreliable in a specific direction: operators remember the state they felt they were in, which is usually the more favourable one.

Why the wrong order is so natural

The result is the interesting number and it is what everyone wants.

Nobody opens a weekly review to find out which gate they were in. The attention goes straight to the outcome, and the state is then consulted afterwards if at all — at which point it has stopped being context and become a qualifier applied to a conclusion already formed. The layout puts the gate above the results because attention follows position, and because an instruction to read in a particular order is honoured far less reliably than a layout that makes the correct order the path of least resistance.

The specific misreading

Recovery mistaken for expansion produces the wrong next decision.

The damaging version of the error runs in one direction. A strong week during compression feels like proof that the compression was unnecessary, which makes the case for restoring deployment early — and restoring deployment early during a drawdown is close to the definition of the behaviour the gate exists to prevent. The gate itself will refuse, since it computes from equity rather than from the week. But the operator now believes the system is being obstructive, and that belief is where overrides begin. The read order prevents the belief from forming rather than relying on the constraint to survive it. A constraint that holds while the operator resents it is materially weaker than the same constraint the operator never had cause to resent.

The quieter misreading

A weak week under Growth deserves more attention than it gets.

The reverse case is less dramatic and worth naming. A poor week produced at full deployment authority against an account at its peak has no mitigating context available — there was no compression to blame and no damaged capital state to explain it. That is a cleaner negative signal than the same week under a defensive gate, and it tends to receive less scrutiny because the account looks healthy in every other respect. Reading state first is what makes the absence of an excuse visible as information. It is the cleanest read the weekly review produces and the one most often skimmed, because nothing about it demands attention.

• Strong week under compression reads as vindication and is not.
• Weak week under Growth has no mitigating context and is a cleaner signal.
• Layout enforces the order because instructions about order are not honoured.

When the state moved mid-week

A week spanning a gate transition needs both states, not the closing one.

The awkward case is a week that began in one gate and ended in another. Reading only the closing state attributes the whole week's results to authority that applied for part of it, which distorts in whichever direction the transition ran. The daily structural table exists for this — gate state is tracked per day, not only at week end, so a transitioning week can be read as the two segments it actually was. Gate transition velocity is a tracked field for the same reason: how fast the state moved is a fact about the week that the endpoints alone conceal.

The key idea

Sequence is doing work that no amount of care substitutes for.

This is the same principle as reconciling before reading: a number seen first colours everything checked afterwards, and the effect does not depend on the operator being careless. Putting capital state above results is a small structural decision that removes the most common interpretive error in the weekly review, and it works because it never asks anyone to resist anything. The correct reading is simply the one that happens when the page is read from the top.