@nadicodeai/design-system 12.1.120 → 12.1.122

package/DESIGN.md

@@ -751,14 +751,14 @@ The Portal, Nadia and Alveare are product shells: persistent navigation on the l
 | Kind | Its one place | Portal | Nadia | Alveare |
 | --- | --- | --- | --- | --- |
 | Where I can go | The sidebar | Groups by viewer, one selected row | Find, Scheduled tasks, the company's Wiki and Skills, then the Agents | Inbox, Channels, Direct messages |
-| An object's sections | The sidebar, swapped | Back link, the object, its sections | Two swaps only: ⋯ → Edit and Settings | The channel's own panels |
+| An object's sections | The product’s documented section navigation | Customer, Partner and Agent tabs below the top bar; Installation sections in the sidebar | Two swaps only: ⋯ → Edit and Settings | The channel's own panels |
 | The path | The top bar | Customer or Partner switcher on the left and the current section centred; other paths centred | The window header: the Agent's orb and name, then the chat switcher | The channel header names the channel |
 | Find, ⌘K | The top of the sidebar | An outlined field | At the top of the list | Buzz's search, in its sidebar |
 | The account | The sidebar's foot | With the bell | Under the update card | The package's `AccountMenu` |
 | Getting the app | Above the account | Downloads, an outlined row | The update card, only when there is one | The update card |
 | The page's actions | The page's title row | Secondary, primary, the three dots | The window header's trailing edge: the Agent's three dots, after the chat switcher | The channel header's trailing edge |
 
-- **The sidebar swaps, and is never joined by a second.** Inside an object, the same column shows a back link, what you are in (its identity mark at 24 px and its name) and its sections, and the top bar keeps navigation (`SidebarSections`). No rail, second column or tab row of an object's sections appears beside it. In the Portal an Agent is the exception, because she is a deployment: the sidebar stays on the places, and her sections stand as the `TabsNav` band under the top bar, as Vercel draws a deployment's tabs, at most six (Overview, Scheduled tasks, Usage, Capabilities, Messaging, Settings); a tab that holds several sections opens on the first and shows them as line tabs at the top of its content.
+- **The workspace stays in view while working on a company.** In the Portal, Customers and Partners keep the workspace sidebar and use the `TabsNav` band below the top bar. A directory or search result opens Overview; switching companies keeps the current section when available and otherwise opens Overview. Customer tabs are Overview, Agents, Subscriptions, Members, Activity and Settings, reduced to the viewer’s authority. Partner tabs are Overview, Customers, Finances, Members, Activity and Settings. Related views, such as Finances’ Commissions and Bulk pool, use line tabs inside their section. Agents also keep the workspace sidebar with their six local tabs. Installations retain `SidebarSections`; no object adds a second sidebar. A company Overview starts with one `ObjectPage` identity card, company details, subscription state and Agent counts, then its scoped charts and actionable issues. Subscription status summarizes member-account subscriptions; Partner company figures, assigned Customer figures, commissions and bulk-pool credit stay distinct.
 - **An area whose pages are siblings opens as a sub-menu, as Vercel's sidebar does.** Vercel marks such a row with a › at its end ("Logs", "Observability", "Firewall", "Settings"), and its press replaces the places with one row, a ‹ at its start and the area's name centred, above the area's pages as words alone, the open one filled like a selected row; a row that only opens a page has no ›. In the Portal these areas are Settings (nadicode), Company (whoever manages a company) and Library (everyone who sees it: Agent templates, Skills, Plugins), each with its › row, and Account, opened from the account menu; their pages are never tabs (`SidebarSections` without an identity, its row ending in `SidebarMenuChevron`). “Tabs imply the views share scope, URL parent, and data model” (https://vercel.com/geist/tabs): Library's pages hold different objects with different lists and different ways to add, so they are a sub-menu, as Vercel's AI Gateway is. A destination whose pages are views of one reading, Analytics, keeps its tabs, as Vercel's Analytics and OpenRouter's Activity do. The ‹ returns to where the person opened the area from.
 - **The top bar holds navigation, never the page's actions.** Customer and Partner collections and their object sections use `ScopeSwitcher`'s navigation variant on the left: the company's mark and name, a searchable list with the current company checked, and a close link back to the originating collection. The current section is centred, below the switcher on phones so the company name and status remain visible. Other pages keep the centred path, ending at the place or the object. An object's own status sits beside its name in the path and nowhere else on the page.
 - **Find goes to places.** It opens from the outlined field at the top of the sidebar and on ⌘K, and names every sidebar place, chat and settings page; it never runs a command. Its field names what it searches, never a bare "Search"; ⌘K or Ctrl+K opens it and no other field takes that binding; a shortcut on a row is a `CommandShortcut`; and a polite live region reads how many results remain as the person types.
@@ -777,7 +777,7 @@ A product page is one of five page compositions, each answering one question fir
 | --- | --- | --- | --- |
 | Overview | `OverviewPage` | What needs attention? | The period, the figures, the chart cards, then the exceptions that need a person. Never a stack of previews of every section. |
 | Collection | `CollectionPage` | Which record? | The title and the page's actions, the sibling collections as line tabs, one toolbar, then one line per record ("Tables and missing values"); one row is one hover and one open target. Actionable attention stands above the toolbar when present; business summaries belong to Dashboard and Analytics. A `rail` carries context intrinsic to the collection, such as the selected Library hub. The Portal's Agents are its exception, a `DataTable` of entity rows, as Vercel's Deployments list. |
-| Object | `ObjectPage` | What is this, what can I do? | The parent in the path and its sections in the sidebar, then the object card, then its sections, each a card only where it owns a decision. An Agent's first section, Profile, opens with her `AgentProfileCard`, the same in every product. |
+| Object | `ObjectPage` | What is this, what can I do? | The parent in the path and its product’s section navigation, then the object card, then its sections, each a card only where it owns a decision. An Agent's first section, Profile, opens with her `AgentProfileCard`, the same in every product. |
 | Settings | `SettingsPage` | What can I change? | Section cards, each saving its own fields; the danger zone closes the page. |
 | Library | `LibraryShelf` for Agent templates; `CollectionPage` for Skills and Plugins | What reusable thing can I use? | Agent templates as Vercel's Templates gallery; Skills and Plugins as an entity collection, with staff's hub as its rail. |
 
@@ -1135,7 +1135,7 @@ An Agent shown as an object, in the Portal's Library and Nadia's gallery alike,
 
 ### Company card
 
-The company's card is `CompanyCard`, whose usage page holds where it appears (sign-up, the account's Profile, the Partner invitation), its face, foil and motion.
+The company's card is `CompanyCard`, whose usage page holds where it appears (sign-up, the account's Profile, a Sign-up invitation, a colleague's invitation), its face, foil and motion.
 
 ### Identity marks
 

package/package.json

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