coulomb/rapp-canned-prompts
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rapp-canned-prompts/docs/evidence/RCP-WP-0002-T05-lease-rotation-2026-09-08.log

28 lines
1.1 KiB
Text
Raw Normal View History

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
2026-09-08 10:48:35 +02:00
started 2026-09-08T10:48:16+02:00 — 22m watch (runtime lease TTL 30m)
2026-09-08T10:48:17+02:00 ready=1/1
RCP-WP-0002 finished: publisher identity done, verified on a verdict that states its basis uptime 36m > lease TTL 30m, 21 samples, zero not-ready, zero query failures, zero kubelet readiness 503s, no restarts. The verdict now names the uptime it checked, so the claim can be audited rather than taken. T05 done upstream in canned-prompts 0.2.0 / migration 0003. DR-3 had already resolved the identity question as app-local accounts with OIDC demand-gated; research found that rather than my judgement supplying it. Left open deliberately: the NetworkPolicy ingress rule still admits any namespace. Publisher identity now gates writes so it is no longer the only control, and it should narrow once the legitimate callers are known — recorded rather than tightened on a guess. 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
2026-09-08 11:11:55 +02:00
2026-09-08T10:49:23+02:00 ready=1/1
2026-09-08T10:50:26+02:00 ready=1/1
2026-09-08T10:51:32+02:00 ready=1/1
2026-09-08T10:52:38+02:00 ready=1/1
2026-09-08T10:53:44+02:00 ready=1/1
2026-09-08T10:54:50+02:00 ready=1/1
2026-09-08T10:55:56+02:00 ready=1/1
2026-09-08T10:57:02+02:00 ready=1/1
2026-09-08T10:58:08+02:00 ready=1/1
2026-09-08T10:59:11+02:00 ready=1/1
2026-09-08T11:00:18+02:00 ready=1/1
2026-09-08T11:01:24+02:00 ready=1/1
2026-09-08T11:02:30+02:00 ready=1/1
2026-09-08T11:03:36+02:00 ready=1/1
2026-09-08T11:04:42+02:00 ready=1/1
2026-09-08T11:05:48+02:00 ready=1/1
2026-09-08T11:06:51+02:00 ready=1/1
2026-09-08T11:07:57+02:00 ready=1/1
2026-09-08T11:09:03+02:00 ready=1/1
2026-09-08T11:10:09+02:00 ready=1/1
finished 2026-09-08T11:11:16+02:00
samples=21 not_ready=0 query_failed=0
kubelet readiness 503s in window: 0 (probe every 5s)
pod started 2026-09-08T08:34:32Z, uptime=36m, restarts=0
RESULT: survived — continuously ready, uptime 36m > lease TTL 30m
Reference in a new issue Copy permalink