Pokyn overiť podanú faktúru; telo nesie výhradne identifikátor dokumentu, samotné XML zostáva v úložisku.
Envelope identity and kind-specific facts from the entity's spec.
validate-invoice-requestcommanda request to do something — one intended handlerDerived from the services' produces / subscribesTo — two relations, never merged into one list (§4).
Produced by (0)
No service declares producing this message.
Subscribed by (1)
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/validate-invoice-request/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/validate-invoice-request/docs/