test-driver/research

Research Control Plane

Deliberately small. This directory exists so that claims about test-driver can be falsified rather than accumulated. It is plain files — no CLI, no schema, no tooling — until there are enough readings to justify tooling.

research/
├── hypotheses/   H-NNN — a claim with a falsification condition
├── experiments/  E-NNN — a planned or executed test of a hypothesis
├── findings/     F-NNNN — findings about test-driver itself
├── concepts/     the Concept ↔ Implementation Fitness Map
└── decisions/    pointers to decisions recorded in State Hub

Identifier convention

Prefix	Scope	Example
H-NNN	Hypothesis	H-001
E-NNN	Experiment	E-001
F-NNNN	Framework Finding	F-0001
C-<slug>	Concept in the fitness map	C-actor-isolation
D-NN	Decision, scoped to its design note	D-07
TD-WP-NNNN-TNN	Workplan task (State Hub)	TD-WP-0002-T04

Identifiers are stable and never reused. A rejected hypothesis keeps its number.

Hypothesis lifecycle

PROPOSED → EXPERIMENTING → SUPPORTED → PRACTICALLY_VALIDATED → ARCHITECTURAL
                  └──────→ REJECTED

A hypothesis may be reopened if later evidence contradicts it. Reopening is recorded in the file, not by creating a new identifier.

Rules

1. Every hypothesis states what would falsify it, in terms of an observable outcome, before any experiment runs. A hypothesis with no falsification condition is an opinion.
2. Concepts with no supporting evidence are marked as such, not quietly retained. The fitness map is expected to contain unsupported entries; hiding them defeats its purpose.
3. Subtraction counts as progress. A rejected hypothesis or a removed abstraction is a result, not a setback.