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:50:20 UTC

G.10:2 - Problem — Failures of reuse, legality and refresh

Shipping fails when:

  1. Format-as-governing-spec. A concrete export format is treated as “the pack,” turning a tool choice into a governing pack definition.
  2. Editionless hand‑offs. Shipped artefacts omit the edition/policy pins required to replay or compare outcomes, so parity and RSCR become non‑actionable.
  3. Shipping changes the rules. The pack adds local rules (hidden scalarisation, competing defaults, private gate decisions), fragmenting the governing spec ref.
  4. Invisible crossings. An actual correspondence, flow crossing or gate lacks the grounds, bundle anchors or policy pins required for its receiving use.
  5. 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.
  6. 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.