Skip to content

DOMAIN PACKS

The same intelligence foundation. Different business worlds.

Domain packs give Motif reusable business-specific vocabularies: entity schemas, relationships, metrics, signals, policies and workflow templates. Multiple packs can describe one enterprise.

Explore the packsDiscuss a domain
TWO PEER VOCABULARIES
Equal domain packs over one domain-independent compiler. Either can contribute to an enterprise model.
Read diagram details
  • Multi-outlet
  • Source-to-sale
  • Shared compiler
  • Multi-outlet → Shared compiler: domain meaning
  • Source-to-sale → Shared compiler: domain meaning

TWO PEER DOMAIN PACKS

Equal building blocks. Different operating context.

DOMAIN PACK / 01Design direction

Multi-Outlet Enterprises

Understand each location in the context of the whole enterprise.

Organization · Brand · Region · Outlet · Employee

For operations leaders across distributed retail and service networks.

An illustrative change in repeat visits, reviewed alongside staffing and feedback.

Explore the domain pack
DOMAIN PACK / 02Design direction

Source-to-Sale

Connect the journey from materials and suppliers to downstream demand.

Supplier · Purchase order · Raw material · Production facility · Batch

For manufacturing, supply-chain and distribution leaders.

An illustrative stock or batch exception linked to inventory movement and demand.

Explore the domain pack

ONE ORGANIZATION. MULTIPLE PACKS.

The factory and the storefront belong in the same picture.

A manufacturer with owned stores could combine Source-to-Sale and Multi-Outlet Enterprises to connect production context with outlet performance.

Illustrative scenario, not a customer result.
UPSTREAM + DOWNSTREAM
A batch and an outlet can be connected by an order in the same context. Illustrative organization.
Read diagram details
  • Production batch
  • Shared order
  • Owned outlet
  • One enterprise context
  • Production batch → Shared order: allocated to
  • Shared order → Owned outlet: ordered for
  • Shared order → One enterprise context: shared identity

WHAT A PACK DESCRIBES

Meaning is more than a list of fields.

A SHARED LANGUAGE
Identity names the object; a typed relation names the connection; evidence makes it inspectable.
Read diagram details
  • Identity
  • Typed relationship
  • Source evidence
  • Identity → Typed relationship: named connection
  • Typed relationship → Source evidence: supported by

Inspect the vocabulary of an outlet. All three parts belong to the pack; opening one does not change its readiness.

Entity + typed relationships

An outlet belongs to an organization or region. Transactions and feedback reference that outlet. The relationship type describes the connection.

02 / THE RELATIONSHIP
A named relationship connects the record to the place it describes.
Read diagram details
  • Order
  • Outlet
  • Order → Outlet: ordered for
Metrics + signals

A repeat-visit definition and comparison period establish what the outlet signal means. A difference warrants review; it does not assign a cause.

QUALITY / COMPARISON
Compare compatible locations and inspect recurring differences.
Read diagram details
  • Location A
  • Location B
  • Location A → Location B: like-for-like review
Policies + workflow template

A response template identifies a proposed step and responsible owner. Permissions and supported execution require deployment evidence.

A HUMAN BOUNDARY
A proposed response stops at a named reviewer. Supported actions require agreement.
Read diagram details
  • Response proposal
  • Named reviewer
  • Response proposal → Named reviewer: awaiting review (possible, subject to review)
01

Entities & relationships

Schemas and relationship types describe the business objects and connections that matter.

02

Metrics & signals

Reusable definitions establish what to measure and which changes deserve review.

03

Policies & workflows

Templates describe possible responses within tenant policy. Specific components and execution support require evidence.

EXPLORATION / ROADMAP

Potential domains, not released packs.

There are no announced release dates, implied certifications or customer deployments for these exploration areas.

EXPLORING / SHARED GRAMMAR
Potential domains can share entity, relationship and evidence grammar. No released pack or certification is implied.
Read diagram details
  • Assets / events: Exploring
  • Services / processes: Exploring
  • Common grammar
  • Assets / events → Common grammar: possible vocabulary (possible, subject to review)
  • Services / processes → Common grammar: possible vocabulary (possible, subject to review)
  • Logistics / Exploring
  • Healthcare / Exploring
  • Financial services / Exploring
  • Energy / Exploring
  • Sports / Exploring
  • Defense & aerospace / Exploring

A CONVERSATION, WITH CONTEXT

Connect the systems. Understand the business.

Start with one operating question. Together, we can map the context it needs.

Talk to our team