coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Close backup handoff task

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-05 16:27:59 +02:00
parent 4eae6abe39
commit 88f84ab33a
2 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
SCOPE.md
View File

@@ -163,7 +163,8 @@ lessons into reusable S5 app release patterns.
the app-side workflow behavior still needs explicit S5 readiness docs. the app-side workflow behavior still needs explicit S5 readiness docs.
- App-level backup and restore responsibilities need clearer handoff contracts - App-level backup and restore responsibilities need clearer handoff contracts
with `railiance-platform`, especially for shared CNPG databases consumed by with `railiance-platform`, especially for shared CNPG databases consumed by
S5 apps. S5 apps. Forge artifact restore and secret-custody evidence is defined in
`/home/worsch/railiance-forge/docs/backup-restore-secret-handoff.md`.
--- ---

10
workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md
View File

@@ -273,7 +273,7 @@ now point at that contract from their scope/intent docs.
```task ```task
id: RAILIANCE-WP-0006-T07 id: RAILIANCE-WP-0006-T07
status: todo status: done
priority: high priority: high
state_hub_task_id: "da8bfbab-4bc3-48f0-9837-acf43fec9f0c" state_hub_task_id: "da8bfbab-4bc3-48f0-9837-acf43fec9f0c"
``` ```
@@ -293,6 +293,14 @@ Cover:
Done when the forge repo can state exactly what it owns, what S3 implements, Done when the forge repo can state exactly what it owns, what S3 implements,
and what evidence consumers can rely on. and what evidence consumers can rely on.
Completed 2026-06-05: the detailed handoff contract now lives in
`/home/worsch/railiance-forge/docs/backup-restore-secret-handoff.md`. It
defines forge asset inventory, database/package blob restore gates,
railiance-platform handoffs for CNPG, object storage, OpenBao, and runtime
secret delivery, allowed versus forbidden operator references, SOPS/age
bootstrap boundaries, and how S5 apps cite forge artifact restore evidence
without owning registry credentials or package backup procedures.
--- ---
## T08 - Add forge observability and operating evidence requirements ## T08 - Add forge observability and operating evidence requirements