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

A.6.B:11 - Common Anti‑Patterns and How to Avoid Them

Anti‑patternSymptomWhy it failsRepair (square‑consistent)
Gate‑as‑lawPreconditions written as “laws”Confuses law and admission condition; breaks substitutionMove to A-* in the canonical source of the admission rule (Mechanism.AdmissibilityConditions for a mechanism); reference L-* terms.
Deontics in predicates“MUST” inside definitions or gatesConfuses governance with truth or admissibilityRewrite the definition or gate as L-*/A-*; add a generic D-* prescription or an independently established individual-duty claim when current.
Unresolved duty bearer“The API promises” is used for an individual duty without its actual bearer and commitmentThe institutional claim cannot be settled from the interface wordingRecover the policy and generic prescription, or the actual bearer and separately obtaining U.Commitment when an individual duty is claimed. Keep measured property (E-*) and metric definition (L-*) separate; use A.6.C when ambiguity changes interpretation or use.
Unestablished operational-result guaranteesAn asserted p95 result lacks its actual evaluationThe operational-result claim lacks the basis needed to settle itUse A.6.C:4.3 when the guarantee’s meaning is ambiguous. For an operational result, state the actual Work, evaluation, or observation, predicate and object, scope/window, and result; if that basis is absent, leave the result unestablished. Add A.10 support and a D-* → E-* link only when the receiving reliance and duty claims need them. A carrier-existence observation alone does not complete the measured claim.
Paraphrase driftA restatement changes the governing ruleDifferent faces can then imply different conditions or consequencesReference the claim ID or canonical location and repair the explanation to preserve its meaning; use a Claim Register when useful.
View‑fork semanticsA face introduces new L/A/D/E contentViolates “no new semantics” publication disciplinePut any new boundary claim in its canonical source before publishing it on a face. Mark explanatory commentary informative when it adds no boundary semantics.