@nadicodeai/design-system 12.1.57 → 12.1.59

package/DESIGN.md

@@ -256,7 +256,7 @@ The neutral spine carries grounds, chrome, text and every control: `{colors.ink}
 
 The identity palette is the brand's colour: cobalto `{colors.identity-cobalto}`, verde `{colors.identity-verde}`, arancio `{colors.identity-arancio}`, giallo `{colors.identity-giallo}` and rosso `{colors.identity-rosso}`, with `{colors.identity-ink}` and `{colors.identity-white}` as the poles type sits on. Azzurro `{colors.identity-azzurro}` has one job: the first stripe of Nadia's ribbon.
 
-The hues appear at full strength and flat, with no tints, steps, gradients or hover variants, in these places. The one exception is the website's shader objects, each the material of one object and never a section's ground: Nadia's ribbon behind a page's hero, a twisting band of fine lines in her four stripes that crowd into solid colour where it turns edge-on; the threads she holds, a fan of lines in her stripes from her orb to her colleagues, on black; Alveare's hive, cells that light in its hues as the work passes; and the company card's holographic foil ("Company card"). Stripes and cells stay pure bands of their hues, never a colour between two of them. Ruled by the founder on 27 September 2026: "shaders are not backgrounds all over the place".
+The hues appear at full strength and flat, with no tints, steps, gradients or hover variants, in these places. The one exception is the website's shader objects, each the material of one object and never a section's ground: Nadia's ribbon on the About page's mission, a twisting band of fine lines in her four stripes that crowd into solid colour where it turns edge-on; the threads she holds, a fan of lines in her stripes from her orb to her colleagues, on black; Alveare's hive, cells that light in its hues as the work passes; and the company card's holographic foil ("Company card"). Stripes and cells stay pure bands of their hues, never a colour between two of them. Ruled by the founder on 27 September 2026: "shaders are not backgrounds all over the place".
 
 - **Section grounds on the website.** A section's ground is white, soft or black, and two neighbouring sections never share one; colour lives in the pictures, the objects, the Agents and the shader objects, never as a section's ground.
 - **Glass.** The colour a glass surface shows through ("Elevation & Depth").
@@ -404,7 +404,7 @@ Product UI sits on one continuous workspace ground, `{colors.material-workspace}
 
 **In light, shadow carries height.** Every surface is white. Each recipe is a 1 px black edge at 8%, a tight contact shadow where the object meets the surface below, and an ambient shadow pushed down with negative spread so it stays under the object. The ambient shadow grows with the height, from 8 px of blur at resting to 128 px at modal.
 
-**In dark, tone carries height.** Shadows cannot show on true black, so each height's surface is one fixed step lighter than the page: resting `{colors.dark-material-resting}` #0c0c0c, raised `{colors.dark-material-raised}` #121212, floating `{colors.dark-material-floating}` #181818, modal `{colors.dark-material-modal}` #1c1c1c. The steps are equal-channel greys with nothing between or above them, so dark surfaces still read as black. `{colors.dark-ink}` keeps at least 14.5:1 and `{colors.dark-muted}` at least 5.2:1 on the lightest step. Each dark recipe adds an inset white hairline and a 1 px top highlight that strengthen with the height, and an outer black edge that separates a surface from a lighter one below it. A component names only its height and its role (`bg-card`, `bg-popover`); `@nadicodeai/ui/globals.css` sets those roles to the height's tone on the element.
+**In dark, tone carries height.** Shadows cannot show on true black, so each height's surface is one fixed step lighter than the page: resting `{colors.dark-material-resting}`, raised `{colors.dark-material-raised}`, floating `{colors.dark-material-floating}`, modal `{colors.dark-material-modal}`. The steps are equal-channel greys with nothing between or above them, so dark surfaces still read as black. `{colors.dark-ink}` keeps at least 14.5:1 and `{colors.dark-muted}` at least 5.2:1 on the lightest step. Each dark recipe adds an inset white hairline and a 1 px top highlight that strengthen with the height, and an outer black edge that separates a surface from a lighter one below it. A component names only its height and its role (`bg-card`, `bg-popover`); `@nadicodeai/ui/globals.css` sets those roles to the height's tone on the element.
 
 | Surface | Fill | Height | Use |
 | --- | --- | --- | --- |
@@ -579,7 +579,7 @@ The company is **nadicode**, lowercase. Its logo has three forms:
 
 On `{colors.canvas}` and the soft canvases the letters are ink and the dot is `{colors.logo-dot}`; on black and other dark grounds the letters are `{colors.identity-white}` and the dot `{colors.dark-logo-dot}`, a brighter cobalt. `logo-dot` is the only colour a consumer paints the dot with. A one-ink form exists only where a single ink prints. On a photograph, the logo sits in a quiet area or over a scrim that keeps it legible, or on an approved solid field.
 
-Every form is drawn from one geometry source, `@nadicodeai/design-system/assets/logo-geometry`: on a 100-unit x-height, an 18-unit stroke with flat ends, bowls and the n's arch of radius 41, and a dot of radius 14 centred 79 units above the baseline over the i's stem. Nothing re-authors, traces, typesets or rearranges it. React draws `BrandWordmark` or `BrandMark`; there is no lockup, because the mark is already inside the wordmark.
+Every form is drawn from one geometry source, `@nadicodeai/design-system/assets/logo-geometry`, which holds every dimension. Nothing re-authors, traces, typesets or rearranges it. React draws `BrandWordmark` or `BrandMark`; there is no lockup, because the mark is already inside the wordmark.
 
 The clear space is one stroke width of the rendered logo on every side. The minimum sizes are 72 px wide for the wordmark, 12 px for the mark and 16 px for the favicon on screen, and 25 mm and 5 mm in print. A meaningful standalone logo is named `nadicode`; inside a link or control that already has the name, the logo is hidden from assistive technology. Never redraw, retype, stretch, crop, rotate, recolour, outline, shadow, animate or add a gradient to a logo; never add a shape to the mark or move the dot. Other companies' marks, Agent orbs and generated imagery are not nadicode logos.
 

package/GLOSSARY.md

@@ -57,7 +57,7 @@ The five colours that mark where a piece of agentic work stands: ready, running,
 A visual family outside the conversation renderer for work output and workflow state, such as memory, run progress, identity, and handoffs.
 
 **Agent orb**:
-The identity of one Agent across products: one of seven forms in one chosen colour, or Nadia's striped ribbon.
+The identity of one Agent across products: one of seven forms in one chosen colour, or the fixed figure of Nadia or Sofia.
 _Avoid_: Agent glyph, Agent avatar, Agent visual
 
 **Product view**:

package/README.md

@@ -103,24 +103,19 @@ Consumer overrides belong in an explicit later layer:
 `@google/design.md` CLI exports the YAML front matter, and
 `scripts/sd/design-tokens-fence.ts` reads the one `json design-tokens` fence.
 `scripts/sd/compose-token-graph.ts` joins them into the single `nadicode` token
-graph, checks that every alias resolves and points the allowed way (`core`
+graph and checks that every alias resolves and points the allowed way (`core`
 reaches nothing outside itself; `semantic` names only `core`; a register reaches
-`core` and itself), and writes the two DTCG files after validating them against
-the vendored schema.
+`core` and itself). `scripts/build.ts` validates the graph against the vendored
+schema and writes the two DTCG files.
 
-Style Dictionary (`scripts/sd/`) emits the CSS from that graph:
-
-| File | Holds |
-| --- | --- |
-| `src/css/tokens.generated.css` | Every token as `--nc-*`, hex colours as `oklch()`, elevation as its full `box-shadow` per mode |
-| `src/css/modes.generated.css` | The `.dark` remap of every `X` / `dark-X` colour pair |
-| `src/css/theme.generated.css` | The shadcn role maps from the `semantic` group, the Tailwind v4 `@theme` bridge, and the raw `--color-nc-*` projection |
-| `src/css/theme-host.generated.css` | The same projection for a host that keeps its own shadcn roles |
+Style Dictionary emits the CSS from that graph into `src/css/*.generated.css`;
+the header of each `scripts/sd/format-*.ts` says what its output holds, and
+`scripts/build.ts` (`OUTPUT 3b`) says what `theme-host.generated.css` holds.
 
 The source graph under `src/css/` is bundled into three public stylesheets:
 `css` (everything), `css/tokens` (the token layer alone) and `css/host` (for a
-host with base styles of its own). The cascade is
-`@layer tokens, theme, reset, foundation, motion, primitives, components;`.
+host with base styles of its own). `src/css/index.css` declares the cascade's
+layer order.
 Generated files and `dist/` are outputs: edit `DESIGN.md` and rebuild, never the
 output. CI rebuilds and fails when a committed generated file differs from the
 fresh build, and `tests/guards/` holds the structural checks on every output.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nadicodeai/design-system",
-  "version": "12.1.57",
+  "version": "12.1.59",
   "type": "module",
   "publishConfig": {
     "access": "public"