Lumen documentation

Lumen is a research environment that keeps objectives, work, execution, artifacts, claims, and evidence connected. The current build begins with a deterministic local research story so every later provider and workflow can be added behind a contract that already works end to end.

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.

Current checkpoint

The deterministic local path uses PostgreSQL as semantic truth and the filesystem as immutable artifact storage. The static workbench sends typed REST commands and resumes typed events through authenticated fetch-based SSE. Cloud and paid-provider pages identify their activation gates; they do not claim a live capability merely because its target architecture is documented.

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.