Backend support and evidence
Current corpus
Section titled “Current corpus”The Lucid suite guide owns the case inventory and generation/native-compilation obligations. Three positive future cases additionally execute generated assertions. The generated inventory lists the registered cases.
Rejection corpus
Section titled “Rejection corpus”Malformed compositions must return classified errors without changing inputs, returning partial bundles, or panicking. The Lucid guide records the rejection families and focused checks. Its frozen manifest protects the eighteen segment definitions; expected artifacts remain independent oracles.
What the evidence does not say
Section titled “What the evidence does not say”Generation, compilation, and execution establish different facts. Compile-only selection and scheduling cases do not establish runtime fairness, cancellation, cleanup, or lifetime inference. Generated start/stop scripts remain unexecuted. See the backend ledger and separate frontend/runtime ledger for results tied to specific revisions and hosts.
Integration limits
Section titled “Integration limits”Deferred and three-part loops are unsupported. CV/DV and CO/COB provide bounded future composition. Function receiver methods, async-FW modifiers, general enums/patterns, implementations, and method generic parameters remain outside the maintained contracts.
Support assets
Section titled “Support assets”Config/Cargo templates supply configuration and manifests; start/stop templates produce deployment artifacts. Runtime support combines authored L policy with bounded host adapters. These assets are separate from the eighteen segments and L's public standard library.
Canonical source: docs/reference/logemes/support.md.