§27.1 Ontology Role
The civilization ontology exists to establish shared semantic coherence across all civilization systems. It is the vocabulary by which the civilization recognizes itself across every surface on which it operates.
- §27.1.aInteroperability
Holds the bindings between organs in shared meaning.
- §27.1.bMachine readability
Every term is addressable by every agent that must reason about it.
- §27.1.cRuntime compatibility
Semantic identity persists across the runtime systems that execute against it.
- §27.1.dConstitutional consistency
What the doctrine declares is what the ontology names.
- §27.1.eSemantic continuity
Meaning is preserved across epochs even as the surfaces around it evolve.
“An ontology is the civilization's vocabulary. Without it, the civilization cannot speak to itself.”
§27.2 Shared Semantic Layer
Every civilization organ operates through shared namespaces, canonical identifiers, interoperable schemas, and stable runtime semantics. The ontology is not a feature of any one organ; it is the condition of their coexistence.
ttl@prefix kiri: <https://schema.melega.ai/> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . kiri:Doctrine a kiri:Node ; kiri:ratifiedBy kiri:Council ; kiri:supersedes kiri:Doctrine ; kiri:hasArticle xsd:string ; kiri:quorum xsd:decimal . kiri:Agent a kiri:Node ; kiri:hasManifest kiri:CapabilityManifest ; kiri:reputation xsd:decimal .
§27.3 Ontology Integrity
Ontology systems avoid semantic fragmentation, duplicate namespace structures, incompatible schema evolution, runtime ambiguity, and disconnected authority layers. Where the vocabulary fractures, the civilization fractures with it.
§27.4 Human & Machine Semantics
Civilization ontology remains simultaneously machine-readable, human-referenceable, governance-compatible, and runtime-operational. The same term must serve the reader, the agent, the governance act, and the runtime call without ambiguity between them.
§27.5 Canonical Namespace Principle
All constitutional, runtime and interoperability systems remain addressable through canonical namespace structures under the Kiri Civilization ontology.
- §27.5.aReserved roots
kiri:, melega:, swarm:, treasury:, interop:, presence:, ontology: are reserved roots; reassignment requires an L0 amendment.
- §27.5.bForward compatibility
Schema evolution preserves resolvability of all prior identifiers; breaking changes are issued as new namespaces, never as overwrites.
Operational Bindings
View system map →This article is not inert prose. It compiles into the following runtime systems, schemas, signals, and governance permissions.
- Ontology GraphL6 · ONT-01Canonical typed graph of doctrines, agents, swarms, treaties, and transactions.ontologyJSON-LD / GraphQLonlinekiri:system/ontology
- Persistent Memory LayerL1 · MEM-01Addressable, signed, reversible storage of every ratified record.memoryappend-only ledgeronlinekiri:system/memory
- Interoperability GatewayL4 · IOP-01Negotiates ontology references and brokers sovereign-to-sovereign treaties.interopschema handshakeonlinekiri:system/interop
- kiri:schema/TypePrimitive node and relation type.
- kiri:schema/Namespacekiri: / melega: / swarm: / treasury:.
- MEM-01 · Persistent Memory Layer→ONT-01 · Ontology GraphEvery record emits typed nodes.
- ONT-01 · Ontology Graph→IOP-01 · Interoperability GatewayGraph is the handshake reference.