Where it sits in the production loop.

Layer 01 — From the manual

Where it sits in the production loop.

Execution evidence is logged → the CP3 Journal and Weekly Summary compress trades into weekly probabilities and branch counts → the Scorecard converts probabilities into branch EV, blended EV, week status, volatility context, and quota governance → dashboards and governance panels read the result → SDE decides whether the trend is structural.

• The Legend tab holds constants and profile weights — edited only when intentionally changing assumptions.
• Summary v3.1 rolls weeks into monthly/quarterly/annual context: average EV, weighted EV, status counts, quota flags, pace tags.
• Doctrine: if the Scorecard says RED, the operator respects the risk doctrine instead of negotiating with the result.

Layer 02 — Where it lives

Inside Weekly Scorecard.

Within Weekly Scorecard, this is one load-bearing idea — worth its own page. The parent module frames it this way: The Weekly Trading Scorecard is the weekly expectancy health monitor. It converts branch-level probabilities into branch EV, blends by the active profile weights, and tags the week by expectancy health — replacing 'did I make money?' with 'is the system still worth deploying?'

Layer 03 — Downstream consumers

Three systems read the scorecard's output every week.

The weekly grade is not a report that gets admired — it is an input: gate review consumes it for state confirmation, the regime engine consumes its structural components monthly, and quota governance consumes its counts. A scorecard week left ungraded starves three downstream systems, which is why the Saturday discipline is non-negotiable.