Skip to main content

Architecture Decision Records

ADRs explain why LSF works as it does and which constraints an implementation must preserve. Acceptance records an architectural decision; availability comes from the current implementation and its qualification. Superseding a decision requires another ADR with an explicit scope.

Current implementation​

The standalone node executes Component Model capsules in fresh Wasmtime Stores, resolves immutable local routes and uses activation-scoped capability grants. It provides exact publication admission, bounded OCI transfer, isolated compiler work, authenticated native reuse, managed delivery and shared HTTP ingress. The closed Angular renderer and static web targets use that shared ingress. See the architecture overview, execution profiles and current host ABI for the supported boundary.

Application transactions, durable effect dispatch and clustered control remain planned. A fixed execution-host backend for process-compromise containment is also unavailable. A compiler sandbox does not supply that guest boundary.

Read superseded decisions in context​

  • ADR-0027 replaces the original one-component/one-publication association with exact tenant-scoped publication authority.
  • ADR-0025 separates immediate capability calls from future transactional intents.
  • ADR-0029 adds an explicitly configured Bearer transport alongside the restricted static OCI profile. Its tested topology does not imply support for every registry.
  • ADR-0032/0033 extend the original ABI with exact HTTP/blob resource ownership; ADR-0035 adds the buffered async application contract.
  • ADR-0039/0040/0042 record the shared listener, installed Angular adapter and optional scoped backend request beyond the initial renderer qualification.
  • ADR-0043 adds a distinct static target. ADR-0044 supersedes its original old-format recovery policy and the obsolete catalog/selector compatibility in ADR-0019/0027.
  • ADR-0041 governs documentation ownership, versions and publishing. A working website build does not complete human guide review or authorize a runtime release.

Dates, original rationale and historical measurements remain useful decision history. Current guides and reference pages must use the implemented contract; old implementation snapshots are not setup instructions.

Decision index​

Runtime and authority​

Packages, trust and activation ownership​

Capabilities and application hosting​

Documentation and current alpha contracts​