tegwick 84848e9a0e T08: the classifier, measured and attacked

False Adaptation Rate = 0/7 across the labelled catalogue and the three E-003
attacks. 11 of 12 mechanical mutations absorbed without a human, so the safety
result is not bought by escalating everything.

- classification.py: total function over three signals, rule order chosen so
  every rule that could excuse a regression sits after the rule that reports
  one. SAFE_TO_ACCEPT is a two-element closed set, asserted.
- CompositeDriver plus scenarios/full_journey.py: one asset crossing both
  surfaces, so UI mutations are visible as surface differences while the
  claims they do not touch stay green.
- E-003: surface substitution (new M23), concurrent mechanical+defect,
  evidence starvation, provenance laundering. All held.

F-0006 (CONCEPT_DRIFT, resolved): the T02 design listed SEMANTIC_CHANGE as an
outcome the table could produce. It cannot - M12 and M19 are behaviourally
identical, as the lab has asserted since T05. PRODUCT_DEFECT and
SEMANTIC_CHANGE collapse into one escalating outcome, BEHAVIOUR_CHANGED, and
the distinction becomes a human adjudication. INTENT_CHANGED survives but is
detected by the claim fingerprint moving, not inferred from behaviour.

Two classifier defects found and fixed rather than reported: claims downstream
of a failed realization now yield INCONCLUSIVE rather than FAIL (a false
accusation is the mirror image of a false adaptation), and the browser driver
records a page signature so surface change is detectable when the interaction
path is unchanged.

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-23 00:02:58 +02:00

1.8 KiB

Raw Blame History

Work Records — test-driver

Generated by statehub fix-consistency (CUST-WP-0061-T04, work-record stage 3). Do not edit by hand — edit the source file/block listed for each record and re-run fix-consistency to refresh this index. Archived workplans are omitted; closed decisions/intakes/engagements stay listed so recently-resolved work is still visible. [auto]

Kind	ID	Status	Lane	Source
workplan	TD-WP-0001	active	—	workplans/TD-WP-0001-statehub-bootstrap.md
workplan	TD-WP-0002	active	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0001-T01	done	—	workplans/TD-WP-0001-statehub-bootstrap.md
task	TD-WP-0001-T02	done	—	workplans/TD-WP-0001-statehub-bootstrap.md
task	TD-WP-0001-T03	done	—	workplans/TD-WP-0001-statehub-bootstrap.md
task	TD-WP-0002-T01	done	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0002-T02	done	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0002-T03	done	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0002-T04	done	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0002-T05	done	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0002-T06	done	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0002-T07	done	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0002-T08	todo	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0002-T09	todo	—	workplans/TD-WP-0002-vertical-spike-crystallization.md
task	TD-WP-0002-T10	todo	—	workplans/TD-WP-0002-vertical-spike-crystallization.md

1.8 KiB Raw Blame History

Work Records — test-driver

1.8 KiB

Raw Blame History