v-ac-axis-split

What problem does it solve?

Mixed V-AC validations can accidentally hide the real uncertainty by combining deterministic pass/fail evidence with statistical, window-based evidence in a single group.

Core Features & Use Cases

• V-AC axis separation: Splits mixed deterministic and statistical V-AC entries into two distinct V-AC groups before finalising the specification.
• Evidence-chain enforcement: Requires statistical V-AC to cite measurement window, sample size, and confidence interval, while deterministic V-AC must be tied to bats/spec/grep evidence or an equivalent monotonic assertion.
• Validator gate scope safety: During /dr-plan, enforces a validator dry-run row that enumerates every currently failing file under the gate invocation --scope, resolving PRD Out-of-Scope conflicts as rewrite-in-task or an explicit scope-reduction waiver.

Quick Start

Ask the planner to apply v-ac-axis-split to every V-AC in the PRD and component breakdown so deterministic checks and statistical checks are separated and validator gate scopes are dry-run and reconciled in plan time.