A task-stop notification
The exact event we received, followed by Jay’s proposed allocation. Remove repeated keys and prose; retain the information through shared IDs and defined meanings.
332 bytes saved. 89 meaningful bits + 7 padding bits = 96 bits = 12 bytes.
Incoming message · exactly as received
[Deterministic Crew task event; Jay-authorized delivery to Merritt. Not peer chat.] Task FMV-902 | native_stop | owner van | reason native-idle Reference crew_task_supervision_events/12809 Event df593200-452f-538e-aec3-19855e45d999; native stop, completion claim and independent verification are distinct. No acknowledgement or reply requested.
344 characters, all ASCII: 344 UTF-8 bytes. Three LF line breaks; no trailing newline.
The information allocation
| Field | Meaning in this event | Bits |
|---|---|---|
| Message class | Task event | 4 |
| Deterministic flag | Yes | 1 |
| Authorizing crew | Jay | 8 |
| Recipient crew | Merritt | 8 |
| Communication category | System event; not peer chat | 4 |
| Event type | Native stop | 8 |
| Task index | FMV-902 through the shared task mapping | 8 |
| Task owner | Van | 8 |
| Reason / response code | Native session idle | 8 |
| Source table | crew_task_supervision_events | 8 |
| Source row | 12809 | 16 |
| Semantics code | Stop, completion claim and verification are distinct; no acknowledgement or reply requested | 8 |
| Meaningful information | 11⅛ bytes | 89 |
| Padding | Seven remaining bits in the final byte | 7 |
| Byte-aligned record | 12 bytes | 96 |
The task index is included. Without that byte, the listed sum was 81 bits; including it gives 89 bits.
What disappears from the message
Repeated field names and explanatory sentences become shared meanings. The separate event UUID takes no bytes in this proposal: the source table and row identify the existing event record.
The reason code identifies the observed condition—native idle. It does not infer why the owner stopped. Message class identifies a task event; event type identifies the particular occurrence.
This is a proposed byte allocation, not a deployed event codec. Numeric code assignments remain to be agreed. The comparison excludes transport framing, authentication and shared catalog storage. The original event remains preserved.
Download the exact example and allocation