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

Record Qonto failure-domain blocker

Browse source
This commit is contained in:
codex 2026-07-30 00:52:54 +02:00
parent 85e35b1a7c
commit 0144bfff9e
2 changed files with 11 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
WORK-RECORDS.md
View file

@ -10,7 +10,7 @@
| --- | --- | --- | --- | --- |
| workplan | REEF-RAILIANCE-WP-0001 | finished | — | workplans/REEF-RAILIANCE-WP-0001-bootstrap-and-wave1-import.md |
| workplan | REEF-RAILIANCE-WP-0002 | finished | — | workplans/REEF-RAILIANCE-WP-0002-knative-and-qonto-production-admission.md |
| workplan | REEF-RAILIANCE-WP-0003 | active | — | workplans/REEF-RAILIANCE-WP-0003-rapp-qonto-production-gates.md |
| workplan | REEF-RAILIANCE-WP-0003 | blocked | — | workplans/REEF-RAILIANCE-WP-0003-rapp-qonto-production-gates.md |
| task | REEF-RAILIANCE-WP-0001-T01 | done | — | workplans/REEF-RAILIANCE-WP-0001-bootstrap-and-wave1-import.md |
| task | REEF-RAILIANCE-WP-0001-T02 | done | — | workplans/REEF-RAILIANCE-WP-0001-bootstrap-and-wave1-import.md |
| task | REEF-RAILIANCE-WP-0001-T03 | done | — | workplans/REEF-RAILIANCE-WP-0001-bootstrap-and-wave1-import.md |

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

@ -4,7 +4,7 @@ type: workplan
title: "Complete rapp-qonto production gates"
domain: financials
repo: reef-railiance
status: active
status: blocked
owner: codex
topic_slug: railiance
created: "2026-07-26"
@ -110,3 +110,12 @@ state_hub_task_id: "9d0c1f61-0ed8-4d5c-b4c2-2578424ad3b4"
Production approval requires mitigation or explicit acceptance of the
single-node/shared-control-plane risk after all automated workload gates pass.
2026-07-30 reassessment: the reef still exposes exactly one Ready Kubernetes
node (`239.62.205.92.host.secureserver.net`). All workload-level gates are
green, but no node or control-plane failure domain has been added. This is a
real infrastructure availability risk, not stale task bookkeeping. The
workplan is therefore `blocked` until either a second independent failure
domain is implemented and drilled or the founder explicitly accepts
single-node production availability risk for Qonto. The current binding
remains accurately `verified`, not `production-approved`.