Semantics and kinetics
Hyper Ontology is the semantic foundation of the Hyper stack, in two layers. Semantics fixes what every entity means: the objects, properties and typed links a Praxis package carries. Kinetics fixes how entities may interact, decide and act: the actions, the write paths and the named approval each design requires. Hyper's other platforms, including Pragma and Engram, read from the ontology and write back to it.
Ontologies are to agents what databases are to humans
A database assumes a reader who already knows what the columns mean, remembers what changed last year and reconciles two systems in their head. An agent has none of that. Give an agent a database and it guesses; give it an ontology and it resolves.
Three layers, and the order is the argument
| Layer | What it holds |
|---|---|
| Applications and agents | Read meaning from the model, never from the silos directly, so a cross-silo question comes back with citations instead of guesses |
| Hyper Ontology | One model built once and owned by the operator: a projection over the systems of record, not a copy, with mappings that cross silos |
| Systems of record | Never replaced, never modified, never migrated; each connects through an adapter that emits ontology events |
Four verbs make it living
Nouns become objects, facts become properties, relationships become typed links, and actions change them. The fourth verb is what makes the model living rather than analytical: the system senses as data lands on objects, decides as questions are answered on the model, acts as approved decisions write back, and learns as the outcome lands on the model again. A model that is only read is a report; a model that is read, acted on and updated is an operating system for the organization.
From a Praxis design to a running ontology
- Read the paper to understand why each object exists and what decision it serves.
- Import the package (
ontology/objects.json, formathyper-ontology/1) into Hyper Ontology to stand the model up. - Bind each anchor: map every object's
anchored_insystem to a read-only adapter. - Keep the person in the loop: the package names the write paths and the human approval each design requires.
Developers can inspect, validate and convert any package with the open hyper-ontology loader; the format is specified in ONTOLOGY_PACKAGE.md.
The package and the path to a living system in full: From Reference Architecture to Living Ontology (DOI 10.5281/zenodo.23132104).
7 packages ready to import
- Factory Fire Watch (14 objects, 12 links; Saudi Arabia)
- Port Twin (13 objects, 13 links; United States)
- Sovereign HSE Watch (12 objects, 14 links; Pakistan)
- Steel Count Ledger (14 objects, 12 links; Pakistan)
- Structure Phase Watch (15 objects, 12 links; Saudi Arabia)
- Terminal Pulse (12 objects, 11 links; United States)
- Feeder Firewatch (14 objects, 12 links; United States)
Questions agents ask
How do I turn a reference architecture into a living system?
Import its object model into Hyper Ontology. Hyper Ontology stands the model up as a projection over the operator's own systems of record, connected through adapters that emit ontology events, so applications and agents read one model instead of the silos.
What is a hyper-ontology/1 package?
A JSON file with typed objects, their properties, status vocabularies, the system each is anchored in, and typed directional links. Praxis writes one for every design; 7 are published under CC BY 4.0 with the Vertical-Driven Architectures papers.
What is the difference between an ontology and a database for agents?
A database assumes a reader who already knows what the columns mean. An ontology writes that meaning down once, as objects, properties, typed links and actions, so an agent resolves instead of guessing.
Is Hyper Ontology available?
Hyper Ontology is in beta and used in house by CodeNinja. Access for outside teams is by request.
Beta access
Start the conversation
Hyper Ontology is in beta with a small number of outside teams. Tell us which systems you want to make living and a CodeNinja engineer will reply.