@elevasis/sdk 1.19.0 → 1.20.1

package/reference/scaffold/recipes/add-a-resource.md

@@ -1,6 +1,6 @@
 ---
 title: Add a Resource
-description: Add a workflow or agent with resource metadata, graph links, and deployment verification.
+description: Add an OM-owned workflow or agent descriptor, bind executable behavior in operations, and verify descriptor-backed deployment.
 ---
 <!-- @generated by packages/sdk/scripts/copy-reference-docs.mjs -- DO NOT EDIT -->
 <!-- Regenerate: pnpm scaffold:sync -->
@@ -8,18 +8,58 @@ description: Add a workflow or agent with resource metadata, graph links, and de
 
 # Add a Resource
 
-Resources are workflows, agents, triggers, integrations, external systems, or human checkpoints collected in a `DeploymentSpec`. They link into the Organization Model graph through resource metadata, not through `OrganizationModel` mapping tables.
+Resources are governed descriptors in the Organization Model. The OM owns resource identity, System membership, owner role, and lifecycle status. Operations code imports those descriptors, attaches executable workflow or agent behavior, and exports a `DeploymentSpec` for deployment.
 
-## 1. Author the resource
+Do not keep a second identity catalog in operations. `DeploymentSpec` is the runtime/deploy assembly artifact; it should not be the place where a workflow ID is invented.
+
+## 1. Author the OM descriptor
+
+Add the descriptor in `core/config/organization-model.ts`:
+
+```ts
+import { defineResources } from '@elevasis/core/organization-model'
+
+export const resourceDescriptors = defineResources({
+  myWorkflow: {
+    id: 'my-workflow',
+    kind: 'workflow',
+    systemId: 'sys.operations',
+    ownerRoleId: 'role-ops-lead',
+    status: 'active',
+    capabilityKey: 'operations.my-workflow'
+  }
+})
+```
+
+Then expose the descriptor catalog through the Organization Model:
+
+```ts
+export const resourceGovernanceModel = {
+  systems: {
+    systems
+  },
+  resources: {
+    entries: Object.values(resourceDescriptors)
+  }
+} as const
+```
+
+Use `organizationModel.resources.entries` as the Resources descriptor catalog. `links[].nodeId` still uses the kind-prefixed graph grammar, such as `feature:sales.crm`, `integration:instantly`, or `capability:operations.queue.review`, when a runtime resource needs semantic graph binding.
+
+## 2. Author executable behavior
+
+Operations code owns schemas, steps, handlers, triggers, and UI execution metadata. Import the descriptor and derive runtime identity from it at the binding boundary:
 
 ```ts
 import type { WorkflowDefinition } from '@elevasis/sdk'
+import { resourceDescriptors } from '@core/config/organization-model'
 
 export const myWorkflow: WorkflowDefinition = {
   config: {
-    resourceId: 'my-workflow',
+    resource: resourceDescriptors.myWorkflow,
+    resourceId: resourceDescriptors.myWorkflow.id,
     name: 'My Workflow',
-    type: 'workflow',
+    type: resourceDescriptors.myWorkflow.kind,
     version: '1.0.0',
     status: 'dev',
     links: [{ nodeId: 'feature:operations', kind: 'operates-on' }],
@@ -46,17 +86,17 @@ export const myWorkflow: WorkflowDefinition = {
 }
 ```
 
-`links[].nodeId` uses the kind-prefixed graph grammar, such as `feature:sales.crm`, `integration:instantly`, or `capability:operations.queue.review`.
-
 `category` is one of `production`, `diagnostic`, `internal`, or `testing`.
 
-## 2. Register in the deployment spec
+## 3. Register in the deployment spec
 
 ```ts
+import { resourceGovernanceModel } from '@core/config/organization-model'
 import { myWorkflow } from './my-workflow/index.js'
 
 export const org = {
   version: '0.1.0',
+  organizationModel: resourceGovernanceModel,
   workflows: [myWorkflow],
   agents: []
 }
@@ -64,7 +104,7 @@ export const org = {
 
 Use `.js` extensions in TypeScript source imports for ESM compatibility.
 
-## 3. Declare runtime relationships
+## 4. Declare runtime relationships
 
 Use `DeploymentSpec.relationships` for execution topology:
 
@@ -79,7 +119,7 @@ relationships: {
 
 Use `config.links` for semantic graph binding and `relationships` for runtime execution relationships.
 
-## 4. Verify
+## 5. Verify
 
 ```bash
 pnpm -C operations check

package/reference/scaffold/recipes/customize-crm-actions.md

@@ -84,13 +84,15 @@ The canonical transition workflow (see `packages/elevasis-operations/src/sales/c
 // operations/src/sales/crm/actions/move-to-proposal.ts
 import type { WorkflowDefinition } from '@elevasis/sdk'
 import { acqDb } from '@elevasis/sdk/worker'
+import { resourceDescriptors } from '@core/config/organization-model'
 import { ActionWorkflowInputSchema, ActionWorkflowOutputSchema } from '../shared/action-workflow-schemas.js'
 
 export const moveToProposalWorkflow: WorkflowDefinition = {
   config: {
-    resourceId: 'move_to_proposal-workflow',
+    resource: resourceDescriptors.moveToProposal,
+    resourceId: resourceDescriptors.moveToProposal.id,
     name: 'Move to Proposal',
-    type: 'workflow',
+    type: resourceDescriptors.moveToProposal.kind,
     version: '1.0.0',
     status: 'prod',
     category: 'internal',
@@ -119,7 +121,7 @@ export const moveToProposalWorkflow: WorkflowDefinition = {
 }
 ```
 
-To add side effects (create a task, send a Slack message, log a deal activity), extend the handler before the `return`. The `resourceId` must match the action's `workflowId` in `DEFAULT_CRM_ACTIONS` from `@elevasis/sdk` exactly.
+To add side effects (create a task, send a Slack message, log a deal activity), extend the handler before the `return`. The OM descriptor ID must match the action's `workflowId` in `DEFAULT_CRM_ACTIONS` from `@elevasis/sdk` exactly.
 
 Register the workflow in the operations manifest:
 
@@ -232,6 +234,7 @@ export type SendQuoteOutput = z.infer<typeof sendQuoteOutputSchema>
 // operations/src/sales/send-quote.ts
 import type { WorkflowDefinition } from '@elevasis/sdk'
 import { acqDb, createResendAdapter } from '@elevasis/sdk/worker'
+import { resourceDescriptors } from '@core/config/organization-model'
 import {
   sendQuoteInputSchema,
   sendQuoteOutputSchema
@@ -239,9 +242,10 @@ import {
 
 export const sendQuoteWorkflow: WorkflowDefinition = {
   config: {
-    resourceId: 'send-quote-workflow',
+    resource: resourceDescriptors.sendQuote,
+    resourceId: resourceDescriptors.sendQuote.id,
     name: 'Send Quote',
-    type: 'workflow',
+    type: resourceDescriptors.sendQuote.kind,
     version: '1.0.0',
     status: 'dev',
     category: 'internal',
@@ -315,9 +319,11 @@ A custom `ActionDef` entry with `workflowId: 'send-quote-workflow'` can be rende
 import { Button } from '@mantine/core'
 import { useMutation } from '@tanstack/react-query'
 import { useElevasisServices } from '@elevasis/ui/provider'
+import { resourceDescriptors } from '@core/config/organization-model'
 
 export function SendQuoteButton({ dealId }: { dealId: string }) {
   const { apiRequest, organizationId } = useElevasisServices()
+  const resourceId = resourceDescriptors.sendQuote.id
 
   const sendQuote = useMutation({
     mutationFn: async () => {
@@ -327,7 +333,7 @@ export function SendQuoteButton({ dealId }: { dealId: string }) {
         method: 'POST',
         body: JSON.stringify({
           resourceType: 'workflow',
-          resourceId: 'send-quote-workflow',
+          resourceId,
           input: { dealId, organizationId }
         })
       })

package/reference/scaffold/recipes/customize-organization-model.md

@@ -78,13 +78,28 @@ Feature field reference:
 
 ## Resource Binding
 
-Resources do not live in `OrganizationModel`. Workflows, agents, triggers, integrations, and external resources declare semantic graph links in their resource metadata.
+Resource identity and governance metadata live in `OrganizationModel` under `resources.entries`. Workflows, agents, and integrations import those descriptors and derive runtime `resourceId` / `type` from them while still declaring semantic graph links in resource metadata.
 
 ```ts
+// core/config/organization-model.ts
+import { defineResources } from '@elevasis/core/organization-model'
+
+export const resourceDescriptors = defineResources({
+  leadImport: {
+    id: 'lead-import',
+    kind: 'workflow',
+    systemId: 'sys.prospecting',
+    ownerRoleId: 'role-ops-lead',
+    status: 'active'
+  }
+})
+
+// operations/src/lead-import/index.ts
 config: {
-  resourceId: 'lead-import',
+  resource: resourceDescriptors.leadImport,
+  resourceId: resourceDescriptors.leadImport.id,
   name: 'Lead Import',
-  type: 'workflow',
+  type: resourceDescriptors.leadImport.kind,
   version: '1.0.0',
   status: 'prod',
   links: [{ nodeId: 'feature:sales.lead-gen', kind: 'operates-on' }],

package/reference/scaffold/recipes/extend-crm.md

@@ -31,7 +31,7 @@ CRM is a layered platform surface, not one component:
 
 | User wants | Start here | Notes |
 | --- | --- | --- |
-| Change CRM feature availability, labels, or pipeline stages | `core/config/organization-model.ts` plus `core/config/organization-model.examples.ts` | Treat this as Organization OS work. Use the project's configure ceremony if available. |
+| Change CRM feature availability, labels, pipeline stages, or resource descriptors | `core/config/organization-model.ts` | Treat this as Organization OS work. Use the project's configure ceremony if available. |
 | Add CRM sidebar nav or a CRM route | `@elevasis/ui/features/crm` and `node_modules/@elevasis/sdk/reference/scaffold/ui/customization.md` | Prefer manifest/sidebar composition. Do not fork shared source first. |
 | Wrap a shared CRM page with project chrome | `DealsListPage`, `DealDetailPage`, `CrmOverview` from `@elevasis/ui/features/crm` | Keep route files thin and put project-specific logic in local feature modules. |
 | Build a custom deal page | `useDealDetail`, `useDealNotes`, `useDealTasks`, `useExecuteAction` from `@elevasis/ui/hooks` | Use hooks for platform data and compose your own UI. |
@@ -164,9 +164,10 @@ Inside deployed workflows, use worker adapters instead of browser hooks or direc
 
 ```ts
 // operations/src/sales/follow-up-stale-deals.ts
-import type { WorkflowDefinition } from '@elevasis/sdk'
-import { crm } from '@elevasis/sdk/worker'
-import { z } from 'zod'
+import type { WorkflowDefinition } from '@elevasis/sdk'
+import { crm } from '@elevasis/sdk/worker'
+import { resourceDescriptors } from '@core/config/organization-model'
+import { z } from 'zod'
 
 const inputSchema = z.object({
   stage: z.string().default('proposal')
@@ -176,14 +177,15 @@ const outputSchema = z.object({
   touched: z.number()
 })
 
-export const followUpStaleDealsWorkflow: WorkflowDefinition = {
-  config: {
-    resourceId: 'follow-up-stale-deals',
-    name: 'Follow Up Stale Deals',
-    type: 'workflow',
-    version: '1.0.0',
-    status: 'dev',
-    links: [{ nodeId: 'feature:sales.crm', kind: 'operates-on' }]
+export const followUpStaleDealsWorkflow: WorkflowDefinition = {
+  config: {
+    resource: resourceDescriptors.followUpStaleDeals,
+    resourceId: resourceDescriptors.followUpStaleDeals.id,
+    name: 'Follow Up Stale Deals',
+    type: resourceDescriptors.followUpStaleDeals.kind,
+    version: '1.0.0',
+    status: 'dev',
+    links: [{ nodeId: 'feature:sales.crm', kind: 'operates-on' }]
   },
   contract: { inputSchema, outputSchema },
   steps: {
@@ -226,13 +228,9 @@ Use `crm` for focused CRM deal reads, notes, tasks, activity, and cleanup. Use `
 
 CRM feature identity remains `sales.crm`, but the organization-model domain is `sales`.
 
-For stage labels or stage sets, start from the project reference file:
-
-`core/config/organization-model.examples.ts`
-
-Then update the project model:
-
-`core/config/organization-model.ts`
+For stage labels or stage sets, update the project model:
+
+`core/config/organization-model.ts`
 
 Keep these boundaries straight:
 

package/reference/scaffold/recipes/extend-lead-gen.md

@@ -30,31 +30,31 @@ Lead gen is a layered platform surface, not one component:
 
 ## Decision Table
 
-| User wants                                                                        | Start here                                                                                                                                      | Notes                                                                                                           |
-| --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
-| Change lead-gen feature availability, labels, quick access, or pipeline semantics | `core/config/organization-model.ts` plus `core/config/organization-model.examples.ts`                                                           | Treat this as Organization OS work. Use the project's configure ceremony if available.                          |
-| Add lead-gen sidebar nav or a lead-gen route                                      | `@elevasis/ui/features/lead-gen` and `node_modules/@elevasis/sdk/reference/scaffold/ui/customization.md`                                        | Prefer manifest/sidebar composition. Do not fork shared source first.                                           |
-| Wrap a shared lead-gen page with project chrome                                   | `LeadGenOverviewPage`, `LeadGenListsPage`, `LeadGenListDetailPage`, `ListBuilderPage`, `LeadGenCompaniesPage`, `LeadGenContactsPage`            | Keep route files thin and put project-specific behavior in local feature modules.                               |
-| Build a custom campaign/list workspace                                            | `ListBuilderPage`, `useLists`, `useList`, `useListProgress`, `useListExecutions`, `useWorkflowExecution`, `useExecutionSSE` from `@elevasis/ui` | Use the shared builder when possible; otherwise compose hooks for platform data and workflow execution.         |
-| Render artifacts or list-member detail                                            | `LeadGenListDetailPage`, `useArtifacts`, `useCreateArtifact`, `useListMember`                                                                   | Artifacts are a substrate primitive. Keep vertical-specific rendering local until there are repeated use cases. |
-| Read or mutate lead-gen data inside a workflow                                    | `acqDb` or `list` from `@elevasis/sdk/worker`                                                                                                   | `organizationId` is injected server-side by the platform dispatcher. Do not pass it from workflow code.         |
-| Add a new persisted lead-gen field, artifact kind, or transition API              | Platform/API migration work, not just scaffold work                                                                                             | Update DB, core schemas/types, API service/handlers, hooks, docs, and scaffold contracts together.              |
+| User wants                                                                                              | Start here                                                                                                                                      | Notes                                                                                                           |
+| ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
+| Change lead-gen feature availability, labels, quick access, pipeline semantics, or resource descriptors | `core/config/organization-model.ts`                                                                                                             | Treat this as Organization OS work. Use the project's configure ceremony if available.                          |
+| Add lead-gen sidebar nav or a lead-gen route                                                            | `@elevasis/ui/features/lead-gen` and `node_modules/@elevasis/sdk/reference/scaffold/ui/customization.md`                                        | Prefer manifest/sidebar composition. Do not fork shared source first.                                           |
+| Wrap a shared lead-gen page with project chrome                                                         | `LeadGenOverviewPage`, `LeadGenListsPage`, `LeadGenListDetailPage`, `ListBuilderPage`, `LeadGenCompaniesPage`, `LeadGenContactsPage`            | Keep route files thin and put project-specific behavior in local feature modules.                               |
+| Build a custom campaign/list workspace                                                                  | `ListBuilderPage`, `useLists`, `useList`, `useListProgress`, `useListExecutions`, `useWorkflowExecution`, `useExecutionSSE` from `@elevasis/ui` | Use the shared builder when possible; otherwise compose hooks for platform data and workflow execution.         |
+| Render artifacts or list-member detail                                                                  | `LeadGenListDetailPage`, `useArtifacts`, `useCreateArtifact`, `useListMember`                                                                   | Artifacts are a substrate primitive. Keep vertical-specific rendering local until there are repeated use cases. |
+| Read or mutate lead-gen data inside a workflow                                                          | `acqDb` or `list` from `@elevasis/sdk/worker`                                                                                                   | `organizationId` is injected server-side by the platform dispatcher. Do not pass it from workflow code.         |
+| Add a new persisted lead-gen field, artifact kind, or transition API                                    | Platform/API migration work, not just scaffold work                                                                                             | Update DB, core schemas/types, API service/handlers, hooks, docs, and scaffold contracts together.              |
 
 ## Published Lead-Gen Surfaces
 
-| Surface                                                                                                                                                      | Import from                      | Use for                                                                                     |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------- | ------------------------------------------------------------------------------------------- |
-| `leadGenManifest`, `LEAD_GEN_ITEMS`, `LeadGenSidebar`, `LeadGenSidebarTop`, `LeadGenSidebarMiddle`                                                           | `@elevasis/ui/features/lead-gen` | Feature registration and sidebar composition                                                |
-| `LeadGenOverviewPage`, `LeadGenListsPage`, `LeadGenListDetailPage`, `ListBuilderPage`, `LeadGenCompaniesPage`, `LeadGenContactsPage`                         | `@elevasis/ui/features/lead-gen` | Shared lead-gen pages you can route to or wrap                                              |
-| `ListActionsProvider`, `useListActions`, `ListBuilderWorkflow`, `ListBuilderRegistry`, `LeadGenCapabilityKey`                                                | `@elevasis/ui/features/lead-gen` | List Builder workflow registry, slot-based field contracts, and project-owned action wiring |
-| `LeadGenRouteShell`, `CompanyDetailModal`, `ContactDetailModal`, `LIST_TEMPLATE_OPTIONS`, `buildListConfig`                                                  | `@elevasis/ui/features/lead-gen` | Route shell helpers, detail modals, and list creation config helpers                        |
-| `useLists`, `useList`, `useListsTelemetry`, `useListProgress`, `useListExecutions`, `useCreateList`, `useUpdateList`, `useUpdateListConfig`, `useDeleteList` | `@elevasis/ui/hooks`             | Headless list and telemetry data access                                                     |
-| `useWorkflowExecution`, `useExecutionSSE`, `useAddCompaniesToList`, `useRemoveCompaniesFromList`, `useAddContactsToList`                                     | `@elevasis/ui/hooks`             | List Builder workflow triggering, live execution tailing, and list membership mutations     |
-| `useCompanies`, `useCompany`, `useContacts`, `useContact`                                                                                                    | `@elevasis/ui/hooks`             | Acquisition company/contact data access                                                     |
-| `useArtifacts`, `useCreateArtifact`, `useListMembers`, `useListMember`                                                                                       | `@elevasis/ui/hooks`             | Lead-gen substrate data access                                                              |
-| `useTransitionList`, `useTransitionListMember`, `useTransitionListCompany`, `useDeriveActions`                                                               | `@elevasis/ui/hooks`             | Stateful transition mutations and contextual action derivation                              |
-| `ElevasisUIProvider`, `ElevasisCoreProvider`, `useElevasisServices`                                                                                          | `@elevasis/ui/provider`          | Provider setup, API access, organization context, and `listActions` registry injection      |
-| `acqDb`, `list`                                                                                                                                              | `@elevasis/sdk/worker`           | Workflow-side acquisition and list-scoped platform adapters                                 |
+| Surface                                                                                                                                                      | Import from                      | Use for                                                                                                                                                                   |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `leadGenManifest`, `LEAD_GEN_ITEMS`, `LeadGenSidebar`, `LeadGenSidebarTop`, `LeadGenSidebarMiddle`                                                           | `@elevasis/ui/features/lead-gen` | Feature registration and sidebar composition                                                                                                                              |
+| `LeadGenOverviewPage`, `LeadGenListsPage`, `LeadGenListDetailPage`, `ListBuilderPage`, `LeadGenCompaniesPage`, `LeadGenContactsPage`                         | `@elevasis/ui/features/lead-gen` | Shared lead-gen pages you can route to or wrap                                                                                                                            |
+| `ListActionsProvider`, `useListActions`, `ListBuilderWorkflow`, `ListBuilderRegistry`, `LeadGenCapabilityKey`                                                | `@elevasis/ui/features/lead-gen` | List Builder workflow registry, slot-based field contracts, and project-owned action wiring                                                                               |
+| `LeadGenRouteShell`, `LIST_TEMPLATE_OPTIONS`, `buildListConfig`                                                                                              | `@elevasis/ui/features/lead-gen` | Route shell helpers and list creation config helpers (contact/company detail surfaces are now `ContactDetailPage` / `CompanyDetailPage` from `@elevasis/ui/features/crm`) |
+| `useLists`, `useList`, `useListsTelemetry`, `useListProgress`, `useListExecutions`, `useCreateList`, `useUpdateList`, `useUpdateListConfig`, `useDeleteList` | `@elevasis/ui/hooks`             | Headless list and telemetry data access                                                                                                                                   |
+| `useWorkflowExecution`, `useExecutionSSE`, `useAddCompaniesToList`, `useRemoveCompaniesFromList`, `useAddContactsToList`                                     | `@elevasis/ui/hooks`             | List Builder workflow triggering, live execution tailing, and list membership mutations                                                                                   |
+| `useCompanies`, `useCompany`, `useContacts`, `useContact`                                                                                                    | `@elevasis/ui/hooks`             | Acquisition company/contact data access                                                                                                                                   |
+| `useArtifacts`, `useCreateArtifact`, `useListMembers`, `useListMember`                                                                                       | `@elevasis/ui/hooks`             | Lead-gen substrate data access                                                                                                                                            |
+| `useTransitionList`, `useTransitionListMember`, `useTransitionListCompany`, `useDeriveActions`                                                               | `@elevasis/ui/hooks`             | Stateful transition mutations and contextual action derivation                                                                                                            |
+| `ElevasisUIProvider`, `ElevasisCoreProvider`, `useElevasisServices`                                                                                          | `@elevasis/ui/provider`          | Provider setup, API access, organization context, and `listActions` registry injection                                                                                    |
+| `acqDb`, `list`                                                                                                                                              | `@elevasis/sdk/worker`           | Workflow-side acquisition and list-scoped platform adapters                                                                                                               |
 
 Read the generated contracts before changing typed boundaries:
 
@@ -164,6 +164,7 @@ import * as z from 'zod'
 import { type ListBuilderRegistry } from '@elevasis/ui/features/lead-gen'
 import type { StepConfigLayout } from '@elevasis/ui/components/forms'
 import { ElevasisUIProvider } from '@elevasis/ui/provider'
+import { resourceDescriptors } from '@core/config/organization-model'
 
 const companyCleanupInputSchema = z.object({
   listId: z.string().uuid(),
@@ -174,6 +175,7 @@ const companyCleanupInputSchema = z.object({
 })
 
 type CompanyCleanupInput = z.infer<typeof companyCleanupInputSchema>
+const companyCleanupResource = resourceDescriptors.companyCleanup
 
 const companyCleanupLayout: StepConfigLayout<CompanyCleanupInput> = {
   sections: [
@@ -209,8 +211,8 @@ const companyCleanupLayout: StepConfigLayout<CompanyCleanupInput> = {
 
 const listActions: ListBuilderRegistry = [
   {
-    resourceId: 'lgn-company-cleanup-workflow',
-    workflowId: 'lgn-company-cleanup-workflow',
+    resourceId: companyCleanupResource.id,
+    workflowId: companyCleanupResource.id,
     capabilityKey: 'lead-gen.company.cleanup',
     label: 'Company Cleanup',
     description: 'Normalize and clean company records for the list.',
@@ -310,12 +312,14 @@ External projects should define workflow input/output schemas in `@shared/types`
 import type { WorkflowDefinition } from '@elevasis/sdk'
 import { acqDb, list } from '@elevasis/sdk/worker'
 import { qualifyListInputSchema, qualifyListOutputSchema } from '@shared/types'
+import { resourceDescriptors } from '@core/config/organization-model'
 
 export const qualifyListWorkflow: WorkflowDefinition = {
   config: {
-    resourceId: 'qualify-list',
+    resource: resourceDescriptors.qualifyList,
+    resourceId: resourceDescriptors.qualifyList.id,
     name: 'Qualify List',
-    type: 'workflow',
+    type: resourceDescriptors.qualifyList.kind,
     version: '1.0.0',
     status: 'dev',
     links: [{ nodeId: 'feature:sales.lead-gen', kind: 'operates-on' }]
@@ -368,11 +372,7 @@ Keep these boundaries straight:
 
 The lead-gen shell feature key is `lead-gen`, the Organization OS feature id is `sales.lead-gen`, and the capability currently used by the shared manifest is `leadgen.lists.manage`.
 
-For feature toggles, labels, or lifecycle semantics, start from the project reference file:
-
-`core/config/organization-model.examples.ts`
-
-Then update the project model:
+For feature toggles, labels, lifecycle semantics, or resource descriptors, update the project model:
 
 `core/config/organization-model.ts`
 

package/reference/scaffold/recipes/index.md

@@ -20,7 +20,7 @@ Before starting, read [glossary.md](../reference/glossary.md) to disambiguate ov
 You want a new shell feature (e.g., `analytics`) with its own nav entry, sidebar, routes, and org-model gate. Covers adding a feature object to the org model, `FeatureModule` manifest authoring, route creation, and gating.
 
 **[Add a Resource](add-a-resource.md)**
-You want a new workflow or agent deployed to the platform. Covers `WorkflowDefinition` authoring, `DeploymentSpec` registration, relationship declarations, domain mapping, and CLI verification.
+You want a new workflow or agent deployed to the platform. Covers OM Resource descriptor authoring, descriptor-backed `WorkflowDefinition` binding, `DeploymentSpec` assembly, relationship declarations, and CLI verification.
 
 **[Gate by Feature or Admin](gate-by-feature-or-admin.md)**
 You want to restrict a route, nav item, or UI element by feature flag or admin role. Covers the decision table, `FeatureGuard`, `AdminGuard`, nav-entry visibility fields, per-member `MembershipFeatureConfig` overrides, and the settings-asymmetry gotcha.