---
id: E-003
title: Deliberate attack on the adaptation safety boundary
status: PLANNED
hypotheses: [H-004]
task: TD-WP-0002-T08
created: "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.