Lucim ships capabilities in three runtime stages. LUCIM_STAGE controls whether staged REST routes, MCP tools, and console views are available.
Code presence does not mean a workflow is mounted or automatically orchestrated. Lucim distinguishes implemented services, mounted routes, worker-registered jobs, and end-to-end automation.
Independent gates
High-risk or provider-backed capabilities have their own switches in addition to the stage gate. Examples include Firecrawl acquisition, Exa search, repository scanning, dependency evidence producers, provider routing, live observations, and sandbox execution.
The sandbox execution plane defaults off even when its control-plane models and routes are present. Enabling it requires immutable runtime identity, provider conformance evidence, a dedicated worker, and credential-broker controls.
Client behavior
Clients should treat a missing higher-stage route or MCP tool as “not enabled,” not as evidence that the deployment is unhealthy. Do not synthesize staged results into live tenant totals. 