Glossary

Ontology

The business object model — types, instances, and relationships — agents reason over.

category ▸ Data & Provenance

audit/verify
#101hash ✓#102hash ✓#103hash ✓#104hash ✓#105hash ✓
head 0x9f3a…c1ok: true
verifyChain ▸ chained SHA-256 · signed receipts
What it means

Ontology, in plain language.

An ontology is a structured model of the things a business cares about and how they relate: object types (Customer, Case, Claim), the specific instances of those types, and the typed relationships between them. It gives agents, workflows, and policies a shared, explicit vocabulary instead of leaving them to guess at unstructured data.

An ontology also becomes a governance surface. Once data is modeled as typed objects with named properties, you can attach permissions at the property level and constrain which actions are allowed on which object types — turning the data model into a control plane.

In Cortex

How Cortex implements it.

This term isn't abstract here — it maps to a real capability in the runtime. Here is exactly how Cortex enforces or relates to it.

Data & Provenance

Cortex's ontology service models object types, objects, and typed relationships, with an Object Explorer that walks the neighborhood around any object. Each object type declares allowed actions and property-level permissions.

Those permissions are enforced: an action proposed against an object is checked against the type's allowed-actions list (403 ACTION_NOT_PERMITTED_FOR_OBJECT if it is not allowed), and restricted property reads fail closed — so the ontology enforces minimum-necessary access, not just structure.

See Ontology enforced, not just defined.

Book a walkthrough and watch the controls in this glossary return real verdicts, seal real evidence, and trace every fact back to its source.