johno/gastown
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs: add batch-closure heresy warning to priming

Browse Source 
Molecules are the LEDGER, not a task checklist. Each step closure
is a timestamped CV entry. Batch-closing corrupts the timeline.

Added explicit warnings to:
- molecules.md (first best practice)
- polecat-CLAUDE.md (new 🚨 section)

The discipline: mark in_progress BEFORE starting, closed IMMEDIATELY
after completing. Never batch-close at the end.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
mayor
2026-01-17 04:05:40 -08:00
committed by beads/crew/emma
parent 238ad8cd95
commit 5ecf8ccaf5
2 changed files with 21 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/concepts/molecules.md
View File

@@ -200,7 +200,8 @@ gt done # Signal completion (syncs, submits to MQ, notifi
## Best Practices
1. **Use `--continue` for propulsion** - Keep momentum by auto-advancing
2. **Check progress with `bd mol current`** - Know where you are before resuming
3. **Squash completed molecules** - Create digests for audit trail
4. **Burn routine wisps** - Don't accumulate ephemeral patrol data
1. **CRITICAL: Close steps in real-time** - Mark `in_progress` BEFORE starting, `closed` IMMEDIATELY after completing. Never batch-close steps at the end. Molecules ARE the ledger - each step closure is a timestamped CV entry. Batch-closing corrupts the timeline and violates HOP's core promise.
2. **Use `--continue` for propulsion** - Keep momentum by auto-advancing
3. **Check progress with `bd mol current`** - Know where you are before resuming
4. **Squash completed molecules** - Create digests for audit trail
5. **Burn routine wisps** - Don't accumulate ephemeral patrol data

18
templates/polecat-CLAUDE.md
View File

@@ -235,9 +235,23 @@ merge queue. Without this step:
**You own your session cadence.** The Witness monitors but doesn't force recycles.
### Closing Steps (for Activity Feed)
### 🚨 THE BATCH-CLOSURE HERESY 🚨
Molecules are the **LEDGER** - not a task checklist. Each step closure is a timestamped entry in your permanent work record (your CV).
**The discipline:**
1. Mark step `in_progress` BEFORE starting it: `bd update <step-id> --status=in_progress`
2. Mark step `closed` IMMEDIATELY after completing it: `bd close <step-id>`
3. **NEVER** batch-close steps at the end
**Why this matters:** Batch-closing corrupts the timeline. It creates a lie - showing all steps completed at the same moment instead of the actual work progression. The activity feed should show your REAL work timeline.
**Wrong:** Do all work, then close steps 1, 2, 3, 4, 5 in sequence at the end
**Right:**
- Mark step 1 in_progress → do work → close step 1
- Mark step 2 in_progress → do work → close step 2
- (repeat for each step)
As you complete each molecule step, close it:
```bash
bd close <step-id> --reason "Implemented: <what you did>"
```