Quota governance: why the fat tail is mandatory.

The avoidance problem

The fat-tail branch is unpleasant to trade, and that's why it gets skipped.

Trend No-Partial is the true fat-tail accelerator: no partial cushion, full position to the trail unlock, the highest variance in the family — and a losing experience most of the time it's deployed, because fat tails pay rarely by definition. An operator left to discretion will systematically under-trade it, one defensible skip at a time: the trend looks late, the week's already green, the last three TNPs stopped out. Each skip is locally reasonable. The aggregate is a system that has quietly amputated its geometric-growth engine while still reporting expectancy against a profile that assumes it's there. The quota's insight is that this drift is invisible week to week and predictable in aggregate — so it gets governed, not trusted.

The constraint values

The rules, as the Legend actually stores them.

The quota system is specific: Trend No-Partial carries a hard monthly minimum of 8 trades, checked at mid-month against a threshold of 4, with a weekly minimum of 2 and an upper reference band of 3 — participation is required and bounded, because the quota must never become emotional acceleration either. Overflow carries a hard monthly minimum of 4, a mid-month check at 2, and a weekly baseline of 1 — the stability branch has its own floor because under-deploying it lets the weekly mix drift away from the intended expectancy profile just as surely. Both branches carry urgency thresholds at half-pace: fall below 50% of expected progress and the flag fires while the month can still recover. The Journal_Inputs, Quota_Ledger, and Audit_Card tabs turn all of it into a running governance read — actual versus expected, discipline state, recovery triggers, pace tags.

Why quotas protect expectancy

The blend's honesty depends on the mix being real.

The quota system is ultimately an integrity mechanism for every number downstream. The All-Blended EV weights each branch by the profile's intended mix; the Monte Carlo benchmark simulates that same mix across fifty thousand paths; the live comparison reads results against bands built on it. All of it silently assumes the live system actually trades the mix. A month of TNP avoidance breaks the assumption invisibly: the blend still computes, the benchmark still compares, but the system being measured is no longer the system that was modeled — the fat-tail contribution the profile prices in simply never occurred, and its absence reads as underperformance nobody can locate. This is why the manual's quota principle is blunt: quota tracking is not decoration. Under-deployed TNP loses fat-tail capture; drifted Overflow bends the weekly mix off-profile. The quota is the branch weights, enforced.

• The monthly Summary tracks quota-met as a governance pass/fail alongside EV — a green month with a failed quota is not a clean month.
• Participation is bounded above too: the weekly TNP band exists so quota pressure never becomes emotional fat-tail chasing.
• Quota trades still pass every other filter — the quota mandates seeking valid TNP setups, never taking invalid ones.

The audit rhythm

Mid-month checks make the quota repairable instead of historical.

A quota checked only at month-end is a report card; the system's design makes it a steering input instead. The mid-month thresholds — 4 for TNP, 2 for Overflow — split the month into a first half that can fail quietly and a second half that gets told about it, with urgency flags firing at half-pace so the operator's remaining weeks are planned with the deficit in view. The pace tags — ahead, on pace, behind — turn the ledger into a one-glance read during the weekly routine, where confirming quota inputs is a standing step. The rhythm matters because quota failure is almost never a decision; it's an accumulation of skips. Checkpoints turn the accumulation into a visible number while the response can still be 'seek valid TNP setups this week' rather than 'explain the month.'

The key idea

Discipline for the trades you'd rather not take is where the profile lives or dies.

Most governance protects the operator from doing too much — oversizing, overriding, overtrading. The quota system is the rare control that protects against doing too little, because the branch mix's most fragile component is participation in the branch that hurts most often and matters most in the long run. Eight TNPs a month, four Overflows, checked at the half, flagged at half-pace, passed or failed in the monthly record: it's unglamorous machinery for an unglamorous truth — the fat tail only pays the operators who keep showing up for it.