Define your world. Do not customize our software.
Customizing software usually means paying for a custom copy that someone must then maintain. Here it means describing your operation in a definition you own: what you manage, how it behaves, what actions cost and who may do what. The definition is versioned and reviewed like any other business document.
In plain termsYou change it by editing a description of your business, not by changing our software.
Eleven surfaces, all configuration
It sounds like a lot of knobs. It is the opposite: each one is a business decision that must live somewhere.
| Surface | What you define | Typical driver |
|---|---|---|
| Entities | The nouns the operation is managed through | Business unit, region, industry |
| State dimensions | What each entity carries, its bounds, its primary dimension | What the business measures and argues about |
| Relationships | How entities connect | Cascade and blast-radius reasoning |
| Dynamics | How state moves absent surprises | Seasonality, wear, contracts, throughput |
| Interventions | What actions exist, and what each costs | Operational reality and budget |
| Decision horizon | How far ahead the platform must be right | How decisions are actually made |
| Bands and thresholds | What counts as elevated, for whom | Risk appetite |
| Evidence weightings | How much each source is trusted | Source reliability, known blind spots |
| Policies and limits | What may be done, by whom, within what ceilings | Governance and spend control |
| Action framework | Which actions need a human, which may be automatic | Autonomy policy |
| Retention | How much history remains influential | Regulatory and operational need |
The question is whether each lives in a definition your team can read and version, or in a professional-services change request.
Configuration, not code, and why that earns money
What customization is not
| Not this | Why |
|---|---|
| A per-customer code fork | Unmaintainable, and it silently diverges from the product. |
| A settings screen with forty toggles | Knobs without semantics are noise. |
| A bespoke model trained from scratch per customer | Slow, expensive and unexplainable. |
| Only for the largest customers | A definition change is available to everyone. It is not an enterprise feature. |
| A substitute for domain knowledge | It encodes your domain knowledge. It does not supply it. |
Customization that partners can own
An asset, not a services hour.
Because a domain is a definition, an industry partner can build and own one: a world for a specific industry, with its entities, dynamics and priced interventions already encoded, plus a reference evaluation set. That is a different commercial shape from integration labor, and it is why the partner program is built around worlds rather than billable hours.
Governance of customization itself
Customization and governance ship together or not at all.
| Risk | Control |
|---|---|
| Someone redefines the primary dimension in production | Versioned definitions, review required, previous version retained |
| An intervention’s cost is edited to fit a budget | Costs are versioned and attributed; budget limits are separate from cost |
| Thresholds drift to make numbers look better | Threshold changes are recorded and diffable |
| One business unit’s definition leaks into another | Tenant and domain scoping enforced at the data layer |
Bring a definition change you would normally raise as a ticket
We will make it in the session, show the version diff, and show what changed downstream.