System Rule
One checkable domain or build rule, where it holds, what it constrains and what enforces it.
One System Rule row is one checkable statement that must hold in the systems, typed bds:Rule. A Domain rule is about business data, such as “No two people share the same email”. A Build rule is about how the systems are made, such as “Intakes are view sections of grid steps, never forms”. The row states the rule. The steps to follow and the full reasoning live in the document named in Source.
What a row is
On 2026-10-28 the table has 104 rules:
| Scope | Domain | Build |
|---|---|---|
| system (holds in the linked systems) | 54 | 2 |
| global (holds everywhere) | 7 | 41 |
Enforced By, counted per selected option (a rule may have several): Manual Review 55, Formula Check 25, Validator Script 19, Airtable Setting 8, Automation 6, Not Enforced 5. No rule is Checked yet.
Fields
| Field | Type | Meaning |
|---|---|---|
| Name | Text, primary | The rule in a few words, as people search for it |
| Scope | Single select | global (no System link) or system (at least one System link) |
| System | Links → System | Where the rule holds when Scope is system |
| Description | Rich text | What must hold and what happens when it does not |
| Kind | Single select | Domain or Build |
| Applies To | Links → Record Type | The kinds of record the rule constrains; blank for most Build rules |
| Enforced By | Multiple select | Formula Check, Automation, Validator Script, Airtable Setting, Manual Review, Not Enforced |
| Source | Text | Paths of the documents that state the rule, separated by semicolons |
| Checked | Checkbox | Wording, links and Enforced By were confirmed |
| Review Note | Long text | What still needs a look; blank when Checked |
| Based On ADR | Links → Architecture Decision | The decision the rule comes from |
| Work Items | Links → Work Item | Inverse of System Rules on the work item |
System Rule has no Tags link yet; a Work Item asks for it.
Rules about rules
- Enforced By lists only mechanisms that exist today. Never select a planned one. “Not Enforced” is an honest value.
- Scope and System agree. A global rule links no system; a system rule links at least one. Nothing checks this automatically; the pairing was not audited for all 104 rows.
- Source holds file paths, not links. A reader without the group’s model files cannot open them. 61 of the 104 rules cite at least one path under
tmp/, a temporary folder that is not kept, so those paths open nowhere. See Known gaps. - Based On ADR is empty everywhere because Architecture Decision has no rows. The decision is cited in Source instead.
Example
A fictitious rule: Name A service visit has one technician, Scope system, System Field Service, Kind Domain, Applies To Service Visit, Enforced By Formula Check, Source Field Service model, rule 3, Checked unticked, Review Note Confirm the check column name.
Related
Record rules and decisions · Architecture Decision · Record Type