section · _guidelines/tools/7.1 · s-6uqu6vn5fnp7fwb
Checks made by sheriff validate
Checkedconfirmed by its owner
How sheriff validate checks the specification itself.
Under it
- A key written twice in one object _guidelines/tools/7.1.1
- The schema and a project's extension _guidelines/tools/7.1.2
- Sids, locations, terms and names of RecordTypes, counted _guidelines/tools/7.1.3
- Locations computed anew _guidelines/tools/7.1.4
- A checked node's confirmation _guidelines/tools/7.1.5
- A removed node and the archive _guidelines/tools/7.1.6
- Outgoing links and citations _guidelines/tools/7.1.7
- The kinds at the ends of a link _guidelines/tools/7.1.8
- Indexes, incoming links and gathered values, rebuilt _guidelines/tools/7.1.9
- Words running in capitals _guidelines/tools/7.1.10
- A section with a rule in it _guidelines/tools/7.1.11
- Consumes and exempts links _guidelines/tools/7.1.12
- No circular dependency between the domains _guidelines/tools/7.1.13
- A used domain's RecordType, only from the declared sections _guidelines/tools/7.1.14
- A header's level _guidelines/tools/7.1.15
- What a RecordType variant must agree with _guidelines/tools/7.1.16
- An identifier followed to its end _guidelines/tools/7.1.17
- Where the values of a field of type one of are collected _guidelines/tools/7.1.18
- An object in a list _guidelines/tools/7.1.19
- No copy of the SpecSheriff guidelines _guidelines/tools/7.1.20
- Implements and refines links of the appendices and a project's own guidelines _guidelines/tools/7.1.21
- A file of the technical appendix named after a domain _guidelines/tools/7.1.22
- How a project's own check is run _guidelines/tools/7.1.23