T10: gate review and first compression pass

All four gate criteria met. False Adaptation Rate 0/7 with 12 of 13 mechanical
mutations absorbed. 178 tests pass. TD-WP-0002 finished.

Fitness loop closed via F-0003: actor isolation was a property of scenarios
written to expose it, not of runs. Actors now carry an automatic private
marker and the runner examines all of them on every scenario, with two
permanent regressions behind it.

Compression - six abstractions removed, each declared and never used:
Verdict.SUSPICIOUS (a verdict no oracle could emit), Step.expect_refusal,
ActorIsolationError, World.seed, EvidencePack.latest, Trajectory.method.

F-0008: Temperature may be redundant. Crystallization was built without it
ever being consulted; measured stability of realization did the work, and is
observed rather than declared. Gated for removal alongside energy.py.

INTENT_CHANGED and REALIZATION_FAILED had never run. Both now have
purpose-built cases and a test that fails if a seventh outcome is added
without one.

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
This commit is contained in:
tegwick 2026-08-23 00:39:36 +02:00
parent 4f4219d8f7
commit 1b9860a8ee
40 changed files with 1074 additions and 46 deletions

View file

@ -2,12 +2,13 @@
id: F-0003
type: framework-finding
class: FRAMEWORK_LIMITATION
status: open
status: resolved
discovered: "2026-08-22"
discovered_by: TD-WP-0002-T06
workplan: TD-WP-0002
task: TD-WP-0002-T06
carried_to: TD-WP-0002-T10
resolved: "2026-08-23"
resolved_in: TD-WP-0002-T10
---
# F-0003 — Actor isolation is only observable if the scenario plants canaries
@ -55,9 +56,31 @@ system.
Worth stating plainly rather than counting four green self-tests as four
equivalent proofs. They are not equivalent.
## Candidate resolutions
## Resolution (T10)
Not resolved now; deciding cheaply here would be guessing.
Candidate 3 — **both**.
Every `Actor` is seeded at construction with an automatic private marker
(`Actor.canary`), and `Runner._isolation_violations` examines every actor on
**every** scenario, recording the verdict as S3 evidence. An isolation violation
now leaves a trace whether or not anyone thought to look for one.
Two permanent regressions stand behind it:
- `tests/test_reference_scenario.py::test_every_run_records_a_verdict_on_isolation`
- `tests/selfverification/test_checks_can_fail.py::test_a_leak_is_caught_without_the_test_planting_anything`
— an actor holding another's marker is caught by the ordinary run, with the
harness planting nothing.
The second limitation stands as recorded: oracle independence is enforced by
construction, so it is verified once rather than per run. That asymmetry is real
and is now stated in the fitness map rather than hidden behind two equally green
self-tests.
This finding closed the first ConceptImplementation Fitness Loop — see
`history/2026-08-23-td-wp-0002-gate-review.md` § 4.
## Candidate resolutions considered
1. **Automatic canaries** — the runtime seeds each actor with a unique private
marker at construction and the isolation check runs on every Evidence Pack,