@nadicodeai/design-system 12.1.29 → 12.1.31

package/DESIGN.md

@@ -421,7 +421,7 @@ Content stays solid: cards, KPIs, tables, chat, forms, and dialog, sheet and dra
 
 **Product views on the website** are the product itself, built from the real components with example data that is labelled as such; never a screenshot, a device mockup or an invented interface. A product window takes the raised height on its ground; a card that overlaps it floats; its chrome may be glass over a colour or black ground; in a black section it renders in dark mode.
 
-Absence follows its container. A page or region with nothing in it is an opaque region with a dashed boundary; an empty state inside a card is unframed, because the card already owns the edge. A persistent notice sits in the section it concerns, action feedback is a toast, and field validation stays with its field.
+Absence follows its container. A page or region with nothing in it is an opaque region with a dashed boundary; an empty state inside a card is unframed, because the card already owns the edge. Every absence leads with its icon tile, in every product, and a read that failed where content would be takes the same shape with the warning mark and its retry. A persistent notice sits in the section it concerns, action feedback is a toast, and field validation stays with its field.
 
 Modal overlays use the scrim with no blur. Focus is not elevation: it is always the focus outline.
 
@@ -504,14 +504,14 @@ One wait gets one indicator. A request waiting for a person is not a wait: queue
 
 ### Failure surfaces
 
-A page that cannot show what was asked for is a picture with the words standing in it. The picture is art direction's, built around the gap, and it fills the plane behind the page in a product and stands beside the words on the website; in the gap sit a mono eyebrow naming the situation, the page's one heading, one plain sentence, and the recovery action, which leads. The words keep their contrast over the picture at every width, and the picture yields to them when the viewport is too small to hold both.
+A page that cannot show what was asked for opens with a picture, the way a Portal email does: one whole cut-out in art direction's editorial register, centred above the words, whose idea says what happened. The picture carries a label, the way a museum labels a work: its title says what the figure is doing, which is the page's one joke, and a mono line gives its materials and year. From `lg` the label stands beside the picture's base while the picture keeps the centre line; below that it stands centred under the picture. Below the picture, on the same centre line, stand a mono eyebrow naming the situation, the page's one heading, one plain sentence, and the recovery action, which leads. The cut-out's transparent ground takes the page's own, so one file serves light and dark, and it stays whole at every width: it scales down with the column and is never cropped by the viewport. No orb turns on a failure page.
 
 Two registers share that composition:
 
-- **An absence** is an address or a record that is not there. In its gap, beside the words, stands a short note signed by Nadia. The note is authored copy, not a report of anything an Agent did; it is never the instruction, which is the plain sentence and the action. Where the picture leaves a place for it, Nadia's orb turns there in ambient motion and claims no activity ("Agent orbs"); where the picture does not, the note stands alone. Nothing went wrong, so nothing takes a feedback role and no glyph stands in for the failure. Without a picture the note takes the dashed absence boundary at page scale ("Absence follows its container").
-- **A fault** is a request the product stopped. Its picture is calm and never a joke about lost work, and it carries no note and no Agent, because a stopped request is not a moment for one to perform in. Beside the words stands the evidence: the diagnostic code, the label that names it and one line saying what to do with it. The error pair marks the eyebrow.
+- **An absence** is an address or a record that is not there. Its picture and label are the joke of the missing address. Nothing went wrong, so nothing takes a feedback role, no glyph stands in for the failure and no code is printed.
+- **A fault** is a request the product stopped. Its picture and label are calm and never a joke about lost work. Below the actions stands the evidence: the diagnostic code, the word that names it and one line saying what to do with it. The error pair marks the eyebrow.
 
-A failure inside a product's own chrome takes no picture: the picture is the plane the chrome stands on, never something inside it, so an in-chrome failure keeps the words, the note where there is one, and the dashed absence boundary. Identity hue reaches a product failure surface only through the picture and the orb. The words never apologize and never name the mechanism ("Product messages" in `product-design`). On the website a failure surface is an ordinary full-bleed section and takes a section ground like any other.
+A failure inside a product's own chrome takes no picture, because the chrome already frames the page: it keeps the words alone. Identity hue reaches a product failure surface only through the picture. The words never apologize and never name the mechanism ("Product messages" in `product-design`). On the website a failure surface is an ordinary full-bleed section and takes a section ground like any other.
 
 ### Agent orbs
 
@@ -593,7 +593,7 @@ The clear space is one stroke width of the rendered logo on every side. The mini
 - Do round every surface and control at `{rounded.md}`. Don't give a higher surface a bigger corner.
 - Do give every line one owner, and draw focus only with the focus outline.
 - Do say a status with a Badge tone, a mark and a word. Don't use colour alone or a bare dot.
-- Do build a failure page around its picture's gap, with the recovery action leading in it: Nadia's note for a thing that is not there, the diagnostic code for a request that stopped. Don't apologise, and don't put a note or an Agent on a fault.
+- Do open a failure page with one whole cut-out whose idea says what happened, labelled like a work in a museum, above the words on one centre line, with the recovery action leading and the diagnostic code only for a request that stopped. Don't apologise, don't crop the picture, don't joke about lost work, and don't put an orb on a failure page.
 - Do use the dotted field only on a canvas where things are arranged. Don't put it behind lists, dashboards, settings or website sections.
 - Do add a rule here before a product needs it. Don't restate a rule in another document; link to it.
 

package/package.json

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