Asymmetric Interface Discipline

Some systems survive interaction by enforcing strict guarantees on what they emit while tolerating wide variation in what they receive.

The Pattern

Asymmetric Interface Discipline describes a structural posture at system boundaries:

• Outputs are constrained
• Inputs are tolerated

This asymmetry allows independently evolving systems to interact without requiring synchronized change.

The discipline applies only at interfaces. Internally, systems may be strict, optimized, or fragile.

What This Is (Structurally)

This is not about correctness. It is not about politeness. It is not about safety.

It is about survivability under variation.

The discipline assumes:

• heterogeneous peers
• incomplete coordination
• asynchronous evolution
• unpredictable environments

Under these conditions, symmetric strictness leads to fragmentation.

Why the Asymmetry Matters

Symmetric strategies fail:

• strict send / strict receive → brittleness
• permissive send / permissive receive → incoherence

Asymmetry works because it:

• limits the blast radius of change
• localizes responsibility
• prevents cascading failure

Strictness travels outward. Tolerance absorbs inward.

Canonical Instances

This pattern appears repeatedly across domains.

Protocols

The internet survives because protocols tolerate malformed, unexpected, or legacy inputs while emitting predictable outputs.

Regulation

Devices governed by interference rules must continue to function despite environmental noise.

Mechanical Systems

Clearances, tolerances, and compliance protect assemblies from cumulative error.

Organizations

Teams that publish clear contracts but absorb ambiguity outperform teams that demand perfect inputs.

Lineage (Non-Authoritative)

This discipline is historically associated with:

• Error-correction and early internet protocol design
• FCC interference acceptance requirements for unlicensed devices

These are instances, not the source. The structure predates them.

Tradeoffs and Failure Modes

Asymmetric tolerance is not free.

Common failure modes include:

• Silent degradation
  Errors are absorbed but never surfaced.

• Exploitability
  Tolerance becomes an attack surface in adversarial contexts.

• Complexity creep
  Edge cases accumulate until the receiver becomes opaque.

• Loss of accountability
  Producers externalize responsibility onto tolerant consumers.

When incentives are misaligned, this discipline accelerates collapse.

When This Discipline Applies

Use this posture when:

• coordination costs are high
• evolution is decentralized
• failure must be non-catastrophic
• long-term compatibility matters

Do not apply it when:

• inputs are adversarial
• safety is critical
• correctness dominates survivability
• incentives reward abuse

Asymmetry is contextual, not universal.

Relationship to Other SYSTEMS Primitives

• Interfaces
  This discipline applies only at boundaries.

• Coupling
  It enables loose coupling without eliminating guarantees.

• Failure Modes
  It trades visible failure for degraded continuity.

• Scaling
  It allows systems to grow without synchronized redesign.

Orientation

When evaluating an interface, ask:

• Where is strictness enforced?
• Where is tolerance absorbed?
• Who pays the cost of ambiguity?
• What happens when tolerance is exhausted?

If both sides demand purity, the system fractures. If neither side does, the system dissolves.

Survivable systems choose asymmetry deliberately.

Tags: #interfaces #coupling #failure-modes #survivability #compatibility

Aliases:

• robustness principle
• Postel’s formulation
• FCC Rule 15