Composition
Compose public component parts while preserving their native context, props and focus behavior.
Compound components
Use the root and parts exported by the same family. For example, a dialog connects its trigger, backdrop and content through Modal.Root. UI SDK manages the native top layer; no Portal part is needed:
import { Modal } from "@lenso/ui";
export function Example() {
return (
<Modal.Root>
<Modal.Trigger>Open dialog</Modal.Trigger>
<Modal.Backdrop />
<Modal.Content>
<Modal.Title>Account settings</Modal.Title>
<Modal.Description>Manage your account preferences.</Modal.Description>
<Modal.Close>Close</Modal.Close>
</Modal.Content>
</Modal.Root>
);
}The root coordinates open state and focus restoration; the heading and description label the popup. Keep these relationships when rearranging the content.
Interaction boundary
UI SDK owns ordinary native controls, navigation and overlays. Lenso composes concrete native parts with component-specific StyleX maps; there is no generic compatibility wrapper that translates every family into another library's API.
ListBox uses native UI SDK scalar or array values and selection callbacks. TagGroup and Table retain Lenso's separate collection model with stable keys, Set-based selection, registered items and collection-aware focus. They are not React Aria collection wrappers. Read each family's signatures rather than assuming that these collection contracts are interchangeable.
Date, time and color families retain internationalized value models and compose native UI SDK controls. A date segment, calendar grid or color input section cannot be substituted into an unrelated UI SDK field simply because its appearance is similar.
Native HTML owns noninteractive structure. Cards, text surfaces and layout regions do not acquire keyboard behavior merely by being styled.
Public contracts
The public React exports determine the component family inventory. Native props, refs, state attributes, render composition and callback signatures remain observable. Local variants add presentation without inventing an onPress adapter or normalizing every value into a DOM event.
For compound families, compose their contextual parts together. The generated API identifies each actual exported part and declaration source; imported historical snippets are not executable contract evidence.
Styles and delivery
@lenso/tokens supplies themes and compiler-readable StyleX declarations. The official StyleX integration compiles package and application declarations together. Import theme CSS from every rendering document. Compiler tooling stays outside browser JavaScript.
Documentation as a projection
Public documentation is authored separately from the immutable reference archive. One versioned index combines authored guides, the current native API and local runnable example placements. Rendering, navigation, search, sitemap, copied Markdown and example-proof planning consume that index.
The reference archive remains an integrity-checked provenance input, not a public release history or migration guide. Removing public archive pages does not excuse dropping their maintained example scenarios: those scenarios belong on the corresponding Lenso component page.
Evidence boundaries
An export proves availability, and a registered local module proves a runnable placement. Neither proves visual parity, accessible keyboard operation or WCAG compliance. Source colors can have known normal-text contrast failures; report them rather than claiming certification.