Style guide

This project’s docs follow a project-narrative tone: they explain what we built, how we run it, and why the choices were made.

Conventions we aim for

• Use “we” language for operational stories.
• Link to the canonical deep-dives instead of duplicating runbooks in multiple places.
• Keep code blocks runnable and aligned with the repo.
• Prefer consistent spellings and naming (e.g. Canadian spelling where applicable).