Expand description
Journal entries as RDF: what one turn records and how it is read back.
An entry is the named graph named <address>/entry/<position>. An input entry records the
accepted input (event name, type, payload, send id, origin, origin type, invoke id, message
id), the chart version, the timestamp stamped at dequeue, the configuration digest after the
macrostep, and its effects: outgoing sends, timers scheduled and cancelled, invocations
started, requests issued and answered, transitions taken (annotated with the entry as their
cause) and whether the session terminated. Migration and fork entries carry snapshots
instead. The store adds rdf:type vt:JournalEntry, vt:actor and vt:position.
Structs§
- Decode
Error - A malformed journal entry or snapshot.
- Effects
- What an input entry records besides its input.
- Entry
Data - One journal entry, decoded.
- Input
Record - The accepted input of an entry.
- Reminder
Spec - A reminder registration carried by a timer.
- Send
Record - An outgoing send recorded in an entry; dispatched by the outbox after the append.
- Snapshot
Data - A snapshot of an actor at a journal position.
- Timer
Record - A durable timer: a delayed send, a request timeout or a reminder.
Enums§
- Entry
Body - The kind-specific content of an entry.
Functions§
- digest
- The digest of a configuration and datamodel snapshot: SHA-256 (hex) of the active state ids, the datamodel JSON and the termination flag.
- snapshot_
triples - The triples of a snapshot record.
- timer_
triples - The triples describing a pending timer in its actor’s current-state graph.