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

E.20:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomWhy it failsRepair
Wiring carries semanticsPart G extensions start redefining what a mechanism “means”.Meaning becomes edition-fragile and non-local.Move semantics back to the mechanism-subject pattern; keep extensions as binding only.
Suite becomes a meta-mechanismSuite text defines ops/laws or embeds thresholds/decisions.Collapses suite, mechanism, and gate kinds; creates hidden gate behavior.Restore suite as description-only; push thresholds to acceptance/gate kind.
Plan becomes enactmentDeclaration-local planned-filling rows contain launch values, witnesses, or decisions.This destroys the P2W planning-to-work boundary and prevents replay of what was planned versus what occurred.Keep those rows inside the exact WorkPlan with planned values or designations and only the conditions required by A.15.3; actual application, Work and gate claims retain their separate grounds.
Kernel churn by convenienceNew required stage is added directly to kernel suite membership.Expands the E.15 impact radius; destabilizes citations.Prefer suite variant; if not possible, pair with alias docking and explicit deltas.
Token drift by silent rename“Just rename UNM to …” without aliasing.Breaks citations and downstream reasoning.Use F.18 alias docking; update the registers.
MIP as gate surrogateA MIP-run manifest is treated as a runtime pass/fail result or gate passage.Governing-definition assignment is being mistaken for project execution or gate decision.Keep MIP as authoring-side governing-definition assignment; use A.21 for gate decisions and A.15 for work or enactment claims.
Governing-definition ambiguity“We’ll put it somewhere later.”Leaves incompleteness and drift invisible.Name the governing definition up front; otherwise treat as non-normative.