diff --git a/workplans/RAILIANCE-WP-0012-rapp-openbao-extraction-boundary.md b/workplans/RAILIANCE-WP-0012-rapp-openbao-extraction-boundary.md
index 8dacbfe..76c86dc 100644
--- a/workplans/RAILIANCE-WP-0012-rapp-openbao-extraction-boundary.md
+++ b/workplans/RAILIANCE-WP-0012-rapp-openbao-extraction-boundary.md
@@ -127,4 +127,4 @@ copies without losing source-of-truth clarity.
 ## Notes
 
 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`.
diff --git a/workplans/RAILIANCE-WP-0015-platform-rapp-consistency.md b/workplans/RAILIANCE-WP-0015-platform-rapp-consistency.md
index 1eb0861..f8cd4fe 100644
--- a/workplans/RAILIANCE-WP-0015-platform-rapp-consistency.md
+++ b/workplans/RAILIANCE-WP-0015-platform-rapp-consistency.md
@@ -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.
 
 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
 been drifting quietly since the first wave.