Wireframe uses layer-specific terms. Keep these boundaries explicit so transport concerns do not leak into routing or domain logic.
| Layer | Canonical term | Meaning |
|---|---|---|
| Transport | Frame | The wire unit produced and consumed by FrameCodec. |
| Routing envelope | Envelope | The routable wrapper that carries id, optional correlation_id, and payload bytes (Packet is the trait abstraction). |
| Domain payload | Message | The typed value encoded into and decoded from payload bytes. |
| Transport subdivision | Fragment | A bounded slice of large payload bytes plus fragmentation metadata. |
Vocabulary rules:
- Use
framefor wire-format codec units only. - Use
envelopefor routable wrappers and instances; usepacketwhen discussing thePackettrait abstraction orPacketParts. - Use
messagefor typed application payloads implementingwireframe::message::EncodeWith/wireframe::message::DecodeWith(orwireframe::message::Messagefor bincode-compatible types). - Use
fragmentonly for transport-level split/reassembly units.
For invariants and naming rules used across internal modules, see the developers' guide.