Správa o stave doručenia, ktorou náš Access Point v role C3 potvrdí alebo odmietne prijatú faktúru.
Envelope identity and kind-specific facts from the entity's spec.
mls-outboundeventsomething happened — fan-out, no reply expectedDerived from the services' produces / subscribesTo — two relations, never merged into one list (§4).
Produced by (1)
Subscribed by (0)
Nothing subscribes to this message yet.
The topics, queues or exchanges this message travels on (spec.channels).
The shape of what travels on the wire.
This message declares no spec.schemaPath. That is a legitimate choice: a contract can also live on an Api entity that the message's documentation points at, which keeps one schema shared by several messages. Either add the file next to the entity, or link the Api that owns the shape.
spec:
schemaPath: schema.json # next to messages/mls-outbound/message.yaml
or document the Api entity that carries the shape.
Declared spec links and inverses derived from the graph.
Declared here
Derived from the graph
Markdown texts from the entity's docs/ folder.
Architecture notes, runbooks, and onboarding texts belong here — anything a new operator should read.
Add markdown files under messages/mls-outbound/docs/