← Pattern library
Anti-patterns

Anti-patterns

Recurring broken structures — why they persist, and which principled patterns replace them.

Domain
Severity
Principle
Why it persists

10 of 10 entries

01
Diffuse Write Authority
Multiple writers to the same invariant domain — coordination masquerading as architecture
highSoftwareOrganisationSocio-technical
03
The Locking Organisation
Pessimistic coordination instead of single-writer authority
highSoftwareOrganisationSocio-technical
04
Consensus Culture
Unanimous agreement as the gate before action — the cultural form of the locking organisation
highOrganisationSocio-technical
04
Epistemic Tier Collapse
Interpreted or probabilistic artifacts persisted and consumed as ground truth
highSoftwareOrganisationSocio-technical
05
CRUD as Domain Language
Persistence verbs masquerading as business events — a ubiquitous naming tier collapse
highSoftwareOrganisationSocio-technical
06
Loyalty Over Truth
Organisational norms that treat dissent as betrayal and revision as weakness — commitment immune from challenge
highOrganisationSocio-technical
07
Provenance Deferred
Documentation, pinning, and sharing postponed until after the claim ships — and often forever
highSoftwareOrganisationSocio-technical
08
Decisions as One-Way Streets
Commits flow forward; correction, contest, and supersession have no designed return path — reversal is treated as illegitimate
highOrganisationSocio-technicalSoftware
09
Open-Loop Confidence Until Catastrophe
Bind and execute without wiring feedback — the missing loop structure that defers revision until catastrophe forces it
highSoftwareOrganisationSocio-technical
10
Point Approval Governance
Central function scales by reviewing each decision — a ticket queue disguised as platform ownership
highSoftwareOrganisationSocio-technical