Lease-watch verdict must check what it claims
Version 3 reported 'survived past the lease TTL' after a clean 12-minute window on a 13-minute-old pod. Every measurement in it was accurate; the conclusion was not, because nothing checked that the observation window had actually exceeded the 30-minute lease it claimed to have outlasted. Fifth defect in this instrument, and the first to err toward reassurance. Versions 1 and 2 cried wolf, which provokes investigation. This one would have been believed, and readiness_state: verified recorded on it — the same way live-image-digest-match would have been believed. A check reporting success it has not established is indistinguishable from one that works, until it matters. The verdict now requires uptime > lease TTL and reports INCONCLUSIVE when a window is clean but too short. 'Clean' and 'proven' are different claims and only one of them was being measured. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bjefh8NUiEiahN4JLwoSKM Assistant: claude-code Assistant-Model: opus Assistant-Process: 388925@bnt-lap001 Assistant-Session: 3507023f-e0fd-4a1e-9d90-a0d4217d1502
This commit is contained in:
parent
bd5ee3dfbb
commit
bdbef58259
8 changed files with 55 additions and 12 deletions
|
|
@ -16,5 +16,5 @@
|
|||
| task | RCP-WP-0002-T01 | done | — | workplans/RCP-WP-0002-first-deployment.md |
|
||||
| task | RCP-WP-0002-T02 | done | — | workplans/RCP-WP-0002-first-deployment.md |
|
||||
| task | RCP-WP-0002-T03 | done | — | workplans/RCP-WP-0002-first-deployment.md |
|
||||
| task | RCP-WP-0002-T04 | progress | — | workplans/RCP-WP-0002-first-deployment.md |
|
||||
| task | RCP-WP-0002-T04 | done | — | workplans/RCP-WP-0002-first-deployment.md |
|
||||
| task | RCP-WP-0002-T05 | wait | — | workplans/RCP-WP-0002-first-deployment.md |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue