The ontology
Model the things your organization works with, their relationships, and their meaning.
On this page
Object types and objects
An object type defines an organizational concept: an asset, a project, a supplier, or another thing your team recognizes. Its properties describe that concept with explicit types and, where needed, sensitivity markings. A source mapping connects those properties to existing data.
An object is a particular indexed identity of that type, with a natural key, lifecycle, and source-backed properties. Creating a type does not automatically create every object. Indexed properties support the workspace, but do not become a separate authoritative source system.
Relationships and capabilities
A link type declares a relationship between object types; recorded links connect particular objects. For example, a supplier may fulfill an order. A sentence mentioning two objects does not create that relationship.
Action types describe capabilities that can operate on the model. Knowledge records explain subjects, while work threads track coordinated work about them. These are distinct records with distinct permissions: reading an action does not authorize execution, and sharing a note does not approve a source update.
Stable identity, reviewed versions
Catalog definitions have immutable logical UUIDs and namespaced references called fqids. Use the exact identifiers returned by nondro when connecting definitions or calling an API. Display labels are for people and must not be substituted for identifiers.
Changes are versioned. Authoring creates a draft, promotion checks the rulebook and current authority, and execution uses the live definition. Editing a draft does not silently change the live contract. Review the relevant version when deciding whether a change is ready.
acme:object_type:projects
acme:link_type:project-supplier
acme:action_type:review-projectReading the ontology map
The Structure view shows definitions and data-flow relationships. Knowledge and Work overlays add the records you are allowed to see. The map is a navigable view of the model, not an enumeration of every business object.
Overlay results are bounded and permission-filtered. A missing node does not prove that a record does not exist elsewhere in the organization. Open a node to inspect its current authoritative details, then use the library when you need to search additional knowledge or work.