Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:30:10 UTC

G.10:3 - Forces

ForceTension
Notation independenceMake packs portable across tools ↔ still make them concrete enough to be used.
Completeness vs minimalityShip enough to be selector‑ready ↔ avoid duplicating governing definition semantics.
Continuity vs evolvabilityPreserve public IDs across edition bumps ↔ allow legitimate upgrades and deprecations.
Cross‑context reuse vs the cost of documenting crossingsEnable reuse across Traditions/contexts ↔ keep crossings explicit and auditable.
Telemetry usefulness vs semantic contaminationExport useful signals ↔ avoid turning telemetry into dominance/acceptance without pinned policy.
Fast shipping vs refreshabilityShip quickly ↔ ensure RSCR triggers can be planned and scoped (P2W‑path aware).