diff --git a/README.md b/README.md
index 52272d6..705e9e6 100644
--- a/README.md
+++ b/README.md
@@ -191,9 +191,14 @@ nothing.
 
 ### The rules
 
-- **Milestone = batch.** Name it `0.2 Payments`. The description says what the
-  batch is for and how anybody will know it landed. A due date means a
-  commitment — leave it empty rather than inventing one.
+- **Milestone = batch.** Name it `Batch 02 — Payments`, and **start it with a
+  word rather than a version number**: the dashboard reads a leading version
+  token as the whole phase and drops the rest, so `0.2 Payments` displays as
+  `0.2` and the batch loses its name on the project card. No comma either — a
+  comma breaks the `milestones=` filter and the card shows the wrong next
+  action. The description says what the batch is for and how anybody will know
+  it landed. A due date means a commitment — leave it empty rather than
+  inventing one.
 - **Issue = deliverable.** One per item, in its milestone, ending with a
   `Verify:` line stating the acceptance check.
 - **Labels:** `P0` ships broken or loses data · `P1` materially wrong but
diff --git a/docs/WORK_CYCLE.md b/docs/WORK_CYCLE.md
index 4122746..e454875 100644
--- a/docs/WORK_CYCLE.md
+++ b/docs/WORK_CYCLE.md
@@ -76,6 +76,14 @@ Monday, specific enough to begin without asking a question. "Continue the work"
 is not one. If the honest answer is that you do not know, that is a real answer —
 say what has to be decided and by whom.
 
+**Filing an issue can change what the project card says next, without anyone
+choosing that.** The dashboard's next action is the *newest open issue in the
+current milestone* — not the most severe one; severity labels have no influence
+on it at all. So a routine `P2` filed into the batch you are working in replaces
+whatever the card was showing, and it will keep showing that until something
+newer arrives. The `nextAction` field is the only way to say something different
+on purpose, which is most of why step 7 exists.
+
 `currentSummary`, `nextAction` and `description` are **write-only**: they are
 deliberately absent from every API response, because free text can name a
 customer or an unannounced product. Only the admin screen shows them back. Never