The product vocabulary.

Domain holds product-specific components that go beyond generic UI — Tarva-original material that encodes Tarva's own product concepts: agents, pipelines, governance, a painter sub-portal. This is where the design system meets one product's language. Tarva ships these as the reference implementation; a Lumos build would define its own domain layer here — practitioners, treatments, memberships, client journeys.

Domain components

Sub Portal · the painter sub-portal cluster

A self-contained cluster for the painter sub-portal — its own brand surface, payout view, and job-run rails. Brand Mark · Iso Payout · Job Context Rail · Milestone Strip · Sub Job Card

Why it's light here

These are Tarva's own product surfaces, off-brand for a wellness book — so this chapter maps the layer rather than dressing agents and jobs in clinic clothes.

Not app-agnostic

Domain composes primitives from Components but bakes in product semantics, so it is not interchangeable with generic equivalents. Reach for Components for app-agnostic UI.

The product layer

Domain is the product layer. These are Tarva's — shipped as reference. In a Lumos build, this is where you'd define your own domain components — practitioners, treatments, memberships — on top of Foundations, Components, and Patterns.

8.5 × 11 · Portrait