Link to current text
A.16.0:3 - Forces
| Force | Tension |
|---|
| History value vs wrapper inflation | Publish lineage only when it matters, without making trajectory accounts mandatory around every admissible move. |
| Lineage fidelity vs readable publication | Trajectory history must stay branch-aware without becoming unreadable bookkeeping. |
| Seam usefulness vs endpoint discipline | Upstream publications must be useful while remaining visibly upstream of endpoint admission. |
| Account clarity vs neighboring rules | The trajectory account must explain heavy-history cases without taking over the position, move, publication, path, or endpoint rules. |
| Local move lineage vs bridge entry | A trajectory may later cross viewpoint or context boundaries, but that crossing does not redefine its move or lineage semantics. |