| Concept | Meaning | Client–Commande example |
|---|---|---|
| Business model | Shared definitions for a domain | Customers, orders and delivery rules |
| Entity type | Reusable structure | Client and Commande |
| Instance | Record of a type | Customer CLI-001, named ACME France |
| Property | Value on an instance | nom, montant, devise |
| Relationship | Business link between entities | Customer places Order |
| Action | Operation defined for a use case | Prepare an authorized intervention |
Technical interfaces also use ObjectType for an object type and LinkType for a relationship type. A reference property alone does not explain cardinality or the lifecycle of a business relationship.
Type or instance?
Creating Client defines fields; it does not create actual customers. Creating instance CLI-001 fills those fields for one customer. In the Modeler, select Client and open Instances to see the distinction.
Changing a property definition may affect forms, integrations and existing records. Adding a constraint does not automatically repair old instances. Check the impact of a change.
Property or relationship?
Use a property for a value without its own identity, such as an order amount. Specify its unit and currency. Use a relationship when the target is a concept you need to identify and inspect, such as the customer associated with an order.
A customer name stored as text cannot distinguish namesakes. Use mappings based on stable identifiers.
Definition, data and evidence
The schema describes expectations. An instance holds actual values. Provenance explains their origin. A document may provide a rule or justification without being automatically converted into an instance.
To check your understanding, locate CLI-001, open its record and identify its type, populated properties, provenance and relationships. If no order relationship exists, do not infer one from the name alone.
Continue with the UI quickstart or design guide.
