Three ways to work with us, and none of them is a directory listing.

What the partner does

• Runs the engagement: the decision map, the model design, the build, the handover to the client’s own team.
• Builds in Studio with the same tools we use, and with the agent interface if that is how they work.
• Owns the client relationship. We are the platform behind it, and we say so.

What we do

• Train the partner’s modellers — the decision-first method, the engine’s semantics, the agent workflow. See training.
• Give a partner sandbox to build and demonstrate in.
• Back the partner technically during a build, and take the product gaps back into the roadmap.

Terms

• Commercial model — [Owner: implementation partner commercial model — reseller margin, referral fee, or client contracts direct with Superiora]
• Certification or accreditation — none today; we do not issue certificates we cannot stand behind.
• Minimum commitment — [Owner: any volume or revenue commitment]

• An introduction, made in the open — the client knows it is a referral, and so do we.
• We take it from there: the demo, the pilot, the contract. The referrer can stay in the room or step out.
• Referral fee — [Owner: referral fee, how it is calculated and when it is paid]
• Attribution window — [Owner: how long an introduction is attributed to the referrer]
• A signed referral agreement is required before a fee is payable: [Owner: referral agreement document]

What the interface actually offers

• Read the model as a model. Not a table dump: the structure, the semantic graph, a formula’s precedents and dependents, and everything that would break on a rename.
• Compute the blast radius before changing anything. Ask what a dimension change reaches; check a change before applying it.
• Write through the same gates a person passes. An agent is a user with a role. A locked period refuses it. A dimensional access grant refuses it. Its writes land in the audit log under its own identity.
• Record why. A change can carry the reasoning that produced it, attached to the object rather than to a chat log.

What a builder partnership looks like

• An integration — an ERP, a data warehouse, a CRM, a source system — that lands data into a model on a schedule, or reads a plan back out.
• An agent or an application built on the platform for a vertical we do not cover ourselves.
• Access to a development model and to the interface documentation; technical review of what you build.
• Licensing and distribution terms — [Owner: terms for building on and distributing against the platform, including any API licence]
• There is no public marketplace and no app store. That is a decision for later, not an omission.

The platform is proprietary software. Building against its interfaces is welcome; the Terms and the acceptable-use policy still apply, and a partner agreement is the instrument that grants anything beyond them.