@lumenflow/surfaces
v5.3.2
Published
LumenFlow kernel surfaces — HTTP, CLI, and MCP integration layers (LumenFlow Proprietary cloud-facing boundary, ADR-011 §1)
Maintainers
Readme
@lumenflow/surfaces
LumenFlow kernel surfaces — HTTP, CLI, and MCP integration layers.
License: LumenFlow Proprietary (cloud-facing boundary per ADR-011 §1).
Scope
This package hosts the integration surfaces external consumers (including
lumenflow.cloud) can link against without pulling Proprietary-licensed code:
http/— the HTTP tool-invocation surface (POST /tools/:name), auth, scope enforcement, AG-UI adapter, control-plane event subscriber, sidecar entry point.cli/— CLI glue for gates, inspect, task lifecycle surfaces.mcp/— MCP server entry point.
License boundary
Per ADR-011 §1, the LumenFlow Proprietary boundary sits at @lumenflow/surfaces so that
proprietary or differently-licensed consumers (e.g. the cloud conductor) can
call the tool-invocation surface without inheriting Proprietary obligations. Deep
CLI-only glue that must remain Proprietary lives in @lumenflow/cli.
Consumption today
Internal callers consume this package via TypeScript path aliases against the
source files (see apps/web/tsconfig.json). A proper pre-built dist/
artifact for external npm install consumption is tracked separately — the
pre-existing cross-package relative imports (../../control-plane-sdk/src/*,
../../host/src/workspace-config/*) need to be refactored to package-level
imports before the source can compile in isolation. Until that lands, this
package is "source-shipped": the tarball contains .ts files and consumers
bring their own TypeScript toolchain.
Related
- ADR-011 — Conductor-Mode Kernel Surfaces Architecture
- WU-2637 — SDK contract mirror (Apache boundary establishment)
- WU-2839 — This license flip (Proprietary → LumenFlow Proprietary)
