tegwick bec7fdc465 T03: research control plane

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

2026-08-22 23:11:21 +02:00

1.5 KiB

Raw Blame History

title

status

created

experiments

concepts

H-004

Independent Judgment

PROPOSED

2026-08-22

E-001

E-003

C-oracle-independence

C-intent-provenance

H-004 — Independent Judgment

Claim

Separating actor execution from deterministic oracles reduces false-positive adaptation to defective behaviour.

Falsification condition

The framework classifies any seeded DEFECT-labelled mutation as MECHANICAL_ADAPTATION — i.e. False Adaptation Rate > 0 over the labelled set.

This is the project's existential safety metric. A non-zero result is a stop-and-redesign signal, not a tuning exercise.

Measurement

False Adaptation Rate over DEFECT-labelled mutations. Target: exactly 0.
Classification precision/recall over the full labelled set.
Rate of AMBIGUOUS escalation — tracked as a cost, not as a failure. A system that escalates everything is safe and useless.

Relationship to the design

docs/TestDriverClassificationDesign.md argues that FAR = 0 follows architecturally from D-02 (claims are run inputs with no adaptation write path) rather than from classifier accuracy. This hypothesis therefore tests the architecture, not a model.

The most plausible route to falsification is not a misclassification but surface-substitution: an actor routing around a broken authorization control via another surface and scoring as a successful recovery. D-05 exists to close that route; E-003 exists to attack it deliberately.

Status log

2026-08-22 PROPOSED. No evidence.

1.5 KiB Raw Blame History