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

docs: cite RMASTER-WP ids for railiance-master workplans

Browse source
This commit is contained in:
codex 2026-08-14 14:29:19 +02:00
parent 917d3a1687
commit 6e744b0adb
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -127,4 +127,4 @@ copies without losing source-of-truth clarity.
## Notes ## Notes
This workplan is repo-local. The framework-level sequencing stays in This workplan is repo-local. The framework-level sequencing stays in
`railiance-master/workplans/RAILIANCE-WP-0017-rail-rapp-reef-repo-separation.md`. `railiance-master/workplans/RMASTER-WP-0017-rail-rapp-reef-repo-separation.md`.

2
workplans/RAILIANCE-WP-0015-platform-rapp-consistency.md
View file

@ -37,7 +37,7 @@ conforms, and to supply the platform-service reference shape.
Surveyed 2026-08-11 against the live cluster and all six family repos. Surveyed 2026-08-11 against the live cluster and all six family repos.
The concepts are in better shape than their enforcement. The four families are The concepts are in better shape than their enforcement. The four families are
cleanly defined and `RAILIANCE-WP-0018`/`WP-0019` in `railiance-master` are both cleanly defined and `RMASTER-WP-0018`/`RMASTER-WP-0019` in `railiance-master` are both
`finished`. Nothing, however, validates a declaration file, so the model has `finished`. Nothing, however, validates a declaration file, so the model has
been drifting quietly since the first wave. been drifting quietly since the first wave.