Accepting an input does not mean relaxing every rule¶
Cross-Domain EchoesShared pattern · Interface
A medical intake process may accept older document formats while keeping uncertain facts out of the patient chart until they are resolved. Postel’s Law is a protocol-design rule that combines tolerant receiving with strictly formatted sending. Both separate decisions that are easily collapsed into a single claim that an interface is “permissive.” The intake example distinguishes receiving a document from trusting its content; the protocol rule distinguishes receiving from producing messages. Those distinctions are not identical, but both make the tolerance boundary explicit. Silent acceptance can also preserve defects, so this comparison is a question about where tolerance belongs, not a recommendation to accept every input.
Choose a role to see its counterpart in both examples. The diagrams show relationships, not measured quantities.
Medical record intake
Accept the document; quarantine uncertain facts
Read Asymmetric Interface Tolerance CalibrationSolution archetype
Legacy formats can be received without silently promoting uncertain clinical content into the chart.
In this example: Document acceptance is not a clinical validation rule, and the sketch prescribes no care decision.
Network protocol design
Tolerant receiving; conservative sending
Read Postel's Law (Robustness Principle)Domain-specific abstraction
The historical robustness heuristic pairs a wider acceptance envelope with stricter local message production.
In this example: Silent tolerance can entrench incompatible variants; the heuristic is conditional, not a universal security rule.
The second obligation is not erased by tolerance at the first boundary.
Written comparison
An explicit tolerance envelope
Medical record intake
Receive legacy documents
Network protocol design
Accept a wider input region
Tolerance is attached to a particular boundary rather than the entire system.
A separate strict commitment
Medical record intake
Keep uncertain facts quarantined
Network protocol design
Produce conforming messages
The second obligation is not erased by tolerance at the first boundary.
What carries across
Name exactly what is tolerated, what remains strict, and where a tolerated input is prevented from becoming an unqualified output.
Where the comparison stops
The intake boundary separates receipt from trust, while Postel’s rule separates reception from production. The shared insight is explicitly asymmetric obligations, not identical validation semantics.
- Semantic uncertainty in medical facts is not the same as syntactic protocol variation.
- The diagram rows are separate policy obligations, not proof that every input can be safely converted.
- The comparison supplies no universal tolerant-parser rule or clinical acceptance threshold.
Conditions for this comparison
- Declare which variation is acceptable and which uncertainty or defect requires quarantine or rejection.
- Distinguish inbound compatibility from the guarantees made by the receiving system.
Source entries
Shared pattern
Interface
Prime
Core Idea
A bounded surface—physical, digital, or abstract—across which two distinct systems exchange information, energy, matter, or control, the foundational concept Parnas (1972) crystallized in his analysis of modular decomposition. An interface is not merely a boundary; it is a contract specifying what gets exposed, what remains hidden, what signals cross, and what guarantees hold on each side, as Liskov and Zilles (1974) formalized in their treatment of abstract data types.
Medical record intake
Asymmetric Interface Tolerance Calibration
Solution archetype
Examples and non-examples
A medical intake process that accepts legacy documents but quarantines uncertain clinical facts before chart insertion is another example.
Essence
Asymmetric Interface Tolerance Calibration treats interface strictness as a two-sided design problem. One side may be strict about what it sends and tolerant about what it receives; another may be strict in both directions; a transitional adapter may accept old variants while emitting only the current canonical form. The useful question is not whether the interface is strict or tolerant in general. The useful question is which side is strict about what, under which context, with which repair boundary, and for how long.
Network protocol design
Postel's Law (Robustness Principle)
Domain-specific abstraction
Core Idea
Postel's Law — also called the Robustness Principle — is Jon Postel's 1980–81 prescriptive design heuristic for protocol implementors, stated in RFC 760 and RFC 793: "Be conservative in what you do, be liberal in what you accept from others." The prescription operates on a structural asymmetry inherent to any multi-implementor shared protocol: the spec defines a region of strictly-valid messages, but real implementations produce a wider scatter around that region, and each receiver controls its own acceptance boundary independently of what producers do. If every implementation narrows its production tightly to the spec while widening its acceptance to cover the realistic scatter of other implementations, the union of acceptance windows covers everything in circulation, and the heterogeneous system remains interoperable without requiring every participant to achieve strict conformance simultaneously.