Complete local generalisation tasks and document remaining experiment blockers
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e76f-be98-7ae3-965d-e0b31290a4c4
This commit is contained in:
parent
d54af628df
commit
cf682281d7
36 changed files with 5394 additions and 279 deletions
|
|
@ -61,3 +61,18 @@ relayout is untested.
|
|||
|
||||
- 2026-08-22 `PROPOSED`. No evidence.
|
||||
- 2026-08-22 `EXPERIMENTING`. Partial evidence from T07; awaiting E-001 in full.
|
||||
|
||||
## Expanded measurement — 2026-09-28 (TD-WP-0003-T03)
|
||||
|
||||
38 mutations, including ten that drop test ids and seven new paired structural
|
||||
controls. Discovery and recorded selectors both pass 17/17 preserved-id cases;
|
||||
on dropped ids discovery passes 9/10 and recorded selectors 0/10. M22 remains
|
||||
unrealizable. The full journey accepts 26/27 mechanical cases; FAR remains 0/7
|
||||
on the unchanged defect set. Claim/provenance indices remain unchanged.
|
||||
|
||||
Reproduce: `PYTHONPATH=src:. python3 tools/measure_e001.py /tmp/e001.json`.
|
||||
[Raw result](../evidence/2026-09-28-e001.json).
|
||||
These selected and correlated synthetic HTML cases do not establish population
|
||||
reliability, visual/browser coverage, model capability or economics. See
|
||||
[review](../../docs/TestDriverGeneralisationReview.md) for the mechanism list and
|
||||
limits. H-001 remains supported only in the narrowed identifier-loss setting.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
id: H-005
|
||||
title: Verification Energy
|
||||
status: PROPOSED
|
||||
status: DORMANT-INDEFINITE
|
||||
created: "2026-08-22"
|
||||
experiments: []
|
||||
concepts: [C-energy]
|
||||
|
|
@ -28,9 +28,9 @@ dormant.** Validating it requires event history across many assets over months
|
|||
history the spike will not accumulate. Implementing a scoring function now would
|
||||
produce a number that cannot be checked, which is worse than no number.
|
||||
|
||||
`TD-WP-0002` therefore records **raw immutable `EnergyEvent`s from the first run**
|
||||
and implements no scoring, decay, or selection logic. Events cannot be
|
||||
reconstructed later; scores can always be computed later.
|
||||
`TD-WP-0002` recorded raw events, but no decision used them. TD-WP-0003-T04
|
||||
removed capture and scoring concepts on 2026-09-28. Ordinary run evidence and
|
||||
verdicts remain; no energy history is promised for future reconstruction.
|
||||
|
||||
This is the hypothesis most likely to be **cheaply built and never validated**,
|
||||
which is precisely why it is fenced off.
|
||||
|
|
@ -38,3 +38,5 @@ which is precisely why it is fenced off.
|
|||
## Status log
|
||||
|
||||
- 2026-08-22 `PROPOSED`, dormant by decision. Event capture only.
|
||||
|
||||
- 2026-09-28 `DORMANT-INDEFINITE`. Capture removed; no new implementation gate.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue