Everything in docs/ is readable in the office at /office/library. Five
directories, organized by audience and purpose, plus an archive. File names
are kebab-case with no numeric prefixes; reading order lives here, not in
file names.
Where things live
| Directory | What | For whom |
|---|---|---|
business/ | What the company does and the policies it runs on — the overview, processes, pricing model and knobs, roadmap, open questions, launch checklist | Owner, ops review, staff onboarding |
guides/ | Plain-language walkthroughs of the tools | Desk staff |
architecture/ | How the system is built — per surface (office, rentals, portal) and per concern (auth, data model, migrations, APIs) | Engineers and agents |
operations/ | Runbooks for recurring chores (media uploads, replacement-price refresh, gear-image sourcing) | Whoever does the chore |
website/ | The public site's brand, tone, copy reference, variants, and i18n | Copy writers, agents editing the site |
archive/ | Superseded designs and historical session journals — kept for the reasoning, not the facts. Nothing in here is current. | Archaeology only |
Reading order
- New to the business?
business/overview.md→business/positioning.md→business/processes.md. - Working the desk?
guides/reservations.md, then the tooltips in the office teach the rest. - New agent session touching code?
architecture/office.md(the load-bearing facts) →architecture/data-model.md→architecture/migrations.md(read this before any schema change) → whatever surface you're editing. - Writing copy?
website/copy-guide.md(tone) →website/pages.md(what exists where) →website/copy-variants.md(the A/B system). - Tuning prices?
business/pricing.md(the model) →business/pricing-settings.md(every knob, with launch guidance).
Conventions
- A doc states what IS. Superseded content moves to
archive/(or just dies — git remembers); don't leave "this used to be different" trails outside an explicit history section. - New docs go in the directory matching their audience, kebab-case. If a doc doesn't fit any directory, question the doc.
- Cross-link with relative paths (they resolve in the office reader and on
GitHub). Images live next to their doc (see
guides/assets/). - Decisions belong in the doc that owns the topic, dated when the date matters (e.g. "owner-decided, 2026-06"). The CHANGELOG records shipping; docs record policy and design.