A.6.P:3 — Forces

Preface node heading:a-6-p-3-forces:10590

Content

ForceTension
Universality vs precisionThe repair must be reusable across domains, but must not hide the distinctions it is meant to recover.
Prose convenience vs contract clarityHumans want short verbs; engineering/assurance needs declared kinds, slots, and invariants.
Kernel minimality vs safetyFew primitives are good; umbrella relations are cross‑Context safety hazards.
Multi‑view reality vs coherenceViewpoints must be expressible without silent polarity flips or re‑typing.
Evolution vs auditabilityRelations change; edits must not rewrite meaning invisibly.
Stack disciplineLaws, admissibility, deontics, and evidence/work must not be mixed (A.6 + A.6.B).