张宗平
71 lines
2.4 KiB
Markdown
71 lines
2.4 KiB
Markdown
# Quality Mode
|
|
|
|
## When to Use
|
|
|
|
Use `--quality` when:
|
|
- Post-mortem findings are accumulating faster than they're consumed
|
|
- All GOALS pass but `next-work.jsonl` has unconsumed high-severity items
|
|
- You want to resolve context-hot findings from a just-completed epic
|
|
- Running immediately after `/post-mortem` to action its findings
|
|
|
|
Do NOT use `--quality` when:
|
|
- GOALS have critical failures (build broken, tests failing)
|
|
- No `next-work.jsonl` exists or is empty
|
|
- You want standard fitness-driven improvement
|
|
|
|
## Quality Score
|
|
|
|
Simple severity-weighted score:
|
|
|
|
```
|
|
score = 100 - (high_count * 10) - (medium_count * 3)
|
|
```
|
|
|
|
Where counts are unconsumed findings remaining in next-work.jsonl.
|
|
|
|
| Score | Meaning |
|
|
|-------|---------|
|
|
| 90-100 | Excellent — few or no findings remaining |
|
|
| 70-89 | Good — medium-severity items remain |
|
|
| 50-69 | Attention needed — high-severity items remain |
|
|
| <50 | Quality debt — many high-severity findings |
|
|
|
|
## Priority Cascade (Quality Mode)
|
|
|
|
1. High-severity unconsumed findings → /rpi
|
|
2. Medium-severity unconsumed findings → /rpi
|
|
3. Open ready beads → prefer /rpi with bead context
|
|
4. Failing GOALS.yaml goals and directive gaps → /rpi
|
|
5. Testing improvements → /rpi
|
|
6. Validation tightening / bug-hunt / drift mining → /rpi
|
|
7. Feature suggestions → durable work + /rpi
|
|
8. Nothing after repeated generator passes → dormancy fallback
|
|
|
|
## Marking Findings Consumed
|
|
|
|
When evolve picks a finding from next-work.jsonl, claim it first:
|
|
- Set `claim_status: "in_progress"`
|
|
- Set `claimed_by: "evolve-quality:cycle-N"`
|
|
- Set `claimed_at: "<timestamp>"`
|
|
- Keep `consumed: false` until the /rpi cycle and regression gate both succeed
|
|
|
|
If the /rpi cycle fails (regression), clear the claim and leave the finding available.
|
|
|
|
## Artifacts
|
|
|
|
| File | Purpose |
|
|
|------|---------|
|
|
| `cycle-history.jsonl` | Same as standard mode + `quality_score` field |
|
|
| `fitness-latest.json` | Same as standard mode (goals measurement) |
|
|
| `quality-trajectory.md` | Quality score over time (written at teardown) |
|
|
|
|
## Interaction with Standard Mode
|
|
|
|
Quality mode and standard mode share:
|
|
- The same cycle-history.jsonl
|
|
- The same fitness measurement (goals are still checked)
|
|
- The same dormancy guard (repeated empty queue + generator passes)
|
|
- The same circuit breaker (60 minutes)
|
|
|
|
They differ in work selection priority at the top of the ladder: quality mode picks findings first, then still falls through to the same producer layers before dormancy is allowed.
|