Payload
Purpose
An opaque blob the transport carries end to end — a sealed message handed down from the layer above,
meaningless to this layer. The transport never reads a payload, never learns what it is or who it
concerns; it only splits it into fixed-size chunks for the wire and puts the chunks back together
whole at the far end. That the payload arrived from the comms layer already sealed (an
EncryptedMessage, in that layer's words) is not something the mix knows or needs to: at this layer a
payload is bytes, and bytes are all it moves.
Attributes
- bytes: is
Textthat carries the opaque blob
Invariants
- The bytes are not empty.
Scenarios
A payload is opaque bytes
Given: the bytes of a sealed message When: a Payload is created Then: it is accepted and reads back those bytes — no structure the transport can see
An empty payload is rejected
Given: empty bytes When: a Payload is created Then: the creation is rejected because there is nothing to carry