Link to current text
G.10:3 - Forces
| Force | Tension |
|---|
| Notation independence | Make packs portable across tools ↔ still make them concrete enough to be used. |
| Completeness vs minimality | Ship enough to be selector‑ready ↔ avoid duplicating governing definition semantics. |
| Continuity vs evolvability | Preserve public IDs across edition bumps ↔ allow legitimate upgrades and deprecations. |
| Cross‑context reuse vs honesty | Enable reuse across Traditions/contexts ↔ keep crossings explicit and auditable. |
| Telemetry usefulness vs semantic contamination | Export useful signals ↔ avoid turning telemetry into dominance/acceptance without pinned policy. |
| Fast shipping vs refreshability | Ship quickly ↔ ensure RSCR triggers can be planned and scoped (P2W‑path aware). |