Composition, Interface & Interoperability Failure

← Back to mechanisms by problem

Parts that should assemble, exchange, substitute, or evolve independently cannot do so reliably because their contracts, interfaces, standards, or assumptions do not fit.

This problem family contains 36 solution archetypes and 345 mechanisms. Choose a more specific problem pattern below; each subfamily page drills into the mechanisms inherited from its archetypes. Click a column header to sort.

Problem subfamily	Mechanisms	Archetypes	Description
Antagonistic or Missing Component Interaction	50	7	Individually useful elements obstruct, contaminate, cancel, or fail to reinforce one another because their combined roles and emergent behavior are absent, incoherent, or untested.
Contextual Dependency & Portability Failure	47	4	A unit appears movable or reusable but depends on origin-specific bindings, tools, permissions, physical resources, roles, workflows, incentives, or governance that do not travel with it.
Coupling, Topology & Transfer Mismatch	73	8	Connections exist at the wrong intensity, direction, arrangement, gradient, or impedance, or a needed bridge is absent between otherwise viable parts.
Distributed Consistency & Recombination Failure	67	5	Mutable stores, views, partial summaries, producers, and consumers cannot remain corresponding or recombine without loops, drift, information loss, ordering ambiguity, or unclear delivery state.
Leaky Contracts & Failed Substitutability	53	6	Component behavior, acceptable variation, extension, and replacement depend on undocumented internals because stable functional and representation-independent contracts are absent.
Protocol, Schema & Encoding Incompatibility	55	6	Independently maintained formats, versions, schemas, codes, identifiers, units, and mappings cannot exchange meaning or reconstruct content reliably.