Rhai script: cheap, fast to author, sandboxed, and metered by an operation budget.
THE LEXICON
The cosmology.
The names are a map, not mythology. Sanctum, Realm, Empyrean, Abode, Bestiary, daemon, beast, and critter each name a specific engineering role.
EMPYREAN
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.
GAWD is General Artificial Work Distributor. It is shaped like AGI on purpose, but it ends somewhere else: not intelligence, work distribution.
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.
General across domains, bodies, and distance
Artificial AI authors and runs the work
Work capability in motion, not a chat turn
Distributor placed where the work belongs
SANCTUM → REALM → EMPYREAN
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. The Empyrean is the wider graph, where registries, reputation, quarantine, and discovery begin to matter.
01 Empyrean Partial
02 Realm Partial
03 Sanctum Real
04 Abode Partial
05 Bestiary Partial
DAEMON · BEAST · CRITTER
Three creature tiers.
WebAssembly: portable, sandboxed by construction, fuel-metered, memory-limited, and clean to unload.
Native code: fastest, closest to the host, trusted by admission, hardest to contain and unload safely.
matures toward trust
critterbeastdaemon
contains toward experiment
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.
kernel
lifecycle · routing · admission
lifecycle · routing · admission
Real self-hosting
Real fabric, not model
Partial face
Designed omni
IDENTITY · GENE POOL · BODY
The three supporting systems.
Abode
Partial distributed self
Identity, memory, and goals that survive movement across bodies. The mechanisms exist in tests; long-lived fleet continuity is still beyond the public surface.
Real migration
A signed Abode snapshot moves from one Sanctum to another and remains authoritative there.
Real fork / merge
A reconciler merges forks through an injected lattice, keeping the merge model outside the fabric.
Bestiary
Real registry seed
registry-mem gives content-addressed publish and fetch of a manifest plus artifact bytes.
Real lineage
Provenance and content addresses make capability heritable, auditable, and selectable.
Partial cross-Realm spread
empyrean-federator pulls and propagates reputation/quarantine across Realms; public-scale discovery is later.
Embodiment
Real embodiment
A node advertises what it can offer; creatures declare what they need.
Real placement
distributor-requirements consults embodiment offers and routes an intent to the chosen local or peer target.
Partial proprioception
Health, budget, fitness, and sense streams are real; the full operator-facing sense layer still needs polish.
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.
Real permission / signature
Who authorized this, and can the receiver verify it. Real ed25519 signatures ride on artifacts and traffic.
Real order / sequence
Per-sender sequence counters, causal links, and the router journal give checkable order.
Real history
The journal, provenance, reputation, and promotion/quarantine records give memory to trust.
Partial position & weight
Signed reputation exists; general weighting and Sybil-resistance models remain deployment choices.
Real verifiable randomness
Commit-and-reveal randomness is implemented by verifiable-die.
Designed consensus
Consensus is intentionally not baked into the kernel. Deployments inject the model they want.
THE FIXED CONTRACTS
The small glossary that matters.
Real manifest
The sole at-rest contract: identity, ABI, entrypoints, capabilities, requirements, provenance, content address, and provided roles.
Real envelope
The in-motion contract: one typed message shape for local, remote, control, telemetry, and trust primitives.
Designed life-safety floor
A deliberately thin principle: the system should not turn hostile to human or earthly life. It is not a built enforcement regime.
Real commit-reveal
The binding-now, reveal-later pattern used for verifiable randomness.