Link to current text
E.18.NET:3 - Forces
| Force | Tension to hold |
|---|
| Local autonomy vs one engineering question | Members keep their identity and state while a selected structure makes their exact coordination inspectable. |
| Recursive reuse vs fixed levels | A member may itself be a network, but membership paths must remain finite and acyclic. |
| Plain diagrams vs exact relations | A readable edge helps recognition, but only an obtaining relation of an admitted kind contributes to identity. |
| Boundary exposure vs flattening | A parent can use a nested boundary position without copying the nested member’s internal structure. |
| Useful local state vs false global state | Valuation, path slice, and DesignRunTag remain local to one leaf TFS position binding. |
| Stable selection vs evolving members | Reidentify only when an A.22 discriminator changes; records, renderings, and selection Work remain separate. |