Worldant builds a world by discovering filesystem artifacts, validating imports and migrations, transpiling TypeScript, reflecting schema, and publishing an immutable run snapshot.

OXC is the compiler frontend and owns parsing, artifact semantics, graphs, transformation, and emitted files. Before native Command source is staged, an optional final diagnostics-only plugin also checks its complete TypeScript source/type closure with Worldant's pinned TypeScript-Go artifact. Browser authoring performs the same acceptance check for mounted presentation and receiver-owned Command roots in its compiler worker after exact package declarations are prepared. The checker cannot emit code, alter catalogs, or contribute compiler facts.

Native checker bundles include the pinned Bun/Node declaration graph used by the embedded runtime, so acceptance validation preserves supported node: and bun: imports. Browser package graphs carry complete explicit runtime relationships and matching declaration relationships. Both checker loaders recompute exact declaration inventories against compiled pins before checking; a rewritten manifest cannot silently remove part of the type environment.

A definite semantic error blocks the candidate before staging or browser activation. Missing, corrupt, crashed, or timed-out checker execution also blocks explicitly; native authoring never falls back to an unchecked snapshot, and browser authoring retains its previous active generation and package locks.

The host serves compatible snapshots. New calls use the current compatible snapshot. In-flight Workflow runs stay pinned to the snapshot they started with.

Serve first evaluates working-tree configuration for data and build settings, publishes a new snapshot, then loads serving settings and middleware from that snapshot. The snapshot configuration is evaluated once and remains authoritative for the process lifetime. Editing worldant.ts does not hot-reload a running node; stop and rerun serve to publish and apply a new snapshot.

Every enabled inbound transport binds before Workflow workers or the sweeper start. A bind failure releases all acquired listeners, starts no background work, and never reports readiness. The newly published immutable snapshot remains available even when binding later fails.

Commands execute immediately. Workflows replay from a PostgreSQL journal. Steps perform supported IO at durable boundaries.

Hosted capabilities are intentionally explicit:

• PostgreSQL reads and writes.
• Explicit Command transactions.
• Workflow scheduling and replay.
• Step database effects with durable completion.
• Event and collection transport facilities.
• The full Bun/Node builtin surface in Commands and Steps: external fetch, timers, filesystem access, and node:/bun: modules, exactly as a normal Bun process provides them.

Workflow bodies stay deterministic regardless: the build rejects external imports reachable from a Workflow closure, and replay contexts expose no IO surface.