Worldant is being rebuilt around one idea: a world is a directory that can grow into database schema, immediate Commands, durable Workflows, internal Steps, event streams, and generated runtime knowledge.
The project is actively in progress. The current documentation describes the direction we are implementing, not a stable production API.
The goal
Developers and AI tools should be able to add capability by editing files, running a validated build, and receiving a stable world interface. Clients call Commands for immediate work and run Workflows for durable orchestration.
The boundary
Worldant owns the runtime, PostgreSQL truth, build snapshots, durable Workflow replay, event streams, and the client protocol. UI and application services remain separate consumers.
The proof
The design is proven when a small application world can publish a snapshot, call Commands, run long Workflow jobs durably, subscribe to data changes, and keep every participant on the same committed PostgreSQL truth.