fix: unify feedback routing tables across orchestration, act-phase, artifact-routing

This commit is contained in:
2026-04-04 07:32:47 +02:00
parent 6bc5e48357
commit 2247e52ae4
3 changed files with 27 additions and 17 deletions

View File

@@ -164,6 +164,8 @@ No agents are spawned in Act. The orchestrator reads all `check-*.md` artifacts
## Feedback Routing
> **This is the canonical routing table.** Other skills (orchestration, act-phase) must match this table exactly. When updating routing rules, update this table first, then sync the others.
When building `act-feedback.md` after the Check phase, route each finding to the right agent for the next cycle:
| Finding Source | Finding Category | Routes To | Rationale |
@@ -177,7 +179,7 @@ When building `act-feedback.md` after the Check phase, route each finding to the
| Trickster | reliability (test gap) | **Maker** | Needs more tests |
| Trickster | testing | **Maker** | Edge case not covered |
**Ambiguous cases:** If a Trickster finding could be either a design flaw or a test gap, check: does the fix require changing the proposal's architecture/approach, or just adding a test/validation? Architecture change → Creator. Additional test → Maker.
**Disambiguation rule:** When in doubt: if the fix requires changing the approach, route to Creator. If it requires changing the code within the existing approach, route to Maker.
### Feedback File Format