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

Document rapp-openbao compatibility handoff
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source
This commit is contained in:
codex 2026-07-26 10:39:40 +02:00
parent 963b1caceb
commit 09c6e41caa
6 changed files with 131 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

14
workplans/RAILIANCE-WP-0012-rapp-openbao-extraction-boundary.md
View file

@ -4,11 +4,11 @@ type: workplan
title: "rapp-openbao extraction boundary"
domain: financials
repo: railiance-platform
status: active
status: finished
owner: codex
topic_slug: railiance
created: "2026-07-25"
updated: "2026-07-25"
updated: "2026-07-26"
state_hub_workstream_id: "6ec5f317-e6c6-48e8-a7d4-850c13541641"
---
@ -104,7 +104,7 @@ lane governance, delegated automation, credential grants, and SSH signing.
```task
id: RAILIANCE-WP-0012-T04
status: wait
status: done
priority: medium
state_hub_task_id: "25bf2d11-4a85-4259-9027-79768a23a06c"
```
@ -116,6 +116,14 @@ current operators or losing source-of-truth clarity inside `railiance-platform`.
Done when the future package extraction can start from a stable boundary.
2026-07-26: Added `docs/rapp-openbao-compatibility-handoff.md` to define the
current migration-window split: `rapp-openbao` is now the canonical home for
package-owned deploy/overlay/smoke assets, while `railiance-platform` retains
bootstrap, policy, credential-lane governance, and authenticated verification.
`docs/rapp-openbao-boundary.md`, `docs/openbao.md`, and `SCOPE.md` now point to
that split explicitly, so current operators can keep using temporary platform
copies without losing source-of-truth clarity.
## Notes
This workplan is repo-local. The framework-level sequencing stays in