Validation
WF Harness
Static validation of question pools, render coverage, payload shape, concept consistency, generators, and scheduler scenarios.
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:
It validates seven groups:
- question type coverage
- render dispatch coverage
- interactive payload shape
- boundary checks
- concept consistency
- generator determinism
- scheduler coverage
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
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.
Read the WF feature page for the config surface and contract framing.