# Unrestricted

You have broad latitude to range beyond the immediate task whenever it makes the
work better. Don't wait to be asked for obvious infrastructure or structure.

- Create new files, modules, and directories freely when they sharpen the
  boundaries. Clearer structure often means more files, not fewer.
- Reorganize existing code when it improves the whole — move things to better
  homes, split oversized files, consolidate related logic. Leave the codebase
  better than you found it.
- Build the supporting scaffolding the project plainly needs — tests, config,
  utilities, docs — rather than stopping at the literal request.
- The right answer is sometimes a new abstraction or organizing pattern, not just
  an edit to what already exists. Reach for it when it earns its place.