0003. The glossary is part of the specification
- Status: Accepted (provisional)
- Date: 2026-11-14
- Decided by: Mik, on recommendation
- Planning item: D37
Context
The planning documents used several words for one concept: store, resource and signal; extension and module; capability and effect. A framework whose selling point is a small, strict format cannot have a fuzzy vocabulary.
Decision
spec/glossary.yaml is the ubiquitous language. One term per concept, each with what it means and the words to avoid. Public names in Rust and TypeScript must be glossary terms or made of them (a lint, added with WP4). Words from third-party systems stay inside their adapter.
Changing a term marked visibility: user is a language change: decision record and Mik's approval. The integrator may add internal terms with a decision record.
Resolved by this record: store, resource and signal are all state; extension and plugin are module; capability is effect.
Consequences
The docs glossary page and editor hover text are generated from this file. Error messages, skills and docs use the same words.