Tensions in Practice: Shared connectors and freedom behind them¶
Two makers supplying interchangeable fixtures
Two independent makers supply fixtures that must attach to the same mount. They can agree on a complete shared construction, or agree only on the mounting interface while designing the interiors differently. Both can produce compatible fixtures. The narrower agreement leaves more room for different internal designs, but also leaves more variety to inspect and support.
Agree on what needs to be shared
Secure common fit and, where separately justified, common construction for inspection or servicing.
Preserve useful internal variety
Let each maker choose a different internal design when the shared connection does not require uniformity.
Why these aims pull against each other
A shared specification enables fit, but extending it into the interior restricts designs that could still interoperate. A narrower scope preserves those choices while leaving their differences to be managed.
Choose an arrangement to see what changes and what remains difficult.
Arrows show the stated work, authority, or access paths. Position, length, and color do not measure time, risk, cost, or performance.
What this choice protects
What it costs
When it fits
Compare the arrangements
One complete design
The makers adopt a common construction and mounting interface. Their internal designs must follow that same agreed construction.
- What it protects
- A common construction may simplify shared inspection, parts, or servicing, if those are separate stated goals.
- What it costs
- Internal alternatives are excluded even when they could attach to the same mount; this extra restriction earns no additional interoperability by itself.
- When it fits
- Plausible when the parties actually need and justify common internal construction, rather than treating it as necessary merely for fit.
Illustration note: Common servicing and inspection are editorial possible benefits beyond the source’s interoperability goal. They require independent justification; T5 does not certify them.
Agree on the boundary
The makers agree on the mounting specification. Each chooses its own internal construction, while both must produce a conforming connector.
- What it protects
- Different internal designs remain possible without forfeiting the agreed fit.
- What it costs
- Conformance still needs checking; different interiors can add inspection and service work, and may differ in performance unrelated to the connector.
- When it fits
- Plausible when the interface can be specified sufficiently and internal variation is acceptable for the intended use.
Illustration note: The two internal designs are illustrative, not tested products. Connector conformance alone does not establish that every fixture is safe or suitable.
What this illustration does—and does not—establish
Standardization: Standardize the Interface versus Standardize the Implementation (Scope) supplies the interface-versus-implementation boundary. The fixtures make the scope visible, while any benefit of uniform servicing is explicitly an additional editorial design goal.
- No connector dimensions, construction recommendation, or safety certification is supplied. The fixture is hypothetical.
- The diagrams show the scope of an agreement among independent makers. They are not about revealing hidden runtime state for debugging.
- Interface conformance can coexist with differences that matter elsewhere; those need separate requirements rather than being silently called interoperability.
Source entries
Standardization
Standardization: Standardize the Interface versus Standardize the Implementation (Scope) supplies the scope distinction. The boundary section explicitly permits products with a common interface and different interiors.
T5
T5 — Standardize the Interface versus Standardize the Implementation (Scope). The interoperability benefit comes from converging on the *shared specification at the boundary*, while the implementations behind the interface can and should remain free to vary — but standardization tends to creep beyond the interface into the implementation. The tension is between standardizing enough to interoperate and standardizing so much that innovation behind the interface is foreclosed. The failure mode is *scope creep into the implementation*: specifying not just the interface but how parties must build behind it, eliminating the variety and competition that the implementation layer could carry and gaining nothing further for interoperability. Diagnostic: ask whether the standard is confined to what is needed for parts to interwork (the interface) or extends into how each part is internally built (the implementation); a standard that dictates implementation suppresses innovation for no interoperability gain, and the disciplined scope is the minimal shared specification at the boundary.
Shared fit does not require identical interiors
- Not uniformity or homogenization as such. Standardization is convergence on a *specification for a purpose* (so parts interoperate or messages parse), not the elimination of all difference. Two products can conform to the same interface standard while differing in everything else; standardization targets the shared specification, leaving the rest free, whereas blanket uniformity flattens variety with no interoperability purpose. The prime is about agreeing on a *norm at an interface*, not making everything the same.