Skip to content
Lenso
English
Esc
navigateopen⌘Jpreview
On this page

Repository map

Route changes to the repository that owns the Interface and its evidence.

Repository Current ownership
LioRael/lenso App Plan, portable Kernel, Kernel conformance, canonical ADRs
LioRael/lenso-runtime-rust host-side Drivers, Runner, and native Execution Adapter
LioRael/lenso-bun-adapter Bun SDK, child-process Adapter, and lenso-host-runtime
LioRael/lenso-protocols Descriptor codegen, portable contract runtime, value conformance
LioRael/lenso-cli authoring, project checks, Plan resolution, transition CLI
LioRael/lenso-examples executable examples and product-neutral fixtures
LioRael/lenso-web backend HTTP Endpoint/Client Capabilities, Ingress/Egress Plugins, and optional OpenAPI document Plugin
LioRael/lenso-auth-plugin portable Auth Capability and assertion SDK
LioRael/lenso-otel-plugin removable OpenTelemetry Plugin
LioRael/lenso-site this versioned public documentation

Dependencies point inward toward the portable core. A change that needs core to import one of these concrete owners is usually at the wrong seam.

Choosing an owner

  • Graph, lifecycle, invocation, cancellation, readiness, or diagnostics semantics: core Kernel.
  • Scheduling, time, joins, or host shutdown: Runtime Driver.
  • Plugin generation, process/wire endpoint, or isolation: Execution Adapter.
  • Product behavior, state, Auth, secrets, telemetry, or UI: ordinary Plugin.
  • Package edits, lock inspection, schema/codegen freshness, or Plan resolution: authoring tooling.

The CLI declares and prepares TypeScript/Bun Hosts; lenso-host-runtime assembles the Rust Kernel and Bun/Process Adapters. See TypeScript Host for the entrypoint and current limits.

Last updated on September 6, 2026

Was this page helpful?