axess-events 0.2.0

Shared event vocabulary for the axess workspace and platform domains. The Event<P> envelope carries cross-cutting metadata (id, time, tenant, kind, subject, actor, trace context, status) while leaving the payload type-parameterised per domain. EventSink<P> is the trait every producer rides; concrete sinks include a no-op default and a LogAndSwallow wrapper for best-effort emission paths.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

//! [`EventStatus`]: coarse outcome bucket. Detailed reason lives in
//! the payload.

/// Three-valued event outcome. Drives dashboard pivots cheaply
/// (success-rate, failure-rate) without parsing payload contents.
///
/// - [`Success`](EventStatus::Success): the operation completed as intended
/// - [`Failure`](EventStatus::Failure): the operation was attempted and refused / errored
/// - [`Info`](EventStatus::Info): a state change that is neither success nor
///   failure (e.g. a device re-sighted with no transition, an
///   informational state-change event)
#[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
#[cfg_attr(
    feature = "rkyv",
    derive(rkyv::Archive, rkyv::Serialize, rkyv::Deserialize)
)]
#[derive(Clone, Copy, Debug, Default, PartialEq, Eq, Hash)]
pub enum EventStatus {
    /// Operation completed as intended.
    Success,
    /// Operation refused or errored.
    Failure,
    /// State-change with no success/failure semantics.
    #[default]
    Info,
}