Certified Validation QA — The Five Principles

The five principles of the QA doctrine.

How MARS uses this

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.

How it benefits you

You learn to distinguish a bad week from a broken system. Variance stops triggering rule changes, and genuine expectancy decay gets caught while it is still one line on a chart instead of a hole in the account. The GREEN/YELLOW/RED language also makes weekly review fast and unambiguous.

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

The key idea

The principles

Five rules, no exceptions.

Each principle closes a specific door that bad verification walks through:

Black-box testing prevents false security from formulas that calculate but misbehave — inputs and outputs are tested, internals are never assumed correct.
Scenario contracts turn testing into objective comparison instead of opinion.
Maturity gating stops a one-week sample pretending it proves monthly or structural behavior.
Source-of-truth routing forces every output to trace back to the correct truth layer.
The error lifecycle — failure → register → fix → retest → close — forces disciplined repair proof instead of 'I think it's fixed.'

Why black-box

Internals lie politely.

A formula audit can pass while the workbook misbehaves — mirrored stale rows, off-by-one windows, dashboards reading future cells. Testing from visible inputs to visible outputs catches what formula inspection can't: wrong behavior that computes cleanly.

In context

The pipeline these principles protect.

The deepest QA target is CP3's Journal → Weekly Summary → EV Scorecard → Dashboard → SDE/Regime/Gate pipeline — the spine of the whole system. If that pipeline can't be trusted, no downstream authority can either.

In practice

Six structural inputs are scored monthly into a composite, and the composite maps onto the regime ladder. MARS reads results in context: the same numbers mean different things earned in Expansion tailwind versus survived through Instability, and posture is adjusted to the regime rather than to the last trade.

Twelve months classified across the regime ladder - the system's own weather record, from Expansion down toward Drawdown Control.

Connected inside MARS

This module doesn't work alone.

Connected — 01

Certified Validation QA (full module)

Open system page →

Connected — 02

The Audit Flow

Open system page →

Connected — 03

Compliance Panel 3

Open system page →

Go deeper

Operator briefs on this territory.

Deep dive — 01

Maturity gating: an output that cannot yet be true stays dark.

One week cannot prove a quarter. So the quarterly output does not appear until a quarter exists.

Read the full brief →

Deep dive — 02

Every output must name where its truth came from.

A panel that invents a value and a panel that reports one look identical. Routing is what separates them.

Read the full brief →

Deep dive — 03

Black-box testing: proving the workbooks behave, not that the formulas compute.

Formulas that compute can still be wrong. Black-box testing checks behavior, not arithmetic.

Read the full brief →

Every module ships in the complete MARS package.

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

Get MARS Pro — $497 Explore the Platform