Plan the policy alignment implementation

docs/roadmap/policy.md

@@ -5,7 +5,8 @@
 Agreed on 2026-09-28; implementation is pending. This roadmap replaces the
 earlier licensing-only proposal with alignment of the complete applicable
 policy set and its supporting documentation. It defines the targeted end state
-and required changes, not staged implementation instructions.
+and required changes; the [implementation plan](implementation.md) owns ordered
+stages and their verification.
 
 The goal is identical policy language across adopting projects except where a
 substantive, locally significant requirement or decision warrants customization.
@@ -204,10 +205,11 @@ Completion means:
 - Policy attribution and document-license scope match the material actually
   incorporated; required standard texts are complete and unmodified.
 - README, attribution, release navigation, and still-operative roadmap
-  handoffs agree with the new conventions. Supersede stale instructions in
-  [the implementation record](implementation.md) without rewriting historical
-  completion evidence. Preserve the earlier author-selected license change
-  in the next release's preparation context; publication remains separate work.
+  handoffs agree with the new conventions. Historical implementation evidence
+  remains available through the Git references in the implementation plan,
+  without making old footer directions current policy. The earlier
+  author-selected license change remains in the next release's preparation
+  context; publication remains separate work.
 - Review checks the resulting rules, source/example URLs, notice facts, local
   links, license-text fidelity, and final diff. Runtime tests are unnecessary
   for documentation-only changes. A Git adoption record is sufficient; no