tegwick
84848e9a0e
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 |
||
|---|---|---|
| .. | ||
| F-0001-milestone-sequence-drift.md | ||
| F-0002-scenario-coverage-gap.md | ||
| F-0003-isolation-needs-canaries.md | ||
| F-0004-stdlib-driver-instead-of-playwright.md | ||
| F-0005-semantic-actions-earn-their-keep-narrowly.md | ||
| F-0006-classifier-cannot-infer-intent.md | ||
| README.md | ||
Framework Findings
Findings about test-driver itself, kept strictly separate from findings about
any system under test. Classes are defined in
docs/TestDriverImprovementLoop.md § 9:
PRODUCT_DEFECT · TEST_DEFECT · MECHANICAL_ADAPTATION · SEMANTIC_CHANGE ·
CONCEPT_DRIFT · FRAMEWORK_LIMITATION · EVIDENCE_FAILURE ·
UNNECESSARY_COMPLEXITY
File naming: F-NNNN-<slug>.md. Identifiers are stable and never reused.
Each finding carries frontmatter (id, class, status, dates, originating
workplan/task) and, when resolved, states which of the three §5 resolution paths
was taken. A finding that leaves an open question records it under "Residual" and
names the task that will answer it — residuals are not parked in prose.
The wider research control plane (hypotheses/, experiments/, concepts/,
decisions/) is built in TD-WP-0002-T03.