H-001..H-005 with explicit falsification conditions, E-001..E-003, the Concept-Implementation Fitness Map, findings log and ID convention. Plain files, no tooling. - fitness map corrects Improvement Loop section 13 levels downward: nothing exceeds C1 without implementation - H-005 (Energy) dormant by decision - events captured, no scoring written - H-001 gets a genuine control arm so the semantic-action thesis is not trivially true - E-003 added: deliberately attacks the safety boundary rather than only sampling benign cases 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
1.3 KiB
1.3 KiB
| id | title | status | created | experiments | concepts | ||
|---|---|---|---|---|---|---|---|
| H-002 | Mechanical Adaptation | PROPOSED | 2026-08-22 |
|
|
H-002 — Mechanical Adaptation
Claim
An agentic driver can recover from a mechanical implementation change without modifying the semantics of the protected use case.
Falsification condition
Either:
- the driver fails to recover from a majority of labelled
MECHANICALmutations (recovery is not achievable in practice); or - recovery is achieved only in runs where claims or invariants were altered (recovery is achievable but not semantics-preserving).
The second branch matters more than the first. A high recovery rate purchased by weakening assertions falsifies this hypothesis just as decisively as no recovery at all.
Measurement
- Mechanical Recovery Rate over
MECHANICAL-labelled mutations. - Claim/invariant diff per run — expected to be empty by construction
(
docs/TestDriverClassificationDesign.mdD-02). Any non-empty diff is both a falsification signal and a framework defect, since no write path should exist.
Status log
- 2026-08-22
PROPOSED. Design decision D-02 makes the second falsification branch structurally unreachable; the measurement is retained anyway, as an assertion that the architecture is what we believe it is.