Safe native lifecycle
Load, exercise, fully unload, and reload native code in a live node with no leaks and no undefined behavior.
ROADMAP
The hard parts are proven. Here is the rest.
No calendar. The substrate already runs end to end; this page is honest about what ships, what comes next, and what is deferred by design.
PROVEN FIRST
Three hard problems, gone first.
If native lifecycle, mobile code, or decentralized trust failed, everything above would be decoration. So they were proven before any product surface. All three hold today.
Mobile code across trust
Ship code authored elsewhere, verify provenance and integrity, and run it under a containment the operator chose.
Trust without a center
Settle who acted, in what order, by whom, weighted how, from primitives every party can check, not a central authority.
WHAT RUNS TODAY
The substrate runs end to end.
Every row is a mechanism with a test or a demo behind it. The release is source-first and pre-1.0: proven in code, not yet a hosted production service, and not externally audited.
Real Three execution tiers Native daemon, WASM beast, and script critter load through one Kernel path, differing only by abi.backend.
Real Safe hot-unload Kernel-driven deregister → drain → engine-unload, proven by a 1000-cycle reload loop that stays RSS-stable and ASan-clean.
Real AI self-authoring A plain-English request becomes a signed, admitted, hot-loaded creature; native cargo builds and no-compiler critter builds ride the same path.
Real ed25519 transport A creature authored on one Sanctum ships to another over an authenticated handshake and framed TCP, then verifies, admits, loads, and runs there.
Real Dynamic clustering Nodes gossip membership into a many-to-many mesh that self-completes from one introduction — an operator-gated admission, then gossip closes the graph (every link is mutually ed25519-authenticated, no TOFU); run a creature living on a peer with send <node>:<id>.
Real Abode migration + fork/merge A running self relocates between Sanctums with its state cryptographically intact; a reconciler merges forks through an injected lattice.
Real The five governing loops Sense→act, author→select→promote, distribute, defend, and acculturate, each an injected creature with an end-to-end test.
Real Control surfaces A local REPL, a Bearer-auth HTTP/WebSocket plane, and an MCP hub all drive a CONTROL role over the bus, with a human allow-AI gate.
Real Verifiable randomness Commit-and-reveal over the envelope commitment slot: provably unpredictable yet provably un-rigged.
THE CONTROL SURFACE
One node, three ways to drive it.
The AI-first control surface threads through everything: list, author, build, load, place, unload, publish, and read the senses. A human and an AI share it behind one allow-AI gate.
Real REPL The local operator seat, never gated: list, author, build, load, route, bind, unload, cluster, and inspect.
Real HTTP + WebSocket A Bearer-authenticated control plane with an allow-AI gate and a live sense stream; the loadable surface-http creature.
Real MCP hub alpha mcp is itself a GAWD node: its surface-mcp creature owns stdio and turns each tool call into a Verb on the node’s own bus.
WHERE IT GOES NEXT
Designed in now, built later.
These are designed into the contracts already, so reaching them is hardening and extension, not a redesign. Partial means a mechanism exists; designed means it is specified, not yet built.
Partial LLM-backed authoring The AUTHORING socket is real; the shipped reference author is a deterministic template matcher. An LLM author binds the same socket.
Partial Cross-Realm placement The distributor places work within and across nodes today; placement intelligence that spans Realms is the next rung.
Partial Budget gradient CPU, WASM fuel, and critter operations are metered; memory and wall-clock gradients are designed onto the same signal.
Designed UDP / delay-tolerant transport Store-and-forward over an unreliable or light-lagged link, for the edge and off-world nodes.
Designed Omega discovery + hosted registry Public-scale publication, discovery, and a Bestiary that spans Realms.
Designed Richer trust models Consensus, weighting, and Sybil-resistance ride the envelope primitives; the concrete models stay injected per deployment.
Designed Declarative runbooks A scenario format an operator authors and the control plane replays as Verbs over the bus, against a live remote node.
DELIBERATELY DEFERRED
Out of scope, by design.
These are deferred on purpose, not forgotten. Some are business surface; one, kernel-baked consensus, is something we deliberately refuse to build, because the model belongs to the operator.
Designed Hosted gawd.ai Managed Realms, a hosted registry, identity roots, and a product UI: the likely business surface, not a shipped service.
Designed External security audit The current release is source-first and pre-1.0. No third-party audit has been done.
Designed Kernel-baked consensus Consensus stays an injected model by design: fabric, not model.
Designed Native untrusted sandbox Run untrusted code as a beast or critter; native daemons remain trusted by admission.
WHAT WILL NOT CHANGE
The invariants under all of it.
Fabric, not model
The kernel ships sockets and mechanisms; every model (placement, policy, fitness, consensus) is an injected creature.
No second-class primitive
The trust primitives ride structurally on every envelope, designed in once, not bolted on per feature.
Containment is opt-in
Choosing a tier is the security decision. Native is trusted by admission; untrusted code runs as a beast or critter.
Verifiable, not opaque
Every claim points at a signature, a test, or a journal entry you can check for yourself.
Take no side
The substrate forces neither order nor chaos; selection decides, bounded only by the life-safety floor.