Axis 02 · DESIGN
Design Intelligence
What does good look like here, who decides it, and which rule governs the call?
Status
COVERED
answered by a rule or taxonomy today
Rules in force
5
RULE-KIT-ERG-013 · RULE-LIGHT-CCT-001 · RULE-LIGHT-COUNT-001 · RULE-LIGHT-FEATURE-001 · RULE-DWG-CONFIDENCE-001
Open gaps
1
each with a stated fix
Decision purposes
6
INSPIRATION · LAYOUT · ERGONOMICS · LIGHTING · TECHNICAL · MISTAKE
Rules answering this axis
| ID | Rule | Status | Ev. | Publication |
|---|---|---|---|---|
| RULE-KIT-ERG-013 | Galley kitchen working clearances | APPROVED | B | PUBLIC |
| RULE-LIGHT-CCT-001 | Answer a cool-white-throughout request with illuminance and zoning, not a colour-temperature concession | CANDIDATE | B | PROFESSIONAL |
| RULE-LIGHT-COUNT-001 | Fixture count is not the brightness decision | CANDIDATE | C | PROFESSIONAL |
| RULE-LIGHT-FEATURE-001 | Test feature lighting against the maintenance reality, not the showroom moment | CANDIDATE | C | PROFESSIONAL |
| RULE-DWG-CONFIDENCE-001 | A drawing check is only as strong as how the dimension was obtained | CANDIDATE | B | PROFESSIONAL |
Taxonomy
- decision-purposes.json (22 questions)
- scope-ownership.json
- els-canon-sources.json
Canon cited
- ELS-BOOKS 1-17
- ELS Master Execution Matrix (551 items)
- LDS Modern Tropical MT@1.6
What is missing
1 openThe decision boundary is recorded but not enforced anywhere downstream
Every rule carries decision_class and decision_owner. No consuming surface is known to read them, so a DESIGN-class call can still be presented as a PRODUCT choice.
Fix — Ask which surface consumes decision_owner before adding more rules that set it.