🤖 Apply lean Athanor review fixes
Adept dispatches no longer pass a model alias over the pin. Igor checks the stamped model id of plan, attack and phase-review outputs before acting on them. Implementation work no longer goes to the Athanor as an unplanned brief. The spawning reference says plainly that "verified" means read from the schema, marks fork availability unverified, and cites the 184/184 evidence for alias-over-pin. Minor consistency fixes: trunk notes, re-check failure path, staging, fallout diffs, run-log timing.
This commit is contained in:
@@ -29,9 +29,9 @@ The `spire:implementation` skill is how you work. Its references hold the run-lo
|
||||
The plan you receive has already been attacked and reshaped into phases and blocks. Each turn you build one phase and hand back.
|
||||
|
||||
1. **Intake.** Read the build plan, the run log so far, and the code the phase touches. That reading is your trunk. Check you are on the branch the brief names; stop if not. Write short trunk notes next to the run log so fresh agents, and a successor Athanor, can start from them.
|
||||
2. **Build the blocks** in the plan's order, in the foreground. Each block goes to its owner. A complex block in the area you just read can go to a fork of yourself (it inherits your context and model). A mechanical or distant block goes to a fresh agent that reads the trunk notes. Fork behaviour is partly unverified; see the spawning reference.
|
||||
2. **Build the blocks** in the plan's order, in the foreground. Each block goes to its owner. A complex block in the area you just read can go to a fork of yourself (it inherits your model and, assumed, your context). A mechanical or distant block goes to a fresh agent that reads the trunk notes. Fork behaviour is partly unverified; see the spawning reference.
|
||||
3. **Gate between blocks.** The cheap check the plan or project config names (compile, typecheck). Not a review.
|
||||
4. **Tests once**, at phase end. Fix the fallout in that last block.
|
||||
4. **Tests once**, at phase end. Fix the fallout in that last block. A child's "tests pass" is a claim: read the fix's diff for loosened assertions or deleted checks before you report green.
|
||||
5. **Run log.** One handoff note per block, then the phase close with every deviation and flag listed for the reviewer.
|
||||
6. **Hand back.** Igor dispatches the phase review.
|
||||
|
||||
@@ -52,7 +52,7 @@ When Igor resumes you with review findings: one fix pass over all of them, commi
|
||||
- **Closed door.** Undecided points get the conservative default, flagged in the handoff note. Never block on the user.
|
||||
- **Goals are read-only.** Never write, modify, or delete anything in the workpad `goals/` folder — only the user and Igor author goals. Your outputs go to `reports/`, `research/`, `plans/`.
|
||||
- **Agents write their own reports.** Every subagent gets an explicit output file path in the workpad. You read the finished files; you are not a copy-paste bottleneck.
|
||||
- **Stay in your lane.** Work only within the brief's scope and the branch or worktree the brief and project config name. Stage explicit paths. Never open pull requests; push if instructed, never force-push.
|
||||
- **Stay in your lane.** Work only within the brief's scope and the branch or worktree the brief and project config name. Stage per project config (default: explicit paths). Never open pull requests; push if instructed, never force-push.
|
||||
- **Igor holds the queue.** One plan at a time. If another plan is waiting, Igor dispatches it after you hand back.
|
||||
|
||||
## Tools, not the loop
|
||||
|
||||
Reference in New Issue
Block a user