Ontology building
This section is the semantic core of OpenFoundry.
It documents the part of the platform that can turn datasets, streams, workflows, policies, and AI capabilities into a shared operational model of the business.
OpenFoundry mapping
The closest repository components today are:
services/ontology-serviceservices/auth-serviceservices/audit-serviceservices/query-serviceservices/workflow-serviceservices/app-builder-serviceservices/geospatial-serviceservices/ai-serviceproto/ontology/*proto/workflow/*proto/query/*
Section map
- Why create an Ontology?
- Core concepts
- Ontology-aware applications
- Define ontologies
- Object and link types
- Object types
- Properties
- Interfaces
- Action types
- Functions
- Functions by runtime
- Rules and simulation
- Object sets and search
- Semantic search
- Object permissioning
- Indexing and materialization
- Object edits and conflict resolution
- Applications
- Applications catalog
- Ontology architecture
- Ontology Manager
Current status
This is one of the most developed documentation areas in the site because it aligns unusually well with the service boundaries already visible in the monorepo.
The repository already contains real signals for:
- ontology metadata management
- object and link modeling
- action execution
- function simulation
- object-set policy and materialization
- semantic search
- ABAC and restricted views
The main gaps are less about the absence of ontology ideas and more about how much of the full lifecycle has already been consolidated into first-class platform products.