Lumen documentation

Lumen is a research environment that keeps objectives, work, execution, artifacts, claims, and evidence connected. Its deterministic local profile and production adapters share the same durable contracts, so enabling a provider changes deployment configuration rather than product semantics.

Choose a task

• Set up a local environment from a clean checkout.
• Run the first research story and inspect its evidence.
• Learn the workbench nouns before working with projects and runs.
• Understand execution and state before changing durable work.
• Operate and recover the local stack.
• Review the trust boundaries before enabling real data or credentials.
• Use generated reference for exact API, settings, IDs, states, events, limits, and CLI contracts.

Capability boundary

PostgreSQL is semantic truth and the filesystem or R2 is canonical for immutable artifact bytes. The static workbench sends typed REST commands and resumes typed events through authenticated fetch-based SSE. Temporal coordinates durable work, while local Docker or Daytona isolates attempt processes. Provider adapters remain explicitly unconfigured when their credentials are absent; deterministic fakes prove their contracts without becoming an implicit paid fallback.

Documentation contract

This site is fully prerendered. Search data is downloaded only after search opens. It makes no authenticated application request and has no runtime dependency on the Lumen API. Machine-readable reference pages are generated from current source contracts during the build.