diff --git a/templates/planning.yml b/templates/planning.yml
index 53322e5..3fff7fe 100644
--- a/templates/planning.yml
+++ b/templates/planning.yml
@@ -56,6 +56,26 @@ steps:
       No ambiguous assignments. No placeholder names.
       Do NOT invent task type names. Each task_type MUST appear verbatim in the TEAM ROSTER.
 
+      BOARDROOM RULE:
+        - When the request is for a strategic debate, a structured discussion, a decision-making
+          session, or a formal deliberation WITHOUT producing new content artifacts, create ONE task:
+            task_type: boardroom, agent: Selene, priority: 1
+        - boardroom tasks are purely deliberative — no research, no content output.
+        - Example triggers: "convene a boardroom", "debate strategy", "decide on priorities",
+          "executive discussion", "formal boardroom session", "strategic review"
+        - Do NOT create book_research, blog_research, or any other content pipeline task
+          for a boardroom request. ONE boardroom task only.
+
+      NO-RE-PIPELINE RULE:
+        - CRITICALLY IMPORTANT: If the project history above shows that book_research,
+          book_outline, ai_article_research, blog_research, recipe_collection_plan, or
+          short_story tasks have already been created for this project, do NOT create them again.
+        - Check the HISTORY section above. If any content pipeline tasks are listed as
+          InProgress, Completed, or AdjudicationPending, the pipeline is already running.
+        - For an in-flight project, only create tasks that are genuinely missing: editorial
+          review (book_editorial), boardroom deliberations, or quick answers.
+        - NEVER restart a research or outline pipeline mid-flight.
+
       BOOK/FICTION SEQUENCING RULE:
         - For novels and books, the pipeline is: book_research → book_outline → book_chapter (×N) →
           chapter_review (×3 per chapter) → chapter_roundtable → chapter_polish → book_editorial → project_index