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:10:10 UTC

G.10:8.1 - Anti‑patterns and remedies

  • AP‑1 Format‑as‑governing‑specification. Remedy: keep Core surfaces conceptual (E.5.2); move serialisation to Annex/Interop; enforce CC‑G10.1.
  • AP‑2 Hidden edition drift. Remedy: require …Ref.edition pins in AuditPins and treat edition changes as RSCR‑relevant via canonical trigger kinds.
  • AP‑3 “QD archive present” but missing definition pins. Remedy: enforce CC‑G10.2 and the G.10:Ext.QDArchiveShippingPins pin declarations.
  • AP‑4 Telemetry silently becomes dominance. Remedy: keep telemetry report‑only unless an explicit CAL policy promotes it; require policy‑id recorded (ties to CC‑G10.3 and MOO discipline).
  • AP-5 Missing required PathSlice key. Remedy: enforce PathSlice‑keyed telemetry and path citations (G.10‑5, G.10‑6).
  • AP‑6 Cross-context reuse without its required grounds or anchors. Remedy: cite the actual relation and the receiving-use and reliance grounds required by its governor; include calibration and policy pins when that account requires them. For an independently applicable E.18 flow crossing or A.21 gate, expose its required bundle or gate anchors and fail on missing or non-conformant ones (CC‑G10.7, CC‑GCORE‑CROSS‑1).
  • AP‑7 Interop ingestion rewrites semantics. Remedy: ingest interop as cited notes only; semantics remain in G.13 (G.10‑7, G.10:Ext.InteropCitation).
  • AP‑8 Derived-view collapse. Remedy: ship sourceSetFamily, derivedViewKind, basePaletteRef, and the declared Q or reachability basis so the reader can distinguish the derived view from its base palette.