Ontological axes capture what something is in the world. They are factual, structural, and measurable, never evaluative. The catalogue in the specs defines 0–255 as ontology and names each axis; this page summarises the main blocks so you know what is preconfigured before you extend or mask them.

Preconfigured Ontology Blocks

Extensions and Empirical Axes

The final slice of the ontology range, roughly 224–255, is reserved for domain-specific ontology extensions. When you add an axis here, define its meaning precisely, its expected range, and how relevance masks should treat it. Update the catalogue and `dimensions.json` so that every new fact can set it explicitly; overloading existing axes erodes interpretability.

Axes beyond 383 belong to empirical space and are not part of the fixed ontology partition. They can be used for latent or learned features, as described in the Dimensions Overview and the dimension catalogue spec.

Role in Concept Geometry and Ingestion

Ontology axes shape the box and centre of each concept's diamond. Theory layers may override them for counterfactual scenarios—such as altered physics—but such overrides are explicit and recorded. When BiasController masks axiology for audits, ontology remains intact so factual reasoning stays stable. A Sys2DSL statement like @f ASSERT Water BOILS_AT Celsius100 uses the BOILS_AT relation to connect the concept Water to the value concept Celsius100: at encoding time, the relation permutation and value concept contribute to the Temperature axis (and possibly neighbouring physical axes) according to the rules in the encoder specification, tightening the diamond around that region. A counterfactual layer can temporarily shift that bound (for example, using CF with Water BOILS_AT Celsius50) without mutating the base concept.

For the high-level partitioning and the role of empirical dimensions, see Dimensions Overview. For how these axes are populated during ingestion, see the Data Ingestion guide and the Conceptual Spaces and Ontology wiki pages.