PeerMessage
peerMessage: the four facts the consumed card renders. The fold reads them from the drained inbox
record’s delivery snapshot; senderLabel already ran the
gate-off label rule host-side, so the client renders it verbatim.
Stable from day one (the scheduledFire precedent): no
x-msp-stability marker.
Fields and variants
Section titled “Fields and variants”bodyremotesenderLabelsenderSessionId
Source
schema/msp/experimental/msp.schema.json#/types/PeerMessage
{ "description": "`peerMessage`: the four facts the consumed card renders. The fold reads them from the drained inbox\nrecord's delivery snapshot; `senderLabel` already ran the\ngate-off label rule host-side, so the client renders it verbatim.\nStable from day one (the `scheduledFire` precedent): no\n`x-msp-stability` marker.", "properties": { "body": { "description": "The message text verbatim — never cut (an over-budget event\nanswers the typed `pageEventTooLarge` arm).", "type": "string" }, "remote": { "description": "True for mailbox/remote senders, false for local session\nsenders.", "type": "boolean" }, "senderLabel": { "description": "The peer label gate-off shows: the sender name when the\ndurable record names one, else the sender id shortened as\ngate-off shortens it, else `unknown session` — and `remote\nsession` verbatim for a remote sender.", "type": "string" }, "senderSessionId": { "description": "The local sender's session id; absent for remote senders and\nwhen the record names none.", "type": "string" } }, "required": [ "body", "remote", "senderLabel" ], "type": "object"}