[02 / ONTOLOGY CONSOLE]

Define the world your enterprise operates in.

Object types, link types, action types, and interfaces — the four primitives that encode your domain as a typed, versioned, governed graph.

Request a demo Read the ontology primer→

01CONSOLE

The schema editor for reality.

Browse object types, inspect properties, and review action types — all from a single interactive console.

Object Types

Vessel14,283 instances

Properties

imoString

nameString

draft_mDecimal

beam_mDecimal

loa_mDecimal

flagString

operatorLink<Operator>

classEnum<VesselClass>

Action Types

UpdateDraftrole:harbor-master

FlagChangepolicy:four-eyes

FIG 2A · Interactive ontology console — select object types to inspect properties and action types

02PRIMITIVES

Four primitives. Infinite domains.

Every concept in your enterprise maps to one of four ontology primitives. Compose them to model any domain.

[PRIMITIVE]

Object types

Typed entities with property-level lineage, versioning, and schema evolution. Every field tracks its origin, transformation, and downstream consumers.

[PRIMITIVE]

Link types

Typed relationships with cardinality constraints, bidirectional traversal, and referential integrity. Links are first-class citizens — not foreign keys.

[PRIMITIVE]

Action types

Governed mutations with policy guards, idempotency keys, and full audit trails. Every write-back is typed, approved, and reversible.

[PRIMITIVE]

Interfaces

Polymorphic contracts that let you query across object types. Define a shape once, implement it on any type, and compose views that span the graph.

03QUERY DSL

Query the ontology like you think about it.

A typed query language that traverses the ontology graph. Follow links, filter by properties, and compose results — no joins, no impedance mismatch.

Graph-native queries

The query DSL follows link types as naturally as reading a sentence. Ask for a PortCall's vessel's operator's name — the ontology knows the path. Every query is validated against the type system at parse time, so malformed requests fail fast.

Results are shaped exactly as requested — no over-fetching, no under-fetching. Pagination, sorting, and aggregation are built into the grammar. Every query is audit-logged and governed by the same access policies as the rest of the platform.

•Type-safe at parse time

•Link traversal built-in

•Governed by access policies

•Audit-logged queries

// Find all PortCalls arriving today
// with draft exceeding berth max

query {
  PortCall(
    filter: {
      direction: "INBOUND"
      eta: { gte: today(), lt: tomorrow() }
    }
  ) {
    id
    vessel {
      name
      draft_m
      operator { name }
    }
    berth {
      id
      max_draft_m
    }
    slot {
      window_start
      window_end
    }
  }
}

// Returns 23 PortCalls, 4 draft warnings

FIG 2B · Ontology query DSL — typed graph traversal with link-following and access governance

[LOGISTICS]

See how logistics enterprises model port-to-door with the Ontology Console.

Vessels, port calls, customs declarations, containers, and bills of lading — modeled as a single ontology graph with full lineage and governance.

Explore logistics→Request a demo