Reject lossy observations and validate schedules before execution
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e76f-be98-7ae3-965d-e0b31290a4c4
This commit is contained in:
parent
eaf5d348e4
commit
10077edb8c
8 changed files with 184 additions and 21 deletions
|
|
@ -105,3 +105,16 @@ experiment records. The scope update and local implementation do not close those
|
|||
validation gaps.
|
||||
|
||||
Decision: `f3b35dce-6047-4a95-8083-4d7032d4e99f`.
|
||||
|
||||
|
||||
## Evidence/preflight correction — 2026-09-28
|
||||
|
||||
A subsequent review reproduced tuple-to-list conversion changing an oracle result
|
||||
on receipt replay, and a late unknown actor causing failure after earlier SUT
|
||||
mutations. The follow-up under TD-WP-0004-T02/T03 rejects non-JSON-native snapshots
|
||||
before judgment, retains a safe evidence-failure receipt with pending assertions
|
||||
INCONCLUSIVE, and validates the whole schedule/cast before execution. This closes
|
||||
the reproduced cases without changing claim definitions or expanding pilot scope.
|
||||
|
||||
Follow-up validation: **440 tests passed** in 169.07 seconds, including 12 new
|
||||
regressions (10 reproduced failures before implementation).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue