@elevasis/sdk 1.20.2 → 1.22.0

package/reference/scaffold/ui/feature-shell.mdx

@@ -1,75 +1,75 @@
----
-title: Feature Shell & Provider Runtime
-description: Current feature shell contract for flat Organization Model features, manifests, route matching, sidebars, and breadcrumbs.
----
+---
+title: System Shell & Provider Runtime
+description: Current system shell contract for Organization Model systems, manifests, route matching, sidebars, and breadcrumbs.
+---
 <!-- @generated by packages/sdk/scripts/copy-reference-docs.mjs -- DO NOT EDIT -->
 <!-- Regenerate: pnpm scaffold:sync -->
 
-
-## Overview
-
-The feature shell derives app navigation from `OrganizationModel.features`. Feature manifests provide implementation hooks such as icons and sidebars; they no longer own structural navigation.
-
-## Source Of Truth
-
-- `packages/core/src/organization-model/defaults.ts` -- default flat feature list
-- `packages/core/src/organization-model/helpers.ts` -- `childrenOf`, `ancestorsOf`, `parentOf`, `topLevel`, `findByPath`
-- `packages/ui/src/features/registry/types.ts` -- `FeatureModule`
-- `packages/ui/src/provider/ElevasisFeaturesProvider.tsx` -- runtime resolver
-- `packages/ui/src/components/navigation/useBreadcrumbs.ts` -- breadcrumb derivation
-
-## FeatureModule
-
-```ts
-export interface FeatureModule {
-  key: string
-  featureId: string
-  capabilityIds?: string[]
-  icon?: FeatureIconComponent
-  sidebar?: FeatureSidebarComponent
-  organizationGraph?: { featureId: string }
-}
-```
-
-`featureId` must match an Organization Model feature ID. Structural fields such as route lists, nav labels, and nested links belong on `OrganizationModel.features`.
-
-## Shell Model
-
-`useElevasisFeatures()` exposes `shellModel`:
-
-```ts
-{
-  features,
-  findByPath,
-  findById,
-  childrenOf,
-  ancestorsOf,
-  parentOf,
-  topLevel,
-  uiPositionFor,
-  requiresAdminFor,
-  devOnlyFor
-}
-```
-
-Sidebar rendering walks `topLevel()` and `childrenOf(id)`. Breadcrumbs resolve `findByPath(location.pathname)` and then map `ancestorsOf(id)`.
-
-## Access
-
-Feature access is keyed by Organization Model feature ID. `requiresAdmin` and `devOnly` inherit from ancestor feature nodes and are applied when deriving visible sidebar entries.
-
-Routes still need guards:
-
-```tsx
-<ProtectedRoute>
-  <FeatureGuard featureKey="sales.crm">
-    <Outlet />
-  </FeatureGuard>
-</ProtectedRoute>
-```
-
-Use `AdminGuard` for pages that require platform-admin privileges.
-
-## External Shells
-
-External templates pass `canonicalOrganizationModel` into `ElevasisFeaturesProvider` and derive sidebar links locally from `shellModel`. There is no separate nav config file to keep in sync.
+
+## Overview
+
+The system shell derives app navigation from `OrganizationModel.systems`. System manifests provide implementation hooks such as icons and sidebars; they do not own structural navigation.
+
+## Source Of Truth
+
+- `packages/core/src/organization-model/defaults.ts` -- default system list
+- `packages/core/src/organization-model/helpers.ts` -- `childrenOf`, `ancestorsOf`, `parentOf`, `topLevel`, `findByPath`
+- `packages/ui/src/features/registry/types.ts` -- `SystemModule`
+- `packages/ui/src/provider/ElevasisSystemsProvider.tsx` -- runtime resolver
+- `packages/ui/src/components/navigation/useBreadcrumbs.ts` -- breadcrumb derivation
+
+## SystemModule
+
+```ts
+export interface SystemModule {
+  key: string
+  systemId: string
+  capabilityIds?: string[]
+  icon?: SystemIconComponent
+  sidebar?: SystemSidebarComponent
+  organizationGraph?: { systemId: string }
+}
+```
+
+`systemId` must match an Organization Model system ID. Structural fields such as route lists, nav labels, and nested links belong on `OrganizationModel.systems`.
+
+## Shell Model
+
+`useElevasisSystems()` exposes `shellModel`:
+
+```ts
+{
+  systems,
+  findByPath,
+  findById,
+  childrenOf,
+  ancestorsOf,
+  parentOf,
+  topLevel,
+  uiPositionFor,
+  requiresAdminFor,
+  devOnlyFor
+}
+```
+
+Sidebar rendering walks `topLevel()` and `childrenOf(id)`. Breadcrumbs resolve `findByPath(location.pathname)` and then map `ancestorsOf(id)`.
+
+## Access
+
+System access is keyed by Organization Model system ID. `requiresAdmin` and `devOnly` inherit from ancestor system nodes and are applied when deriving visible sidebar entries.
+
+Routes still need guards:
+
+```tsx
+<ProtectedRoute>
+  <SystemGuard systemKey="sales.crm">
+    <Outlet />
+  </SystemGuard>
+</ProtectedRoute>
+```
+
+Use `AdminGuard` for pages that require platform-admin privileges.
+
+## External Shells
+
+Host apps pass `SYSTEM_MANIFESTS` or their own `SystemModule[]` into `ElevasisSystemsProvider` and derive sidebar links locally from `shellModel`. There is no separate nav config file to keep in sync.

package/reference/scaffold/ui/recipes.md

@@ -1,216 +1,224 @@
----
-title: UI Recipes
-description: Current recipes for adding pages, feature-gated routes, feature components, theme tokens, Organization Model sidebar entries, and executable resources.
----
+---
+title: UI Recipes
+description: Current recipes for adding pages, system-gated routes, system components, theme tokens, Organization Model sidebar entries, and executable resources.
+---
 <!-- @generated by packages/sdk/scripts/copy-reference-docs.mjs -- DO NOT EDIT -->
 <!-- Regenerate: pnpm scaffold:sync -->
 
-
-# UI Recipes
-
-## 1. Add a Top-Level Page
-
-Create `ui/src/routes/my-feature.index.tsx`:
-
-```tsx
-import { createFileRoute } from '@tanstack/react-router'
-import { ProtectedRoute } from '@/features/auth'
-import { AppShellContentContainer, AppTopbarAdjusterWrapper, PageContainer } from '@elevasis/ui/layout'
-import { MyFeaturePage } from '@/features/my-feature/components/MyFeaturePage'
-
-export const Route = createFileRoute('/my-feature/')({
-  component: MyFeatureRouteComponent
-})
-
-function MyFeatureRouteComponent() {
-  return (
-    <ProtectedRoute>
-      <AppTopbarAdjusterWrapper>
-        <AppShellContentContainer>
-          <PageContainer>
-            <MyFeaturePage />
-          </PageContainer>
-        </AppShellContentContainer>
-      </AppTopbarAdjusterWrapper>
-    </ProtectedRoute>
-  )
-}
-```
-
-Add the sidebar entry as a feature node in `core/config/organization-model.ts`:
-
-```ts
-features: [
-  {
-    id: 'my-feature',
-    label: 'My Feature',
-    enabled: true,
-    path: '/my-feature',
-    icon: 'star',
-    uiPosition: 'sidebar-primary'
-  }
-]
-```
-
-TanStack Router derives the path from the filename. The sidebar is derived from `OrganizationModel.features`.
-
-## 2. Add a Feature-Gated Page
-
-Wrap the route with `FeatureGuard` and use the same feature ID as the org model node.
-
-```tsx
-import { FeatureGuard } from '@/features/auth/guards/FeatureGuard'
-
-function MyFeatureRouteComponent() {
-  return (
-    <ProtectedRoute>
-      <FeatureGuard featureKey="my-feature">
-        <AppTopbarAdjusterWrapper>
-          <AppShellContentContainer>
-            <PageContainer>
-              <MyFeaturePage />
-            </PageContainer>
-          </AppShellContentContainer>
-        </AppTopbarAdjusterWrapper>
-      </FeatureGuard>
-    </ProtectedRoute>
-  )
-}
-```
-
-Set `enabled: false` in the feature node to hide it by default. Use `requiresAdmin: true` on the feature node plus `AdminGuard` in the route for admin-only pages.
-
-## 3. Add a Nested Page
-
-Create a layout file for the section and child route files under the same directory.
-
-```tsx
-import { createFileRoute, Outlet } from '@tanstack/react-router'
-import { ProtectedRoute } from '@/features/auth'
-
-export const Route = createFileRoute('/reporting')({
-  component: ReportingLayoutComponent
-})
-
-function ReportingLayoutComponent() {
-  return (
-    <ProtectedRoute>
-      <Outlet />
-    </ProtectedRoute>
-  )
-}
-```
-
-Add dotted feature nodes for the sidebar hierarchy:
-
-```ts
-{ id: 'reporting', label: 'Reporting', enabled: true, uiPosition: 'sidebar-primary' },
-{ id: 'reporting.overview', label: 'Overview', enabled: true, path: '/reporting/overview' },
-{ id: 'reporting.reports', label: 'Reports', enabled: true, path: '/reporting/reports' }
-```
-
-Containers omit `path`; leaves provide `path`.
-
-## 4. Add a Feature-Scoped Component
-
-Use `ui/src/features/<name>/` when logic is shared across routes or owns local state.
-
-```text
-ui/src/features/reporting/
-  components/
-    ReportingOverviewPage.tsx
-    ReportCard.tsx
-  hooks/
-    useReports.ts
-  utils/
-    formatReportDate.ts
-  types.ts
-```
-
-Use `@/*` imports for app-local cross-feature imports and keep route layout concerns in route files.
-
-## 5. Change Theme Tokens
-
-Edit `ui/src/config/theme.ts`.
-
-```ts
-default: {
-  label: 'Default',
-  description: 'Project brand theme',
-  colors: ['#2563eb', '#080808', '#f2f2f5'],
-  dark: {
-    primary: '#2563eb',
-    primaryContrast: '#ffffff',
-    background: '#050507',
-    surface: '#0f0f14',
-    surfaceHover: '#1a1a22',
-    text: '#ffffff',
-    textDimmed: '#b0b0c0',
-    textSubtle: '#888898',
-    border: 'rgba(255, 255, 255, 0.07)'
-  }
-}
-```
-
-All tokens flow into CSS variables. Change `defaultPreset` to alter the initial preset for new users.
-
-## 6. Execute a Resource from a Surface
-
-Declare the resource descriptor in the Organization Model, then derive runtime metadata from that descriptor:
-
-```ts
-// core/config/organization-model.ts
-import { defineResources } from '@elevasis/core/organization-model'
-
-export const resourceDescriptors = defineResources({
-  writeNote: {
-    id: 'write-note',
-    kind: 'workflow',
-    systemId: 'sys.sales',
-    ownerRoleId: 'role-sales-ops',
-    status: 'active'
-  }
-})
-
-// operations/src/write-note/index.ts
-config: {
-  resource: resourceDescriptors.writeNote,
-  resourceId: resourceDescriptors.writeNote.id,
-  name: 'Write Note',
-  type: resourceDescriptors.writeNote.kind,
-  version: '1.0.0',
-  status: 'prod',
-  links: [{ nodeId: 'feature:sales.crm', kind: 'operates-on' }],
-  category: 'production'
-}
-```
-
-Render the deployed workflow with `RunResourceButton`:
-
-```tsx
-import { RunResourceButton } from '@elevasis/ui/components'
-import { writeNoteInputSchema } from '@core/types'
-
-export function DealPanel({ dealId }: { dealId: string }) {
-  return (
-    <RunResourceButton
-      resourceId="write-note"
-      resourceType="workflow"
-      label="Write Note"
-      getInput={() => ({
-        schema: writeNoteInputSchema,
-        defaults: { dealId }
-      })}
-    />
-  )
-}
-```
-
-`resourceDescriptors.writeNote.id` is the single authored ID. `RunResourceButton` still receives the deployed runtime ID. `links[].nodeId` binds the resource into the Organization Model graph. `category` drives operational filtering for production, diagnostic, internal, and testing resources.
-
-## Cross-References
-
-- `./feature-flags-and-gating.md` -- feature and admin access model
-- `./feature-shell.mdx` -- provider and sidebar derivation
-- `./customization.md` -- feature sidebar customization
-- `ui/src/config/README.md` -- theme, background, and loader config
+
+# UI Recipes
+
+## 1. Add a Top-Level Page
+
+Create `ui/src/routes/my-system.index.tsx`:
+
+```tsx
+import { createFileRoute } from '@tanstack/react-router'
+import { ProtectedRoute } from '@/features/auth'
+import { AppShellContentContainer, AppTopbarAdjusterWrapper, PageContainer } from '@elevasis/ui/layout'
+import { MySystemPage } from '@/features/my-system/components/MySystemPage'
+
+export const Route = createFileRoute('/my-system/')({
+  component: MySystemRouteComponent
+})
+
+function MySystemRouteComponent() {
+  return (
+    <ProtectedRoute>
+      <AppTopbarAdjusterWrapper>
+        <AppShellContentContainer>
+          <PageContainer>
+            <MySystemPage />
+          </PageContainer>
+        </AppShellContentContainer>
+      </AppTopbarAdjusterWrapper>
+    </ProtectedRoute>
+  )
+}
+```
+
+Add the sidebar entry as a system node in `core/config/organization-model.ts`:
+
+```ts
+systems: {
+  systems: [
+  {
+    id: 'my-system',
+    label: 'My System',
+    enabled: true,
+    path: '/my-system',
+    icon: 'star',
+    uiPosition: 'sidebar-primary'
+  }
+  ]
+}
+```
+
+TanStack Router derives the path from the filename. The sidebar is derived from `OrganizationModel.systems`.
+
+## 2. Add a System-Gated Page
+
+Wrap the route with `SystemGuard` and use the same system ID as the org model node.
+
+```tsx
+import { SystemGuard } from '@elevasis/ui/features/auth'
+
+function MySystemRouteComponent() {
+  return (
+    <ProtectedRoute>
+      <SystemGuard systemKey="my-system">
+        <AppTopbarAdjusterWrapper>
+          <AppShellContentContainer>
+            <PageContainer>
+              <MySystemPage />
+            </PageContainer>
+          </AppShellContentContainer>
+        </AppTopbarAdjusterWrapper>
+      </SystemGuard>
+    </ProtectedRoute>
+  )
+}
+```
+
+Set `enabled: false` in the system node to hide it by default. Use `requiresAdmin: true` on the system node plus `AdminGuard` in the route for admin-only pages.
+
+## 3. Add a Nested Page
+
+Create a layout file for the section and child route files under the same directory.
+
+```tsx
+import { createFileRoute, Outlet } from '@tanstack/react-router'
+import { ProtectedRoute } from '@/features/auth'
+
+export const Route = createFileRoute('/reporting')({
+  component: ReportingLayoutComponent
+})
+
+function ReportingLayoutComponent() {
+  return (
+    <ProtectedRoute>
+      <Outlet />
+    </ProtectedRoute>
+  )
+}
+```
+
+Add dotted system nodes for the sidebar hierarchy:
+
+```ts
+{ id: 'reporting', label: 'Reporting', enabled: true, uiPosition: 'sidebar-primary' },
+{ id: 'reporting.overview', label: 'Overview', enabled: true, path: '/reporting/overview' },
+{ id: 'reporting.reports', label: 'Reports', enabled: true, path: '/reporting/reports' }
+```
+
+Containers omit `path`; leaves provide `path`.
+
+## 4. Add a System-Scoped Component
+
+Use `ui/src/features/<name>/` when logic is shared across routes or owns local state.
+
+```text
+ui/src/features/reporting/
+  components/
+    ReportingOverviewPage.tsx
+    ReportCard.tsx
+  hooks/
+    useReports.ts
+  utils/
+    formatReportDate.ts
+  types.ts
+```
+
+Use `@/*` imports for app-local cross-system imports and keep route layout concerns in route files.
+
+## 5. Change Theme Tokens
+
+Edit `ui/src/config/theme.ts`.
+
+```ts
+default: {
+  label: 'Default',
+  description: 'Project brand theme',
+  colors: ['#2563eb', '#080808', '#f2f2f5'],
+  dark: {
+    primary: '#2563eb',
+    primaryContrast: '#ffffff',
+    background: '#050507',
+    surface: '#0f0f14',
+    surfaceHover: '#1a1a22',
+    text: '#ffffff',
+    textDimmed: '#b0b0c0',
+    textSubtle: '#888898',
+    border: 'rgba(255, 255, 255, 0.07)'
+  }
+}
+```
+
+All tokens flow into CSS variables. Change `defaultPreset` to alter the initial preset for new users.
+
+## 6. Execute a Resource from a Surface
+
+Declare the resource descriptor in the Organization Model, then derive runtime metadata from that descriptor:
+
+```ts
+// core/config/organization-model.ts
+import { defineResources } from '@elevasis/core/organization-model'
+
+export const resourceDescriptors = defineResources({
+  writeNote: {
+    id: 'write-note',
+    kind: 'workflow',
+    systemPath: 'sys.sales',
+    ownerRoleId: 'role-sales-ops',
+    status: 'active',
+    codeRefs: [
+      {
+        path: 'operations/src/write-note/index.ts',
+        role: 'entrypoint',
+        symbol: 'writeNoteWorkflow'
+      }
+    ]
+  }
+})
+
+// operations/src/write-note/index.ts
+config: {
+  resource: resourceDescriptors.writeNote,
+  resourceId: resourceDescriptors.writeNote.id,
+  name: 'Write Note',
+  type: resourceDescriptors.writeNote.kind,
+  version: '1.0.0',
+  status: 'prod',
+  category: 'production'
+}
+```
+
+Render the deployed workflow with `RunResourceButton`:
+
+```tsx
+import { RunResourceButton } from '@elevasis/ui/components'
+import { writeNoteInputSchema } from '@core/types'
+
+export function DealPanel({ dealId }: { dealId: string }) {
+  return (
+    <RunResourceButton
+      resourceId="write-note"
+      resourceType="workflow"
+      label="Write Note"
+      getInput={() => ({
+        schema: writeNoteInputSchema,
+        defaults: { dealId }
+      })}
+    />
+  )
+}
+```
+
+`resourceDescriptors.writeNote.id` is the single authored ID. `RunResourceButton` still receives the deployed runtime ID. `codeRefs` point agents and operators at implementation files, while `links[].nodeId` binds the resource into the Organization Model graph. `category` drives operational filtering for production, diagnostic, internal, and testing resources.
+
+## Cross-References
+
+- `./feature-flags-and-gating.md` -- system and admin access model
+- `./feature-shell.mdx` -- provider and sidebar derivation
+- `./customization.md` -- system sidebar customization
+- `ui/src/config/README.md` -- theme, background, and loader config