at rest
Manifest
The creature contract: what it is, what it can do, where it can run, who signed it.
nameversionabientrypointscapabilitiesrequirementsprovenancecontent_addressprovides
THE RUNTIME
GAWD, the runtime.
An AI-first substrate where an intelligence authors, compiles, signs, ships, and runs its own creatures across any body: server, robot, satellite, edge. The AI is the primary operator. Humans supervise.
THE TENET
Fabric, not model.
The runtime ships sockets and mechanisms. Creatures supply the models. If nothing is plugged in, the runtime does not choose the model for you.
Same rule, two scales: the lab treats ASI as fabric; a node treats the kernel as fabric. The kernel exposes time, trust, consensus, and permission primitives, then leaves meaning to creatures and operators.
lab scale ASI = fabric + models in motion
Many models produce work that other models consume.
node scale kernel = sockets + mechanisms
Injected creatures define policy and behavior.
explicit choice
models and policy stay outside the kernel
TWO CONTRACTS
Everything can change but two things.
The Manifest pins down a creature at rest. The Envelope pins down a message in motion. Get those right and the rest can move: engines, policies, transports, registries, and the creatures themselves.
in motion
Envelope
The message contract: one local and remote wire shape, with trust primitives carried in the header.
fromtoseqcausalstampsigcorr
THE CREATURES
Three tiers, two axes.
daemon
realNative shared library. Fastest, closest to the host, trusted by admission.
beast
realWebAssembly. Portable, sandboxed, clean to unload, safe to ship between nodes.
critter
realRhai script. Cheap variation, sandboxed, metered, and no compiler needed.
maturation
critter → beast → daemon
learning hardens into instinct once a behavior earns trust.containment
daemon → beast → critter
choosing the tier is the operator's security decision.THE WORKSPACE
What actually runs.
fixed kernel
sanctum
lifecycle
routing
admission
gawd-manifest
Manifest type, validation, crypto.
aether
Envelope, Address, Router, journal, ModuleInstance seam.
gawd-engine
NativeEngine, WasmEngine, ScriptEngine.
sanctum
The three-job kernel: lifecycle, routing, admission.
gawd-sdk
Creature authoring surface. No kernel dependency.
sanctumd
Node daemon and REPL control loop.
Transport, registry, authoring, and admission policy are ordinary creatures on the bus. The substrate's organs load through the same path as user work.
THE LOOP
The composed loop.
One agent drives one pipeline. The same Envelope shape crosses in-process hops, native seams, WASM boundaries, and authenticated TCP.
01 author
02 build
03 sign
04 ship
05 admit
06 load
07 run
08 reload
09 gate
The reload is not a restart. The kernel deregisters, drains, then unloads the engine. A 1000-cycle reload loop proves the path stays RSS-stable and ASan-clean.
MATURITY
What is real, and what is still hard.
The source release proves the major mechanisms in code, tests, and demos. Pre-1.0, unaudited, not yet hosted.
Native trust limit
A native daemon is trusted by admission. If an operator loads native code, the operator vouches for it.
Cross-tier ABI evolution
Daemons, beasts, and critters run today. Moving behavior cleanly across tiers is still ongoing work.
Production federation
Federation mechanisms exist. Hosted membership, registry operations, and external trust hardening still need the full service layer.
POSITIONING
Open core below, hosted federation above.
open core
Sanctum runtime
runtime, Manifest contract, infrastructure creatures, wire protocols.
hosted gawd.ai
managed federation
Realms, Empyrean registry, discovery, identity roots, federation as a service.
BOUNDARIES
What GAWD is not.
- not a workflow designer
- not another agent framework
- not a single-machine plugin host
- not a cluster scheduler for fixed workloads