Shared-Interface Constraint Conflict¶
Core Idea¶
Shared-interface constraint conflict occurs when one output must cross a common interface to several receivers whose binding acceptance rules are mutually incompatible. An output that satisfies one receiver necessarily violates at least one other. If receiver \(i\)'s admissible set is \(R_i\), the defining condition is \(\bigcap_i R_i = \varnothing\).
Scope of Application¶
It applies to APIs serving incompatible client contracts, common forms governed by opposing jurisdictions, role-shared control surfaces, and communication to audiences whose norms cannot be jointly satisfied.
Clarity¶
The prime relocates the failure from the chosen output to the architecture that forces distinct receivers through one undifferentiated surface.
Manages Complexity¶
Receiver complaints become constraint sets with an intersection test. Remedies reduce to partitioning, translating, expanding the output repertoire, relaxing a constraint, or accepting an explicit trade-off.
Abstract Reasoning¶
If receivers can each be satisfied separately but not by one common output, the separate-service counterfactual identifies a partition defect rather than an ordinary optimization failure.
Knowledge Transfer¶
Audience segmentation, API versioning, protocol negotiation, and role-specific templates all add a routing variable that replaces one impossible intersection with several conditional feasible sets.
Examples¶
One legacy client requires a field that a regulated client forbids. One unversioned response cannot satisfy both; receiver-selected response versions can.
Relationships to Other Abstractions¶
Current abstraction Shared-Interface Constraint Conflict Prime
Parents (2) — more general patterns this builds on
-
Shared-Interface Constraint Conflict is a kind of Interface Mismatch Prime
Shared-Interface Constraint Conflict is the Interface Mismatch species in which one offered output cannot satisfy the mutually incompatible contracts of several receivers sharing the seam.
-
Shared-Interface Constraint Conflict is part of Constraint Prime
Mutually unsatisfiable receiver constraints are internal constituents of the conflict rather than optional background conditions.
Children (1) — more specific cases that build on this
-
Context Collapse Domain-specific is a kind of Shared-Interface Constraint Conflict
Context Collapse is the social-communication specialization of a shared-interface conflict in which audience-specific norms have no jointly acceptable utterance.
Hierarchy paths (2) — routes to 2 parentless roots
- Shared-Interface Constraint Conflict → Interface Mismatch → Interface → Boundary
Notes¶
Not Multiplexing, which preserves distinct streams through a shared carrier. This prime names the failure produced when receiver-specific differentiation is lost. Queued for Claude style, source, and citation harmonization.