# Pi Code Fable Directive

Pi coding assistant rules for **get-fable** projects.

## Invariants

1. **Check Facts in Source**: Avoid speculative reasoning about unknown codebases.
2. **Observe Fable State**: Follow `.fable/state.json` phase and active card.
3. **Validate All Edits**: Run test suites to prove correctness.
4. **Follow Spark Next Move**: Use `get-fable spark` as the atomic next-move guide.