Prepared by claude-mac-worker at Elikem's request. This is the rulebook for a complete, Linear-inspired overhaul of Oshun's user interfaces. It says what every surface must obey, how the rules are tuned for the builder side and for Lilith, what the numbers are, and how conformance is checked by machine. It changes no code. Approval is Elikem's.
Evidence for every statement about the current state is in the companion audit, UI surface and design-token inventory (2026-10-10), Eve document 5f8247c4-64de-4716-b52e-a44fcea64c27.
Decisions asked of Elikem#
Approving this document approves these. Each has my recommendation; any can be changed before approval.
| # | Decision | Recommendation |
|---|---|---|
| D1 | Lilith gets the complete overhaul under the same rules, with its own tuning and identity. | Decided by Elikem in conversation, 2026-10-10. Recorded here. |
| D2 | The builder side shares one neutral ladder and one accent. Workbenches give up the terracotta accent and warm linen ground. | Yes. The warm palette was matched to Lilith's cream theme, which was retired on 2026-09-27. Use Eve Workspace's cool neutrals and violet accent across Eve, admin, tenant admin and the studio workbenches. |
| D3 | Builder faces are Geist and Geist Mono. Lilith keeps Atkinson Hyperlegible Next and Newsreader. | Yes. Eve Workspace already self-hosts Geist. The workbench layer names Inter, JetBrains Mono and Cormorant Garamond, for which the audit found no loader. |
| D4 | Density is fixed per register. The admin compact toggle and the workbench density multiplier are removed. Text size stays adjustable. | Yes. A density toggle doubles every state to verify and moves a design decision onto the user. |
| D5 | Metis web follows the Lilith register and Metis admin the builder register. | Yes. Metis web is a member-facing room; Metis admin is an operator console. |
| D6 | Dormant surfaces (about fifty apps with no deployment and no real commits since August) are out of scope until one is revived; a revived app adopts this system before it ships. | Yes. Overhauling them now spends effort on UI nobody sees. This narrows "all UI" to all UI that is live or in release scope, so it needs an explicit yes. |
| D7 | libs/oshun/design-tokens becomes the single token engine and libs/oshun/ui the single web primitive set. The four component systems inside the member app converge on it. |
Yes. |
1. What this is and where it comes from#
The starting point was The Linear Design Philosophy (an independent 28-principle field guide dated October 2026, supplied by Elikem as a PDF). I agree with its principles. I did not check its citations of Linear's own writing against the originals. This doctrine keeps its order of work and its core rules, and changes four things:
- It replaces the guide's interview-based review tests with machine checks, because Oshun is one person and a fleet of agents.
- It replaces the guide's seven illustrative hex values with generated, contrast-checked scales. By my calculation two of the guide's own pairs miss the 4.5:1 minimum for body text.
- It adds what the guide leaves out: real numbers, light and high-contrast themes, touch and watch, agent surfaces, writing, and loading behaviour.
- It tunes the rules separately for tools and for a consumer media product.
The guide's own warning is the main risk here: importing a dark gray and purple look without the underlying discipline. The rules in section 3 come first; the look in section 6 follows from them.
2. Where we start#
From the audit:
- Eight surfaces are live: member web (715 pages, 498 of them under
/studio), admin, tenant admin, Telegram mini-app, Metis web, Metis admin, Eve Workspace and the corporate site. Five more are in release scope but not deployed: the member, admin and Eve mobile apps, the watch apps and the Isis web client. - Three current design systems coexist (Lilith Web, Oshun Workbenches, Eve Workspace), each with its own role names, faces and accent, plus an older shared token library that almost nothing uses.
- They already agree on spacing, builder radii, builder motion and easing. They differ in colour, type and naming.
- The debt is hard-coded values and duplicated primitives: 8,608 hex literals and 10,547 numeric
rgb()literals in the member app, 384 distinct font sizes, four button implementations and 4,810 raw<button>elements, at least ten command palettes across the repo. - Good gates exist but each covers one system: the workbench browser audits, Lilith's palette regression test and Eve's browser suite. Nothing checks the whole repo.
So this is a convergence more than a blank page. The recent work on the three systems is the raw material; what is new is one engine under them, one primitive set, one set of gates and a stricter standard.
3. The doctrine#
Sixteen rules. Each has a check, and section 9 says how the check runs. Work on a surface proceeds in the order of the first three rules.
Order of work#
- Remove concepts before removing pixels. Before restyling a surface, list its objects, states and steps, and delete or merge what is redundant. A restyle that keeps fourteen overlapping object types has failed. Check: each surface's task records its object and step count before and after.
- Design the task, not the feature inventory. Navigation is organised by what a person is doing or looking at, not by which service owns it. A task that crosses modules carries its context forward. Check: each archetype's primary journey is one Playwright flow that never returns to a home screen to find the next step.
- Opinionated defaults over options. One layout, one density and one theme set per register. A setting exists only for accessibility (theme, contrast, text size, reduced motion) or where people's needs differ materially. Check: no new display setting is added without a named accessibility or task reason.
Attention and structure#
- Content wins; chrome is quiet. Each view has one focal point. Navigation, toolbars and metadata sit at lower contrast than the content they frame, without dropping below the contrast floors. One primary action per view. Check: at most one accent-filled control is visible per view outside dialogs.
- Structure is felt, not drawn. Group by proximity and alignment first, then by a tonal step, then by one hairline. No box inside a box. A card is only for an object that can be opened, selected or moved. Check: the workbench card-use and composition audits, extended to every archetype.
- Density serves the task. Show the most decision-relevant information that can be scanned comfortably. Lists summarise, detail views explain, editors change. Empty space is never a substitute for organisation, and compression is never a substitute for hierarchy. Check: row heights and control sizes come only from the register's size roles.
- Every screen is one of a few archetypes. Titles, search, filters, view switches, bulk actions and detail panels live in the same place on every screen of the same archetype (section 7). Check: each route declares its archetype; slot positions are asserted per archetype.
- Actions live with their objects. Row menus, inline edits, selection bars and context menus act on what is visible. The target of a destructive action is named before it is confirmed, and can be undone where the system allows. Check: destructive controls use the danger role and have an undo or a confirmation that names the object.
Visual system#
- Colour is scarce and means something. Neutrals carry the interface. One accent family per register marks the primary action, selection and focus. Status colours mean status only, sit at least 30 degrees of hue from the accent, and always travel with a shape or a word. Every colour in product code is a role, never a literal. Check: token lint; the signals audit; grayscale screenshots still show the hierarchy.
- Type carries hierarchy. A small set of named text styles per register; no free font sizes or weights. Numbers in tables and counters are tabular. No all-caps except the overline style. Check: token lint rejects font sizes outside the type roles.
- Geometry is exact. Spacing, radii, sizes and layers come from the scales in section 6. Icons are one family at one stroke weight, optically aligned to text. An icon without a label must be a universally known one and has a tooltip and an accessible name. Check: token lint for spacing and radius; icon imports restricted to the one family.
- Motion explains, and never blocks. Motion shows where something came from, what changed or that an action registered. It never delays input, never loops for decoration, and respects reduced motion. Hover and press feedback is 120 ms or less; panels 180 to 260 ms. Check: durations come only from motion roles; with reduced motion every duration resolves to zero; input is accepted during every transition.
Behaviour#
- Fast is part of the look. Every input is acknowledged within 100 ms. Writes that can be rolled back are shown optimistically; work that cannot is shown as honest progress, never as a result that has not been computed. Loading uses skeletons that match the final layout, so nothing shifts. Check: interaction-to-acknowledgement measured on the primary journeys; layout shift budget of zero on archetype loads.
- State is never ambiguous. Empty, loading, partial, error, offline, permission-denied and long-content states are designed for every component and archetype, with a next step in the message. A failed action says what failed and what to do. Check: the state matrix in section 9.
- The interface remembers. Filters, selection, scroll position, open panels and unsent drafts survive navigation and return. Changing one field never resets the view. Check: a return-to-list flow per index archetype asserts scroll, filter and selection.
- One command model, many routes. Every action is defined once in a command registry with its label, shortcut, permission and handler. Buttons, menus, the command palette, keyboard shortcuts and Eve all invoke that same definition. Everything reachable by keyboard is reachable by pointer and touch, and the reverse. Check: each command is registered once; shortcut collisions scan; core journeys pass keyboard-only.
Accessibility is not a separate rule because it is the floor under all of them: WCAG 2.2 AA on every theme, 7:1 text in the contrast themes, visible focus, forced-colours support, full keyboard operation.
4. One system, three registers#
The rules apply everywhere. Their tuning differs by what the surface is for.
| Builder register | Lilith register | Stage | |
|---|---|---|---|
| What it is for | Tools people work in for hours | A product people browse, read, watch and talk to | The content itself, wherever it appears |
| Surfaces | Eve Workspace, admin, tenant admin, studio workbenches, Metis admin, admin and Eve mobile, Isis web | Member web outside /studio, member mobile, watch, corporate site, Telegram mini-app, Metis web |
Reading text, media viewers, players, the member-facing preview inside a workbench |
| Focal point | The list, document or canvas being worked on | Imagery, video, the conversation, the text being read | Itself |
| Density | High; 32 px rows | Low; larger media, fewer items per screen | Set by the content |
| Colour | Cool neutrals, one violet accent | Ink primary, one hue per room, atmospheres behind chrome | Neutral surround that does not tint the content |
| Type | Geist, 13 px base | Atkinson Hyperlegible Next 17 px base, Newsreader for display and reading | Newsreader for reading; media has no type |
| Radii | 4, 6, 8, 12 | 6, 10, 14, 20, 28 | Inherits the host register |
| Motion | 80 to 260 ms, no spring | 100 to 520 ms, spring allowed for continuity between rooms and media | None of its own |
| Input | Keyboard and pointer first; command palette primary | Touch first; bottom-reachable actions; palette secondary | Direct manipulation |
| Minimum target | 24 px on fine pointers, 44 px on coarse | 44 px | 44 px for player controls |
Lilith's identity rules stand: no gold or yellow accent, the ink mark, the cool moonlight atmosphere, the room hue as its accent. The Lilith audience rules are unchanged by this document.
5. Token architecture#
One engine. libs/oshun/design-tokens holds one source file per theme and one generator, built by generalising the Lilith Web generator that is already in the repo (tokens.json to generated CSS and TypeScript, with a --check mode and contrast floors). The generators for the Eve and Workbench values, which lived only in session scratchpads, are replaced by it.
Few inputs per theme. A theme is defined by: neutral hue and chroma, accent hue and chroma, status hues, mode (light or dark) and contrast level (standard or high). The engine produces 12-step scales in OKLCH and maps them to roles. A theme never lists role values by hand, except where a measured exception is recorded in the source with its reason.
One role vocabulary. The names Lilith Web and Eve Workspace already nearly share become canonical:
| Group | Roles |
|---|---|
| Ground | bg-canvas, bg-surface, bg-sunken, bg-raised, bg-hover, bg-pressed, bg-selected, bg-inverse, scrim |
| Text | text-primary, text-secondary, text-tertiary, text-disabled, text-on-accent, text-inverse |
| Line | border-subtle, border-default, border-control, border-strong, focus-ring |
| Action | accent, accent-hover, accent-subtle, accent-text, danger, danger-hover |
| Status | status-info, status-success, status-warning, status-failure, status-pending, each with -subtle |
| Data | viz-1 to viz-6 |
| Lilith only | room-*, atmos-*, lilith-tint |
| Scale | space-*, radius-*, size-*, text-* styles, duration-*, ease-*, z-*, bp-* |
Existing names become aliases, then go. --l-*, --oshun-*, --wb-*, --admin-*, --tenant-* and Eve's unprefixed names are generated as aliases of the canonical roles so that nothing breaks on day one. Each alias family has a use count that may only fall, and is deleted at zero.
The workbench contract stays. ADR-S4 (Eve document 898431cb, currently a draft with changes requested) says the kit owns the --wk-* role names and each host owns its values. This doctrine does not change that contract. It changes what the Oshun host supplies: the --wk-* roles map to the builder theme from the engine. If D2 is approved, that needs a short amendment to ADR-S4's section on Oshun host values, written by whoever holds that ADR.
Outputs. CSS custom properties scoped per theme attribute (never bare :root for a register that can be nested), a typed TypeScript object, and a React Native theme object for the Expo apps, so web, mobile and watch read the same values. Satori and other renderers that cannot read var() use the TypeScript literals.
Themes shipped. Builder light, dark, light high contrast, dark high contrast. Lilith day, night, day high contrast, night high contrast, plus the observatory register. Admin gains a dark theme, which its token file lacks today.
6. Visual specification#
Values marked existing are already in the named system and are adopted unchanged. Values marked new are proposals of this document.
Shared scales#
| Scale | Values |
|---|---|
| Spacing (px) | 2, 4, 6, 8, 12, 16, 20, 24, 32, 40, 48, 64, 80 (existing in Lilith and Eve). Nothing off the scale. |
| Easing | standard cubic-bezier(0.2, 0, 0, 1) for change in place; enter and exit curves per register (existing) |
| Focus | 2 px ring in focus-ring, 2 px offset, at least 3:1 against both grounds it can sit on |
| Hairline | 1 px in border-subtle for dividers; border-control (3:1) for anything a user operates |
| Layers | sticky 10, navigation 20, panel 30, overlay 40, dialog 50, toast 60, tooltip 70 (existing in Lilith; Eve's 10 to 500 map onto it) |
| Icons | lucide only; 1.5 px stroke; never inside a coloured tile |
| Elevation | Tonal steps for canvas, surface and raised. Shadow only on floating layers (menu, popover, dialog, toast), and a layer has a shadow or a border, never both. |
Builder register#
| Item | Value |
|---|---|
| Faces | Geist (interface), Geist Mono (code, identifiers, keys), Newsreader (long-form reading in documents only) |
| Colour | Eve Workspace's 12-step gray, violet, teal, amber, red and blue scales in light, dark and contrast (existing; its header records 4.5:1 or better on every text pair and 7:1 in contrast). Regenerated by the engine from inputs and re-verified; any step that moves is recorded. |
| Accent | violet; light #6343b5, dark #6e4acb solid with #beb1ff for text (existing) |
| Radii | 4 (inline tags, keys), 6 (controls), 8 (surfaces, menus), 12 (dialogs), full (existing) |
| Controls | 28, 32, 40 px high; default 32 (existing in Eve) |
| Rows | 32 px list and table rows; 28 px menu items; 40 px on coarse pointers (new as a fixed rule; the sizes exist in Eve) |
| Layout | top bar 48, sidebar 248 (56 collapsed), inspector 340, reading measure 68ch, dialogs 440, 640, 960 (existing in Eve) |
| Motion | 80 ms hover and press, 120 ms small state change, 180 ms popovers and menus, 260 ms panels and dialogs (existing). No spring. |
| Breakpoints | 640, 960, 1280, 1536 (existing in Eve) |
Builder type styles (new; today Eve and the workbenches use literal sizes with 12 px as the most common):
| Style | Size / line height | Weight | Use |
|---|---|---|---|
display |
24 / 32 | 600 | Page identity on overview pages |
title |
18 / 26 | 600 | Page and dialog titles |
title-sm |
15 / 22 | 600 | Section and panel headings |
body |
13 / 20 | 400 | Default interface text, rows, controls |
body-strong |
13 / 20 | 550 | Row titles, emphasised labels |
body-lg |
14 / 22 | 400 | Prose in panels, descriptions, comments |
small |
12 / 16 | 400 | Metadata, secondary columns, captions |
micro |
11 / 16 | 500 | Overlines, key caps, counters. Never the only carrier of information a user needs. |
mono |
12 / 16 | 450 | Identifiers, hashes, code |
reading |
16 / 26 | 400 | Document body in the reader |
The default moves from 12 px to 13 px. Sizes are authored in rem so the text-size setting and browser zoom scale them. Headings 18 px and above take -0.01em tracking.
Lilith register#
Lilith Web v2's values in apps/oshun/web/src/design-system/lilith-web/tokens.json are adopted as the Lilith theme's starting values (existing): the 21 text styles from display-xl 64 px to overline 12 px with 17 px interface body and 20 px reading body; radii 6, 10, 14, 20, 28; controls 36, 44, 52 px; 44 px minimum target; top bar 56, tab bar 64, rail 88, sidebar 272, panel 400, content 1200; durations 100, 160, 240, 360, 520 ms with the spring curve; breakpoints 600, 840, 1200, 1600; the six room hues with their atmospheres.
What changes for Lilith is conformance, not palette:
- The 430 files on the older
L*components and the 65 on the still older set move to the one primitive set, themed for Lilith. - Hard-coded colours and sizes in member pages are replaced by roles.
- Each member page is assigned a Lilith archetype and brought to its slots.
- Chrome is made quieter where it competes with content; this is judged per archetype in a browser, not decided here.
- Member mobile and watch read the same generated theme instead of their own palette files.
Stage#
The neutral viewer surround the workbench layer already defines (near-black ground, neutral inks, identical in every theme) is kept for any place media is judged. Reading stages use the Lilith reading styles on Lilith's paper, including when a workbench previews what a member will see.
7. Page archetypes#
Every route declares one. Slots are fixed per archetype; domain content fills them.
Builder
| Archetype | Fixed slots | Varies |
|---|---|---|
| Index | title and count; view switch; search and filters in one bar; list or table; selection bar on select; one create action | columns, grouping, bulk actions |
| Detail | identity and status header; object actions menu; body; inspector on the right | tabs, inspector sections |
| Editor | title; body; dirty state; primary and secondary action in one footer or header position; validation beside the field | controls, preview |
| Queue | list on the left, item in the centre, decision bar with keyboard shortcuts | decision set |
| Overview | one-sentence state of the world; prioritised items that need attention; then trends | charts, alerts |
| Canvas | tool rail; stage; inspector; timeline or layers where needed | tools |
| Settings | grouped sections; each change saved in place with undo or explicit save, never mixed | depth |
Lilith
| Archetype | Fixed slots | Varies |
|---|---|---|
| Home | continuation first; then today's items; navigation at the bottom on phones and a rail from 600 px | sections |
| Room | room identity and atmosphere; primary practice or content; secondary shelf | room hue, content types |
| Reader | text at reading measure; progress; notes and listen controls out of the text column | tools |
| Player | media full-bleed on the neutral surround; controls auto-hide; one primary control | media type |
| Conversation | messages; composer fixed at the bottom; state of the assistant always visible | attachments, voice |
| Library | filterable collection of the member's own items | grouping |
| Profile and settings | grouped sections, saved in place | depth |
| Commerce | plan, price and what changes, stated before the action; receipt after | plans |
Moving a route between archetypes, or adding an archetype, is a change to this document.
8. Components, commands, agents and words#
One primitive set#
libs/oshun/ui becomes the single web primitive library, built up from what it has and from the best of the three systems' components. Each primitive is themed by register through tokens, not forked.
- Set: Button, IconButton, Link, Field, TextArea, Select, Combobox, Checkbox, Radio, Switch, Slider, Tabs, SegmentedControl, Menu, ContextMenu, Popover, Tooltip, Dialog, Sheet, Drawer, Toast, Banner, Badge, Tag, Avatar, Table, List, Row, Tree, Card (object cards only), EmptyState, Skeleton, Progress, Spinner (only inside controls), Kbd, StatusIcon, SelectionBar, CommandPalette.
- States every primitive documents and tests: default, hover, focus-visible, pressed, selected, disabled, loading, invalid, read-only, and destructive where it applies.
- Variants need a reason. A new variant is added only for a semantic difference (primary or secondary, destructive, compact inside a menu), never for a single screen.
- Raw elements go. Raw
<button>,<input>,<select>,<textarea>, hand-rolledrole="dialog"androle="tablist"in app code are replaced by primitives; the counts in the audit are the baseline. - React Native gets the same set by name in a sibling package, reading the same theme object.
One command registry#
libs/oshun/shell-core/src/command-surface.ts already models commands. It becomes the registry every surface uses: each command has an id, label, optional shortcut, permission check, availability rule and handler. The palettes in member web, admin, Eve Workspace and the workbenches become one CommandPalette primitive over that registry. Shortcuts shown in menus and tooltips are read from it. Cmd/Ctrl+K opens the palette everywhere; ? opens the shortcut list.
Eve and other agents#
The guide gives agents one bullet. Oshun is built around them, so they get rules:
- Eve acts through the command registry. An agent action is the same command a person would run, with the same permission check, feedback and undo.
- Three visible states, always: idle, working (with what it is doing in words, and a stop control), and waiting on the person. Streaming text never moves what is already on screen.
- Proposals before changes. Anything Eve would change is shown as a reviewable difference with accept, edit and reject, unless the person has turned on a named autonomy level for that kind of action.
- Provenance on every generated thing: which model or agent, when, and from what sources, one interaction away.
- No fabricated success. An agent surface never shows a result that was not computed; a failure is shown as a failure with its reason. This is the repository's quality bar applied to UI.
- Voice and hands-free states (listening, thinking, speaking, muted) use one shared indicator and never rely on colour alone.
- Agent presence is quiet. No animated avatars or pulsing in work surfaces; the working state is a small, steady indicator.
Words#
- Labels are verbs or nouns, sentence case, no full stop: "Create task", not "Click here to create a new task".
- One name per thing across every surface; the glossary in
libs/oshun/navigationis the source. - Errors say what happened and what to do next, in that order, without blame or apology.
- Empty states say what belongs here and offer the one action that fills it.
- No marketing language inside the product. No exclamation marks.
- Times are relative when recent and absolute on hover, through the shared
RelativeTime. - Lilith's voice (plain, source-aware, non-shaming) is defined in
libs/oshun/design-languageand stays; the builder side is terser.
9. How conformance is checked#
Every check runs without a person. A surface is done when it passes all of them, not when it looks right in one screenshot.
| Gate | What it enforces | How |
|---|---|---|
| Token lint | No colour literal, no font size or weight outside the type styles, no spacing, radius, duration or z-index off the scales, in app or library source | A repo-wide lint over TS, TSX and CSS. It starts as a ratchet: each app's current count is its ceiling, the count may only fall, and new files start at zero. |
| Theme contrast matrix | Every text role on every ground it can land on meets 4.5:1 (7:1 in contrast themes); controls, focus rings and status marks meet 3:1; statuses sit at least 30 degrees from the accent | Unit test in the token engine, generalising Lilith's palette regression test, for every theme |
| Primitive state matrix | Each primitive in each state, in each theme, at each text size, with long content and right-to-left where relevant | Browser snapshots and axe, generalising the workbench primitive proofs |
| Archetype audits | One accent-filled action per view; no nested boundaries; cards only for objects; slots in their fixed positions; hierarchy survives grayscale | The workbench signals, chrome, card-use and composition audits, run against one fixture route per archetype in both registers |
| Edge-state matrix | Empty, loading, partial, error, offline, permission-denied, very long names, hundreds of rows, narrow width | Playwright fixtures per archetype; visual regression snapshots committed |
| Behaviour | Acknowledgement within 100 ms on primary journeys; zero layout shift on load; state survives a round trip; input works during transitions; reduced motion zeroes every duration | Playwright traces and assertions |
| Keyboard and assistive | Core journeys pass keyboard-only; focus order and return are asserted; forced colours renders usable; WCAG 2.2 AA axe rules with no disabled rule left unmeasured | workbench-kit keyboard and focus scans, extended; axe in the browser suites |
| Command registry | Every command registered once; no shortcut collision; every button with a command reads its label from the registry | Scan, extending the kit's shortcut-collision scan |
| Faces | Every face a theme names is actually loaded by the app that uses the theme | Browser check of computed font per register |
Browser checks run on the Linux hosts in Chromium; on the Mac the Playwright inspect harness is used, not the Chrome extension.
A design defect is filed and fixed like a functional one. A surface that passes its functional tests and fails these gates is not done.
10. Scope and sequence#
In scope: the eight live surfaces and the five release-scope surfaces named in section 2.
Out of scope until revived (D6): the roughly fifty dormant apps and the pre-rebrand apps/lilith/*, apps/tara/* and similar built-but-undeployed apps listed in the audit.
Sequence. Each phase ends with its gates green on the surfaces it touched.
| Phase | Work | Result |
|---|---|---|
| 0. Engine and gates | Token engine with builder and Lilith themes; alias generation; token lint with ratchet baselines; contrast matrix | Every live app reads generated values; no visual change intended; debt is counted and can only fall |
| 1. Primitives | The primitive set in libs/oshun/ui with state matrices in both registers; command registry and palette |
One Button, one Dialog, one palette exist and are proven |
| 2. Builder shells | Eve Workspace, admin (with its new dark theme) and tenant admin moved to builder theme, primitives and archetypes | The three tools read as one product |
| 3. Studio workbenches | The 498 /studio pages: builder theme through the --wk-* contract, faces fixed, the 139 pages still on the member shell moved to the workbench shell, archetypes assigned |
Studio matches the other tools |
| 4. Lilith web | Member pages outside /studio, corporate site and mini-app: primitives, archetypes, literals removed, chrome quietened |
Lilith is one system end to end |
| 5. Mobile and watch | Member, admin and Eve mobile apps and the watch apps on the generated theme and the native primitive set | Web and native share values and names |
| 6. Metis and Isis web | Metis web to the Lilith register, Metis admin and Isis web to the builder register | No live surface is outside the system |
| 7. Removal | Alias families and superseded component systems deleted as their counts reach zero; globals.css reduced |
One system remains |
Phases 0 and 1 are prerequisites. After them, 2 to 6 can run in parallel across board-worker seats, one surface per task, because each is isolated by app or route tree.
The work is tracked as a board family created after approval, one task per surface per phase, each naming its archetype, its gates and its debt baseline from the audit.
11. What this document does not decide#
- The final look of any screen. Chrome contrast, exact layouts and Lilith's per-archetype tuning are judged in a browser during each phase, against the gates.
- Changes to information architecture. Rule 1 requires a concept review per surface; what each review removes is decided in that surface's task and, where it changes product scope, by Elikem.
- Whether the workbench faces really fall back today, and whether every value in Eve's scales survives regeneration. Both are checked in phase 0.
- Native platform conventions on iOS, Android, watchOS and Wear OS where they conflict with these rules; the platform convention wins and the exception is recorded.
- The older V1 design documents imported on 2026-09-20 (customer visual thesis, motion language, grid rules). They were not reviewed here. On approval of this document they should be marked superseded or reconciled.
- Effort and dates. Not estimated here.
12. Sources#
- The Linear Design Philosophy: 28 principles, independent field guide, October 2026, supplied by Elikem. Its references to Linear's publications were not verified.
- UI surface and design-token inventory (2026-10-10), Eve document
5f8247c4-64de-4716-b52e-a44fcea64c27. - ADR-S4: UI Composition and Theming, Eve document
898431cb-48d0-8d71-84f2-82c3b551ff37, revision 7. apps/oshun/web/src/design-system/lilith-web/tokens.json;apps/oshun/web/src/components/workbench/workbench-tokens.css;apps/oshun/eve-content/src/workspace/tokens.css;libs/oshun/design-tokens;libs/oshun/design-language.- WCAG 2.2.