Module event

Module event 

Source
Expand description

Reducer inputs. Maps RFC-0005 §4.2 wire events onto reducer transitions.

Local* variants are synthesized by the agent runtime from its own workers (probe outputs, activation outcomes, sustained-failure timing). Remote* variants are synthesized by the CP runtime from inbound POSTs to /v1/agent/events. Both halves drive the same transitions: a LocalActivationCompleted on the agent and a RemoteActivationCompleted on the CP mirror both move Activating → Soaking with the same invariants applied (RFC-0006 §2 principle 4).

Structs§

ProbeTopologyEntry
One entry in a LocalProbeTopologyDeclared / RemoteProbeTopologyDeclared event. Carries the per-probe metadata CP needs to evaluate the gate without reading the agent’s filesystem (RFC-0007 §8). Threading mode per-event would also work, but the upfront declaration also lets the gate distinguish “this enforce probe declared but never reported” from “no enforce probe declared at all” — the difference matters for wave-hold semantics.

Enums§

Event
Inputs to crate::step. Each variant maps to exactly one (legal) outbound or inbound RFC-0005 §4.2 event.