Read cofounder Muhammad Umar's memo, Compression and Reinflation
CodeNinja AtomsUnited StatesSaudi ArabiaPakistan
E4160E4320E4480E4640E4800E4960E5120E5280E5440E5600E5760E5920E6080E6240E6400E6560E6720PIT 3 · RL 1140HAUL ROADSHOVEL 02CRUSHERCAM 07PERSONTHE OPERATIONTHE TWIN · HYPER ONTOLOGYShovel LoaderHaul TruckPerson on FootFixed CameraInteraction EventCollision AlertEvidence ClipCrusher Dump PocketMaintenance Work Order

Ontology

Dedicated inference for your sovereign AI models.

ProductHyper OntologyDrawingThe digital twin of your organizationRunsInside your wallsDeliveredAs code you own
§00The idea

Every operation already has a twin. It is scattered across a dozen systems and a hundred heads. Hyper Ontology writes it down once.

The data, the logic, the actions and the rules of your operation, in one model that people and agents decide on. Not a diagram on a wall: a running system, exported as code you own.

§01Overview

Run your operation as one living model.

Your systems feed it from below. Analytics, workflows and agents act on it from above. What one of them changes, every other one sees.

AnalyticsWorkflowsAgents on Hyper PragmaOpen work orders, high priority7 openRecordOntologyAgentWrite backfault-to-work-ordercritical-escalationsla-watch10 agents scheduledinvolved inraisesescalatesrecorded infilmsrepaired byauthorisesWork PermitHaul TruckShovel LoaderLight VehicleShiftPerson on FootInteraction EventCollision AlertSupervisor AlertModel VersionHaul RoadEvidence ClipFixed CameraWork OrderCrusher PocketOntologyAtlas: your systems, connected in placeFleet managementCollision avoidanceMaintenance ERPVideo managementPermit registerPlant historianModels, inside your wallsGLM 5.3Detection modelForecast
An agent or a person actedSomething drifted past its limitData moving
Sheet 01Living ontologyMining GOLD Copper
§02Ontology language

Model every part of a decision.

Four layers, each one a part you can point at in your own code. Below is the bill of materials of one real ontology, counted from its export.

0137 synonyms

Semantics

Every object, property and link written down once, in the words the business uses. A repair ticket and a service order resolve to the same Maintenance Work Order, for a person and for an agent.

Explore the objects →
029 transitions

Kinetics

Lifecycles say which states a record can be in and which moves are allowed. The server enforces them: no screen, script or agent can skip a step.

Move a work order →
038 functions

Functions

The numbers the operation runs on, computed in one place and callable by name by any application or agent.

Read the docs →
044 agent tools

Governance

Roles decide who sees which object, property and action. An agent sees exactly what its role allows, through four tools, and nothing it was never granted.

Read the docs →
ItemPartQtyWhere it lives in your repository
01Objects18src/mcp/manifest.ts
02Properties146src/models/*.ts
03Typed links46manifest.ts · links
04Business synonyms37manifest.ts · synonyms
05Lifecycles2src/kinetics/*.ts
06Governed transitions9src/kinetics/*.ts
07Functions8manifest.ts · functions
08Agent meta tools4src/mcp/gateway.ts
§03Semantics

One mine. 18 objects. One meaning each.

The Mining GOLD Copper ontology, built in Hyper Studio: 18 objects, 46 links and 37 business synonyms across five domains. Click an object, or ask for it by the name your teams use.

FLEET AND ASSETSSAFETY EVENTSCOMPLIANCEINFRASTRUCTUREOPERATIONSCollision AlertCrusher Dump PocketDozer GraderEvidence ClipFixed CameraGeofence ViolationHaul Road SegmentHaul TruckInteraction EventLight VehicleMaintenance Work OrderModel VersionPerson On FootShiftShovel LoaderSupervisor AlertWork PermitZone Configuration

Has a lifecycle Linked to the selection

Sheet 03SemanticsMining GOLD Copper
§04Kinetics

State only moves the way you allow.

A work order can only be assigned while it is unassigned, and only completed while work is in progress. Try a move that breaks the rule: the platform refuses it, the same way it refuses an agent.

Maintenance Work Orderlifecycle on orderStatus
unassignedassignedin_progresswaiting_on_partscompletedcancelled

Move work order MFS 115

  1. MFS 115 created in unassigned, the lifecycle's initial state
Sheet 04KineticsMining GOLD Copper
§05Ontology engine

Connect what you have. Put agents to work on it.

Atlas brings the systems you already run onto the ontology. Agentic Studio runs the agents that work on it. Both export with your application.

Atlas connects the systems you already run.

YOUR SYSTEMSATLASONE SET OF OBJECTSMaintenance ERPSAP PMFleet managementDISPATCHCollision avoidanceCAS FEEDVideo managementVMSSpreadsheetsPERMITS.XLSXmap · syncin placeWork OrderHaul TruckCollision AlertEvidence ClipWork Permit

Maintenance, fleet, safety and video systems stay where they are. Atlas maps their records onto the ontology's objects and keeps them in step, so the model is the operation and not a copy of it.

Agentic Studio runs the agents that work on it.

Agentic StudioAgentsMemoryExportfault-to-work-orderBOUND TO MAINTENANCE WORK ORDERmemory on+1.00critical-escalationBOUND TO SUPERVISOR ALERTmemory onnewevidence-attachBOUND TO EVIDENCE CLIPmemory onnewEACH RUN GRADED · LESSONS KEPT · EXPORTED WITH THE APP

Managed agents bound to objects, governed by the same roles and kinetics as people. Every run is graded and the agent keeps what it learned, the way Hyper Pragma does.

ONE REALITYFor every reader and writer.

Applications, analytics and agents read and write the same objects through the same rules, so a decision made in one place is true everywhere.

SOVEREIGNInside your walls.

The ontology, its data and its agents run where your data lives: on premises, in your private cloud or air gapped, on models you host yourself.

YOURSTo keep.

Publish and the whole system exports as code: the ontology, its kinetics, its endpoint for agents and its applications. Nothing about your operation is held in anyone else's cloud.

§06Ontology toolchain

Treat your ontology as a codebase.

Every Hyper application exports its ontology as a typed manifest beside the code that enforces it. Your engineers review it, version it and run it like any other part of the stack.

Start building →
// src/mcp/manifest.ts, generated by Hyper Studio
{
  apiName: "maintenance-work-order",
  synonyms: ["Repair Ticket", "Service Order"],
  semanticDomain: "Operations and Maintenance",
  links: [{ to: "haul-truck", phrase: "belongs to" }],
  lifecycles: [{
    stateField: "orderStatus",
    transitions: [{ label: "Assign",
      from: ["unassigned"], to: "assigned",
      tool: "assignMaintenanceWorkOrder" }]
  }]
}
ProjectHyper Ontology
Approved byYour engineers
Talk to us →Start building →

CodeNinja · Hyper Ontology

Hyper Ontology: turn a reference architecture into a living system

Hyper Ontology is CodeNinja's ontology platform: the control plane every system of record connects into and every application and agent reads from. It imports the object models Praxis designs and stands them up as a living ontology over the operator's own systems, owned by the operator and sovereign to them.

Status: beta (v0.9). Used in house by CodeNinja. Access for outside teams is by request. Product overview on codeninjaconsulting.com.

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

LayerWhat it holds
Applications and agentsRead meaning from the model, never from the silos directly, so a cross-silo question comes back with citations instead of guesses
Hyper OntologyOne 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 recordNever 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

  1. Read the paper to understand why each object exists and what decision it serves.
  2. Import the package (ontology/objects.json, format hyper-ontology/1) into Hyper Ontology to stand the model up.
  3. Bind each anchor: map every object's anchored_in system to a read-only adapter.
  4. 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).

44 packages ready to import

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; 44 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.