@nadicodeai/design-system 12.1.168 → 12.1.170

package/DESIGN.md

@@ -699,8 +699,12 @@ page renders it: the Portal's `PortalFunnelFrame` with `AccountEntryHeader`
 (sign-in, sign-up, an invitation, and the pages that hand a person to Nadia,
 which stand on the dark plane with her ambient orb at 96 px over the card),
 Nadia's `EntryScene` (her entry, update and installer screens, her orb at
-160 px, 96 px under 640 px wide or 600 px tall) and Alveare Server's
-`HiveScene`.
+160 px, 96 px under 640 px wide or 600 px tall), Alveare Server's
+`HiveScene`, and the website's invite page, where an invite link opens: the
+centred `InviteCard` (the app's mark, the words, the open action, the
+installers one row per computer, and the QR code that opens the same link on a
+phone). A picture beside an entry page's centred column is `EntryPicture`, in
+every product.
 
 Every pairing in Nadia, a phone linking to her or to one of her Agents
 (WhatsApp, Telegram, WhatsApp calls), is one step: a form drawer whose body
@@ -1062,7 +1066,7 @@ The owner's decisions where Geist and ours differ:
 
 ### Cards and sections
 
-A card or settings section is composed around a real task, collection or form; its header names the content and may explain scope or consequence, and it is never a card holding only an introduction. A card's or a section's title carries no icon, unless the card stands for one external system, whose mark it then carries. On a settings page the shape follows the data. Settings that one card's description covers share that card, whatever their controls, as Vercel's Root Directory card holds its switches, and `SettingsRows`' usage page holds their rows; a typed value, a name or an address, keeps a card of its own. Every choice on a settings card, a switch, a theme, a language or a pick from a short list among them, is a draft until the card's footer Save applies it, and the product's toast confirms it; a save that fails says so under the card and keeps the draft. A collection is a table whose Add opens a form and whose every row carries **⋯**, and a destructive action there confirms first. A status is a read-only card with the one action that fixes it. A row of five figures sits in one row from 1280 px, three over two below that, two by two with the fifth across on a tablet, and one column on a phone; it never leaves one figure alone beside a hole.
+A card or settings section is composed around a real task, collection or form; its header names the content and may explain scope or consequence, and it is never a card holding only an introduction. A card's or a section's title carries no icon, unless the card stands for one external system, whose mark it then carries. On a settings page the shape follows the data. Settings that one card's description covers share that card, whatever their controls, as Vercel's Root Directory card holds its switches, and `SettingsRows`' usage page holds their rows; a typed value, a name or an address, keeps a card of its own. Every choice on a settings card, a switch, a theme, a language or a pick from a short list among them, is a draft until the card's footer Save applies it, and the product's toast confirms it; a save that fails says so under the card and keeps the draft. A collection is a table whose Add opens a form and whose every row carries **⋯**, and a destructive action there confirms first. A row of five figures sits in one row from 1280 px, three over two below that, two by two with the fifth across on a tablet, and one column on a phone; it never leaves one figure alone beside a hole.
 
 `Card`, `CardRow`, `SettingsSection`, `SettingsFactsSection` and `KpiCard` hold their own shapes on their usage pages.
 

package/package.json

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