From 5c44e3ef41efd7a5b63ce05fd9d2b85bebfa8161 Mon Sep 17 00:00:00 2001
From: reachableceo <charles@turnsys.com>
Date: Tue, 11 Aug 2026 19:50:16 -0500
Subject: [PATCH] =?UTF-8?q?docs(agents):=20clarify=20questions-v(N).md=20v?=
 =?UTF-8?q?ersioning=20=E2=80=94=20increment=20on=20each=20answer=20round?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

💘 Generated with Crush

Assisted-by: Crush:glm-5.2
---
 AGENTS.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/AGENTS.md b/AGENTS.md
index 87b3b07..413839a 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -130,7 +130,10 @@ docker run --rm --env-file ~/.creds/discourse.env \
   harness. Not portable, not version-controlled, bypasses the git record.
   Non-negotiable. (See `BASELINE-PROMPT.md` §10.)
 - **All questions go in the git-tracked `questions-v(N).md` file.** The
-  human edits the answer inline in the same file; version up per round.
+  human edits the answer inline in the same file. **Version up the filename
+  each time answers land** (v1 → v2 → v3...): create `questions-v2.md`
+  with resolved Q&A marked, new questions appended. This preserves the
+  history of each Q&A round.
 - Capture questions for the human in a git-tracked `questions-v(N).md` file.
 - The human reviews and edits it inline. Version up when a round of answers lands.
 - Questions, answers, and the reasoning behind decisions are often more important than the code. Synthesize resolved Q&A into Discourse (decisions) and Redmine (work items).