From c02224df647e249653da6e3aa20fd471c708b728 Mon Sep 17 00:00:00 2001
From: "marcin p. joachimiak" <4625870+realmarcin@users.noreply.github.com>
Date: Mon, 24 Aug 2026 09:45:52 -0700
Subject: [PATCH] Add fact-based-answers discipline to CLAUDE.md

Direct user request after a separate session presented an unverified
comparison as fact and had to redo the analysis. Mirrors the same
section added to culturebotai-claw's CLAUDE.md in PR #128, adapted here
to reference this repo's own stale-tracker pitfall (issue #669's
P0/P1/P2 checklist) instead of the multi-repo staleness case that only
applies to the orchestrator.
---
 CLAUDE.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/CLAUDE.md b/CLAUDE.md
index 5277f422..ac657ad9 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -24,6 +24,29 @@ Before changing anything:
 - Do not make network calls, spend provider credits, or apply generated curation
   unless the task authorizes it.
 
+## Fact-based answers only
+
+Never state a comparison, count, status, or historical claim without having
+verified it in the current conversation via a tool call (`gh`, `git`, `grep`,
+`Read`, etc.). "I recall," "this is typically the case," or a prior summary
+are not verification -- the KB, issue tracker, and generated artifacts change
+between turns and across concurrent sessions.
+
+- Prefer a live check over memory: `gh api`/`gh issue view`/`gh pr view` over
+  a remembered issue list; `git log`/`git blame` over a recalled commit; a
+  fresh `Read` of a `kb/communities/` or `kb/taxa/` record over trusting an
+  earlier read of the same file.
+- Tracking issues with checklists (for example #669) record priority and
+  sequencing, not current state -- their sub-issue checkboxes and P0/P1/P2
+  counts move as work lands. Re-fetch with `gh issue view` before citing what
+  is open, closed, or "done" rather than repeating a count from earlier in
+  the conversation.
+- If a claim can't be verified this session, say so ("I did not check X" /
+  "I don't know") instead of presenting a plausible guess as fact.
+- Re-verify rather than repeat: restating an earlier claim in this same
+  conversation without re-checking it is exactly the failure mode this rule
+  exists to prevent.
+
 ## Canonical and generated files
 
 | Path | Role | Editing rule |