Link to current text
A.3:4 - Forces
| Force | Tension |
|---|
| Identity vs behaviour | Keep holon identity stable while roles/behaviours change. |
| Simplicity vs precision | Managers want one “process” box; kernel must keep MethodDescription / Method / Work distinct. |
| Universality vs idioms | Pumps, proofs, and data‑pipelines must read the same, yet allow domain names. |
| Reusable semantics vs dated occurrence | Keep Method, any MethodDescription edition, and Work distinct; make each relied-on connection explicit. |
| Evidence vs mereology | Provenance edges (EPV‑DAG) must never turn into part‑whole edges. |