Understanding the extension model
An extension is an installable capability that enriches Ormuz. It describes what it can do and the contracts it exposes; an extension config is the configured instance of that extension within a merchant scope.
Extension and extension config
| Concept | Responsibility | Lifetime |
|---|---|---|
| Extension | Declares a reusable capability: configuration, channels, nodes, tools, events, external objects, and other supported contributions. | Versioned and maintained by its publisher. |
| Extension config | Makes the extension operational for a given merchant and carries the configuration required for that installation. | Created, activated, suspended, or deleted within the merchant scope. |
Ormuz does not use a parallel “module” abstraction. An optional capability follows the same extension model whether it calls an external service or provides an installable native feature.
What an extension can contribute
An extension may combine several contributions without being required to provide all of them.
Configuration
Configuration fields, merchant-provided secrets, and activation policy.
Exchanges
Consumed or exposed APIs, received or sent events, and associated authentication.
Data
Typed external objects, projections to platform objects, and durable mappings.
Orchestration
Process nodes and triggering events. Process templates may be distributed separately when a reusable composition needs to accompany the extension.
Agents
Tools explicitly designed to be selected and used by an Agent, independently from the node catalog.
User Journeys
Participant-facing actions loaded on demand for embedded UI or an external interaction provided by the extension.
Types d’extension
The current contract recognizes three structural types.
| Type | When to use it |
|---|---|
provider_integration | The extension connects Ormuz to an external service or provider orchestrated by Ormuz. |
host_connector | The extension connects Ormuz to a business system anchoring the merchant in its information system, for example an ERP or e-commerce platform. |
bundle | The extension bundles installable capabilities without exposing its own external channel. |
The type describes the shape of the extension; it determines neither its trust level, nor the partner's commercial relationship, nor the rights the extension receives at runtime.
Do not conflate the axes
| Axe | Question | What it does not decide |
|---|---|---|
| Partner type | What relationship does the organization have with Ormuz? | The runtime rights of an extension. |
| Extension capabilities | What does the product being built expose? | Its commercial level. |
| Distribution/trust status | Under what framework may the extension be distributed? | An implicit permission over data. |
| Partner level | What maturity and benefits characterize the relationship? | The extension's business authority. |
This separation is a governance invariant: a higher partner status never replaces permissions, merchant consent, authority rules, or risk classification.