@elevasis/sdk 1.20.2 → 1.22.0

package/reference/examples/organization-model.ts

@@ -18,89 +18,135 @@ export const brandingOverrideExample = defineOrganizationModel({
 })
 
 // ---------------------------------------------------------------------------
-// Flat feature hierarchy
+// System hierarchy, system-local config, ontology scopes, and sidebar navigation
 // ---------------------------------------------------------------------------
-export const featureTreeExample = defineOrganizationModel({
-  features: [
-    {
-      id: 'dashboard',
-      label: 'Dashboard',
-      enabled: true,
-      path: '/',
-      icon: 'dashboard',
-      uiPosition: 'sidebar-primary'
-    },
-    {
+export const systemNavigationExample = defineOrganizationModel({
+  ontology: {
+    valueTypes: {
+      'global:value-type/text': {
+        id: 'global:value-type/text',
+        label: 'Text'
+      }
+    }
+  },
+  systems: {
+    sales: {
       id: 'sales',
       label: 'Sales',
-      enabled: true,
-      icon: 'briefcase',
-      uiPosition: 'sidebar-primary'
-    },
-    {
-      id: 'sales.crm',
-      label: 'CRM',
-      enabled: true,
-      path: '/crm'
-    },
-    {
-      id: 'sales.lead-gen',
-      label: 'Lead Gen',
-      enabled: true,
-      path: '/lead-gen'
-    },
-    {
-      id: 'admin',
-      label: 'Admin',
-      enabled: true,
-      path: '/admin',
-      icon: 'shield',
-      uiPosition: 'sidebar-bottom',
-      requiresAdmin: true
-    }
-  ]
-})
-
-// ---------------------------------------------------------------------------
-// Sales customization
-// ---------------------------------------------------------------------------
-export const salesCustomizationExample = defineOrganizationModel({
-  sales: {
-    entityId: 'crm.deal',
-    defaultPipelineId: 'sales',
-    pipelines: [
-      {
-        id: 'sales',
-        label: 'Sales Pipeline',
-        entityId: 'crm.deal',
-        stages: [
-          { id: 'qualified', label: 'Qualified', color: 'blue', order: 1, semanticClass: 'open' },
-          { id: 'negotiating', label: 'Negotiating', color: 'yellow', order: 2, semanticClass: 'active' },
-          { id: 'won', label: 'Won', color: 'green', order: 3, semanticClass: 'closed_won' }
-        ]
+      order: 20,
+      lifecycle: 'active',
+      systems: {
+        crm: {
+          id: 'sales.crm',
+          label: 'CRM',
+          order: 10,
+          lifecycle: 'active',
+          parentSystemId: 'sales',
+          config: {
+            defaultPipelineId: 'sales.crm:catalog/pipeline',
+            kanban: {
+              groupBy: 'stage',
+              showProbability: true
+            }
+          },
+          ontology: {
+            objectTypes: {
+              'sales.crm:object/deal': {
+                id: 'sales.crm:object/deal',
+                label: 'Deal',
+                ownerSystemId: 'sales.crm'
+              }
+            },
+            actionTypes: {
+              'sales.crm:action/deal.update-stage': {
+                id: 'sales.crm:action/deal.update-stage',
+                label: 'Update Deal Stage',
+                ownerSystemId: 'sales.crm',
+                actsOn: ['sales.crm:object/deal']
+              }
+            },
+            catalogTypes: {
+              'sales.crm:catalog/pipeline': {
+                id: 'sales.crm:catalog/pipeline',
+                label: 'Sales Pipeline',
+                ownerSystemId: 'sales.crm',
+                kind: 'pipeline',
+                appliesTo: 'sales.crm:object/deal',
+                entries: {
+                  qualified: { label: 'Qualified', color: 'blue', order: 10, semanticClass: 'open' },
+                  negotiating: { label: 'Negotiating', color: 'yellow', order: 20, semanticClass: 'active' },
+                  won: { label: 'Won', color: 'green', order: 30, semanticClass: 'closed_won' }
+                }
+              }
+            }
+          }
+        },
+        leadGen: {
+          id: 'sales.lead-gen',
+          label: 'Lead Gen',
+          order: 20,
+          lifecycle: 'active',
+          parentSystemId: 'sales'
+        }
       }
-    ]
+    }
+  },
+  navigation: {
+    sidebar: {
+      primary: {
+        dashboard: {
+          type: 'surface',
+          order: 10,
+          label: 'Dashboard',
+          path: '/',
+          surfaceType: 'dashboard',
+          targets: { systems: [] }
+        },
+        sales: {
+          type: 'group',
+          order: 20,
+          label: 'Sales',
+          children: {
+            crm: {
+              type: 'surface',
+              order: 10,
+              label: 'CRM',
+              path: '/crm',
+              surfaceType: 'page',
+              targets: { systems: ['sales.crm'] }
+            },
+            leadGen: {
+              type: 'surface',
+              order: 20,
+              label: 'Lead Gen',
+              path: '/lead-gen',
+              surfaceType: 'list',
+              targets: { systems: ['sales.lead-gen'] }
+            }
+          }
+        }
+      },
+      bottom: {}
+    }
   }
 })
 
 // ---------------------------------------------------------------------------
-// Prospecting customization
+// System-local settings
 // ---------------------------------------------------------------------------
-export const prospectingCustomizationExample = defineOrganizationModel({
-  prospecting: {
-    listEntityId: 'leadgen.list',
-    companyEntityId: 'leadgen.company',
-    contactEntityId: 'leadgen.contact',
-    companyStages: [
-      { id: 'scraped', label: 'Scraped', order: 1 },
-      { id: 'enriched', label: 'Enriched', order: 2 },
-      { id: 'approved', label: 'Approved', order: 3 }
-    ],
-    contactStages: [
-      { id: 'found', label: 'Found', order: 1 },
-      { id: 'verified', label: 'Verified', order: 2 },
-      { id: 'ready', label: 'Ready', order: 3 }
-    ]
+export const systemConfigExample = defineOrganizationModel({
+  systems: {
+    projects: {
+      id: 'projects',
+      label: 'Projects',
+      order: 40,
+      lifecycle: 'active',
+      config: {
+        defaultPriority: 'normal',
+        reviewCadenceDays: 7,
+        requiresOwner: true
+      }
+    }
   }
 })
 
@@ -172,10 +218,24 @@ export const workflowResourceDescriptorsExample = defineResources({
   leadEnrichment: {
     id: 'lead-enrichment-workflow',
     kind: 'workflow',
-    systemId: 'sys.prospecting',
+    systemPath: 'sales.lead-gen',
     ownerRoleId: 'role-ops-lead',
-    capabilityKey: 'prospecting.lead-enrichment',
-    status: 'active' as const
+    actionKey: 'prospecting.lead-enrichment',
+    status: 'active' as const,
+    ontology: {
+      implements: ['sales.lead-gen:action/lead.enrich'],
+      reads: ['sales.lead-gen:object/lead'],
+      writes: ['sales.crm:object/deal'],
+      usesCatalogs: ['sales.crm:catalog/pipeline'],
+      emits: ['sales.lead-gen:event/lead-enriched']
+    },
+    codeRefs: [
+      {
+        path: 'operations/src/lead-enrichment/index.ts',
+        role: 'entrypoint',
+        symbol: 'leadEnrichmentWorkflow'
+      }
+    ]
   }
 })
 
@@ -186,11 +246,14 @@ export const workflowResourceRuntimeMetadataExample = {
   type: workflowResourceDescriptorsExample.leadEnrichment.kind,
   version: '1.0.0',
   status: 'prod' as const,
+  category: 'production' as const
+}
+
+export const compatibilityGraphLinksExample = {
   links: [
-    { nodeId: 'feature:sales.lead-gen', kind: 'operates-on' as const },
+    { nodeId: 'system:sales.lead-gen', kind: 'operates-on' as const },
     { nodeId: 'integration:instantly', kind: 'uses' as const }
-  ],
-  category: 'production' as const
+  ]
 }
 
 // ---------------------------------------------------------------------------
@@ -247,7 +310,7 @@ export const knowledgeExample = defineOrganizationModel({
         title: 'Example Outreach Playbook',
         summary: 'Step-by-step runbook for launching a cold outreach campaign.',
         body: '## Overview\n\nThis playbook walks through prospect sourcing, message templates, scheduling, and reply triage.\n\n## Steps\n\n1. Source prospects from the lead-gen list.\n2. Personalize the cold email template.\n3. Schedule the sending campaign.\n4. Triage replies in the CRM.',
-        links: [{ nodeId: 'feature:sales.crm' }, { nodeId: 'feature:sales.lead-gen' }],
+        links: [{ nodeId: 'system:sales.crm' }, { nodeId: 'system:sales.lead-gen' }],
         ownerIds: [],
         updatedAt: '2026-05-01'
       },
@@ -257,7 +320,7 @@ export const knowledgeExample = defineOrganizationModel({
         title: 'Example ICP Strategy',
         summary: 'Describes the ideal customer profile and qualification thresholds.',
         body: '## ICP Profile\n\n- **Industry:** SMB marketing agencies\n- **Size:** 5-50 employees\n- **Region:** North America\n\nProspects scoring \\<60 are excluded from outreach.',
-        links: [{ nodeId: 'feature:sales' }],
+        links: [{ nodeId: 'system:sales' }],
         ownerIds: [],
         updatedAt: '2026-05-01'
       },
@@ -265,8 +328,8 @@ export const knowledgeExample = defineOrganizationModel({
         id: 'knowledge.example-org-model-reference',
         kind: 'reference',
         title: 'Example Organization Model Reference',
-        summary: 'Glossary of OM domains and how they relate to features and resources.',
-        body: '## Domains\n\nThe organization model splits configuration into typed domains: identity, customers, offerings, roles, goals, techStack, features, statuses, operations, knowledge.',
+        summary: 'Glossary of OM domains and how they relate to systems and resources.',
+        body: '## Domains\n\nThe organization model separates semantic contracts in ontology, system-local settings in config, executable governance in resources, and explanatory material in knowledge. Secrets and runtime state stay outside the Organization Model.',
         links: [],
         ownerIds: [],
         updatedAt: '2026-05-01'

package/reference/framework/agent.mdx

@@ -1,156 +1,156 @@
----
-title: Agent System
-description: CLAUDE.md drives all agent behavior -- project instructions, slash commands, memory-based developer profile, and three-tier adaptive guidance
-loadWhen: "Configuring agent behavior or capabilities"
----
-
-The agent system is the set of files that shape how Claude Code behaves in your SDK project. It consists of four parts: `CLAUDE.md` (the instruction file), slash commands (structured task entry points), the developer profile stored in `memory/profile/`, and the adaptive guidance rules that translate profile data into concrete agent behavior.
-
-Nothing here requires configuration. The agent reads these files at session start and adapts automatically.
-
-## CLAUDE.md
-
-`CLAUDE.md` is the project instruction file for Claude Code. It is read at the start of every session and governs all agent behavior. In an Elevasis SDK project, it is generated by `elevasis-sdk init` and lives at the project root.
-
-The file is instruction-driven by design. Non-technical developers should never need to edit it. When the agent learns a new rule worth preserving -- such as an error pattern that recurs three times -- it promotes that rule into `CLAUDE.md` automatically.
-
-### Sections
-
-The generated `CLAUDE.md` contains these sections:
-
-- **Session Initialization** -- Checks the `<!-- initialized: false -->` auto-init flag; if false, runs `/meta init` automatically. Otherwise reads `memory/profile/skills.md` for adaptive behavior, reads `memory/index.md` for project context, checks if the template version is current, and suggests `/tutorial` for users with no Platform Navigation experience.
-- **Identity** -- Project orientation: what an Elevasis SDK project is, the developer's role, and how to adapt to non-technical users.
-- **Navigation** -- A table mapping concepts to file paths with load conditions (when to load each file). Includes SDK reference docs, credential model, error history, `docs/project-map.mdx`, and `docs/priorities.mdx`.
-- **Rules** -- Points to auto-loaded rule files in `.claude/rules/`. SDK patterns load automatically; project-specific patterns live in `workspace-patterns.md`. Includes error handling protocol.
-- **Interaction Guidance** -- Per-dimension behavior rules derived from `memory/profile/skills.md`. Covers vocabulary, code completeness, explanation depth, and growth logging.
-- **Commands** -- Table of the 4 slash commands (`/meta`, `/docs`, `/work`, `/tutorial`) with one-line purpose descriptions.
-- **Skills** -- Auto-trigger conditions for the `creds` skill.
-- **Maintaining Memory** -- Hierarchical structure, pruning rules, and what belongs in memory vs. `docs/` vs. `.claude/rules/`.
-
-### Session Initialization
-
-At the start of every session the agent runs these steps silently before responding:
-
-0. Check the `<!-- initialized: ... -->` flag at the top of `CLAUDE.md`. If `false`, run the `/meta init` flow automatically. If `true`, proceed with steps below.
-1. Read `.claude/memory/profile/skills.md` -- adapt all responses to the user's assessed skill levels (see Interaction Guidance below).
-2. Read `.claude/memory/index.md` if it exists -- drill into relevant topic files as needed, balancing context relevance against token usage.
-3. Check the installed `@elevasis/sdk` template version against `templateVersion` in `elevasis.config.ts`. If the SDK has a newer version, notify the user and suggest running `/meta fix`.
-4. If `.claude/memory/` does not exist, suggest running `/meta init` to set up the project.
-5. If the user's Platform Navigation level is none (from skills.md) and `.claude/memory/tutorial-progress.md` does not exist, suggest `/tutorial`.
-
-## Slash Commands
-
-Skills are Markdown instruction files in `.claude/skills/`. When you type `/skill-name` in a Claude Code session, the agent reads the corresponding `SKILL.md` and follows its instructions.
-
-The following skills are scaffolded by `elevasis-sdk init` and committed to version control so collaborators get the same experience:
-
-| Skill       | File                       | Purpose                                                  |
-| ----------- | -------------------------- | -------------------------------------------------------- |
-| `/work`     | `skills/work/SKILL.md`     | Task tracking -- list, create, save, resume, complete    |
-| `/elevasis` | `skills/elevasis/SKILL.md` | SDK operations -- check, deploy, exec                    |
-| `/deploy`   | `skills/deploy/skill.md`   | Full deploy pipeline (test, build, commit, push)         |
-| `/setup`    | `skills/setup/SKILL.md`    | First-time project setup (placeholder replacement, deps) |
-| `/status`   | `skills/status/SKILL.md`   | Quick project health check                               |
-| `/continue` | `skills/continue/SKILL.md` | Resume in-progress work from docs                        |
-| `/project`  | `skills/project/SKILL.md`  | Route project management to `elevasis-sdk project:*`     |
-| `/sync`     | `skills/sync/SKILL.md`     | Pull latest, wipe caches, fresh reinstall                |
-| `/explore`  | `skills/explore/SKILL.md`  | Codebase exploration anchored to docs                    |
-| `/save`     | `skills/save/SKILL.md`     | Auto-manage docs from conversation context               |
-| `/dsp`      | `skills/dsp/SKILL.md`      | Parallel agent dispatch for implementation tasks         |
-
-### Key Skills
-
-**`/setup`** -- First-time project setup. Replaces template placeholders, installs dependencies, configures `.env`, verifies the project, and optionally runs a first deploy.
-
-**`/deploy`** -- Full deploy pipeline: type-check, validate resources, commit, deploy (auto-regenerates `docs/index.md` and `docs/resources.md`), verify platform, and optionally push.
-
-**`/elevasis`** -- SDK operations entry point: `check` validates resource definitions, `deploy` bundles and uploads, `exec` runs a resource with input.
-
-**`/work`** -- File-based task lifecycle. Creates, resumes, saves, and completes task docs in `docs/in-progress/`. It tracks in-progress work state, not project records.
-
-**`/status`** -- Quick project health check: shows SDK version, deployed resources, last deploy date, and environment status.
-
-**`/save`** -- Auto-manages docs from conversation context: writes or updates docs based on what was discussed in the session.
-
-**`/explore`** -- Codebase exploration anchored to `docs/`. Reads the doc map first, then drills into source as needed.
-
-**`/continue`** -- Resumes in-progress work by reading `docs/in-progress/` and picking up where the last session left off.
-
-**`/project`** -- Project-management routing for milestones, tasks, notes, and status. It should call the canonical `elevasis-sdk project:*` CLI surface rather than inventing a parallel workflow.
-
-That routing is interface-first, not a separate semantic model. `/project` should treat the SDK CLI as the operational entrypoint for the Organization OS delivery/projects contract: `deliveryManifest` in the shared UI, `featureId: 'projects'` in the organization model, and `organizationModel.delivery` for project/milestone/task status semantics.
-
-When these command families overlap conceptually, use this boundary:
-
-- `/project` -- update or inspect project data in the shared Projects system
-- `/work` -- capture implementation progress and resume context in docs
-- `/adev` -- build, debug, test, or execute resources
-
-**`/dsp`** -- Dispatches subagents in parallel for implementation tasks that can run concurrently.
-
-**`/sync`** -- Pulls latest changes, wipes all `node_modules` and caches, and runs a fresh reinstall.
-
-## Developer Profile
-
-The developer profile is stored in `.claude/memory/profile/` as a set of markdown files. It is gitignored -- personal to each developer, not shared with collaborators. Profile data lives in the memory system alongside error patterns, deployment state, and decisions.
-
-### Onboarding Flow
-
-Profile data is created during `/meta init`. The command runs a 6-question assessment and writes the responses to `memory/profile/`:
-
-- **Identity & Goals (3 questions):** What the business does, what to automate, which tools are already in use.
-- **Competency (2 questions):** Command Center familiarity (maps to `platformNavigation`), automation tool familiarity (maps to `automation`). Two additional dimensions (`apiIntegration`, `domainExpertise`) are inferred from these answers.
-- **Communication (1 question):** Step-by-step explanations vs. concise answers.
-
-### Profile Structure
-
-```
-.claude/memory/profile/
-├── index.md          # Profile summary with links to sub-files
-├── identity.md       # Organization, industry, goals, integrations
-├── skills.md         # Skill dimensions (platformNavigation, apiIntegration, automation, domainExpertise)
-└── preferences.md    # Verbosity, guidance style, interaction patterns
-```
-
-`identity.md` records the organization name, industry, size, project goals, and known tool integrations. `skills.md` stores four skill dimensions as structured values (`platformNavigation`, `apiIntegration`, `automation`, `domainExpertise`) along with a Growth Log table. See [Interaction Guidance](interaction-guidance.mdx) for the full set of per-dimension adaptation rules. `preferences.md` stores verbosity (`detailed / concise`) and proactive guidance preference.
-
-### Auto-Update Triggers
-
-The agent updates `memory/profile/` files when it observes:
-
-- The user successfully completes an advanced task (level upgrade candidate in `skills.md`)
-- The user mentions new tools or integrations not in `identity.md`
-- The user explicitly asks to change preferences
-
-The agent does not prompt for confirmation on minor updates. Major changes (level upgrades) are surfaced to the user before writing.
-
-## Rules System
-
-Ten rule files are scaffolded in `.claude/rules/`. Rule files are auto-injected by Claude Code when their path patterns match the current file being edited -- no manual loading needed.
-
-Rules injected for operations source files (`operations/src/`):
-
-- **`platform.md`** -- SDK adapter patterns, typed adapters, platform tool usage.
-- **`error-handling.md`** -- Error types (`ExecutionError`, `PlatformToolError`), retry behavior.
-- **`execution.md`** -- Worker thread model, timeouts, concurrency, org isolation.
-- **`observability.md`** -- Logging with `context.logger`, step-level auto-logging, debugging.
-- **`deployment.md`** -- Deploy commands, dev vs prod, version bumping, common errors.
-
-Rules injected for docs files (`docs/`):
-
-- **`docs.md`** -- Documentation structure, frontmatter conventions, auto-generated files.
-- **`task-tracking.md`** -- Task doc conventions, injected for in-progress files.
-
-Additional contextual rules:
-
-- **`frontend.md`** -- React/Mantine patterns, injected for UI source files.
-- **`shared-types.md`** -- Cross-runtime type conventions, injected for foundations files.
-- **`organization-os.md`** -- Organization model and feature shell conventions.
-
-## Interaction Guidance
-
-The `CLAUDE.md` Interaction Guidance section translates skill dimensions from `memory/profile/skills.md` into concrete behavior rules -- adapting vocabulary, code completeness, explanation depth, and growth logging per dimension. For the full set of per-dimension adaptation rules, see [Interaction Guidance](interaction-guidance.mdx).
-
----
-
-**Last Updated:** 2026-04-17
+---
+title: Agent System
+description: CLAUDE.md drives all agent behavior -- project instructions, slash commands, memory-based developer profile, and three-tier adaptive guidance
+loadWhen: "Configuring agent behavior or capabilities"
+---
+
+The agent system is the set of files that shape how Claude Code behaves in your SDK project. It consists of four parts: `CLAUDE.md` (the instruction file), slash commands (structured task entry points), the developer profile stored in `memory/profile/`, and the adaptive guidance rules that translate profile data into concrete agent behavior.
+
+Nothing here requires configuration. The agent reads these files at session start and adapts automatically.
+
+## CLAUDE.md
+
+`CLAUDE.md` is the project instruction file for Claude Code. It is read at the start of every session and governs all agent behavior. In an Elevasis SDK project, it is generated by `elevasis-sdk init` and lives at the project root.
+
+The file is instruction-driven by design. Non-technical developers should never need to edit it. When the agent learns a new rule worth preserving -- such as an error pattern that recurs three times -- it promotes that rule into `CLAUDE.md` automatically.
+
+### Sections
+
+The generated `CLAUDE.md` contains these sections:
+
+- **Session Initialization** -- Checks the `<!-- initialized: false -->` auto-init flag; if false, runs `/meta init` automatically. Otherwise reads `memory/profile/skills.md` for adaptive behavior, reads `memory/index.md` for project context, checks if the template version is current, and suggests `/tutorial` for users with no Platform Navigation experience.
+- **Identity** -- Project orientation: what an Elevasis SDK project is, the developer's role, and how to adapt to non-technical users.
+- **Navigation** -- A table mapping concepts to file paths with load conditions (when to load each file). Includes SDK reference docs, credential model, error history, `docs/project-map.mdx`, and `docs/priorities.mdx`.
+- **Rules** -- Points to auto-loaded rule files in `.claude/rules/`. SDK patterns load automatically; project-specific patterns live in `workspace-patterns.md`. Includes error handling protocol.
+- **Interaction Guidance** -- Per-dimension behavior rules derived from `memory/profile/skills.md`. Covers vocabulary, code completeness, explanation depth, and growth logging.
+- **Commands** -- Table of the 4 slash commands (`/meta`, `/docs`, `/work`, `/tutorial`) with one-line purpose descriptions.
+- **Skills** -- Auto-trigger conditions for the `creds` skill.
+- **Maintaining Memory** -- Hierarchical structure, pruning rules, and what belongs in memory vs. `docs/` vs. `.claude/rules/`.
+
+### Session Initialization
+
+At the start of every session the agent runs these steps silently before responding:
+
+0. Check the `<!-- initialized: ... -->` flag at the top of `CLAUDE.md`. If `false`, run the `/meta init` flow automatically. If `true`, proceed with steps below.
+1. Read `.claude/memory/profile/skills.md` -- adapt all responses to the user's assessed skill levels (see Interaction Guidance below).
+2. Read `.claude/memory/index.md` if it exists -- drill into relevant topic files as needed, balancing context relevance against token usage.
+3. Check the installed `@elevasis/sdk` template version against `templateVersion` in `elevasis.config.ts`. If the SDK has a newer version, notify the user and suggest running `/meta fix`.
+4. If `.claude/memory/` does not exist, suggest running `/meta init` to set up the project.
+5. If the user's Platform Navigation level is none (from skills.md) and `.claude/memory/tutorial-progress.md` does not exist, suggest `/tutorial`.
+
+## Slash Commands
+
+Skills are Markdown instruction files in `.claude/skills/`. When you type `/skill-name` in a Claude Code session, the agent reads the corresponding `SKILL.md` and follows its instructions.
+
+The following skills are scaffolded by `elevasis-sdk init` and committed to version control so collaborators get the same experience:
+
+| Skill       | File                       | Purpose                                                  |
+| ----------- | -------------------------- | -------------------------------------------------------- |
+| `/work`     | `skills/work/SKILL.md`     | Task tracking -- list, create, save, resume, complete    |
+| `/elevasis` | `skills/elevasis/SKILL.md` | SDK operations -- check, deploy, exec                    |
+| `/deploy`   | `skills/deploy/skill.md`   | Full deploy pipeline (test, build, commit, push)         |
+| `/setup`    | `skills/setup/SKILL.md`    | First-time project setup (placeholder replacement, deps) |
+| `/status`   | `skills/status/SKILL.md`   | Quick project health check                               |
+| `/continue` | `skills/continue/SKILL.md` | Resume in-progress work from docs                        |
+| `/project`  | `skills/project/SKILL.md`  | Route project management to `elevasis-sdk project:*`     |
+| `/sync`     | `skills/sync/SKILL.md`     | Pull latest, wipe caches, fresh reinstall                |
+| `/explore`  | `skills/explore/SKILL.md`  | Codebase exploration anchored to docs                    |
+| `/save`     | `skills/save/SKILL.md`     | Auto-manage docs from conversation context               |
+| `/dsp`      | `skills/dsp/SKILL.md`      | Parallel agent dispatch for implementation tasks         |
+
+### Key Skills
+
+**`/setup`** -- First-time project setup. Replaces template placeholders, installs dependencies, configures `.env`, verifies the project, and optionally runs a first deploy.
+
+**`/deploy`** -- Full deploy pipeline: type-check, validate resources, commit, deploy (auto-regenerates `docs/index.md` and `docs/resources.md`), verify platform, and optionally push.
+
+**`/elevasis`** -- SDK operations entry point: `check` validates resource definitions, `deploy` bundles and uploads, `exec` runs a resource with input.
+
+**`/work`** -- File-based task lifecycle. Creates, resumes, saves, and completes task docs in `docs/in-progress/`. It tracks in-progress work state, not project records.
+
+**`/status`** -- Quick project health check: shows SDK version, deployed resources, last deploy date, and environment status.
+
+**`/save`** -- Auto-manages docs from conversation context: writes or updates docs based on what was discussed in the session.
+
+**`/explore`** -- Codebase exploration anchored to `docs/`. Reads the doc map first, then drills into source as needed.
+
+**`/continue`** -- Resumes in-progress work by reading `docs/in-progress/` and picking up where the last session left off.
+
+**`/project`** -- Project-management routing for milestones, tasks, notes, and status. It should call the canonical `elevasis-sdk project:*` CLI surface rather than inventing a parallel workflow.
+
+That routing is interface-first, not a separate semantic model. `/project` should treat the SDK CLI as the operational entrypoint for the Organization OS delivery/projects contract: `deliveryManifest` in the shared UI, `featureId: 'projects'` in the organization model, and `organizationModel.delivery` for project/milestone/task status semantics.
+
+When these command families overlap conceptually, use this boundary:
+
+- `/project` -- update or inspect project data in the shared Projects system
+- `/work` -- capture implementation progress and resume context in docs
+- `/adev` -- build, debug, test, or execute resources
+
+**`/dsp`** -- Dispatches subagents in parallel for implementation tasks that can run concurrently.
+
+**`/sync`** -- Pulls latest changes, wipes all `node_modules` and caches, and runs a fresh reinstall.
+
+## Developer Profile
+
+The developer profile is stored in `.claude/memory/profile/` as a set of markdown files. It is gitignored -- personal to each developer, not shared with collaborators. Profile data lives in the memory system alongside error patterns, deployment state, and decisions.
+
+### Onboarding Flow
+
+Profile data is created during `/meta init`. The command runs a 6-question assessment and writes the responses to `memory/profile/`:
+
+- **Identity & Goals (3 questions):** What the business does, what to automate, which tools are already in use.
+- **Competency (2 questions):** Command Center familiarity (maps to `platformNavigation`), automation tool familiarity (maps to `automation`). Two additional dimensions (`apiIntegration`, `domainExpertise`) are inferred from these answers.
+- **Communication (1 question):** Step-by-step explanations vs. concise answers.
+
+### Profile Structure
+
+```
+.claude/memory/profile/
+├── index.md          # Profile summary with links to sub-files
+├── identity.md       # Organization, industry, goals, integrations
+├── skills.md         # Skill dimensions (platformNavigation, apiIntegration, automation, domainExpertise)
+└── preferences.md    # Verbosity, guidance style, interaction patterns
+```
+
+`identity.md` records the organization name, industry, size, project goals, and known tool integrations. `skills.md` stores four skill dimensions as structured values (`platformNavigation`, `apiIntegration`, `automation`, `domainExpertise`) along with a Growth Log table. See [Interaction Guidance](interaction-guidance.mdx) for the full set of per-dimension adaptation rules. `preferences.md` stores verbosity (`detailed / concise`) and proactive guidance preference.
+
+### Auto-Update Triggers
+
+The agent updates `memory/profile/` files when it observes:
+
+- The user successfully completes an advanced task (level upgrade candidate in `skills.md`)
+- The user mentions new tools or integrations not in `identity.md`
+- The user explicitly asks to change preferences
+
+The agent does not prompt for confirmation on minor updates. Major changes (level upgrades) are surfaced to the user before writing.
+
+## Rules System
+
+Ten rule files are scaffolded in `.claude/rules/`. Rule files are auto-injected by Claude Code when their path patterns match the current file being edited -- no manual loading needed.
+
+Rules injected for operations source files (`operations/src/`):
+
+- **`platform.md`** -- SDK adapter patterns, typed adapters, platform tool usage.
+- **`error-handling.md`** -- Error types (`ExecutionError`, `PlatformToolError`), retry behavior.
+- **`execution.md`** -- Worker thread model, timeouts, concurrency, org isolation.
+- **`observability.md`** -- Logging with `context.logger`, step-level auto-logging, debugging.
+- **`deployment.md`** -- Deploy commands, dev vs prod, version bumping, common errors.
+
+Rules injected for docs files (`docs/`):
+
+- **`docs.md`** -- Documentation structure, frontmatter conventions, auto-generated files.
+- **`task-tracking.md`** -- Task doc conventions, injected for in-progress files.
+
+Additional contextual rules:
+
+- **`frontend.md`** -- React/Mantine patterns, injected for UI source files.
+- **`shared-types.md`** -- Cross-runtime type conventions, injected for foundations files.
+- **`organization-os.md`** -- Organization model and feature shell conventions.
+
+## Interaction Guidance
+
+The `CLAUDE.md` Interaction Guidance section translates skill dimensions from `memory/profile/skills.md` into concrete behavior rules -- adapting vocabulary, code completeness, explanation depth, and growth logging per dimension. For the full set of per-dimension adaptation rules, see [Interaction Guidance](interaction-guidance.mdx).
+
+---
+
+**Last Updated:** 2026-04-17