Link to current text
G.8:3 - Forces
| Force | Tension |
|---|
| Pluralism vs. dispatchability | Preserve multiple method families and partial orders ↔ still provide a consumable artefact for G.5. |
| Auditability vs. authoring friction | Fine‑grained pins and citations ↔ keeping authoring lightweight and notation‑independent. |
| Maturity as poset vs. scalar ranking | Maturity is inherently non‑scalar ↔ teams want a “single readiness number”. |
| Telemetry richness vs. decision hygiene | Rich QD/OEE telemetry ↔ avoid illegitimate promotion into dominance without explicit policy. |
| Design‑time packaging vs. run‑time trace | Authoring produces stable bundles ↔ run‑time produces branch‑specific path traces and admissibility ledgers. |
| Interoperability vs. crossing discipline | Reuse across contexts or planes ↔ prevent implicit crossings (Bridge‑only + visible). |