Validation

WF Harness

Static validation of question pools, render coverage, payload shape, concept consistency, generators, scheduler scenarios, and optional deterministic question-quality rules.

Route: /docs/wf-harness

The WF harness is regression infrastructure, not a substitute for low-context WF passes.

The canonical repo docs adjacent to this layer are:

• docs/wf-contract.md
• docs/per-question-wf-gating.md
• docs/wf-kit.md

It validates eight groups:

1. question type coverage
2. render dispatch coverage
3. interactive payload shape
4. boundary checks
5. concept consistency
6. generator determinism
7. scheduler coverage
8. optional deterministic question-quality rules

Why this matters

Consumer repos can catch static drift quickly:

• question types used but not registered
• renderer branches missing
• payloads missing required keys
• concept trees or generators drifting out of contract
• configured question-quality rules catching disclosure, signal, helper, or distractor drift

That lets browser time focus on:

• discoverability
• copy clarity
• recovery paths
• the visible framing of the learning loop

Experimental or LLM-shaped question variants may need additional per-question gating even when deterministic harness checks pass. The harness can run deterministic configured rules, but it is still regression infrastructure; low-context WF remains the discoverability and workflow-completion gate.

Read the WF feature page for the config surface and contract framing.