Patterns d’extension
These recipes show how to compose Ormuz primitives without bypassing their authority, security, or observability boundaries. They do not replace the reference contracts.
Provider webhook → Ormuz event
Normalize an inbound event without creating a persistent business resource in the handler.
View the pattern →Create a legitimate mapping
Correlate an external object and a platform object without creating new authority.
View the pattern →Materialize an external fact
Create a canonical object only when the external role truly has creation_authority.
View the pattern →Expose a read Tool
Give an Agent a bounded observation without turning the read into general data access.
View the pattern →Expose a high-risk mutation
Make the irreversible effect, authority, parameters, and idempotency explicit.
View the pattern →Observe a provider cost
Declare near the intent and observe the cost at the point where the economic effect is known.
View the pattern →