Diagnostics — Certified Validation QA

Trust nothing until it survives the audit.

The key idea

The five principles

From the QA workbook's own doctrine.

Black-box testing prevents false security from formulas that calculate but misbehave. 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.”

The audit flow

Eligibility → scenarios → runs → verdict.

The Test Matrix defines valid timeframe-scenario combinations; the Scenario Library assigns stable IDs; Expected Outputs define the contract; Test Runs record each formal pass against a workbook version; CHK tabs compare expected to actual; the Error Register blocks advancement on failures; the Retest Log proves repairs; Master Control summarizes readiness and next action.

Deepest target: CP3's Journal → Weekly Summary → EV Scorecard → Dashboard → SDE/Regime/Gate pipeline.
Also audits the Weekly EV Scorecard, Throttle Control Panel, and Cycle Command Console.

Further illustration

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.

Reference

The QA spine — from scenario to certification

Stage	Tab family	Output
Eligibility	Test Matrix	Valid timeframe × scenario combinations only
Scenario registry	Scenario Library	Stable, reusable scenario IDs
Contract	Expected Outputs	What the workbook must do under each scenario
Inspection	CHK tabs	Pass / fail against the contract, source-of-truth first
Failure control	Error Register + Retest Log	Defect history preserved; fixes proven, not assumed
Certification	Master Control	Readiness as a computed result, not an opinion

Use cases

Where it earns its place

▸Certifying a workbook version before its outputs are trusted in live governance
▸Catching dashboards that mirror stale or future rows instead of the correct truth layer
▸Proving a repair actually worked before an error is closed

Before you go deeper

Inside this module

2 pages go deeper than this one.

The Five Principles

Go deeper →

The Audit Flow

Go deeper →

Connected inside MARS

This module doesn't work alone.

Connected — 01

System Architecture

Open system page →

Connected — 02

Compliance Panel 3

Open system page →

Go deeper

Operator briefs on this territory.

Deep dive — 01

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 →

Deep dive — 02

Failure, register, fix, retest, close: the lifecycle that forbids 'I think it's fixed.'

A fix isn't done when it's applied. It's done when the scenario that broke it passes again.

Read the full brief →

Deep dive — 03

Certification: what it means for a workbook to be trusted.

Certified means: this version, these scenarios, no blocking errors. Not 'the workbook is good.'

Read the full brief →

Take it further

QA asks whether a change is safe to promote. The Foundry is where the change gets built and broken first, so QA is auditing something that has already been argued with.

Open the AlphaRail Foundry Lab ↗

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