From 5d852b76b0b7e01eaa2ed3b0e1a522bd078622f3 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Fri, 4 Sep 2026 00:28:50 +0200 Subject: [PATCH] Warn that evidence.jsonl edits are silently reverted The existing rule said evidence.jsonl is an export surface rather than the direct-write API, which is true but understates the failure. A hand edit does not fail loudly; it survives until the next add-evidence regenerates the file from the CultCache evidence document and restores whatever was removed. An agent compacting the ledger would see a clean result, commit it, and have it silently undone by the next append. Say so where the rule already lives, since AGENTS.md is read before anyone reaches the store. Co-Authored-By: Claude Opus 5 --- AGENTS.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index a9b1e76..668d0d6 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -20,7 +20,11 @@ inside another project. subgoal. - Treat `state/evidence.jsonl` and `state/branches.json` as readable export surfaces during the persistence migration, not as the long-term direct-write - API. + API. A direct write to either is silently reverted: every `add-evidence` + regenerates `evidence.jsonl` from the CultCache evidence document, so edits + and deletions that do not go through `tools/ghostlight_state_store.py` look + applied until the next append restores what you removed. Compaction means + deleting from the store and letting the export follow. - Treat `state/evidence.jsonl` as the distilled durable ledger of what was learned, verified, rejected, or accepted. - Treat `notes/ghostlight-implementation-plan.md` as the current implementation