/
├── GLOSSARY.md
├── docs/
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/
A GLOSSARY-MAP.md at the root means the repo has multiple contexts. The map points to where each one lives. System-wide decisions stay in the root docs/adr/, and context-specific decisions sit in each context's own docs/adr/.
/
├── GLOSSARY-MAP.md
├── docs/
│ └── adr/
├── src/
│ ├── ordering/
│ │ ├── GLOSSARY.md
│ │ └── docs/adr/
│ └── billing/
│ ├── GLOSSARY.md
│ └── docs/adr/
Create files lazily, only when you have something to write. If no glossary exists, offer to create a root GLOSSARY.md when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.
GLOSSARY.md holds no implementation details. It is not a spec, a scratch pad, or a store for implementation decisions. It is a glossary and nothing else.
If any of the three is missing, skip the ADR. Read ADR-FORMAT.md before you write one, for its template, numbering, and the kinds of decisions that qualify.