Skip to main content

Module event_network

Module event_network 

Source
Expand description

Authenticated Event transport and profile-aware initialization. Native Event transport bootstrap. Identity admission and MAC are independent.

Structs§

EventNetworkService
Owns the Event carrier and announcement cancellation for the service lifetime.

Functions§

ensure_event_origin_for_profile
Initialize both CLI and service Event clients according to the deployment profile. Required mode never opens a UDS, including when credentials are absent.
event_handler
Build the Event-owned admission authenticator and the independent explicit ingress grant. An absent MAC policy still denies every Event source.
event_ingress_authorizer
The Event ingress grant: the already-admitted peer’s verified DID resolves (through the same live accepted-state roster admission used) to a deployment service NAME, which must be a member of the operator’s name-keyed quic.event_publishers set (#1652). Names survive identity churn, so the grant never goes stale when a service’s DID changes; an empty set denies every peer — read-only, never all-publishers.
probe_event_network
Probe the native Event capability: authenticate to the freshly resolved carrier and receive an actual frame from the authorized system source. A carrier handshake alone, or a local retained Event, cannot satisfy it.
require_event_tenant
The fixed Event tree belongs only to the provisioned local tenant. The process’s own proof must be a current accepted deployment service identity — resolved from the live checkpoint store (#1652), never from a DID-valued config binding that could go stale at identity churn.