Answer architecture round 1: 0 🔴, 1 🟡 (0 misread); record in item 410 that do-epic's cycles name do-epic
This commit is contained in:
@@ -121,7 +121,7 @@ Touches:
|
||||
|
||||
### 410. Run `do-epic <EPIC-KEY>`: one tmux session per epic, a window per chunk, up to the epic's cap of running chunks and each repo's `parallel-chunks`, and never in a repo a loop-claude is running chunks in.
|
||||
|
||||
The lock that keeps do-epic and loop-claude apart is the per-project `starting` flock, shared by both (`docs/decisions.md` → `do-epic: drives one Jira epic …`). Each chunk routes on its repo's model and ladder, a no-repo chunk on the machine setting's model. `loop/chunk_windows.py` `start_chunks` is a place the seats found hard: make it easier to read where it changes.
|
||||
The lock that keeps do-epic and loop-claude apart is the per-project `starting` flock, shared by both (`docs/decisions.md` → `do-epic: drives one Jira epic …`). Each chunk routes on its repo's model and ladder, a no-repo chunk on the machine setting's model. `loop/chunk_windows.py` `start_chunks` is a place the seats found hard: make it easier to read where it changes. Where a do-epic cycle's worker, judge or human reads the driver's name, they read do-epic, never loop-claude: item 401 left `agent_cycle`'s own text naming loop-claude, since whether the markers that code matches (`TYPED_HERE`, `TRANSCRIPT_HEADING`) vary by driver depends on what do-epic calls itself and where it archives its cycles. The worker's prompt and the judge's rules share the phrase a worker asks for a higher rung with, so both take it from one place.
|
||||
|
||||
Touches:
|
||||
|
||||
@@ -130,6 +130,11 @@ Touches:
|
||||
- `bin/do-epic`
|
||||
- `bin/do_epic/main.py`
|
||||
- `bin/do_epic/scheduler.py`
|
||||
- `bin/agent_cycle/worker_prompts.py`: `TYPED_HERE`, `stepped_to` (small)
|
||||
- `bin/agent_cycle/judge.py`: `TRANSCRIPT_HEADING`, `Reply.escalation` (small)
|
||||
- `bin/agent_cycle/escalation_mark.py`: `STEP_LINE` (small)
|
||||
- `bin/agent_cycle/interrupt.py` (small)
|
||||
- `bin/agent_cycle/stop.py` (small)
|
||||
|
||||
### 416. Finish an epic's repo item with a bullet under its repo's `CHANGELOG.md` → `## Unreleased`, or with none where the repo's plan is in Jira.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user