Understand the system
Understand the system
Learn which subsystem owns truth, execution, bytes, isolation, and browser delivery.
Lumen has two backend roles from one modular Python codebase: app owns authenticated commands,
reads, streams, and trusted gateways; worker owns durable workflow activities, dispatch, provider
reconciliation, and artifact finalization. The static workbench and static documentation are separate
artifacts and hold no privileged credential.
Ownership map
- PostgreSQL owns current semantic state and durable product events.
- Immutable object storage owns canonical artifact bytes; the filesystem is the local implementation.
- Temporal owns durable execution history, not research truth.
- Isolated compute runs disposable attempt and notebook processes.
- The browser uses REST commands, resumable authenticated SSE, and narrowly ticketed runtime sockets.
Start with execution and state, then follow the workspace, provenance, and trust-boundary pages.