forked from mosaicstack/stack
mos-dt-0andClaude Opus 5
bdf8932328
Condition 1 tested: the signature is stable — pods "wp-svc-<ULID>-ci-postgres" not found across all five observed failures, an orchestration-layer lookup miss structurally unlike a service-level failure. But discrimination is UNPROVEN: every observation co-occurs with a demonstrably working database, and we have never seen a real ci-postgres failure on this provider. If PostgreSQL crashes and the pod is GC'd, the status query may also return pod-not-found — the exemption would over-match and mask a real failure. So conditions 1 and 2 are not independent: 2 is the evidence for 1. Build the negative control first, prove a real failure produces a different signature, then adopt the exemption. Kill criterion stated in advance: if an injected real failure also yields pod-not-found, B is unsafe and we do A. Filed as RM-61, unassigned — no free write-capable seat; flagged rather than stacked onto a busy lane. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>