Knowledge Layer

Actively build and sharpen the project's knowledge layer as you design. This is the active discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise.

File structure

/
├── GLOSSARY.md
├── docs/
│   └── decisions/
│       ├── README.md
│       ├── event-sourced-orders.md
│       └── postgres-for-write-model.md
└── src/

GLOSSARY.md says what a term means now. docs/decisions/README.md says what the project has decided now: one line per standing position, grouped by subject. The records themselves hold the arguments, addressed by slug alone. Without the index the current position exists nowhere and every session rebuilds it from the whole folder.