QoI anatomy
A QoI carries: name, units, scope (region / node / surface / line / time window), extraction method (function-object, parser, post-script), tolerance or uncertainty, and the evidence path. Declaring it up front gives the solver pack a chance to wire the right runtime monitor.
Extraction recipes
Extraction is a typed recipe, not a one-off script. The same recipe runs on a 64×64 mesh and a 256×256 mesh; the same recipe re-runs months later for the regression check. Recipes live alongside the CaseSpec so they migrate with the case.
Mesh-quality gate
ADR 0012 freezes mesh-quality thresholds at the case level in ValidationSpec. The solver pack refuses to launch a run on a mesh that fails its gate (non-orthogonality, skewness, aspect ratio, y+ targets, element order, rigid-body support, benchmark-specific rules).
y+ and wall-resolution
For wall-bounded turbulent flow, the gate evaluates y+ against the chosen turbulence-model assumptions (low-Re wall integration, wall functions, hybrid). A mismatched y+ is not a runtime warning — it's a pre-flight failure.
Who owns each threshold
Solver packs propose defaults; the CaseSpec author can override; the standards pack can tighten. The report records the active threshold, who set it, and which evidence proves it was met.