---
description: Documentation and development log update rules
alwaysApply: true
---

# Documentation Rules

After every meaningful code change, update the relevant documentation. Do not let code and documentation drift apart.

Always consider whether these files need updates:
- `docs/dev-log.md`
- `docs/protocol.md`
- `docs/architecture.md`
- `docs/setup.md`
- `docs/testing.md`

At minimum, after every milestone or feature change, update `docs/dev-log.md` with:
- Date
- Summary of what changed
- Files modified
- What was tested
- What worked
- Any known issues
- Suggested next steps

Use this dev-log format:

```md
## YYYY-MM-DD - Feature or Milestone Name

### Summary
Briefly explain what changed.

### Files Changed
- `path/to/file`
- `path/to/file`

### Details
- Important technical detail
- Important technical detail

### Testing
- What was tested
- What the expected result was
- What actually happened

### Known Issues
- Issue or `None currently known`

### Next Steps
- Suggested next task
```

If the protocol changes, update `docs/protocol.md`. If the architecture changes, update `docs/architecture.md`. If setup changes, update `docs/setup.md`. If testing workflow changes, update `docs/testing.md`.