Introduction
Foundations for consistent, maintainable operational data systems.
Operational Truth Data
Operational truth requires clear definitions, stable interfaces, and shared meaning. This section covers the core practices for defining, naming, and governing data systems that keep humans and AI aligned.
What's Inside
Database Naming Guidelines — Conventions for SQL objects that ensure readability, stability, and long-term maintainability using a "views-over-tables" architecture.
Ontology Process — How to use OWL ontologies to define canonical concepts, relationships, and semantic contracts for operational reasoning.
Core Idea
Good naming makes bad choices inconvenient. Good ontologies make inconsistent reasoning harder. Both create conditions where correct behavior is also the easiest behavior.
How is this guide?
Last updated on