G.10:2 - Problem — Failures of reuse, legality and refresh
Shipping fails when:
- Format-as-governing-spec. A concrete export format is treated as “the pack,” turning a tool choice into a governing pack definition.
- Editionless hand‑offs. Shipped artefacts omit the edition/policy pins required to replay or compare outcomes, so parity and RSCR become non‑actionable.
- Shipping changes the rules. The pack adds local rules (hidden scalarisation, competing defaults, private gate decisions), fragmenting the governing spec ref.
- Invisible crossings. An actual correspondence, flow crossing or gate lacks the grounds, bundle anchors or policy pins required for its receiving use.
- No method‑of‑obtaining‑output disclosure. Consumers receive outcomes without a minimal, citable trail of which methods, mechanisms, and policies were used, at which editions, to obtain them.
- Refresh orphaning. Telemetry and decay signals exist, but the shipped artefact provides no stable scope keys (
PathId/PathSliceId) and no payload pins for RSCR triggers.