An ontology becomes operational when its definitions are used to read actual data, prepare a decision and perform an authorized operation. The model alone does not synchronize sources or automate a process.
From a model to a verifiable result
View the diagram description
flowchart LR Sources[Structured sources] --> Mapping[Linking and mapping] Mapping --> Instances[Types, instances and relationships] Documents[Imported documents] --> Index[Extraction and indexing] Instances --> Read[Reading through an agent or API] Index --> Read Read --> Decision[Decision and verification] Decision --> Action[Available authorized action]
These paths have separate lifecycles. Synchronization supplies external records; document processing prepares search. A linked source is not necessarily synchronized, and an imported document is not necessarily searchable yet.
Client–Commande example
Client defines identifiant and nom. Commande defines reference, montant and devise. Instances hold actual values. A contract supplies a delivery condition. A useful question requests orders for CLI-001 over a specified period and distinguishes recorded values from interpretation of the contract.
Check the customer identifier, accessible orders, data timestamp and supporting passage. When evidence is missing, expect an explicitly partial answer rather than an invented conclusion.
Checks throughout the journey
| Stage | Check |
|---|---|
| Source | Connection, selected stream, last successful synchronization |
| Model | Identifiers, types, units and relationships |
| Instance | Provenance, values and reading permission |
| Document | Completed processing and authorized scope |
| Agent | Effective capabilities, arguments and evidence |
| Action | Inputs, authorization and resulting state |
The workspace provides the access context. Roles, permissions and available capabilities determine what can be read or modified. A skill or reusable instruction guides the agent without granting additional rights.
Choose your first journey
Start with a verifiable read. Use the UI quickstart for demonstration data, then answer using records and documents. Add a controlled action when the published contract and environment allow it.
