The receiver contract at publish: whether the event a sender or a binding names is one the receiving document accepts (ADR-0008).

Two things in this package name an event another document's chart is expected to take. A binding names one in its event, and a <send> to the reserved execution target names one in its event and the receiving document in its document param (ADR-0006, section 1). When either name is one the receiving chart never listens for, nothing at run time refuses it: the event is delivered and recorded as delivered, and the receiver's step selects no transition (ADR-0008, decision 5). These functions find it before a chart or a configuration ships.

This package has no publish step and gains none here. A host calls these functions from its own - when it saves a revision, when it compiles a document in CI, when an author presses publish - and an editor calls them at edit time. The host decides whether a finding blocks the publish or only warns (ADR-0008, decision 6). They are pure over their arguments: a resolved StatifierRouter.Config.t/0, a compiled Statifier.Machine.t/0 and the host's lookup, which is the only call that reaches outside them. Nothing here adds a Statifier.Validator finding.

The lookup

The host supplies an arity-1 function from a receiving document id to one of three answers (ADR-0008, decision 2):

• {:ok, names} - the receiver declares these event names. An event is accepted when it is equal, as a string, to one of them. [] is a declaration that accepts nothing.
• {:ok, :undeclared, machine} - the receiver declares nothing, and machine is the chart a new execution of it would start on. Its contract is the engine's computed vocabulary: an event is accepted when Statifier.Chart.check_accepts(machine, [event]) answers unreachable: []. The package never matches descriptors itself.
• {:error, :not_published} - the receiver has no published chart.

Any other answer is the host's fault, and the function raises ArgumentError. The lookup takes no scope: the host builds it over the scope it is publishing into (ADR-0008, decision 2).

The three reasons

A finding carries reason, which says which contract refused it (ADR-0008, decisions 2 and 4):

• :undeclared - the receiver declares names and this is not one.
• :undeclared_by_computed_set - the receiver declares nothing, and no reachable transition of its chart matches this name.
• :not_published - the lookup answered {:error, :not_published}.

What cannot be checked

Only a literal can be judged. A send undeclared_events/3 selects but cannot judge is never a finding and never passed silently: it is reported under :unchecked as %{reason: reason, location: location}, the shape StatifierRouter.Routes.unregistered/2's own unchecked entries have (ADR-0008, decision 3). The reasons are :eventexpr, :no_event, :document_expr and :no_document; see unchecked/0. A send whose type or target is an expression is not selected here at all: StatifierRouter.Routes.unregistered/2 reports it, and check/3 carries that list once.

An example

A parcel is scanned from depot to doorstep. The parcel document declares the two events its chart takes, and a third binding routes the depot's missing-parcel report as an event the parcel never declared:

iex> lookup = fn
...>   "parcel" -> {:ok, ["parcel.scanned", "parcel.delivered"]}
...>   _other -> {:error, :not_published}
...> end
iex> {:ok, lost} =
...>   StatifierRouter.Binding.new(
...>     id: "depot_lost",
...>     source: "depot_feed",
...>     match: "event.kind == 'lost'",
...>     key: "event.parcel_id",
...>     document: "parcel",
...>     event: "parcel.lost"
...>   )
iex> StatifierRouter.Contracts.undeclared_binding_events([lost], lookup)
[%{event: "parcel.lost", document: "parcel", binding_id: "depot_lost", reason: :undeclared}]