ROADMAP

Proofs before promises.

The roadmap is not a calendar. It is a set of proofs for the parts that would sink the thesis if they fail.

WHY PROOFS

Three hard problems go first.

If native lifecycle, mobile code, or decentralized trust fails, everything built above it is decoration. So the wave proves those mechanisms before any product surface.

The current release line is source-first and pre-1.0: mechanisms are proven by tests and demos, not by a hosted production service.

safe native lifecycle

mobile code across trust

trust without a center

THE GUARDING RULE

No second-class primitive.

The four proofs are co-designed around the Manifest. If a proof needs a field later, the design already failed. The contract carries the shape up front.

versionprovenancecapabilitiestierentrypointscontent addressrequirements

THE FOUR PROOFS

The wave.

module substrate

one manifest, three tiers

lifecycle

load, unload, reload

self-authoring

agent writes capability

transport

ship to another Sanctum

sandbox

contain what you distrust

Real ADR-0001 · module substrate One substrate, three tiers, one manifest, one Kernel load path.

Real POC-1 · safe native lifecycle Load, exercise, fully unload, and reload a native creature in a live Sanctum with no leaks and no undefined behavior.

Real POC-2 · AI self-authoring loop A request becomes a signed, admitted, loaded creature. Native cargo authoring and critter no-cargo authoring both ride the same loop.

Real POC-3 · inter-node transport A creature authored on one Sanctum ships to another over ed25519-authenticated TCP, then verifies, admits, loads, and runs there.

Real POC-4 · capability and sandbox WASM fuel/memory limits, critter operation budgets, and bus-level call gates work when invoked. Native remains trusted by admission.

THE CONNECTIVE TISSUE

An agent that runs the loop.

The AI-first control surface is not a separate proof. It is the API that threads through all four: list nodes, author, build, load, unload, place, publish, and read telemetry.

Real REPL The local operator seat: list, author, build, load, route, bind, unload, and inspect.

Real HTTP + WebSocket API Bearer-authenticated daemon control plane with an allow-AI gate and live sense stream.

Real MCP bridge gawd-mcp is a stateless stdio MCP server that proxies tool calls to the daemon.

NOW · NEXT · LATER

The phase ladder.

The cosmology climbs only when criteria are met. No dates, no implied maturity. One Sanctum now, a Realm next, Empyrean later.

Real Now: Sanctum A node that loads, routes, unloads, authors, budgets, and exposes supervised AI control.

Partial Now: Realm seed Peer Sanctums ship code and route across trust. The mechanism exists; hardened membership and operations still need work.

Partial Next: Empyrean service Federation primitives, reputation, quarantine, and registry seeds exist. A public hosted graph is later.

DESIGNED FOR NOW, BUILT LATER

Primitives we design for now.

Placement, Abode continuity, proof-of-trust models, and entropy are designed into the contracts now so the wave does not paint itself into a corner.

Partial Production security posture The mechanisms are real, but the project is pre-1.0 and unaudited. Native code is still trusted by admission.

Partial Long-lived Abode continuity Migration and fork/merge are proven; sustained identity across a real fleet is not yet a product.

Designed Consensus and weight models The primitives are on the envelope. The concrete trust model stays injected, not kernel-baked.

Designed Hosted registry and managed Realms The likely business surface, but not yet a shipped service.

Partial External developer ergonomics The SDK, manifest, daemon, MCP, demos, and docs exist; the public quickstart still needs a calmer path.

DEFINITION OF DONE

The loop that proves the substrate is real.

01 author

02 load

03 sandbox

04 ship

05 verify

06 run

07 publish

08 reload

Partial Composed governing loops The suite proves authoring, distribution, migration, federation, selection, and immune response through the real mechanisms. It is strong proof, not a hardened deployment.

OUT OF SCOPE

What waits until the wave lands.

These are deferred by design, not because they are forgotten. They become meaningful only after the wave's proofs hold.

Designed Production SLA No hosted availability promise exists yet.

Designed External security audit The current release is source-first and unaudited.

Designed Kernel-baked consensus Consensus remains an injected model by design.

Designed Native untrusted sandbox Run untrusted code as beast or critter; native daemons are trusted by admission.

See the runtime →
Why these are the proofs that matter →