Expand description
Causal events: observations, interventions, and checked derivation ancestry. Causal events over the existing derivation kernel.
crate::Packet keeps its single-predecessor publication chain. An event
has a separate causal parent set, so a reply can name several antecedents
without changing what a packet’s prior means. A store links the two in its
publication record. Elision events reference the existing Unit proof;
they do not mint a competing representation of a derivation.
Derivation sources are an explicit subset of causal parents. Only those
sources determine generation depth: receiving a reply after a harness nudge
is a new external observation, while retrieving that nudge preserves its
harness origin and generation depth. Both construction and foreign decoding
resolve and verify every parent before admitting an immutable Event.
Admission establishes structure and provenance claims, not the truth of a generated verdict or the authenticity of an external observation. The host must own observation recording and must resolve roots, retain/check payload bytes, and enforce session authorization. A resolver must expose only the caller’s authorized events; content identity alone grants no read authority.
Structs§
- Event
- An immutable event whose parent membership and derivation laws were checked.
- Event
Body - The addressed event body. Public fields are untrusted until admission.
Enums§
- Event
Error - Why an event or its elision proof was refused.
- Event
Kind - The event’s operation; operation-specific references cannot be omitted.
- Event
Origin - Who produced the material, independently of who later retrieved it.
- Reply
Verdict - The auxiliary classifier’s claim about a recorded model reply.
Type Aliases§
- RawEvent
- Foreign bytes decode to this untrusted Merkle node before
Event::admit.