Overview

Lemn UI is a provider-first ecosystem, not a collection of locally rewritten widgets. LEMN selects individual battle-tested open-source capabilities, gives each semantic capability one provider of record, and exposes a stable provider-neutral API with a minimal compiled branding layer.

What this workspace owns

@lemn-ltd/brand-contract: BrandingDefinition v1, deterministic compiler, diagnostics, signed artifact envelope, semantic tokens, font governance, and Recharts/ECharts theme projections.
@lemn-ltd/brand-runtime: server-only active/preview resolution, integrity verification, selected-mode projection, SSR markup helpers, and one embedded branded fallback.
@lemn-ltd/ui: controlled components, visualizations, styles, blocks, and public catalog metadata.
@lemn-ltd/brand-studio: controlled, persistence-free authoring wizard and real component preview. Hosts supply catalog data and execute typed intents.
A Git-authoritative provider registry with exact origins, licenses, notices, adapters, conformance, and reviewed update status.
One Lemn UI Portal with a public Catalog and Access-protected Admin under the same Worker and release identity.

Non-negotiable boundaries

Consumers install exact approved @lemn-ltd/* versions; never latest.
Consumers never import an upstream UI provider for a catalog-owned capability.
Components consume compiled --lemn-* roles, never source branding JSON or Workspace-specific variable names.
Production hosts resolve and verify branding before the first HTML byte.
AgentOps owns Workspaces, versions, persistence, publication, activation, preview sessions, authorization, and audit.
Data fetching, routing, authentication, global state, internationalization, analytics, and product policy remain outside the UI packages.

Production surfaces

Start with Install and use, then read Architecture, Branding, and the SSR branding runbook.