Skip to content

CP3 — Layer 05 · Allocation Quality

The Branch Risk Engine. Who earns the risk budget?

How MARS uses this

MARS is a closed loop, not a pipeline. Trades produce evidence, evidence produces weekly grades, grades move gate state, gate state feeds the throttle, and the throttle governs what the next execution is allowed to be. No stage is optional and no stage runs on memory or mood - each one reads the outputs of the stage before it.

How it benefits you

Discipline stops depending on willpower. Because every decision point consumes the previous stage's output, skipping a step becomes visible instead of invisible - and the system keeps improving itself, since every completed loop leaves the evidence base one cycle richer than it found it.

EXECUTEclearance + entryCAPTUREevidence + journalSCOREweekly EV gradeGATEcapital stateTHROTTLEdeployment mathDEPLOYgoverned riskEVIDENCEevery cycle feeds the next

The MARS operating loop: execute, capture, score, gate, throttle, deploy - every cycle feeding evidence into the next.

The key idea

What it scores

Consumption versus contribution, per branch.

Blended P&L camouflages weak branches. This engine strips the camouflage by scoring what each branch takes against what it gives back.

  • Per-branch risk consumption vs. contribution
  • Quality context feeding the Risk Deployment Quality diagnostics
  • Attribution that survives blended P&L camouflage

Why it matters

02

Habit is the silent allocator.

Without attribution, traders keep feeding risk to the branch they like trading rather than the branch that pays. When EV looks positive but capital is falling, the manual routes the investigation here — alongside Capital_Dynamics and Gate_Brake_State — because poor risk efficiency can overpower expectancy.

Position in CP3

The allocation-quality conscience of the ledger.

Branch Risk Engine outputs feed the Risk Deployment Quality Score diagnostics and give the Variant Attribution Module its risk-side context. It is the layer that keeps 'diversified across branches' from quietly meaning 'subsidizing the weakest one'.

Budget migration

Risk budget follows the evidence trail, slowly.

The Branch Risk Engine reallocates on review cadence with deliberate inertia: a branch must sustain its case across multiple windows before its share moves materially. The lag filters out hot streaks masquerading as improvement — budget earned in one loud month is exactly the budget most likely to be handed back.

Worked example

The Weekly Scorecard converts branch hit probabilities into EV and tags each week by threshold. The rolling line is what MARS actually trusts: single-week readings are treated as noise until the rolling window confirms direction. RED weeks trigger doctrine - reduced aggression and review - rather than negotiation.

Weekly EV tagged GREEN / YELLOW / RED against expectancy thresholds, with the rolling-EV line separating persistent edge from one lucky week.

GREEN ≥ +0.25RYELLOWREDROLLING EVW1W2W3W4W5W6W7W8W9W10W11W12

Before you go deeper

Connected inside MARS

This module doesn't work alone.

Go deeper

Operator briefs on this territory.

Every module ships in the complete MARS package.

One price. Eleven workbooks, three TradingView indicators, and the full manual library — $497.