tegwick
5734b280c6
Checks written as plain functions over a serialized Evidence Pack, outside the framework - no Oracle, no Runner, no Verdict aggregation. 12 tests that they hold, 12 that they can fail. All four td://self identifiers covered. The substantive check is verdict reproducibility from S3 evidence alone, asserted on failing runs as well as passing ones. F-0003 (open): actor isolation leaves no trace in ordinary evidence - the self-test catches a shared memory store only because the harness plants per-actor canaries. Isolation is currently a property of a scenario written to expose it, not of runs in general. The mirror-image case is noted too: a guarantee enforced by construction cannot be verified by observing real runs, so four green self-tests are not four equivalent proofs. Carried to T10. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 1629012@bnt-lap001 Assistant-Session: 78d4fb13-8a1e-474b-87a3-9b9261c49a39 |
||
|---|---|---|
| .. | ||
| concepts | ||
| decisions | ||
| experiments | ||
| findings | ||
| hypotheses | ||
| README.md | ||
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
- 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.
- 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.
- Subtraction counts as progress. A rejected hypothesis or a removed abstraction is a result, not a setback.