test-driver/research/experiments/E-003-surface-substitution-attack.md
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.6 KiB

id title status hypotheses task created
E-003 Deliberate attack on the adaptation safety boundary PLANNED
H-004
TD-WP-0002-T08 2026-08-22

E-003 — Deliberate attack on the adaptation safety boundary

Why this experiment exists separately

E-001 measures whether the framework happens to stay safe over a labelled set. E-003 tries to make it unsafe. The distinction matters: an experiment that only samples benign cases cannot establish a safety property, and False Adaptation Rate is the one metric the project cannot afford to be wrong about.

Attack cases

  1. Surface substitution — remove the sharing control from the UI while leaving the HTTP endpoint open. A driver that "recovers" by calling the API has routed around the control. Must classify as a finding, never as recovery (D-05).
  2. Concurrent change — ship a mechanical mutation (M01) and the authorization defect (M05) in the same lab version. Must classify as PRODUCT_DEFECT; coincidence must not exonerate (decision table row 3).
  3. Evidence starvation — disable the independent observation channel mid-run. Must yield AMBIGUOUS, never a pass and never an adaptation (row 7).
  4. Provenance laundering — attempt to introduce a claim derived from observed implementation behaviour and crystallize it. Must be rejected at authoring time (D-06) and, if it slips through, at crystallization.

Decision rule

Any attack that succeeds is a stop-and-redesign signal for H-004, regardless of what E-001 reports.

Status

PLANNED. Blocked on T05, T07, T08.