Skip to main content

notify

Since v2.66.0 · Top-level declaration

Grammar​

notify <Name> {
    channel: <provider-slug>
    to: <config key>
    # + the governed-egress clauses (attribute/shield, per v2.66.0)
}

notify is the third egress dual: where deliver writes assertions into a system of record and document synthesizes a human artifact, notify spends human attention — the scarcest resource an agent can consume.

What the runtime actually does (v2.66.0)​

  • Carried lineage or refusal (axon-T933/T934/T935): a notification whose content cannot carry its provenance is refused, never sent.
  • At-most-once-per-window across replicas — the attention ledger (enterprise migration 033) deduplicates: an alert storm is a defect, not a feature.
  • The legal flag defaults OFF, fail-closed (the v2.57.0/v2.58.0 posture).

Proof​

axon-rs/src/notification.rs (axon-T933/T934/T935 unit gates) + axon-frontend/tests/notify_grammar.rs.

See also​

  • axon://primitives/deliver — the CRM egress dual.
  • axon://primitives/document — the artifact egress dual.