Rename or split the project glossary
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
What
The current doc/meta/glossary.org is in practice an agile glossary: it defines
sprint, story, task, capture, and similar agile process terms. It does not cover
finance/ORE domain concepts or tooling terms, yet it is presented as the
project-wide glossary. The preferred fix — more in keeping with the Zettelkasten
approach already used across the doc graph — is to split it: rename the existing
file to agile_glossary.org (or retitle it "Agile Glossary") and, as domain and
tooling knowledge grows, introduce focused companion documents (e.g. a finance /
ORE domain glossary, a tooling glossary). Each term then lives in its natural
context and is linked directly from the pages that use it, rather than all terms
being lumped into one mixed-domain document.
Why
A single project-wide glossary that mixes agile, finance/ORE, and tooling terminology is confusing: readers have to hunt through unrelated terms, and the implied promise that "everything is here" is never fulfilled. Zettelkasten practice calls for focused, single-topic documents linked by context — the same principle the rest of the doc graph already follows.
References
doc/meta/glossary.org— the current file to be renamed / split.
See also
- Glossary — the document this capture proposes to rename or replace.