IEventPayloadPolicy Interface
What a deployment refuses to emit. An event vocabulary's base specification says what a payload MAY carry; a profile a deployment claims can demand more of the same payload, and this is where that extra demand is stated.
public interface IEventPayloadPolicyRemarks
It lives here, in the assembly every event vocabulary and every transmitter references, because the two sides of the question are in packages that do not reference each other: the rule belongs to the vocabulary that defines the payload, and the moment it must be asked belongs to the transmitter.
A policy speaks about the payload alone, so it is consulted ONCE per event rather than once per stream: the payload is the same for every receiver, and a per-stream answer would emit to some and withhold from others by iteration order.
Registering one is how a deployment CLAIMS a profile. Nothing is registered by default, so a transmitter that claims nothing keeps emitting whatever its host builds.
Methods
IEventPayloadPolicy.RefusalOf(string, IEventPayload) Method
Why this deployment will not emit the event, or null when it will.
string? RefusalOf(string eventType, Abblix.SecurityEvents.Events.IEventPayload? payload);Parameters
eventType System.String
The event type URI the payload is carried under.
payload IEventPayload
The payload the application built; null for an event that carries none.
Returns
System.String
An operator-facing sentence naming what is missing, or null to let the event go.