Developers
Architecture concepts
Understand the boundaries between modules, tenants, workflows, and executors.
Control plane and business modules
The control plane handles identity, tenants, shared governance, and task admission. Business entities, resource ACLs, and dedicated APIs belong in modules. UI visibility is not authorization; APIs and the database enforce access.
Modules
A module is a reviewed business boundary with a manifest, configuration, API, UI, permissions, and optional workers. Modules cannot freely query each other's data.
Organizations and workspaces
An Organization defines tenant isolation. A Workspace defines a collaboration scope. A supplied tenant identifier selects a context; the server must still verify membership and resource access.
Tasks, workflows, and executions
A business transaction writes a task and its outbox entry together. Progress and results use the stable task ID across retries. Each task has a workflow started with a deterministic Workflow ID. An execution is an attempt; at least once delivery requires idempotent external effects.
Bridges and executors
Workflow activities use bridges to invoke executors in different runtimes. The protocol stays stable. A local journal covers one node, not consistency across nodes.
Collaboration
Broadcast, receipt by another client, and durable server storage are separate states. The system can report “saved” only after meeting its durability contract.
Agents and tools
Model output is data, not authority. Tool calls require identity, tenant and resource checks, scope, budget controls, and audit.
Capability states
- Source tested: pure logic, static checks, or local executor tests have run.
- Integration skeleton: integration code exists, but a complete real-service verification is still missing.
- Contract awaiting implementation: boundaries and acceptance criteria exist; implementation is incomplete.