Receiver Comprehension Test¶
Comprehension test — instantiates Channel-Fit Design
Checks empirically whether real receivers decode the channel as intended, under realistic conditions, before the system relies on it.
Receiver Comprehension Test is the empirical, receiver-side check on a channel. It does not design the code, specify the schema, or define the legend; it measures whether actual receivers, in realistic conditions, decode what was encoded well enough to make the intended decision. Its defining move is to shift the success question from the sender's side — "was it sent? is it well-formed and on-spec?" — to the receiver's: "did the person actually get it?" A message can be perfectly transmitted, fully schema-conformant, and still land wrong; only observing real receivers reveals that gap.
Example¶
A hospital discharges patients on a new anticoagulant with a printed leaflet and a verbal briefing. What actually has to succeed is a receiver decision: the patient takes the right dose on the right schedule and knows which symptoms mean "call us now." Before relying on the leaflet, the nurse runs a teach-back — "just so I know I explained it clearly, tell me in your own words how you'll take this and when you'd phone." The patient's restatement is the test: it exposes whether the intended meaning decoded. Here it hasn't — the patient has read "twice daily" as "whenever I feel unwell."
The mis-decode is caught before discharge, not after a bleed. The instruction is re-encoded — plainer words, a simple dosing chart — and checked again. A channel that looked fine from the sender's chair has been validated, and corrected, from the receiver's. Teach-back is a real, named clinical method for exactly this: verifying comprehension by asking the receiver to restate, rather than asking "does that make sense?"
How it works¶
- Use real receivers, not designers — sample the people who will actually decode the channel, including the edge cases (novices, non-native speakers, low-vision, the rushed).
- Reproduce real conditions — time pressure, distraction, and noise, because comprehension that only holds in a quiet room is not the comprehension that matters.
- Ask for behaviour, not assent — have them restate, choose, or act on what arrives, rather than nod at "is that clear?"
- Score against the intended decision — grade the receiver's output against the action the channel exists to support, then feed gaps back to re-encode and re-test.
Tuning parameters¶
- Realism of conditions — clean lab versus field noise and time pressure; more realism surfaces the failures that actually occur, at more cost to run.
- Receiver sampling — who and how many; the edge receivers (novice, non-native, impaired) surface the mis-decodes that matter most and that fluent designers never hit.
- Behavioural vs. self-report — asking them to do or restate versus asking "did you understand?"; behavioural evidence is far more valid and considerably heavier.
- Pass criterion — how accurate decoding must be to count as passing, and for which distinctions — a dosage error weighs more than a misread footnote.
- Cadence — a one-off pre-launch check versus a recurring one that catches drift as receivers, context, or the message change.
When it helps, and when it misleads¶
Its strength is catching the one failure every sender-side control misses: a message that is well-formed, on-spec, and still misread. It is the direct counter to the curse of knowledge[n1] — the designer, fluent in the code, literally cannot see the ambiguity a fresh receiver walks straight into — and it is the only component that closes the loop on whether meaning, not just bits, arrived.
Its failure modes are all about a test rigged to pass. Leading questions, friendly samples, and "does that make sense?" manufacture a green light; testing unrealistic receivers under unrealistic ease flatters a channel that will fail in the field. It also validates comprehension, not decision quality — a receiver can decode perfectly and still choose badly, which is a different problem. The classic misuse is running it after launch to justify a design already shipped rather than to find its faults. The discipline is to sample real and edge receivers, demand behavioural evidence, and fix the pass criterion before the test rather than after.
How it implements the components¶
receiver_decision_model— it is built around the named receiver and the decision or action the channel must support, and grades everything against that.encoder_decoder_alignment— it empirically measures whether the receiver's decoding matches the sender's encoding, exposing the units, assumptions, and status meanings that diverged.
It does not specify the code, schema, or legend being tested — those are defined by Schema or Protocol Contract and Message Codebook or Legend; this mechanism only verifies whether receivers actually decode them.
Related¶
- Instantiates: Channel-Fit Design — it is the receiver-side evidence that a designed channel actually carries its distinctions to the people who must act on them.
- Consumes: Schema or Protocol Contract and Message Codebook or Legend — the intended encoding it tests real receivers against.
- Sibling mechanisms: Schema or Protocol Contract · Message Codebook or Legend · Message Template or Structured Form · Multimodal Redundant Encoding · Redundancy or Error-Correction Scheme · Out-of-Band Escalation Path · Traffic-Class Separation Rule · Bandwidth and Latency Budget · Channel-Fit Audit · Channel Telemetry Dashboard · Channel Deprecation Notice
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Receiver Comprehension Test operates as an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation because it checks empirically whether real receivers decode the channel as intended, under realistic conditions, before the system relies on it.
Independent corroboration: The frozen evidence defines Receiver Comprehension Test as 'Checks empirically whether real receivers decode the channel as intended, under realistic conditions, before the system relies on it', so its operative form is Experiment, Test & Rehearsal.
Nearest alternative: Assessment, Review & Assurance — Receiver Comprehension Test includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Communication & Media Studies
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Empirically testing whether receivers decode messages as intended is communication research.
Related originating lineages:
- Human-Computer Interaction — Usability testing materially shaped realistic task conditions and predeployment validation.
Review resolution: Both blind reviewers agree that communication_media_studies is the primary origin. Explicit reconciliation of encyclopedia synthesis disagreement adopts reviewer_a's classification because empirically testing whether receivers decode messages as intended is communication research. The resulting lineage records alternates=human_computer_interaction, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The curse of knowledge — a cognitive bias in which someone who knows something finds it hard to imagine not knowing it, so experts systematically overestimate how clearly their message reads to a novice. It is precisely the blind spot a receiver-side comprehension test exists to correct, because the designer cannot self-diagnose it. ↩