Agent Ontology Engine

Knowledge should be more than files loaded into a prompt.

AOE compiles external domain ontologies and corpora into identified, versioned runtimes. An Agent or application can query them, receive an explainable Selection Plan, and call Actions through a separate authorization path.

01

What the engine owns

AOE Core provides the declaration meta-schema, stable IR, ontology-and-corpus compiler, snapshot verification, query and constraint runtime, action, policy, and event runtime, SDKs, transports, and conformance.

02

What stays outside

Domain ontology types, fields, relations, projections, retrieval profiles, actions, validators, plus Corpus Units, assets, and licence policy come from external packages. Frontend Design is a complete reference case.

03

What you can build

Use AOE for a support assistant, compliance review tool, operations knowledge base, data catalogue, or internal workflow that needs to understand domain objects. Your Model Package defines the world, your Corpus Package supplies the material, and the Engine compiles, queries, and governs it.

04

Start here

Begin with the Package model to see how Model, Corpus, and Adapter pieces fit together. Then follow the five-minute guide to build a Snapshot and choose SDK, MCP, or HTTP for your application.