Core modelOperationalEnvironment scoped
Modules
Named groups of entities that own their schema and every contract that touches it.
Instances4Placed in the selected environment
Replica freshness9 / 129 of 12 copies current
Regions3Holding a copy of this environment
In flight2Runtime work running right now
What it guarantees
A module deploys as part of its application and runs as many keyed instances as callers ask for. The boundary is explicit: state stays private to the module, and its exported contracts are the whole public surface.
- Declare a complete entity graph in one module
- Keep tables, queries, actions, events, and workflows inside one boundary
- Reach another module through an imported contract rather than a shared table
Configured resources
What this capability is holding up in the environment in scope right now.
| Resource | Kind | State | Configuration |
|---|---|---|---|
| battles | Module | Active | Battle rooms, entrants, and the rolls each round settles on |
| wallet | Module | Active | One durable balance per player |
| inventory | Module | Active | Item custody, trade holds, and the handoff to delivery |
Telemetry
Registered3 modulesAll of them in the active release
Exports24 valuesContracts and resources
Boundary checks100%No module reads another's tables
Recent activity
- Module graph validatedValidated, 4 minutes agoEvery import resolves to a registered module value.
- wallet activatedCompleted, 18 minutes agoThe release went live with six public exports.