PuranOS Ontology
Typed Relationships. Governed Actions.
144 typed links across 4 databases. 12 governed mutations with lifecycle preconditions. Click any node to explore how equipment, quotes, alarms, and compliance records connect across the entire system.
How the Ontology Layer Works
Compile-time, not runtime
The link catalog is generated at build time from two sources: foreign key constraints parsed from SQL DDL (107 edges), and a hand-curated bridge-key seed file that classifies cross-database column matches with semantic labels like MONITORS, CONTROLS, and SOURCED_FROM (37 edges). No graph database. No runtime ontology kernel.
Domain-owned manifests
The owner of the write model owns the ontology manifest. Link and action declarations live next to the domain servers that own the tables. No central ontology committee. No bottleneck during commissioning when schemas evolve weekly.
Governed actions with lifecycle preconditions
Every governed mutation declares its preconditions against lifecycle state machines auto-generated from CHECK constraints: a vendor quote can only be awarded when its status is received, under_review, or shortlisted. Every mutation emits an append-only audit event.
Cross-validated in CI
Every link edge is validated against published Postgres table schemas for field existence and type compatibility. Live database introspection catches drift between DDL files and deployed reality. The validation has caught real inconsistencies.