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

refactor: Nuanced refinery context heuristic - 20 simple or immediate on complex (gt-nqrh)

Browse Source 
Most MRs are button-pushes (clean rebase + push). Only complex rebases
(conflicts, test failures) consume significant context.

- 20 simple MRs before handoff
- Immediate handoff after any complex rebase

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Steve Yegge
2025-12-23 14:11:40 -08:00
parent 366d3c8ca7
commit d823ced14c
1 changed files with 32 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
internal/templates/roles/refinery.md.tmpl
View File

@@ -163,43 +163,49 @@ atop the new baseline.** This is non-negotiable.
--- ---
## State Files ## Context Management
| File | Purpose | **Heuristic**: Hand off after **20 simple MRs** OR **immediately** after any complex rebase.
|------|---------|
| `{{ .WorkDir }}/state.json` | Patrol tracking and merge counts | Most MRs are trivial:
- Clean rebase (no conflicts)
- Tests pass
- Fast-forward merge + push
These consume minimal context. But complex rebases are different:
- Reading conflict diffs
- Understanding competing changes
- Manual resolution decisions
- Re-running tests after fixes
**Simple MR** (count toward 20):
- `git rebase origin/main` succeeds without conflicts
- Tests pass on first run
**Complex MR** (triggers immediate handoff):
- Rebase has conflicts requiring manual resolution
- Tests fail and require investigation
- Multiple rebase attempts needed
**state.json format:** **state.json format:**
```json ```json
{ {
"merges_processed": 0, "simple_merges": 0,
"last_patrol": "2025-12-23T13:30:00Z", "complex_merge": false,
"conflict_resolutions": 0 "last_patrol": "2025-12-23T13:30:00Z"
} }
``` ```
---
## Context Management
**Heuristic**: Hand off after processing **7 merge requests**.
Merge requests are context-heavy:
- Reading branch diffs
- Resolving conflicts
- Running tests
- Composing notifications
**At burn-or-loop step:** **At burn-or-loop step:**
1. Read `state.json` for `merges_processed` 1. Read `state.json` for `simple_merges` and `complex_merge`
2. If `merges_processed >= 7` → hand off 2. If `complex_merge == true` → hand off immediately
3. Otherwise → continue patrol, spawn new wisp 3. If `simple_merges >= 20` → hand off
4. Otherwise → continue patrol, spawn new wisp
**Rationale**: Merges consume significant context - each involves reading diffs, **Rationale**: A clean rebase is a button-push. A conflict resolution fills context
understanding changes, and sometimes resolving conflicts. A Refinery that has with diffs, decisions, and debugging. Fresh context handles the next conflict better.
processed 7 MRs has filled substantial context.
**Handoff command:** `gt handoff -s "Patrol cycle" -m "Processed N merges"` **Handoff command:** `gt handoff -s "Patrol cycle" -m "Processed N simple merges"`
--- ---