Organize workspace policies by task

docs/roadmap/implementation-template.md

@@ -20,6 +20,8 @@ for scope, rationale, target end state, and acceptance criteria.
   zero-based, decimal, nested, or nonsequential stage identifiers.
 - Before each stage, confirm its preconditions and the working-tree state of
   its owning repository.
+- Before each stage, read every document listed in that stage's Required Policy
+  Review. Do not rely on policy recalled from an earlier stage.
 - Preserve unrelated and pre-existing changes.
 - Do not make unresolved product or architecture decisions during execution;
   stop and report the decision required.
@@ -52,6 +54,21 @@ for scope, rationale, target end state, and acceptance criteria.
 
 State the single outcome delivered by this stage.
 
+### Required Policy Review
+
+Before beginning this stage, read:
+
+- `AGENTS.md`
+- `docs/orientation.md`
+- `docs/conventions.md`
+- `<docs/ansible.md, docs/testing.md, and/or docs/planning.md as applicable>`
+
+Replace the placeholder with every specialized policy applicable to this
+stage. Include `docs/ansible.md` for Ansible design or implementation,
+`docs/testing.md` for test work, and `docs/planning.md` for workspace planning
+or progress management. Do not list an inapplicable policy merely for
+completeness.
+
 ### Preconditions
 
 - List facts that must be true before editing begins.

docs/roadmap/remediation.md

@@ -37,7 +37,7 @@ The directive remains in place. Unlike a desired-state module, the imperative
 build command must explicitly declare its change semantics for lint. The
 existing `when` expression still determines whether the command runs, and
 `changed_when: true` accurately reports that every executed build changes the
-binary. The distinction is now documented in `docs/conventions.md`.
+binary. The distinction is now documented in `docs/ansible.md`.
 
 ## Finding 3: Make the Dependency-Opt-Out Test Prove the Selected Go Binary
 

docs/roadmap/test-suite-audit.md

@@ -34,7 +34,7 @@ three completed standalone-role test suites.
 
 ## Governing Standard
 
-Apply the normative testing house style in `docs/conventions.md`. In
+Apply the normative testing house style in `docs/testing.md`. In
 particular, the audit will favor tests that exercise the role through its
 public variables and inspect meaningful final application behavior. It will
 disfavor tests that: