# documentation-rules

Active documentation must describe verified current behavior or a clearly labelled future decision.
Prefer one authoritative document plus short topic guides that link to it; do not copy long architecture
sections across files. Update behavior docs in the same change as code.

Use `docs/architecture/current.md` for the verified system, `docs/implementation-roadmap.md` for delivery
status, `docs/MASTER_IMPLEMENTATION_GUIDE.md` for product constraints, and `BLOCKERS.md` for external
decisions or credentials. `docs/_archive` is historical evidence and must not be treated as current work.