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.editionpins 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.2and theG.10:Ext.QDArchiveShippingPinspin 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.3and 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.18flow crossing orA.21gate, 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 declaredQor reachability basis so the reader can distinguish the derived view from its base palette.