coulomb/reef-railiance
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Promote Qonto reef binding to verified

Browse source
This commit is contained in:
codex 2026-07-29 23:13:35 +02:00
parent 4a783664a6
commit 85e35b1a7c
3 changed files with 15 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

13
workplans/REEF-RAILIANCE-WP-0003-rapp-qonto-production-gates.md
View file

@ -8,7 +8,7 @@ status: active
owner: codex
topic_slug: railiance
created: "2026-07-26"
updated: "2026-07-27"
updated: "2026-07-29"
state_hub_workstream_id: "c3f9fbfd-3db1-4387-8b65-7d53ba57138d"
---
@ -76,7 +76,7 @@ runtime Kustomization and T02 is complete.
```task
id: REEF-RAILIANCE-WP-0003-T03
status: progress
status: done
priority: high
state_hub_task_id: "ddf25c7b-23b0-4e67-8881-5d29fa71e9ad"
```
@ -90,6 +90,15 @@ passed through the cluster-local Knative service. Full failure, revocation,
idempotency, timing, and rollback evidence is still required before T03 can
close.
2026-07-29: The reversible `rapp-qonto/tools/verify_live.sh` gate produced
machine-readable, secret-free evidence for scale-to-zero, 7.384443-second cold
activation, repeat health, ExternalSecret readiness, fail-closed dependency
loss, recovery, missing-secret denial, secret restoration, previous-revision
rollback, and latest-traffic restoration. The `qonto-assistant` owner suite
passes 80 tests covering domain-level audit, idempotency, authorization, and
redaction behavior. The reef binding is now `verified`, not
`production-approved`.
## T04 - Reassess production failure-domain risk
```task