section · _guidelines/spec/1 · s-5z5setyh8putqph
The model
Checkedconfirmed by its owner
What the specification is made of and how it is changed.
Under it
- The nodes are the specification _guidelines/spec/1.1
- The structure of the specification is defined by its schema _guidelines/spec/1.2
- A node is one rule, and a section holds rules _guidelines/spec/1.3
- A node is cited by its sid, and its id is its address _guidelines/spec/1.4
- Checked means its owner confirmed its present wording _guidelines/spec/1.5
- Only its owner confirms a node _guidelines/spec/1.6
- An unchecked node is not implemented _guidelines/spec/1.7
- Removal goes through the archive when the node was ever confirmed _guidelines/spec/1.8
- A decision lives on the rule it settled _guidelines/spec/1.9
- A rule and its reason are held apart _guidelines/spec/1.10
- What the specification governs _guidelines/spec/1.11
- The specification holds its content; the code implements it _guidelines/spec/1.12
- The base specification names no technology _guidelines/spec/1.13
- Of a user interface the base states what it shows, not how it looks _guidelines/spec/1.14
- The base specification holds no figure of one instance _guidelines/spec/1.15
- The technical appendix stands beside the base specification _guidelines/spec/1.16
- The technical debt holds the problems of the default implementation set aside _guidelines/spec/1.17
- The guidelines hold their base and the appendix of their tools _guidelines/spec/1.18
- A project's own guidelines refine or implement the SpecSheriff guidelines _guidelines/spec/1.19
- Data structures are described in the specification _guidelines/spec/1.20
- A field is required only where its value is guaranteed _guidelines/spec/1.21
- A data record variant exists only for a value carrying fields of its own _guidelines/spec/1.22
- Each value choosing a data record variant is declared once _guidelines/spec/1.23
- What the domains share is agreed in contracts _guidelines/spec/1.24
- The specification is divided into domains _guidelines/spec/1.25
- A part of the specification can be read alone _guidelines/spec/1.26
- An entity is declared once _guidelines/spec/1.27
- A domain's specification opens with its header _guidelines/spec/1.28
- Every domain stands at a level _guidelines/spec/1.29
- The order of the domains _guidelines/spec/1.30