Alignment: the state that authorises nothing.

The two alignments

Both strong and both weak are the same state with opposite meanings.

Alignment means RAER and RAPF agree, and the manual is careful to give the agreement two readings. If both are strong, structure and monetisation are healthy — risk is converting efficiently and the profit that results holds up against the risk deployed. If both are weak, the agreement is negative but clear: the system is not converting risk well and is not producing quality profit either, and at least the two instruments concur about it. The state label is the same in both cases, which is why the base state and the classes underneath it have to be read rather than the conflict type alone. An operator scanning for the word Alignment and relaxing has confused agreement with health.

The playbook for both-strong

Continue. That is the entire instruction.

A strong alignment means the two questions the engine asks have both been answered well and neither is contradicting the other. The correct response is to keep operating the plan inside whatever envelope the gate has set, and to spend the review's attention elsewhere — on the branches, on the execution efficiency data, on whatever the regime engine flagged. What a strong alignment specifically does not do is open a capacity conversation, justify a larger tier, or constitute evidence that risk should expand. The engine has no drawdown input, no capital-state awareness, and no authority over deployment; a clean structural reading during a Floor gate state is still a Floor gate state. The most common misuse of this engine is treating its best output as a permission slip, and the reason it is common is that the reading feels like it ought to be worth something.

• A strong alignment is the expected condition of a working system, not a signal.
• It says nothing about capital state, and capital state is what governs deployment.
• The right use of a clean reading is to redirect review attention, not to change position sizing.

The playbook for both-weak

Clear, negative, and easier to act on than a contradiction.

A weak alignment is bad news delivered unambiguously, and there is genuine value in the unambiguity. When both metrics agree that the system is underperforming, the diagnosis does not require deciding which instrument to believe — the finding is systemic rather than located in a mismatch between execution and monetisation. The review opens on the whole machine rather than on a specific mechanism: entry selection, regime fit, branch allocation, and whether the recent period's conditions were ones the plan is built for. This is different work from what a contradiction demands, and it is why the state deserves its own playbook despite sharing a label with its positive twin.

Why it still gets recorded

Alignment weeks are what make contradiction weeks countable.

The engine's summary counters tally alignment weeks alongside under-monetisation, profit-without-efficiency, dual weakness, transition, and the two leading states. Counting the uneventful weeks may look like bookkeeping, and it is what gives every other count a denominator. Three under-monetisation weeks out of forty is a system that occasionally slips; three out of six is a system with a monetisation problem. Without the alignment tally the contradiction counts are raw numbers with no base rate, and a raw count of a state is exactly the kind of figure that gets read as more alarming or less alarming than it is depending on the operator's mood that Saturday.

The key idea

The state that changes nothing is the one that makes the others legible.

Alignment is the engine's boring output and it is not a wasted reading. It establishes the base rate, it confirms that the two instruments are still capable of agreeing, and it tells the operator that this week's attention belongs somewhere else. A diagnostic that only spoke when something was wrong would leave the operator with no way to judge how wrong.