# Framework Findings

Findings about **test-driver itself**, kept strictly separate from findings about
any system under test. Classes are defined in
`docs/TestDriverImprovementLoop.md` § 9:

`PRODUCT_DEFECT` · `TEST_DEFECT` · `MECHANICAL_ADAPTATION` · `SEMANTIC_CHANGE` ·
`CONCEPT_DRIFT` · `FRAMEWORK_LIMITATION` · `EVIDENCE_FAILURE` ·
`UNNECESSARY_COMPLEXITY`

File naming: `F-NNNN-<slug>.md`. Identifiers are stable and never reused.

Each finding carries frontmatter (`id`, `class`, `status`, dates, originating
workplan/task) and, when resolved, states which of the three §5 resolution paths
was taken. A finding that leaves an open question records it under "Residual" and
names the task that will answer it — residuals are not parked in prose.

The wider research control plane (`hypotheses/`, `experiments/`, `concepts/`,
`decisions/`) is built in `TD-WP-0002-T03`.