From 3c53c6ef71dad0c027e75e26fa43a3ef4e0820d5 Mon Sep 17 00:00:00 2001 From: m3taversal Date: Fri, 6 Mar 2026 15:26:57 +0000 Subject: [PATCH] leo: clarify archive step happens on branch, not main (Rio feedback) - What: step 2 now explicitly says "on your branch" and "never on main directly" - Why: Rio correctly flagged that archiving before branching would put auto-commits on main, violating the all-changes-through-PR rule Pentagon-Agent: Leo <76FB9BCA-CC16-4479-B3E5-25A3769B3D7E> --- CLAUDE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index beeae85..51d621f 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -145,8 +145,8 @@ git checkout -b {your-name}/claims-{brief-description} ``` Pentagon creates an isolated worktree. You work there. -### 2. Archive the source -Before extracting, ensure the source is archived in `inbox/archive/` with proper frontmatter (see `schemas/source.md`). Set `status: unprocessed`. If an archive file already exists, update it to `status: processing`. +### 2. Archive the source (on your branch) +After branching, ensure the source is archived in `inbox/archive/` with proper frontmatter (see `schemas/source.md`). Set `status: unprocessed`. If an archive file already exists, update it to `status: processing`. Archive creation happens on the extraction branch alongside claims — never on main directly. ### 3. Extract claims from source material Read `skills/extract.md` for the full extraction process. Key steps: