Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:10:20 UTC

G.1:8 - Common Anti‑Patterns and How to Avoid Them (informative)

  • Anti‑pattern: “Shadow CN/CG spec inside the chassis.” Avoid: keep CN/CG as cited governing spec refs; use pins and governing definition references only.

  • Anti‑pattern: “Chassis hard‑codes a favourite algorithm.” Avoid: keep M3 core method‑agnostic; add algorithm families only via Extensions with explicit governing patterns and edition pins.

  • Anti‑pattern: “Shortlist = one winner.” Avoid: return the selected set even if it has one member. Choosing one among several selected candidates requires an explicit downstream decision rule.

  • Anti‑pattern: “Refresh plan described as prose triggers.” Avoid: record canonical RSCRTriggerKindId and payload pins; aliases only as labels and only if docked.

  • Anti-pattern: “Packaging implies shipping governance.” Avoid: treat M5 as a library index; treat M6 as readiness wiring; ship only via G.10.