Expand description
The history: one closed pair of an event kind and the payload it carries.
EventKind and EventPayload are one closed pair rather than two
fields that happen to agree. Every kind has exactly one payload variant and
every payload variant has exactly one kind, so a consumer that matches the
kind knows the payload’s shape, and a mismatched pair is unrepresentable
rather than merely undocumented: an EventRecord carries the payload, the
kind on the wire is that payload’s own tag, and a serialized record naming
one kind while carrying another’s payload fails to parse.
Structs§
- Action
Executed Payload - An accepted action reached the printer.
- Action
Rejected Payload - Policy refused an action.
- Action
Requested Payload - An actor asked for an action.
- Agent
Assessment Payload - The agent wrote down what it made of a turn.
- Event
Record - One event, as the store holds it.
- Intervention
Expired Payload - A bounded intervention expired.
- Malformed
External Event Payload - An external body arrived that could not be read.
- Obico
Failure Alert Payload - Obico reported a print failure.
- Obico
Printer Notification Payload - Obico sent a printer notification.
- Operator
Acknowledgement Payload - An operator acknowledged an event.
- Port
Failure Payload - A port failed while one event was being handled.
- Startup
Reconciliation Payload - A supervisor reconciled one thing the store held when it started.
- Supervision
Session Closed Payload - A supervision session was closed.
- Supervision
Session Opened Payload - A supervision session was opened.
Enums§
- Event
Kind - Which event this is, without its payload.
- Event
Payload - What an event carries, tagged by the kind it belongs to.
- Event
Source - Where an event came from.
- Obico
Notification Type - The kind of printer notification Obico sent, normalized.
- Port
Failure Site - Where a port failed while an event was being handled.
- Startup
Outcome - What one restart put back the way it found it.