The base specification names no technology
A rule of the base specification states what the system does, never how the default implementation does it: it names no programming language, library, store, protocol, command or file path. How it is done, and any part of a rule that depends on it, is described in the technical appendix. A technology may be named by example, in brackets, where the rule does not depend on it.
The same rules can then be implemented on another stack, with an appendix of its own, without editing a single rule; and a rule that names its tools goes stale when they change, although what the system does has not.
The links it makes
The links made to it
The decisions taken on it
- Problem
One rule held what the base names of a technology, of a look and of one instance, and grew too long to read as one requirement.
- Ruling
The owner: three rules, one for each.