DynamisLab/docs/JFM_WYQ/ROUND3_BOTTOM_UP/00_QUALITY_GATE.md

Round 3 Quality Gate

The parent coordinator assigns one status per module: PASS, REVISE, or BLOCK. PASS means ready for a second audit, never final manuscript approval. Only after the second audit may the coordinator mark a module ready.

First-pass audit protocol

Before revising a module, classify each defect as systematic prompt defect (also observed or likely in other modules) or module-specific defect (local evidence, scope or reasoning problem). Update the rule/master prompt/quality control first for systematic defects, then issue targeted revisions to affected modules. Do not conceal a control-plane defect as an agent failure.

PASS checks

• Two-layer delivery: readable prose-like paragraph drafts/maps with short source tags first; compact local paragraph notes or claim-to-evidence ledger immediately afterward. Full provenance is local and traceable without giant inline contract blocks, package-path dumps, bold template labels or source/status language dominating the argument.
• Paragraph cadence is readable: one argumentative job per paragraph, substantive bridges, reasonable sentence/paragraph load, and observation → comparator → physical reading → limit → consequence where applicable. Flag repeated mega-paragraphs or overloaded sentences; do not use rigid word-count automation.
• Reads and names the controlling Round-2 freeze/style guide, relevant Round-1 dossiers and current package authorities; ledger distinguishes read, mapped, not-covered, external-inaccessible with reasons.
• Every number and physical claim has exact provenance: authority/artifact, Legacy/V5 chain, solver/geometry, case/seed/role, Re convention, comparator, metric/estimand, ROI/window and status.
• Authority-led hidden/external artifacts explicitly bound by conflict-free authority are marked artifact-audit deferred, not automatically blocked. BLOCK applies only when the missing artifact is necessary to resolve authority conflict, identify exact role/comparator/window, substantiate a proposed number/panel, or answer the section question.
• Distinguishes pipeline Level-2/Level-3 or Stage-3 short/standard gate from spatial L2 field-error metric; no validation level is called an L2 gate. Spatial L2 remains primary for field matching; DTW is complementary/case-specific, with no silent metric pooling or phase relabelling.
• Enforces scope interfaces: bridge/context is brief; SR does not duplicate full steady results; field/CCD does not duplicate SR derivation; contracts do not become a results section.
• Runs a near-collision check for numerically similar cross-module results: compare role acquisition, role set, ROI/domain, mask, weighting/normalization and window; classify same estimand, related diagnostic or different estimand. Prohibit arithmetic combination and replication/validation/agreement/triangulation wording unless exact authority licenses it.
• Defines figure/equation/table roles and caption limits; states imports, exports, section bridge, conflicts, non-claims and genuine blockers.
• Uses fixed terminology and claim ceiling: positive SR Kármán/cloak only; negative Illusion SR; descriptive/noncausal CCD action-correlated correction-field modes; claim-free OID; qualitative experiment.
• Passes anti-index and anti-AI checks: no inventory/package handoff/card stack, generic prose, caption narration, citation/number/artifact invention, or delayed limitations.

REVISE

Use when evidence is traceable but narrative cadence, layer separation, style, interfaces, terminology, redundancy, provenance, local caveats or exact metric semantics are incomplete. Return targeted paragraph-level prompts, not a general wish list. Re-audit after revision.

BLOCK

Use when a controlling source was not read without a justified ledger entry, an authority conflict affects the answer, a required artifact/role is absent, a number lacks provenance, Legacy/V5 are merged, metrics are pooled, or the draft requires unsupported causality/mechanism/generalization. An authority-led artifact deferral alone is not a blocker when its claim and role are explicitly bound without conflict. Preserve the blocker; do not fill it from memory.