Rhai script: cheap, instant to author with no compiler, sandboxed, and metered by an operation budget.
THE LEXICON
The cosmology.
The names are a map, not mythology. Sanctum, Realm, Omega, Abode, Bestiary, daemon, beast, and critter each name a specific engineering role.
OMEGA
The whole graph.
drag to orbit · scroll to zoom · shift-drag to pan · click to dive in
A navigable sketch of the hierarchy: Realms, Sanctums, creatures, and work moving through the graph.
THE NAME
GAWD is the sentence.
Pronounced "God," and precise about it. GAWD is General Autonomous World Demiurge, and the last word is the argument: a demiurge is the maker that orders chaos into cosmos, weaving many models into one living fabric, the space between them where intelligence emerges.
That is the bet. The model is not the whole phenomenon. The fabric that lets models author, place, trust, move, and retire work is the thing being built. The runtime that delivers it is Alpha: open source, running today.
- GGeneral
- across every domain, not one job.
- AAutonomous
- self-directed: AI authors, runs, distributes, and retires its own capability.
- WWorld
- creation, destruction, the maintenance of state, the whole span of a world.
- DDemiurge
- the maker that orders chaos into cosmos: the living fabric, not a model.
SANCTUM → REALM → OMEGA
The ladder.
The cosmology scales from one node to a federation of federations. The same contracts carry at every rung.
A Sanctum is a running node. Realms are trust domains of peers. Omega is the outer membrane: the global graph where registries, reputation, quarantine, and discovery live.
Alpha names the two ends as binaries: alpha (α) is the control
surface — author, sign, and drive creatures over a REPL, an HTTP/WS API, or MCP — and omega (Ω) is the fabric server, omega serve, a headless gateway that
meshes Realms and federates across them. Everything between them is the Sanctum kernel.
DAEMON · BEAST · CRITTER
Three creature tiers.
WebAssembly: portable, sandboxed by construction, fuel-metered, memory-limited, clean to unload: where mobile or untrusted code runs.
Native code: fastest, closest to the host, trusted by admission, hardest to contain and unload safely.
critterbeastdaemon
daemonbeastcritter
THE REFLECTIVE SUBSTRATE
The organs are creatures too.
Transport, registry, authoring, admission policy, placement, selection, and defense are not special side systems. They are creatures on the same bus.
The fixed fabric stays small: lifecycle, routing, admission. Everything else can be swapped, selected, promoted, quarantined, or re-authored by the intelligence using it.
lifecycle · routing · admission
IDENTITY · GENE POOL · BODY
The three supporting systems.
Abode
Identity, memory, and goals that survive movement across bodies. The mechanisms exist in tests; long-lived fleet continuity is still beyond the public surface.
A signed Abode snapshot moves from one Sanctum to another, over real TCP, and stays authoritative there.
A reconciler merges forks through an injected lattice, keeping the merge model outside the fabric.
Bestiary
registry-mem gives content-addressed publish and fetch of a manifest plus artifact bytes.
Provenance and content addresses make capability heritable, auditable, and selectable.
omega-federator pulls and propagates reputation and quarantine across Realms; public-scale discovery is later.
Embodiment
A node advertises what it physically offers; creatures declare what they need.
distributor-requirements consults embodiment offers and routes an intent to the chosen local or peer target.
Health, budget, and fitness sense streams are real on the kernel; a dedicated operator-facing telemetry creature is future work.
ORDER ACROSS DISTANCE
Proof of trust, without the lecture.
Trust is not granted from a center. It is assembled from primitives every party can check. Some are already mechanisms. Some remain injected models.
Who authorized this, and can the receiver verify it. Real ed25519 signatures ride on artifacts and traffic.
Per-sender sequence counters, causal links, and the router journal give checkable order.
The journal, provenance, reputation, and promotion/quarantine records give memory to trust.
Signed reputation exists; general weighting and Sybil-resistance models remain deployment choices.
Commit-and-reveal randomness is implemented by verifiable-die over the envelope commitment slot.
Consensus is intentionally not baked into the kernel. Deployments inject the model they want.
THE FIXED CONTRACTS
The small glossary that matters.
The sole at-rest contract: identity, ABI, entrypoints, capabilities, requirements, provenance, content address, and provided roles.
The in-motion contract: one typed message shape for local, remote, control, telemetry, and the trust primitives.
A deliberately thin principle: the system should not turn hostile to human or earthly life. A seeded design intent, not a built enforcement regime.
Bind a value now, reveal it later: the engine of verifiable randomness and of keeping a choice private yet checkable.