Capabilities
What the platform can do, grouped by area, with the live state of each capability in this project.
Area
Core model
| Capability | Status | What it does |
|---|---|---|
| Modules | Operational | Named groups of entities that own their schema and every contract that touches it. |
| Instances | Operational | Every module key identifies one isolated store, one work queue, and one lifecycle. |
| Validation | Operational | Typed boundaries turn malformed values away before state or a handler is reached. |
| Execution | Operational | One call at a time per instance, so every keyed store runs its work in order. |
Data
| Capability | Status | What it does |
|---|---|---|
| Schema | Operational | Exported table values give each module the private shape and indexes it reads through. |
| Durability | Operational | Committed changes append to a durable history and batch into object storage. |
| Search | Operational | Module-owned indexes keep searchable documents aligned with committed state. |
Contracts
| Capability | Status | What it does |
|---|---|---|
| Queries | Operational | Read-only contracts run against committed state and stay live while a caller subscribes. |
| Actions | Operational | Write contracts run against one instance and may call other instances inside one commit. |
| Events | Operational | Typed committed messages fan out to subscribed callers and to instance consumers. |
| External effects | Watching | A third-party call runs through an explicit boundary with idempotency and compensation. |
Orchestration
| Capability | Status | What it does |
|---|---|---|
| Queues | Watching | Durable per-instance work, with batching, order, retries, and dead letters. |
| Workflows | Operational | Durable procedures that sleep, wait, resume, and survive a runtime restart. |
| Schedules | Operational | Intervals, cron rules, and one-shot calls invoke a contract per instance. |
Platform
| Capability | Status | What it does |
|---|---|---|
| Runtime | Operational | Each active instance executes inside a runtime bounded by the permissions it was granted. |
| Observability | Operational | Logs, traces, and lifecycle records carry the instance they came from. |
| Limits | Watching | Execution, state, payload, queue, and workflow budgets protect shared capacity. |
Scale
| Capability | Status | What it does |
|---|---|---|
| Placement | Operational | A home moves toward the traffic calling an instance, and its identity never moves. |
| Servers | Operational | Adding a regional server adds capacity, homes, and local read coverage. |
| Replication | Operational | Readable replicas form near read traffic and follow the home's committed writes. |
| Cross-instance calls | Operational | An imported contract crosses an instance boundary and joins one nested transaction. |
Delivery
| Capability | Status | What it does |
|---|---|---|
| Deployments and releases | Operational | An immutable release of a whole application moves through admission into an environment. |
| Storage | Configured | One object store for the project holds compacted state and write-ahead logs. |
23 capabilities on this platform