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

docs: record dark deployment preflight

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a028f0-a42f-7582-89a8-ebaad7343834
This commit is contained in:
tegwick 2026-08-22 15:05:23 +02:00
parent 0941a2e5f4
commit 01fb7ecdda
3 changed files with 92 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/production-cutover-plan.md
View file

@ -26,6 +26,19 @@ State Hub rows.
| 6. Stabilize | Nexus | two successful daily fires and one Monday with weekly flood at zero | return façade flags to State Hub |
| 7. Retire | Nexus | retention decision and final backup | restore retained State Hub snapshot store during window |
## Dark deployment placement
The application is packaged separately as `rapp-sbom-nexus` and remains a
private `rail-kubernetes` workload on `reef-railiance`. The application image
is built from this repository and pinned by digest in the package.
`platform-pg` is at its declared four-consumer ceiling. The reviewed database
handoff therefore targets the named `platform-pg-2` overflow cell rather than
quietly exceeding that ceiling. `apps-pg` still has one declared slot, but its
current consumer flow uses static application credentials; SBOM Nexus requires
the canonical OpenBao runtime/migration lease split. The database owner must
admit and provision the overflow consumer before the dark apply.
## Contract ownership
### SBOM Nexus