# Muse Code — get-fable Working Rules

Engineering lifecycle discipline for Muse Code.

## Rules

1. **Route Task**: Identify the owning specialist with `get-fable route "<task>"`.
2. **Track Mutations**: Execute `get-fable mutation` on changes.
3. **Verify Freshly**: Validate test behavior after the last code change.
4. **Diagnose Failures**: Stop blind iterations on failure; use `fable-recover`.
5. **Spark Advice**: Consult `get-fable spark` for next-action clarity.