Understanding the Partner Platform
This documentation describes the public contract between Ormuz and partners who extend the platform: what an extension may expose, which rules it must follow, and which responsibilities apply today.
Who is this documentation for?
This documentation is for software vendors, service providers, and technology partners building an Ormuz extension.
Choose the right documentation
| Documentation | Question it answers |
|---|---|
| User documentation | How do I use, integrate, and operate Ormuz as a merchant or integrator? |
| Documentation partenaire | How do I extend Ormuz and comply with the rules for participating in its ecosystem? |
Building an extension? This documentation guides its design and specifies the contracts to follow. For configuring and using Ormuz day to day, see the user documentation.
Ecosystem principles
Declarative before implicit
An important capability, access, or effect must appear in an explicit contract rather than depend on hidden behavior.
Minimum authority
An extension receives only the authority required for the visible operation it performs; a partnership creates no implicit runtime privilege.
Single source of truth
Follow the types, fields, and values defined in reference contracts so your extension can be used in processes and by Agents.
Durable quality
A distributed extension becomes a maintained contract: design, versioning, observability, documentation, and support are part of the product.
Commencez par the extension model, puis clarifiez the responsibilities of each actor before designing technical contributions.
Partner journey
Understand
Choose the right extension model and identify who owns the data, decisions, and business effects involved.
Build
Declare the extension's capabilities and comply with the platform's public contracts.
Governance
Follow authority, data-access, consent, risk, security, economics, and observability rules.
Maintenir
Version your extension, document its changes, and verify the compatibility of every update.
Operate
Maintain the extension, handle incidents, and preserve the expected guarantees throughout its lifetime.