The realm specification
Realms are self-contained, declarative bundles of agent capabilities that can be installed into an Embabel-based host. Each realm is a git repository (no JVM bytecode, no native binaries) that provides actions, types, APIs, MCP servers, commands, webhooks, event sources, agents, skills, prompts, and apps. The host platform reads the realm and wires its contents into the running agent.
The hosted execution contract defines captured execution, channel publication, finite capacity and credential mediation. It also records the governed reference implementation’s current support. Trusted-host examples below do not authorize a governed guest to bypass those checks.
Status: living draft. Sections marked forward-looking describe shape that is settled but may still be in implementation across hosts. Other sections describe portable declarations and trusted-host formats; capability support differs by host profile. Where this document cites concrete defaults or behaviour of “the reference host”, it means the host implementation this spec is developed against; those values are informative, not part of the contract.
Licence. The specification text in this repository — this document, Virtual Cypher and their companions — is CC BY-ND 4.0; the embedded code, YAML and Cypher samples are Apache 2.0. Authoring realms and building software that uses them is free and unconditional; implementing these specifications in another engine or platform requires a written agreement. NOTICE.md states the rights in full, and License summarizes them.
Writing a captured realm in TypeScript? TypeScript realms walks through
defineRealm from end to end: handlers and their context, credentials, APIs, channels, sources and
consumers, dependencies, producers, graph queries, goals, lenses, watches, apps, write proposals,
and the owner approvals each one needs.
Exposing an existing application to worlds? The Realm Publishing Protocol (proposal, Apache 2.0) lets an application declare its own types, lookups, verbs and identity bridges, so a world installs it from its URL alone, with no realm authored by hand. PUBLISHERS.md says how an Embabel world maps a publisher onto Virtual Cypher and code mode.
Bringing an ontology, or leaving with one? Open standards in, open standards out is the import and export contract: an OWL or RDFS ontology becomes types, edges and DERIVE rule sets (a vocabulary such as the Gene Ontology becomes one type and its rows), every object lands in a mapping report as exact, inferred, noted or refused by name, and a realm’s schema goes back out as OWL under the IRIs it came in with. Import, never conform. Binding realms (proposal) is the seam that import exposes: the ontology in one realm, the binding to a system in another, with every existing realm unchanged as the case where the two are the same.
Asking for a result without writing the steps? Planning
takes a goal — the final query, or a question in English — and a deterministic planner chooses the
realm’s views and DERIVE rules that reach it, compiled to one ordinary query that is shown before it
runs and pinned once saved. A view becomes a step by making a named, described fact; a view may declare
its goal: instead of its cypher:.

