A.2.8:9 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Why it fails	Repair
“The API shall…” as duty-bearer structure	An interface description is an episteme, not the actual bearer.	Identify the policy claim and actual system or party; test institution.
`CommitmentSubject ::= RoleRef	RoleAssignmentRef	PartyRef`
Optional institution source	A published sentence appears sufficient to create the relation.	Require the applicable rule and its actual instituting basis.
Assignment-as-duty	Staffing becomes obligation.	Treat the assignment only as a rule fact and identify a separate commitment.
Duty-as-responsibility	One deontic relation silently creates ownership.	State the independent responsibility predicate or return `missing-governor`.
Gate-as-duty	Entry conditions become obligations.	Keep the A-claim and let an independently instituted commitment cite it when required.
Auditable rhetoric without support	“Guaranteed” cannot be adjudicated.	Cite exact evidence claims and carriers only when reliance or adjudication is current.
Silent mutation	Changed bearer or rule is hidden under one ID.	A changed identity-bearing fact prevents reuse of the same occurrence identity. Establish the new commitment under §4.2 before asserting another occurrence.