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

Source changed 2026-11-21 08:17:28 UTC · snapshot created 2026-11-21 08:18:11 UTC · last check 2026-11-21 08:25:10 UTC

A.6.7:8 - Common Anti-Patterns and How to Avoid Them

  1. Anti-pattern: “Family-as-suite”. Using MechFamilyDescription to list multiple distinct mechanisms. Fix: use MechSuiteDescription for “many mechanisms”, and keep MechFamilyDescription for “many realizations of one mechanism”.

  2. Anti-pattern: “Pack-as-suite”. Naming/using the suite as a Pack. Fix: reserve Pack for publication/shipping bundling; use Suite for mechanism bundles.

  3. Anti-pattern: “Suite contains admissibility tables”. Duplicating CG‑Spec or embedding CL/Φ/Ψ tables in suite obligations. Fix: publish pins and references only; keep admissibility content in ...Spec and policy registries; keep crossing realization in E.18/gate surfaces.

  4. Anti-pattern: “Suite is a hidden gate”. Introducing thresholds, block, or DecisionLog in the suite. Fix: suite declares guard formats and requi