@elevasis/sdk 1.20.1 → 1.21.0

package/reference/packages/core/src/organization-model/README.md

@@ -1,20 +1,19 @@
 # Organization Model
 
-The organization model is the published semantic contract that maps a tenant's product shape to flat feature hierarchy, shell navigation, business semantics, and graph bindings.
+The organization model is the published semantic contract that maps a tenant's System hierarchy, shell navigation, business semantics, resource governance, and graph bindings.
 
-Use this module when resolving or validating an organization's contract before wiring UI shells, routing, feature gates, or domain-specific capability checks.
+Use this module when resolving or validating an organization's contract before wiring UI shells, routing, system gates, or domain-specific capability checks.
 
 ## Published Exports
 
 The public entry point exposes:
 
 - `OrganizationModelSchema`
-- `FeatureSchema`
 - `DEFAULT_ORGANIZATION_MODEL`
 - `defineOrganizationModel`
 - `resolveOrganizationModel`
 - `createFoundationOrganizationModel`
-- node ID and feature helper types
+- node ID and System helper types
 - `OrganizationModel` and supporting domain types
 
 Import it from the published subpath:
@@ -36,8 +35,8 @@ The model is versioned and currently validates against `version: 1`.
 Top-level fields:
 
 - `version`
+- `domainMetadata`
 - `branding`
-- `features`
 - `navigation`
 - `sales`
 - `prospecting`
@@ -49,40 +48,81 @@ Top-level fields:
 - `goals`
 - `systems`
 - `resources`
+- `capabilities`
+- `policies`
 - `statuses`
-- `operations`
 - `knowledge`
 
-Resource identity is authored in `resources.entries`. Runtime workflows, agents, and integrations import those descriptors, derive `resourceId` and kind from them, and attach executable behavior in operations code.
+The pure collection domains are id-keyed maps: `systems`, `roles`, `goals`, `customers`, `offerings`, `resources`, `capabilities`, `policies`, and `statuses`. The map key must match the entry `id`. Entries carry `order` for deterministic ordered views; use `listDomain(record)` when order matters.
 
-## Feature Set
+Resource identity is authored in `resources`. Runtime workflows, agents, integrations, and scripts import those descriptors, derive `resourceId` and kind from them, and attach executable behavior in operations code.
 
-Feature hierarchy is authored as a flat array. Dotted IDs define parent/child relationships:
+## System Set
+
+System hierarchy is authored as an id-keyed `systems` map. Dotted IDs and `parentSystemId` define parent/child relationships:
+
+```ts
+systems: {
+  dashboard: { id: 'dashboard', order: 10, label: 'Dashboard', lifecycle: 'active' },
+  sales: { id: 'sales', order: 20, label: 'Sales', lifecycle: 'active' },
+  clients: { id: 'clients', order: 30, label: 'Clients', lifecycle: 'active' },
+  projects: { id: 'projects', order: 40, label: 'Projects', lifecycle: 'active' }
+}
+```
+
+Systems describe semantic ownership, hierarchy, lifecycle, access, and governance. Sidebar presentation is authored separately under `navigation.sidebar`; UI-backed Systems may still provide `ui.path` for route matching during the migration, but they do not author composed surface lists. Lifecycle values such as `active`, `beta`, `deprecated`, and `archived` replace the old feature enabled/dev-only split.
+
+## Sidebar Navigation
+
+Shell navigation is authored as a recursive sidebar tree:
 
 ```ts
-features: [
-  { id: 'dashboard', label: 'Dashboard', enabled: true, path: '/', uiPosition: 'sidebar-primary' },
-  { id: 'sales', label: 'Sales', enabled: true, uiPosition: 'sidebar-primary' },
-  { id: 'sales.crm', label: 'CRM', enabled: true, path: '/crm' },
-  { id: 'operations.resources', label: 'Resources', enabled: true, path: '/operations/resources' }
-]
+navigation: {
+  sidebar: {
+    primary: {
+      dashboard: {
+        type: 'surface',
+        order: 10,
+        label: 'Dashboard',
+        path: '/',
+        surfaceType: 'dashboard',
+        targets: { systems: ['dashboard'] }
+      },
+      business: {
+        type: 'group',
+        order: 20,
+        label: 'Business',
+        children: {
+          clients: {
+            type: 'surface',
+            order: 20,
+            label: 'Clients',
+            path: '/clients',
+            surfaceType: 'list',
+            targets: { systems: ['clients'] }
+          }
+        }
+      }
+    },
+    bottom: {}
+  }
+}
 ```
 
-Containers omit `path`; leaves provide `path`. `uiPosition`, `requiresAdmin`, and `devOnly` inherit from ancestors.
-Development-only features remain in the contract with `enabled: true` and `devOnly: true`; shell consumers hide them and guard their paths outside development mode.
+Routeable sidebar leaves are projected into flat semantic surface DTOs by `projectOrganizationSurfaces(model)`. Do not author top-level `surfaces` or `navigationGroups` fields on `OrganizationModel`.
 
 ## Graph IDs
 
 Cross-collection links use kind-prefixed IDs:
 
-- `feature:sales.crm`
+- `system:sales.crm`
 - `integration:instantly`
 - `resource:lead-import`
-- `capability:operations.queue.review`
+- `action:operations.queue.review`
 
 ## Resource Descriptors
 
-The OM Resources domain is governance-only. Descriptors declare canonical `id`, required `systemId`, governance `status`, and optional role ownership. `DeploymentSpec` remains the runtime/deploy assembly around those descriptors, not a second resource identity catalog.
+The OM Resources domain is governance-only. Descriptors declare canonical `id`, required `systemPath`, governance `status`, and optional role ownership. `DeploymentSpec` remains the runtime/deploy assembly around those descriptors, not a second resource identity catalog.
 
 ## Resolution Semantics
 
@@ -90,20 +130,20 @@ The OM Resources domain is governance-only. Descriptors declare canonical `id`,
 - `resolveOrganizationModel()` deep-merges a partial override into the default model, then validates it.
 - `createFoundationOrganizationModel()` resolves the canonical model and returns UI-facing helper outputs.
 - Plain objects merge recursively.
+- Id-keyed domain maps merge additively by key.
 - Arrays replace the default value.
 - Missing fields fall back to `DEFAULT_ORGANIZATION_MODEL`.
 
 ## Referential Integrity
 
-- Feature IDs must be unique.
-- Child feature IDs require ancestor feature nodes.
-- Container features omit `path`.
-- Leaf features provide `path`.
+- System IDs must be unique.
+- Child System IDs require valid ancestors or `parentSystemId` links.
+- Systems with UI provide `ui.path`.
 - Systems, resources, roles, knowledge nodes, and goals must resolve their declared cross-references.
 
 ## Practical Guidance
 
 - Use `resolveOrganizationModel()` when you need a runtime-safe model.
 - Use `defineOrganizationModel()` when authoring static overrides.
-- Keep feature IDs stable because shell routing, gating, breadcrumbs, and docs depend on them.
-- Put resource identity and governance in `resources.entries`; attach executable behavior in operations.
+- Keep System IDs stable because shell routing, gating, breadcrumbs, and docs depend on them.
+- Put resource identity and governance in `resources`; attach executable behavior in operations.

package/reference/packages/ui/src/provider/README.md

@@ -1,16 +1,16 @@
 # Provider
 
-The provider surface composes the shared Elevasis service, feature, appearance, notification, and UI providers.
+The provider surface composes the shared Elevasis service, system, appearance, notification, and UI providers.
 
 ## Exports
 
 The following are exported from `published.ts`, which is the external consumer surface for `@elevasis/ui/provider`:
 
 - `ElevasisCoreProvider`
-- `ElevasisFeaturesProvider`
-- `useElevasisFeatures`
-- `useOptionalElevasisFeatures`
-- `FeatureShell`
+- `ElevasisSystemsProvider`
+- `useElevasisSystems`
+- `useOptionalElevasisSystems`
+- `SystemShell`
 - `AppearanceProvider`
 - `useAppearance`
 - `ElevasisServiceProvider`

package/reference/scaffold/core/organization-graph.mdx

@@ -1,6 +1,6 @@
 ---
 title: Organization Graph
-description: Organization OS graph layer documentation for the organization graph derived from flat Organization Model features and resource metadata links.
+description: Organization OS graph layer documentation for the organization graph derived from Organization Model Systems, resources, capabilities, and typed links.
 ---
 <!-- @generated by packages/sdk/scripts/copy-reference-docs.mjs -- DO NOT EDIT -->
 <!-- Regenerate: pnpm scaffold:sync -->
@@ -27,30 +27,31 @@ Graph contracts live in `@repo/core`; rendering lives in `@repo/ui`.
 Node kinds:
 
 - `organization`
-- `feature`
-- `surface`
-- `entity`
+- `system`
+- `role`
 - `capability`
 - `resource`
+- `knowledge`
+- `policy`
 
 Edge kinds:
 
 - `contains`
 - `references`
-- `exposes`
 - `maps_to`
-- `operates-on`
 - `uses`
+- `governs`
+- `governed-by`
 
-Feature nodes come from the flat `OrganizationModel.features` array. Their graph IDs use `feature:<id>`, such as `feature:sales.crm`.
+System nodes come from the id-keyed `OrganizationModel.systems` map. Their graph IDs use `system:<id>`, such as `system:sales.crm`.
 
-Resource edges come from resource metadata:
+Resource and capability edges are derived from canonical OM maps:
 
 ```ts
-links: [
-  { nodeId: 'feature:sales.lead-gen', kind: 'operates-on' },
-  { nodeId: 'integration:instantly', kind: 'uses' }
-]
+// ResourceEntry.systemPath => system -> resource contains
+// SystemEntry.capabilities[] => system -> capability uses
+// Capability.resourceId => capability -> resource maps_to
+// AgentResource.invocations[] => agent resource -> invocation target uses/references
 ```
 
 ## Build Pipeline
@@ -64,9 +65,9 @@ interface BuildOrganizationGraphInput {
 
 `buildOrganizationGraph`:
 
-1. Reads flat Organization Model features and derives `feature:*` nodes.
-2. Reads Command View resources, including integration resources, as `resource` nodes with `resourceType` metadata.
-3. Emits authored graph links from resource/entity/capability metadata.
+1. Reads Organization Model Systems and derives `system:*` nodes.
+2. Reads OM resources, including workflow, agent, integration, and script resources, as `resource` nodes.
+3. Emits derived graph links from System, Resource, Capability, Agent invocation, and Knowledge contracts.
 4. Bridges Command View runtime topology into resource nodes and relationship edges.
 5. Returns a renderer-agnostic DTO.
 

package/reference/scaffold/core/organization-model.mdx

@@ -1,6 +1,6 @@
 ---
 title: Organization Model
-description: Organization OS Model layer documentation for the flat feature hierarchy, semantic domains, resource descriptors, and curated @elevasis/core public API.
+description: Organization OS Model layer documentation for the System hierarchy, semantic domains, resource descriptors, and curated @elevasis/core public API.
 ---
 <!-- @generated by packages/sdk/scripts/copy-reference-docs.mjs -- DO NOT EDIT -->
 <!-- Regenerate: pnpm scaffold:sync -->
@@ -8,7 +8,7 @@ description: Organization OS Model layer documentation for the flat feature hier
 
 ## Overview
 
-The organization model is the semantic contract that maps an organization's product shape to flat feature hierarchy, business semantics, shell navigation, and graph binding. It is schema-first, versioned, and validated.
+The organization model is the semantic contract that maps an organization's System hierarchy, business semantics, shell navigation, resource governance, and graph binding. It is schema-first, versioned, and validated.
 
 The model is authored in `@repo/core` and published through the curated `@elevasis/core/organization-model` surface.
 
@@ -27,7 +27,7 @@ The model is authored in `@repo/core` and published through the curated `@elevas
 Top-level fields on `OrganizationModel`:
 
 - `version`
-- `features`
+- `domainMetadata`
 - `branding`
 - `navigation`
 - `sales`
@@ -40,23 +40,26 @@ Top-level fields on `OrganizationModel`:
 - `goals`
 - `systems`
 - `resources`
+- `capabilities`
+- `policies`
 - `statuses`
-- `operations`
 - `knowledge`
 
-Resource identity is authored inside `OrganizationModel.resources.entries`. Runtime workflows, agents, and integrations import those descriptors, derive `resourceId` and kind from them, and attach executable behavior in operations code.
+The pure collection domains are id-keyed maps: `systems`, `roles`, `goals`, `customers`, `offerings`, `resources`, `capabilities`, `policies`, and `statuses`. The map key must match the entry `id`. Entries carry `order` for deterministic ordered views; use `listDomain(record)` when order matters.
 
-## Feature Shape
+Resource identity is authored inside `OrganizationModel.resources`. Runtime workflows, agents, integrations, and scripts import those descriptors, derive `resourceId` and kind from them, and attach executable behavior in operations code.
 
-`OrganizationModel.features` is a flat array. Hierarchy is derived from dotted IDs:
+## System Shape
+
+`OrganizationModel.systems` is the canonical semantic domain map. Hierarchy is derived from `parentSystemId` and dotted IDs:
 
 ```ts
-features: [
-  { id: 'dashboard', label: 'Dashboard', enabled: true, path: '/', uiPosition: 'sidebar-primary' },
-  { id: 'sales', label: 'Sales', enabled: true, uiPosition: 'sidebar-primary' },
-  { id: 'sales.crm', label: 'CRM', enabled: true, path: '/crm' },
-  { id: 'operations.resources', label: 'Resources', enabled: true, path: '/operations/resources' }
-]
+systems: {
+  dashboard: { id: 'dashboard', order: 10, label: 'Dashboard', lifecycle: 'active' },
+  sales: { id: 'sales', order: 20, label: 'Sales', lifecycle: 'active' },
+  clients: { id: 'clients', order: 30, label: 'Clients', lifecycle: 'active' },
+  projects: { id: 'projects', order: 40, label: 'Projects', lifecycle: 'active' }
+}
 ```
 
 Authored fields:
@@ -64,29 +67,74 @@ Authored fields:
 - `id`
 - `label`
 - `description`
-- `enabled`
-- `path`
-- `icon`
-- `color`
-- `uiPosition`
+- `kind`
+- `parentSystemId`
+- `ui`
+- `lifecycle`
 - `requiresAdmin`
-- `devOnly`
+- `capabilities`
+- `policies`
+- `order`
+
+Systems describe ownership, hierarchy, lifecycle, access, and governance. Sidebar presentation lives in `navigation.sidebar`, not on System entries. UI-backed Systems may still provide `ui.path` for route matching during the migration, but `ui.surfaces` is not an authored contract. `lifecycle` replaces the old feature enabled/dev-only split.
 
-Containers omit `path`; leaves provide `path`. `uiPosition`, `requiresAdmin`, and `devOnly` inherit from ancestors.
-Development-only features remain defined and enabled with `devOnly: true`; shell consumers hide those entries and route paths outside development mode while preserving the semantic contract.
+## Navigation Shape
 
-Navigation surfaces may also carry `devOnly` for compatibility with the legacy/domain navigation model. `knowledge.command-view` is intentionally development-only while its graph visualization modes continue to mature.
+`OrganizationModel.navigation.sidebar` is the authored shell tree. It has `primary` and `bottom` sections whose records contain recursive group nodes and routeable surface nodes:
+
+```ts
+navigation: {
+  sidebar: {
+    primary: {
+      dashboard: {
+        type: 'surface',
+        order: 10,
+        label: 'Dashboard',
+        path: '/',
+        surfaceType: 'dashboard',
+        targets: { systems: ['dashboard'] }
+      },
+      business: {
+        type: 'group',
+        order: 20,
+        label: 'Business',
+        children: {
+          sales: {
+            type: 'surface',
+            order: 10,
+            label: 'Sales',
+            path: '/sales',
+            surfaceType: 'page',
+            targets: { systems: ['sales'] }
+          },
+          clients: {
+            type: 'surface',
+            order: 20,
+            label: 'Clients',
+            path: '/clients',
+            surfaceType: 'list',
+            targets: { systems: ['clients'] }
+          }
+        }
+      }
+    },
+    bottom: {}
+  }
+}
+```
+
+Dashboard is ordered before Business in the primary sidebar. Business is a navigation group only; it is not a System and it is not a URL namespace. Routeable leaves are projected into flat surface DTOs by `projectOrganizationSurfaces(model)`.
 
 ## Graph IDs and Resource Descriptors
 
 Cross-collection links use kind-prefixed graph IDs:
 
-- `feature:sales.crm`
+- `system:sales.crm`
 - `integration:instantly`
 - `resource:lead-import`
-- `capability:operations.queue.review`
+- `action:operations.queue.review`
 
-Resource identity is authored in the OM Resources domain. Operations imports descriptors from `organizationModel.resources.entries` and derives runtime `resourceId` / `type` while attaching executable behavior.
+Resource identity is authored in the OM Resources domain. Operations imports descriptors from `organizationModel.resources` and derives runtime `resourceId` / `type` while attaching executable behavior.
 
 ```ts
 import { defineResources } from '@elevasis/core/organization-model'
@@ -95,23 +143,22 @@ export const resourceDescriptors = defineResources({
   leadImport: {
     id: 'lead-import',
     kind: 'workflow',
-    systemId: 'sys.prospecting',
+    systemPath: 'sales.lead-gen',
     ownerRoleId: 'role-ops-lead',
     status: 'active',
-    capabilityKey: 'prospecting.lead-import'
+    actionKey: 'prospecting.lead-import'
   }
 })
 
 export const resourceGovernanceModel = {
-  systems: {
-    systems
-  },
-  resources: {
-    entries: Object.values(resourceDescriptors)
-  }
+  systems,
+  resources: resourceDescriptors
 } as const
 ```
 
+Legacy `sys.*` paths may still appear in older examples and external compatibility mirrors.
+For new Organization OS examples, prefer the current semantic System path.
+
 ## Domain Semantics
 
 The model keeps business semantics in named domains:
@@ -122,7 +169,7 @@ The model keeps business semantics in named domains:
 - `identity`, `customers`, `offerings`, `roles`, `goals` -- organizational reality
 - `systems` -- bounded contexts that group governed operational resources
 - `resources` -- governance-only workflow, agent, and integration descriptors
-- `statuses` and `operations` -- runtime/vibe-layer semantic registries
+- `statuses` -- runtime/vibe-layer semantic registry
 - `knowledge` -- playbooks, strategies, references, and graph-governing links
 
 ## Authoring and Resolution
@@ -131,15 +178,16 @@ The model keeps business semantics in named domains:
 - `resolveOrganizationModel(partial)` deep-merges a partial override into `DEFAULT_ORGANIZATION_MODEL` and validates the result.
 - `createFoundationOrganizationModel(partial)` resolves the canonical model and returns template-facing helpers.
 - Plain objects merge recursively.
+- Id-keyed domain maps merge additively by key.
 - Arrays replace defaults.
 
 ## Referential Integrity
 
 `OrganizationModelSchema` validates:
 
-- unique feature IDs
-- ancestor existence for dotted feature IDs
-- container/leaf path rules
+- unique System IDs
+- ancestor existence for dotted System IDs and `parentSystemId`
+- UI path rules for Systems with UI presence
 - valid sidebar positions
 - reality-domain cross references such as offering target segments and role reporting lines
 - system, resource, role, knowledge, and goal cross references used by resource governance
@@ -148,11 +196,11 @@ The model keeps business semantics in named domains:
 
 ## Provider Integration
 
-`ElevasisFeaturesProvider` uses the organization model to:
+`ElevasisSystemsProvider` uses the organization model to:
 
-1. validate each manifest's `featureId`
-2. resolve effective feature access
-3. derive sidebar entries from `features`
+1. validate each manifest's `systemId`
+2. resolve effective system access
+3. derive sidebar entries from `navigation.sidebar`
 4. expose shell helpers such as `childrenOf`, `ancestorsOf`, and `findByPath`
 5. bridge the operations graph into shared UI
 

package/reference/scaffold/index.mdx

@@ -10,20 +10,20 @@ description: Universal scaffold documentation for Elevasis SDK projects -- recip
 
 This scaffold reference contains universal documentation that applies to all Elevasis SDK projects. Content is organized by package ownership:
 
-- **recipes/** -- Cross-package pathway recipes (add a feature, add a resource, gating patterns)
-- **ui/** -- UI patterns, feature shell architecture, composition, and customization
+- **recipes/** -- Cross-package pathway recipes (add a system, add a resource, gating patterns)
+- **ui/** -- UI patterns, system shell architecture, composition, and customization
 - **core/** -- Organization model architecture, graph layer, and semantic contracts
 - **operations/** -- Workflow authoring patterns and adapter usage
-- **reference/** -- Glossary, auto-generated contracts, and feature registry
+- **reference/** -- Glossary, auto-generated contracts, and system registry
 
 ## Quick Navigation
 
 ### Pathway Recipes
 
-- [Add a Feature](./recipes/add-a-feature.md) -- end-to-end from org model key through manifest, routes, gating
+- [Add a System](./recipes/add-a-feature.md) -- end-to-end from org model key through manifest, routes, gating
 - [Add a Resource](./recipes/add-a-resource.md) -- author and deploy a workflow or agent
 - [Extend a Base Entity](./recipes/extend-a-base-entity.md) -- add project-specific metadata to canonical entity shapes via the TMeta slot
-- [Gate by Feature or Admin](./recipes/gate-by-feature-or-admin.md) -- decision table for access control patterns
+- [Gate by System or Admin](./recipes/gate-by-feature-or-admin.md) -- decision table for access control patterns
 - [Build and Extend CRM](./recipes/extend-crm.md) -- map CRM UI pages, hooks, actions, workflow adapters, contracts, and org-model boundaries
 - [Build and Extend Lead Gen](./recipes/extend-lead-gen.md) -- map lead-gen UI pages, hooks, list/member state, artifacts, workflow adapters, contracts, and org-model boundaries
 - [Customize CRM Actions](./recipes/customize-crm-actions.md) -- add, hide, or replace CRM deal actions, use the shared `crmActions` provider path, and understand workflow dispatch constraints
@@ -31,9 +31,9 @@ This scaffold reference contains universal documentation that applies to all Ele
 ### UI Patterns
 
 - [UI Recipes](./ui/recipes.md) -- copy-paste recipes for pages, nav items, components, theme tokens
-- [Feature Flags & Gating](./ui/feature-flags-and-gating.md) -- three-concept model for feature access
-- [Customizing Features](./ui/customization.md) -- sidebar composition via manifest overrides
-- [Feature Shell & Provider](./ui/feature-shell.mdx) -- FeatureModule manifest contract, provider runtime
+- [System Flags & Gating](./ui/feature-flags-and-gating.md) -- three-concept model for system access
+- [Customizing Systems](./ui/customization.md) -- sidebar composition via manifest overrides
+- [System Shell & Provider](./ui/feature-shell.mdx) -- SystemModule manifest contract, provider runtime
 - [Composition & Extensibility](./ui/composition-extensibility.mdx) -- layout primitives, router abstraction
 
 ### Core Architecture
@@ -51,7 +51,7 @@ This scaffold reference contains universal documentation that applies to all Ele
 
 - [Glossary](./reference/glossary.md) -- term definitions for Organization OS concepts
 - [Contracts](./reference/contracts.md) -- auto-generated TypeScript contract shapes
-- [Feature Registry](./reference/feature-registry.md) -- auto-generated feature manifest catalog
+- [System Registry](./reference/feature-registry.md) -- auto-generated system manifest catalog
 
 ## Source Locations
 

package/reference/scaffold/operations/propagation-pipeline.md

@@ -36,7 +36,7 @@ Layer 3: Sync Verification (pnpm sync:verify)
 | Script                                  | Input                                                                                                                                         | Output                                                              |
 | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
 | `generate-scaffold-contracts.js`        | `packages/core/src/organization-model/types.ts`, `packages/ui/src/features/registry/types.ts`, `packages/core/src/platform/registry/types.ts` | `packages/core/src/reference/_generated/contracts.md`               |
-| `generate-scaffold-feature-registry.js` | `packages/ui/src/features/*/manifest.ts`, `packages/core/src/organization-model/domains/features.ts`                                          | `packages/ui/src/scaffold/_generated/feature-registry.md`           |
+| `generate-scaffold-feature-registry.js` | `packages/ui/src/features/registry/manifests.ts`, `packages/ui/src/features/*/manifest.ts`                                                    | `packages/ui/src/scaffold/_generated/feature-registry.md`           |
 | `generate-reference-artifacts.js`       | SDK manifest, navigation sources                                                                                                              | `packages/sdk/reference/_reference-manifest.json`, `_navigation.md` |
 
 After generation, `validate-reference-artifacts.js` checks that the outputs are consistent. Exit 1 if drifted.
@@ -102,7 +102,7 @@ The external skill doc (`.claude/skills/external/SKILL.md`) remains the workflow
 | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `deps`         | `@elevasis/ui`, `@elevasis/sdk`, `@elevasis/core` versions match template                                                                                                                                                                                                                                                                                   |
 | `tier1`        | registry-backed replace surfaces match template where verification still models them as exact baselines                                                                                                                                                                                                                                                     |
-| `org-os`       | Organization model exists, exports canonical symbols, imports from `@elevasis/core/organization-model`, calls `createFoundationOrganizationModel`, app-config references org model, `__root.tsx` uses `ElevasisFeaturesProvider` + `canonicalOrganizationModel`, `main.tsx` uses `createElevasisApp`, all 3 CSS subpath imports present |
+| `org-os`       | Organization model exists, exports canonical symbols, imports from `@elevasis/core/organization-model`, calls `createFoundationOrganizationModel`, app-config references org model, `__root.tsx` uses `ElevasisSystemsProvider` + `canonicalOrganizationModel`, `main.tsx` uses `createElevasisApp`, all 3 CSS subpath imports present |
 | `placeholders` | No unresolved `__PROJECT_SLUG__`, `__PROJECT_NAME__`, `__PROJECT_DESCRIPTION__` in key config files                                                                                                                                                                                                                                                         |
 | `scripts`      | `ui` and `operations` `package.json` have required npm scripts                                                                                                                                                                                                                                                                                              |
 | `lib`          | `ui/src/lib/`, `lib/`, `test-utils/` exist with minimum file counts                                                                                                                                                                                                                                                                                         |
@@ -149,7 +149,7 @@ Treat the old tier labels as display shorthand inside the verifier, not as the c
 
 | Gap                                                                       | Priority |
 | ------------------------------------------------------------------------- | -------- |
-| Feature manifest validation (all manifests imported in `__root.tsx`)      | Medium   |
+| System manifest validation (all manifests imported in `__root.tsx`)       | Medium   |
 | TypeScript verification (`check-types` per project)                       | Medium   |
 | Template docs surface validation (`docs/index.md`, `agent-start-here.md`) | Medium   |
 | Environment variable template validation (`.env.example` completeness)    | Low      |

package/reference/scaffold/operations/scaffold-maintenance.md

@@ -32,11 +32,11 @@ Scaffold docs are co-located with their owning package and copied into the SDK r
 | Glossary                    | `packages/core/src/reference/glossary.md`                       | `scaffold/reference/glossary.md`              |
 | Contracts (auto-gen)        | `packages/core/src/reference/_generated/contracts.md`           | `scaffold/reference/contracts.md`             |
 | UI Recipes                  | `packages/ui/src/scaffold/recipes.md`                           | `scaffold/ui/recipes.md`                      |
-| Feature Flags & Gating      | `packages/ui/src/scaffold/feature-flags-and-gating.md`          | `scaffold/ui/feature-flags-and-gating.md`     |
+| System Flags & Gating       | `packages/ui/src/scaffold/feature-flags-and-gating.md`          | `scaffold/ui/feature-flags-and-gating.md`     |
 | Customization               | `packages/ui/src/scaffold/customization.md`                     | `scaffold/ui/customization.md`                |
-| Feature Shell               | `packages/ui/src/scaffold/feature-shell.mdx`                    | `scaffold/ui/feature-shell.mdx`               |
+| System Shell                | `packages/ui/src/scaffold/feature-shell.mdx`                    | `scaffold/ui/feature-shell.mdx`               |
 | Composition & Extensibility | `packages/ui/src/scaffold/composition-extensibility.mdx`        | `scaffold/ui/composition-extensibility.mdx`   |
-| Feature Registry (auto-gen) | `packages/ui/src/scaffold/_generated/feature-registry.md`       | `scaffold/reference/feature-registry.md`      |
+| System Registry (auto-gen)  | `packages/ui/src/scaffold/_generated/feature-registry.md`       | `scaffold/reference/feature-registry.md`      |
 | Scaffold Index              | `packages/sdk/docs/scaffold/index.mdx`                          | `scaffold/index.mdx`                          |
 | Pathway Recipes (4)         | `packages/sdk/docs/scaffold/recipes/`                           | `scaffold/recipes/`                           |
 | Workflow Recipes            | `packages/sdk/docs/scaffold/operations/workflow-recipes.md`     | `scaffold/operations/workflow-recipes.md`     |
@@ -53,18 +53,18 @@ Two types of docs are auto-generated from source:
 
 Generated by `scripts/monorepo/generate-scaffold-contracts.js` from TypeScript source types:
 
-- `packages/core/src/organization-model/types.ts` -- Organization Model, Feature System
-- `packages/ui/src/features/registry/types.ts` -- Feature Registry
+- `packages/core/src/organization-model/types.ts` -- Organization Model, System Model
+- `packages/ui/src/features/registry/types.ts` -- System Registry
 - `packages/core/src/platform/registry/types.ts` -- Resource Registry, Deployment Spec
 
 Output: `packages/core/src/reference/_generated/contracts.md`
 
-### Feature Registry (`feature-registry.md`)
-
-Generated by `scripts/monorepo/generate-scaffold-feature-registry.js` from feature manifests:
-
-- `packages/ui/src/features/*/manifest.ts` -- individual feature manifests
-- `packages/core/src/organization-model/domains/features.ts` -- feature key definitions
+### System Registry (`feature-registry.md`)
+
+Generated by `scripts/monorepo/generate-scaffold-feature-registry.js` from system manifests:
+
+- `packages/ui/src/features/*/manifest.ts` -- individual system manifests
+- `packages/ui/src/features/registry/manifests.ts` -- `SYSTEM_MANIFESTS`
 
 Output: `packages/ui/src/scaffold/_generated/feature-registry.md`