Leaky Contracts & Failed Substitutability¶

← Back to Composition, Interface & Interoperability Failure

Component behavior, acceptable variation, extension, and replacement depend on undocumented internals because stable functional and representation-independent contracts are absent.

53 mechanisms across 6 solution archetypes. This is a recurring problem pattern within Composition, Interface & Interoperability Failure; the mechanisms below inherit it from the primary archetype they instantiate.

Because this set contains more than 30 mechanisms, it is divided by form family—the concrete kind of thing a practitioner deploys, enacts, maintains, or convenes. This is a browsing subdivision only; it does not change the inherited problem classification. Click a form below to jump to its fully visible section.

Form family	Mechanisms	Description
Assessment, Review & Assurance	3	A bounded evaluation of existing evidence, work, compliance, or readiness that produces a finding, approval, correction, or disposition.
Control, Automation & Runtime	5	A state-dependent executable mechanism that senses, triggers, schedules, filters, throttles, routes, or actuates during operation.
Decision, Gate & Allocation	1	A bounded selection, disposition, routing, admission, prioritization, matching, or allocation among eligible alternatives.
Experiment, Test & Rehearsal	11	An active probe, controlled variation, simulated condition, or practiced execution used to generate evidence or readiness.
Interface, Display & Cue	2	A user-facing perceptual surface or interactive affordance that presents status, options, warnings, prompts, or controls.
Monitoring, Sensing & Alerting	2	Ongoing or repeated observation of actual state that emits measurements, indicators, dashboards, surveillance signals, or alerts.
Protocol, Workflow & Routine	3	A repeatable ordered sequence of actions, handoffs, states, or escalation steps, including procedures, runbooks, routines, recovery sequences, and lifecycle workflows.
Record, Log & Register	1	A durable, usually accumulating account of actual events, decisions, custody, exceptions, or state transitions whose value depends on history, provenance, or accountability.
Representation, Specification & Plan	9	A non-executable information artifact that externalizes understood, desired, or future structure, including maps, matrices, templates, checklists, specifications, reports, plans, and schedules.
Rule, Policy & Commitment	8	A standing constraint, permission, default, threshold, quota, obligation, right, or conditional action rule governing future behavior.
Structure, Architecture & Configuration	8	An enduring physical, digital, spatial, material, or organizational topology, partition, boundary, component arrangement, or configured state.

Assessment, Review & Assurance¶

A bounded evaluation of existing evidence, work, compliance, or readiness that produces a finding, approval, correction, or disposition.

3 mechanisms · View full form family

Abstraction-Barrier Code Review — A code review read through a single lens — is anything here reaching past a component's public surface into its internals? — that sends reach-throughs back before the coupling hardens.
Representation Leakage Probe — Hunts for behaviour clients can observe but the contract never promised — the accidental internals that quietly become an unofficial interface.
Supplier or Model Homologation — Formally certifies an alternate supplier, model, material, or procedure as role-equivalent under specified conditions, on the record, with an accountable owner and a re-approval trigger.

Control, Automation & Runtime¶

A state-dependent executable mechanism that senses, triggers, schedules, filters, throttles, routes, or actuates during operation.

5 mechanisms · View full form family

Fallback Switch or Kill Switch — A pre-wired reversion path that can drop the substitute and restore the known-good state the instant a protected invariant is breached.
Input Validation — A runtime gate that checks each incoming case against the accepted input domain and, for anything malformed, incomplete, unsupported, or unsafe, rejects, defers, or escalates it before the main logic ever runs.
Lenient Parser with Canonicalizer — A tolerant front-door parser that accepts a wide envelope of input variants and reduces each to a single canonical form before anything downstream sees it.
Strict Bidirectional Contract Gate — Enforces one strict contract in both directions — nothing off-spec may be sent or accepted — and routes the rare legitimate deviation through a named exception path rather than silent tolerance.
Strict Output Linter — Checks everything a system is about to emit against the canonical form and blocks non-conformant output at the source, so producers never teach the ecosystem a sloppier contract.

Decision, Gate & Allocation¶

A bounded selection, disposition, routing, admission, prioritization, matching, or allocation among eligible alternatives.

1 mechanism · View full form family

Quarantine and Manual Review Queue — Holds inbound artifacts that are neither cleanly acceptable nor safely rejectable in a queue, so a human resolves the ambiguous middle instead of the parser silently guessing.

Experiment, Test & Rehearsal¶

An active probe, controlled variation, simulated condition, or practiced execution used to generate evidence or readiness.

11 mechanisms · View full form family

Black-Box Contract Test Suite — One reusable battery of tests written only against the public contract — no test may peek at internals — so that any implementation which passes it is accepted as a valid substitute.
Blue-Green or Canary Replacement — Runs the substitute alongside the incumbent on a small, reversible slice of real traffic, and only widens the cutover once observed behavior earns each step.
Feature-Flagged Strictness Rollout — Ships a stricter regime behind a flag and ramps it across cohorts on live safety evidence with instant rollback, so a tightening never becomes a surprise outage.
Fuzz Testing Against Acceptance Boundary — Bombards the acceptance boundary with generated malformed and edge-case inputs to find where it crashes, silently accepts the invalid, or repairs into the wrong meaning.
Golden Master or Trace Comparison — Validates a substitute by replaying representative scenarios through it and diffing its output against the incumbent's own recorded reference behavior.
Metamorphic Behavior Test — Checks behavior through relations between related runs — if this input maps to that one, the outputs must relate this way — so a contract can be verified even when no one can state the single correct output.
Parallel Run Reconciliation — Runs the incumbent and the substitute side by side on the same live inputs for a bounded window and reconciles every divergence before committing to the swap.
Property-Based Conformance Test — Checks a contract by generating many random inputs and asserting the laws that must hold for every one, instead of a handful of hand-picked cases.
Reference-Implementation Differential Test — Runs the candidate and a trusted reference implementation on the same inputs and flags any observable divergence — the reference is the oracle.
Strict-Mode Shadow Run — Runs a stricter rule set in log-only mode against live traffic to count exactly what it would reject — before any of it actually blocks — so tightening is a measured step, not a gamble.
Substitutability Trial / Canary — Proves a replacement in production by routing a slice of real traffic to it and promoting only if it behaves indistinguishably from the incumbent.

Interface, Display & Cue¶

A user-facing perceptual surface or interactive affordance that presents status, options, warnings, prompts, or controls.

2 mechanisms · View full form family

Design System Component Slot — A design-system component exposes named content or behavior slots with allowed component types.
Modular Form Schema — A structured form schema with fields, conditional sections, validation rules, and stored responses.

Monitoring, Sensing & Alerting¶

Ongoing or repeated observation of actual state that emits measurements, indicators, dashboards, surveillance signals, or alerts.

2 mechanisms · View full form family

Malformation Rate Dashboard — Turns the stream of rejected and repaired inputs into a live rate-and-trend view per producer, so tolerance drift becomes visible instead of silent.
Service-Level Regression Monitor — Watches production after a swap for degradation in performance, reliability, safety, or user-facing outcomes against a pre-cutover baseline, and raises the alarm when the substitute regresses service.

Protocol, Workflow & Routine¶

A repeatable ordered sequence of actions, handoffs, states, or escalation steps, including procedures, runbooks, routines, recovery sequences, and lifecycle workflows.

3 mechanisms · View full form family

Deprecation Warning and Tightening Schedule — Turns tightening into an announced, dated plan — warn about a tolerated variant, give producers time to migrate, then stop accepting it on a committed schedule.
State Migration Playbook — Moves or maps the durable state, configuration, credentials, and history a substitute needs to perform the role — with a verified, reversible transfer plan.
Version Negotiation or Capability Probe — Has the two sides advertise and agree on a shared version or capability set before exchanging real data, so each tailors what it sends and expects to what the other actually supports.

Record, Log & Register¶

A durable, usually accumulating account of actual events, decisions, custody, exceptions, or state transitions whose value depends on history, provenance, or accountability.

1 mechanism · View full form family

Negative Case and Malformed Corpus — A curated collection of known-bad inputs, each paired with the verdict and diagnostic it should provoke, held as the fixed yardstick for what the interface must refuse.

Representation, Specification & Plan¶

A non-executable information artifact that externalizes understood, desired, or future structure, including maps, matrices, templates, checklists, specifications, reports, plans, and schedules.

9 mechanisms · View full form family

Abstract Data Type Specification — Specifies a type by its abstract values and operations, then pins any concrete storage to that meaning with a representation invariant and an abstraction function — so the storage can change without a client noticing.
API Specification — Defines a software service's behavior at its network boundary — the endpoints it exposes, the requests it accepts, the responses and status codes it returns, and how versions evolve — so any client can integrate against it without reading its code.
Capability Equivalence Matrix — Lays every role requirement in a grid against incumbent and candidate — with the evidence for each, the gaps, and the differences someone has explicitly signed off as acceptable.
Curriculum Template — A learning design scaffold with variable example, activity, assessment, and pacing slots.
Document Template — A reusable document scaffold with fixed sections and variable fields or clauses.
Model Specification — States the inputs a model accepts, the outputs and ranges it produces, and the assumptions and scope of validity under which those outputs can be trusted — so downstream users know where the model applies and where it must not be used.
Recipe Pattern — A culinary scaffold with functional ingredient or process slots that support valid substitutions.
Style Guide or Pattern Library — A curated collection of reusable patterns, allowed variants, and usage rules.
Testable Requirement — States a single expected behavior in a form a specific test can confirm or refute — a given precondition and stimulus paired with the exact postcondition that must result — so 'did it work?' has one unambiguous answer.

Rule, Policy & Commitment¶

A standing constraint, permission, default, threshold, quota, obligation, right, or conditional action rule governing future behavior.

8 mechanisms · View full form family

Clinical Protocol Definition — Specifies when a defined patient-care pathway does and does not apply — its indications and contraindications, the danger signs that halt it and the escalation they trigger, and the clinical body accountable for keeping it current.
Design-by-Contract Clause — Attaches to each operation a precondition, a postcondition, and the policy for a broken precondition — so that when a call goes wrong, the clause names, per call, whether the caller or the component is at fault.
Policy Implementation Rule — Converts a policy's intent into an operational decision rule — the concrete logic that maps a case to a categorical outcome, the exceptions and appeal paths around it, and the versioned record of how the rule changes over time.
Policy Template with Local Options — A shared policy scaffold with bounded fields for local parameters, approved exceptions, and implementation choices.
Semantic Versioning & Deprecation Gate — Governs how the contract may change over time, encoding compatibility in the version number and giving clients a deprecation window before anything breaks.
Service-Level Definition — Specifies the quality dimension of a service as a measured commitment — the performance or availability range it promises, the signal that measures it, and the threshold that counts as meeting or breaching the promise.
Tolerant Reader / Strict Writer Policy — Sets the interface's standing regime as deliberately asymmetric — strict about what the system emits, liberal about what it accepts — and writes that choice down as policy rather than leaving it to each parser.
Unknown-Field Handling Rule — Fixes in advance what a receiver does with fields it doesn't recognize — ignore, preserve, or reject — so tomorrow's additions don't break today's readers.

Structure, Architecture & Configuration¶

An enduring physical, digital, spatial, material, or organizational topology, partition, boundary, component arrangement, or configured state.

8 mechanisms · View full form family

Adapter or Facade Layer — Wraps a substitute so its native interface and data shapes are translated into the exact role the surrounding system expects — containing the mismatch instead of letting it spread.
Adapter or Translation Shim — Inserts a translating layer between two parties so a producer's legacy or foreign variants are accepted and re-emitted as the receiver's current canonical form.
Dependency Injection or Plugin Slot — Turns a hard-wired dependency into a stable named slot, so any conforming implementation can be dropped in — or swapped out — without editing the callers that use it.
Interface Definition Language — A machine-readable schema of a component's operations and their parameter and result types, from which client and server stubs are generated — so both sides compile against the published surface, never against each other's internals.
Mock, Fake, or Stub Implementation — A lightweight stand-in that honors a component's interface but not its real behavior — an in-memory fake, a canned-response stub, or an expectation-checking mock — so clients can be built and tested without the real component.
Opaque Type / Module Boundary — Makes a component's representation physically unreachable to clients, so the only thing they can couple to is its declared operations.
Plugin Slot Registration — A host system exposes extension points that approved plugins can fill through a defined interface.
Product Configuration Matrix — A table or ruleset listing product option slots, allowed fills, dependencies, and invalid combinations.