This is an automated email from the ASF dual-hosted git repository. spmallette pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
commit cc24d55ce3dfbe3dbc5422ba071307262cefc579 Author: Stephen Mallette <[email protected]> AuthorDate: Fri Aug 7 19:46:01 2026 -0400 Number the core rules as section 0 and cite them from the phases The index claimed to name every section but core rules sat outside it. Numbering it 0 closes that, and the entry now names the rules rather than saying to apply them -- with a note that it is not a step, since a 0-7 list otherwise reads as a sequence to work through. Assisted-by: Claude Code:claude-opus-5 --- .beads/PRIME.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.beads/PRIME.md b/.beads/PRIME.md index fce3c9bda8..d8485dbd26 100644 --- a/.beads/PRIME.md +++ b/.beads/PRIME.md @@ -10,6 +10,7 @@ survive context compaction. An index. Each line names a section; **the section is the rule, and the section holds the exceptions.** Do not act on a line here without reading it. +0. **Think in graph; capture every road not taken — throughout, not a step** — section 0 1. **Bind to a root bead before you write code** — section 1 2. **Plan the work with the operator as a dependency graph** — section 2 3. **Claim before editing, close as work finishes** — section 3 @@ -20,7 +21,7 @@ exceptions.** Do not act on a line here without reading it. --- -## Core rules +## 0. Core rules These hold throughout — while planning with the operator and while executing. @@ -101,7 +102,7 @@ Re-ask after a compaction rather than guessing. ## 2. Plan as a graph, not a list The plan is built **with the operator**; what you weigh and reject while building it is -captured as you go, not once you start executing. +captured as you go (section 0), not once you start executing. Tasks are not a checklist. Wire the order between them so the graph itself says what can run in parallel. @@ -136,7 +137,8 @@ the beads graph for review. ## 3. While working — claim, then close -Adjusting the plan mid-flight is normal — section 2 applies again when you do. +Adjusting the plan mid-flight is normal — section 2 applies again when you do, and section 0 +applies the whole time. **Before you touch code for a bead, claim it. Every time, no exceptions:**
