@elevasis/sdk 1.5.2 → 1.5.4

package/reference/claude-config/skills/sync/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: sync
+description: Pull latest changes, wipe all node_modules and caches, fresh reinstall
+---
+
+# Sync
+
+Pull latest changes, wipe all stale packages and caches, fresh reinstall.
+
+**Usage:** `/sync`
+
+Use this when: packages feel stale, Vite cache is serving old code, `pnpm install` didn't fully clean up after a package version bump, or after pulling a branch with dependency changes.
+
+## Process
+
+### Step 1: Check for Uncommitted Changes
+
+```bash
+git status --short
+```
+
+If there are uncommitted changes (modified, staged, or untracked files), ask the user:
+
+```
+You have uncommitted changes:
+<git status --short output>
+
+Commit and push before syncing? (yes/no)
+```
+
+- **Yes** — ask for a commit message (or auto-generate one from the diff), then:
+  ```bash
+  git add -A
+  git commit -m "<message>"
+  git push
+  ```
+  If commit or push fails, stop and report the error.
+- **No** — stop and let the user decide:
+  ```
+  Sync cancelled. Commit, stash, or discard your changes, then re-run /sync.
+  ```
+
+### Step 2: Pull
+
+```bash
+git pull
+```
+
+Report any merge conflicts and stop.
+
+### Step 3: Wipe
+
+Remove all `node_modules` and build caches across the workspace in parallel:
+
+```bash
+rm -rf node_modules
+rm -rf ui/node_modules
+rm -rf ui/node_modules/.vite
+rm -rf operations/node_modules
+rm -rf shared/node_modules
+```
+
+### Step 4: Reinstall
+
+```bash
+pnpm install
+```
+
+Report success or any errors.
+
+### Step 5: Report
+
+```
+Sync Complete
+=============
+Git:     pulled (<branch>)
+Wiped:   node_modules (root, ui, operations, shared) + Vite cache
+Install: success
+```
+
+If `pnpm install` fails, report the error and stop — do not attempt to start the dev server.

package/reference/cli.mdx

@@ -1,10 +1,10 @@
 ---
 title: CLI Reference
-description: Full reference for every elevasis-sdk CLI command -- validate, deploy, execute, inspect resources, and operate project-management surfaces
+description: Full reference for every elevasis-sdk CLI command -- validate, deploy, execute, inspect resources, and manage Projects through the canonical SDK CLI surface
 loadWhen: "Running CLI operations"
 ---
 
-The `elevasis-sdk` CLI is the primary interface for working with your Elevasis SDK project. Install it as part of `@elevasis/sdk` and use it to validate resource definitions, deploy to the platform, inspect execution history, and work with the shared project-management API surfaces.
+The `elevasis-sdk` CLI is the primary interface for working with your Elevasis SDK project. Install it as part of `@elevasis/sdk` and use it to validate resource definitions, deploy to the platform, inspect execution history, and manage Projects through `project:*`.
 
 **Installation:**
 
@@ -402,23 +402,23 @@ elevasis-sdk describe onboard-client
 
 ---
 
-## elevasis-sdk env
+## elevasis-sdk creds
 
-Manage environment variables for your project.
+Manage credentials for your project.
 
 **Synopsis:**
 
 ```
-elevasis-sdk env list
-elevasis-sdk env set <key> <value>
-elevasis-sdk env remove <key>
+elevasis-sdk creds list
+elevasis-sdk creds set <key> <value>
+elevasis-sdk creds remove <key>
 ```
 
 **Behavior:**
 
-- `list` -- display all environment variables configured for the project
-- `set` -- add or update an environment variable
-- `remove` -- delete an environment variable
+- `list` -- display all credentials configured for the project
+- `set` -- add or update a credential
+- `remove` -- delete a credential
 
 **Flags:**
 
@@ -429,9 +429,9 @@ elevasis-sdk env remove <key>
 **Examples:**
 
 ```bash
-elevasis-sdk env list
-elevasis-sdk env set OPENAI_API_KEY sk-proj-***
-elevasis-sdk env remove OPENAI_API_KEY
+elevasis-sdk creds list
+elevasis-sdk creds set OPENAI_API_KEY sk-proj-***
+elevasis-sdk creds remove OPENAI_API_KEY
 ```
 
 ---
@@ -503,9 +503,17 @@ elevasis-sdk rename ist-upload-workflow --to ist-upload-contacts-workflow --exec
 
 ---
 
-## elevasis-sdk project:*
+## elevasis-sdk project:\*
 
-Project-management commands operate on the shared delivery system used by packaged Projects pages and task-oriented agent workflows.
+`elevasis-sdk project:*` is the canonical project-management surface. Use it for project, milestone, task, and note operations whether the caller is a human, a scripted workflow, or a slash-command router like `/project`.
+
+This CLI family is SDK-first, but it is not semantically standalone. It operates on the same Organization OS contract that the shared delivery UI uses:
+
+- UI manifest key: `delivery`
+- Organization model feature ID: `projects`
+- Default surface: `projects.index`
+- Semantic domain fields: `organizationModel.delivery`
+- Core entity/capability IDs: `delivery.project`, `delivery.milestone`, `delivery.task`, `delivery.projects.view`
 
 ### Projects
 
@@ -566,13 +574,20 @@ elevasis-sdk project:note:delete <id>
 
 Most `project:*` commands support:
 
-| Flag | Description |
-| ---- | ----------- |
-| `--pretty` | Human-readable terminal output instead of raw JSON |
-| `--api-url <url>` | Override the API base URL |
+| Flag              | Description                                        |
+| ----------------- | -------------------------------------------------- |
+| `--pretty`        | Human-readable terminal output instead of raw JSON |
+| `--api-url <url>` | Override the API base URL                          |
 
 For exact required flags and accepted enum values, see the command source under `packages/sdk/src/cli/commands/project/`.
 
+### Command Boundary
+
+- `/project` is a convenience router to these `elevasis-sdk project:*` commands. It is not a separate project system.
+- `/work` is for docs-backed in-progress task tracking and session resume, not project CRUD.
+- `/external` is for managing standalone apps in `external/`, not project records inside a deployed system.
+- `/adev` is for implementation, debugging, testing, and platform execution flows. Use it when you need to build or run agent/workflow code rather than update project data.
+
 ---
 
 ## Global Flags
@@ -593,4 +608,4 @@ These flags are accepted by all commands:
 
 ---
 
-**Last Updated:** 2026-04-15
+**Last Updated:** 2026-04-17

package/reference/deployment/index.mdx

@@ -37,7 +37,8 @@ elevasis-sdk deploy
   Uploading...               done
 
   Deployed! 4 resources live.
-  Deployment: deploy_abc123
+  Version:  v1.0.0
+  Duration: 4.2s
 ```
 
 Each deploy creates a new deployment record. The previous active deployment is automatically stopped. You can view all deployments with `elevasis-sdk deployments`.
@@ -62,9 +63,8 @@ The CLI validates your resources before bundling. Validation uses the same `Reso
   Authenticating...          done (acme-corp)
   Validating...
     ERROR  Duplicate resource ID 'onboard-client' in organization 'Acme Corp'
-    ERROR  Workflow step 'send-email' references non-existent next step 'notify'
 
-  2 errors. Deploy aborted.
+  Deploy aborted.
 ```
 
 Run `elevasis-sdk check` at any time to validate without deploying.
@@ -98,8 +98,9 @@ The CLI also accepts a `--api-url` flag on every command, which takes priority o
 **API URL resolution order:**
 
 1. `--api-url` flag (highest priority)
-2. `ELEVASIS_API_URL` environment variable
-3. `NODE_ENV`-based default (production: `https://api.elevasis.io`, development: localhost)
+2. `--prod` flag (forces production URL, overrides `NODE_ENV=development`)
+3. `ELEVASIS_API_URL` environment variable
+4. `NODE_ENV`-based default (production: `https://api.elevasis.io`, development: localhost)
 
 **Setting `ELEVASIS_PLATFORM_KEY` via `.env` file:**
 

package/reference/deployment/provided-features.mdx

@@ -4,7 +4,7 @@ description: Shared UI and API surfaces for packaged business systems like Lead
 loadWhen: "Building against packaged app features, list-oriented lead gen, CRM, or project-management surfaces"
 ---
 
-The SDK now covers more than raw workflow execution. The published `@elevasis/ui@2.7.0` package includes:
+The SDK now covers more than raw workflow execution. The published `@elevasis/ui@2.9.0` package includes:
 
 - manifest-backed shared features under `@elevasis/ui/features/<name>`
 - headless shell/provider exports under `@elevasis/ui/provider`
@@ -16,7 +16,7 @@ Use this page to understand what the shared shell actually owns, which surfaces
 
 ## Shared Shell Contract
 
-`ElevasisFeaturesProvider` and `FeatureShell` give you a shared manifest-driven shell layer, not a full application shell. In `2.7.0` they handle:
+`ElevasisFeaturesProvider` and `FeatureShell` give you a shared manifest-driven shell layer, not a full application shell. In `2.9.0` they handle:
 
 - feature registration
 - feature-gated nav contribution
@@ -79,27 +79,27 @@ Dashboard is not part of that shared manifest shell by default. `@elevasis/ui/fe
 
 ## Contract Matrix
 
-This is the published contract split in `@elevasis/ui@2.7.0`:
+This is the published contract split in `@elevasis/ui@2.9.0`:
 
-| Contract type | What is published | Current examples |
-| ------------- | ----------------- | ---------------- |
-| Manifest-backed shared subshell features | Feature manifest plus shared sidebar/pages, mounted through `@elevasis/ui/provider` | Lead Gen, CRM, Projects, Operations, SEO |
-| Manifest-backed nav/app sections | Feature manifest contributes gated nav and route metadata, but the host still owns the route pages or shell chrome | Monitoring, Settings |
-| Exported compatibility components | Reusable components exported without a manifest-backed shell contract | Dashboard components such as `Dashboard`, `OperationsOverview`, `ResourceOverview`, `RecentExecutionsByResource`, `UnresolvedErrorsTeaser` |
-| Compatibility barrel | Existing imports remain available from `@elevasis/ui/components`, but new host integrations should prefer feature/provider subpaths | Manifests, sidebars, and page components re-exported for compatibility |
+| Contract type                            | What is published                                                                                                                   | Current examples                                                                                                                           |
+| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| Manifest-backed shared subshell features | Feature manifest plus shared sidebar/pages, mounted through `@elevasis/ui/provider`                                                 | Lead Gen, CRM, Projects, Operations, SEO                                                                                                   |
+| Manifest-backed nav/app sections         | Feature manifest contributes gated nav and route metadata, but the host still owns the route pages or shell chrome                  | Monitoring, Settings                                                                                                                       |
+| Exported compatibility components        | Reusable components exported without a manifest-backed shell contract                                                               | Dashboard components such as `Dashboard`, `OperationsOverview`, `ResourceOverview`, `RecentExecutionsByResource`, `UnresolvedErrorsTeaser` |
+| Compatibility barrel                     | Existing imports remain available from `@elevasis/ui/components`, but new host integrations should prefer feature/provider subpaths | Manifests, sidebars, and page components re-exported for compatibility                                                                     |
 
-Projects is currently the only packaged system with a first-class `elevasis-sdk project:*` CLI family. Lead Gen and CRM are still primarily UI + API + workflow/runtime surfaces, and browser-facing interactions remain REST-driven even when runtime tools exist.
+Projects is currently the only packaged system with a first-class `elevasis-sdk project:*` CLI family. Treat that CLI family as the canonical project-management path. Lead Gen and CRM are still primarily UI + API + workflow/runtime surfaces, and browser-facing interactions remain REST-driven even when runtime tools exist.
 
 ## System Map
 
-| System | Primary route space | Shared UI surface | Main data surface | Best SDK entry point |
-| ------ | ------------------- | ----------------- | ----------------- | -------------------- |
-| Lead Gen | `/lead-gen/*` | Lead Gen pages, sidebars, list detail page, run dialogs | Acquisition list APIs + list/acqDb platform tools | `@elevasis/ui/features/lead-gen`, `@elevasis/ui/hooks`, `@elevasis/sdk/worker` |
-| CRM | `/crm/*` | CRM sidebar, overview widgets, deal/detail pages, workbench panels | Deal APIs, recent-activity API, acquisition-backed hooks, and the `crm` runtime adapter | `@elevasis/ui/features/crm`, `@elevasis/ui/hooks`, `@elevasis/sdk/worker` |
-| Projects | `/projects/*` | Projects list page, milestones/tasks/notes sidebars and pages | Project, milestone, task, note REST endpoints + CLI | `@elevasis/ui/features/delivery`, `@elevasis/ui/hooks/delivery`, `elevasis-sdk project:*` |
-| Dashboard | host-owned | Dashboard and overview components only; no shared manifest-backed nav contract | Host-chosen API composition | `@elevasis/ui/features/dashboard` |
-| Monitoring | `/monitoring/*` | Monitoring nav metadata plus exported pages/components; no shared `FeatureShell` sidebar today | Monitoring REST APIs | `@elevasis/ui/features/monitoring` |
-| Settings | `/settings/*` | Settings nav metadata plus exported settings components; no shared `FeatureShell` sidebar today | Settings/account/org REST APIs | `@elevasis/ui/features/settings` |
+| System     | Primary route space | Shared UI surface                                                                               | Main data surface                                                                       | Best SDK entry point                                                                      |
+| ---------- | ------------------- | ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
+| Lead Gen   | `/lead-gen/*`       | Lead Gen pages, sidebars, list detail page, run dialogs                                         | Acquisition list APIs + list/acqDb platform tools                                       | `@elevasis/ui/features/lead-gen`, `@elevasis/ui/hooks`, `@elevasis/sdk/worker`            |
+| CRM        | `/crm/*`            | CRM sidebar, overview widgets, deal/detail pages, workbench panels                              | Deal APIs, recent-activity API, acquisition-backed hooks, and the `crm` runtime adapter | `@elevasis/ui/features/crm`, `@elevasis/ui/hooks`, `@elevasis/sdk/worker`                 |
+| Projects   | `/projects/*`       | Projects list page, milestones/tasks/notes sidebars and pages                                   | Project, milestone, task, note REST endpoints + CLI                                     | `@elevasis/ui/features/delivery`, `@elevasis/ui/hooks/delivery`, `elevasis-sdk project:*` |
+| Dashboard  | host-owned          | Dashboard and overview components only; no shared manifest-backed nav contract                  | Host-chosen API composition                                                             | `@elevasis/ui/features/dashboard`                                                         |
+| Monitoring | `/monitoring/*`     | Monitoring nav metadata plus exported pages/components; no shared `FeatureShell` sidebar today  | Monitoring REST APIs                                                                    | `@elevasis/ui/features/monitoring`                                                        |
+| Settings   | `/settings/*`       | Settings nav metadata plus exported settings components; no shared `FeatureShell` sidebar today | Settings/account/org REST APIs                                                          | `@elevasis/ui/features/settings`                                                          |
 
 ---
 
@@ -131,17 +131,17 @@ The most important page for downstream agents is `LeadGenListDetailPage`. It com
 
 `@elevasis/ui/hooks` exposes list-aware hooks backed by the acquisition API:
 
-| Hook | HTTP path |
-| ---- | --------- |
-| `useLists()` | `GET /acquisition/lists` |
-| `useList(listId)` | `GET /acquisition/lists/:listId` |
-| `useListsTelemetry()` | `GET /acquisition/lists/telemetry` |
-| `useListProgress(listId)` | `GET /acquisition/lists/:listId/progress` |
-| `useListExecutions(listId)` | `GET /acquisition/lists/:listId/executions` |
-| `useCreateList()` | `POST /acquisition/lists` |
-| `useUpdateList(listId)` | `PATCH /acquisition/lists/:listId` |
-| `useUpdateListConfig(listId)` | `PATCH /acquisition/lists/:listId/config` |
-| `useDeleteList()` | `DELETE /acquisition/lists/:listId` |
+| Hook                          | HTTP path                                   |
+| ----------------------------- | ------------------------------------------- |
+| `useLists()`                  | `GET /acquisition/lists`                    |
+| `useList(listId)`             | `GET /acquisition/lists/:listId`            |
+| `useListsTelemetry()`         | `GET /acquisition/lists/telemetry`          |
+| `useListProgress(listId)`     | `GET /acquisition/lists/:listId/progress`   |
+| `useListExecutions(listId)`   | `GET /acquisition/lists/:listId/executions` |
+| `useCreateList()`             | `POST /acquisition/lists`                   |
+| `useUpdateList(listId)`       | `PATCH /acquisition/lists/:listId`          |
+| `useUpdateListConfig(listId)` | `PATCH /acquisition/lists/:listId/config`   |
+| `useDeleteList()`             | `DELETE /acquisition/lists/:listId`         |
 
 Lead Gen also sits on broader acquisition endpoints for companies and contacts:
 
@@ -233,6 +233,15 @@ That means downstream users can build against CRM with shared UI, API, and runti
 
 Projects is the packaged delivery/project-management system. It has both a shared UI surface and a first-class CLI surface in `elevasis-sdk`, plus a dedicated runtime adapter for workflow and agent use.
 
+Within Organization OS, this packaged system sits on the **delivery** semantic domain but is exposed as the first-class feature ID **`projects`**. In practice that means:
+
+- the published UI manifest is `deliveryManifest`
+- the manifest gates against `featureId: 'projects'`
+- the default navigation surface is `projects.index`
+- the underlying semantic entities and capabilities still use delivery-scoped IDs such as `delivery.project`, `delivery.milestone`, `delivery.task`, and `delivery.projects.view`
+
+Treat `elevasis-sdk project:*` as the operational interface to that same contract, not as a separate project system layered beside Organization OS.
+
 ### Shared UI Surface
 
 `@elevasis/ui/features/delivery` exports:
@@ -247,20 +256,20 @@ Projects is the packaged delivery/project-management system. It has both a share
 
 `@elevasis/ui/hooks/delivery` talks to the project-management API:
 
-| Hook | HTTP path |
-| ---- | --------- |
-| `useProjects()` | `GET /projects` |
-| `useProject(id)` | `GET /projects/:id` |
-| `useTasks({ projectId })` | `GET /projects/:projectId/tasks` |
-| `useMilestones({ projectId })` | `GET /projects/:projectId/milestones` |
-| `useProjectNotes({ projectId })` | `GET /projects/:projectId/notes` |
-| `useCreateTask()` | `POST /project-tasks` |
-| `useUpdateTask()` | `PATCH /project-tasks/:id` |
-| `useCreateNote()` | `POST /project-notes` |
+| Hook                             | HTTP path                             |
+| -------------------------------- | ------------------------------------- |
+| `useProjects()`                  | `GET /projects`                       |
+| `useProject(id)`                 | `GET /projects/:id`                   |
+| `useTasks({ projectId })`        | `GET /projects/:projectId/tasks`      |
+| `useMilestones({ projectId })`   | `GET /projects/:projectId/milestones` |
+| `useProjectNotes({ projectId })` | `GET /projects/:projectId/notes`      |
+| `useCreateTask()`                | `POST /project-tasks`                 |
+| `useUpdateTask()`                | `PATCH /project-tasks/:id`            |
+| `useCreateNote()`                | `POST /project-notes`                 |
 
 ### CLI Surface
 
-The SDK CLI now exposes project-management commands:
+The SDK CLI exposes the canonical project-management commands:
 
 ```bash
 elevasis-sdk project:list
@@ -277,6 +286,19 @@ elevasis-sdk project:task:save <task-id> --current-state "Implemented the API sl
 
 This matters for downstream user agents because project tasks now have a resumable machine-readable surface. `project:task:resume` returns `resume_context`, and `project:task:save` updates it.
 
+For semantic context, the CLI maps onto the same Organization OS contract that drives the shared shell:
+
+- project records correspond to the `projects` feature in the organization model
+- the shared UI route space resolves through `projects.index`
+- status semantics still come from `organizationModel.delivery`, not from a separate CLI-only schema
+
+### Command Boundary
+
+- `/project` should route here. It is a convenience layer over `elevasis-sdk project:*`, not a separate system.
+- `/work` should stay focused on docs-backed task tracking and resume notes.
+- `/external` applies only to standalone apps in `external/`.
+- `/adev` applies when building, testing, debugging, or executing resources, not when managing project records.
+
 ---
 
 ## Choosing The Right Surface

package/reference/deployment/ui-execution.mdx

@@ -88,9 +88,8 @@ import { useState } from 'react'
 import { Modal, Button, Text } from '@mantine/core'
 import { ResourceExecuteForm } from '@elevasis/ui/features/operations'
 import { useExecuteAsync } from '@elevasis/ui/hooks'
-import type { SerializedExecutionFormSchema } from '@elevasis/ui/hooks'
 
-const formSchema: SerializedExecutionFormSchema = {
+const formSchema = {
   fields: [
     { name: 'topic', label: 'Topic', type: 'text', required: true },
   ],

package/reference/framework/agent.mdx

@@ -40,67 +40,55 @@ At the start of every session the agent runs these steps silently before respond
 
 ## Slash Commands
 
-Slash commands are short Markdown instruction files in `.claude/commands/`. When you type `/command-name` in a Claude Code session, the agent reads the corresponding file and follows its instructions.
+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.
 
-Four commands and one skill are scaffolded by `elevasis-sdk init` and committed to version control so collaborators get the same experience:
+The following skills are scaffolded by `elevasis-sdk init` and committed to version control so collaborators get the same experience:
 
-| Command     | File          | Purpose                                                                          |
-| ----------- | ------------- | -------------------------------------------------------------------------------- |
-| `/meta`     | `meta.md`     | Project lifecycle -- init, status, fix (incl. docs verification), deploy, health |
-| `/docs`     | `docs.md`     | Browse, create, and verify permanent documentation                               |
-| `/work`     | `work.md`     | Task tracking -- list, create, save, resume, complete                            |
-| `/tutorial` | `tutorial.md` | Progressive learning path -- 3 tracks, menu-driven                               |
+| 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         |
 
-The `/creds` skill (`.claude/skills/creds/SKILL.md`) is also scaffolded. It auto-triggers when the agent detects credential-related context and manages credential storage and retrieval.
+### Key Skills
 
-### `/meta` Command
+**`/setup`** -- First-time project setup. Replaces template placeholders, installs dependencies, configures `.env`, verifies the project, and optionally runs a first deploy.
 
-The `/meta` command namespace manages the full project lifecycle. It has five operations:
+**`/deploy`** -- Full deploy pipeline: type-check, validate resources, commit, deploy (auto-regenerates `docs/index.md` and `docs/resources.md`), verify platform, and optionally push.
 
-- **`/meta init`** -- First-run guided setup. Runs after `elevasis-sdk init` to install dependencies, configure `.env`, run the competency assessment onboarding flow, seed `memory/profile/`, verify the project, and optionally do a first deploy.
-- **`/meta`** (no arguments) -- Project health status. Shows current template version, SDK version, profile summary, a quick drift check, and last deployment status.
-- **`/meta fix`** -- SDK upgrade check and drift repair. Step 0 offers to run `pnpm update @elevasis/sdk` and merge template changes. Steps 1-8 repair drift: missing managed files, gitignore entries, CLAUDE.md sections, memory structure, doc cross-references, settings, rules health, and project map freshness.
-- **`/meta deploy`** -- Full 9-step deploy pipeline: validate, type-check, verify docs, commit, deploy (auto-regenerates `docs/project-map.mdx`), verify platform, update deployment state, and optionally push.
-- **`/meta health`** -- Execution debugging and resource status; shows recent executions, analyzes failures, and checks environment connectivity.
+**`/elevasis`** -- SDK operations entry point: `check` validates resource definitions, `deploy` bundles and uploads, `exec` runs a resource with input.
 
-### `/docs` Command
+**`/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.
 
-The `/docs` command manages the permanent `docs/` tree -- everything except `docs/in-progress/` (owned by `/work`) and auto-generated files (`project-map.mdx`, `resource-map.mdx`). Three operations:
+**`/status`** -- Quick project health check: shows SDK version, deployed resources, last deploy date, and environment status.
 
-- **`/docs`** (no arguments) -- Browse. Scans `docs/` recursively and displays a numbered list of user-maintained docs with auto-generated files shown separately as read-only. Pick a number to read and discuss, or say "create" or "verify."
-- **`/docs create [description]`** -- Interview-driven reference doc creation. If the doc is about a specific resource, the agent scans `src/` and pre-populates from code (config, schemas, step names, platform tools). Scaffolds sections appropriate to the doc type (resource guide, integration guide, architecture notes, process doc, or general reference).
-- **`/docs verify [file?]`** -- Interactive standalone version of `/meta fix` step 5. Cross-references resource IDs, schema fields, and platform tools in docs against `src/`. Shows a summary, then guides fixes interactively. Can be scoped to a single file.
+**`/save`** -- Auto-manages docs from conversation context: writes or updates docs based on what was discussed in the session.
 
-### `/work` Command
+**`/explore`** -- Codebase exploration anchored to `docs/`. Reads the doc map first, then drills into source as needed.
 
-The `/work` command manages in-progress task tracking across sessions. It uses `docs/in-progress/` for task documents with standardized frontmatter (`status: planned | in-progress | complete`).
+**`/continue`** -- Resumes in-progress work by reading `docs/in-progress/` and picking up where the last session left off.
 
-`/work` is intent-driven -- the agent detects what to do from context rather than requiring explicit subcommands:
+**`/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.
 
-- **`/work`** (no arguments) -- Lists tasks sorted by status (`in-progress` first) with last-saved date and current step. Pick by number or name to auto-resume, or describe new work to auto-create a task.
-- **Auto-create** -- When the user describes work that doesn't match an existing task, the agent creates a task doc automatically. If intent is clear, it skips the interview; if ambiguous, it asks 1-2 focused questions.
-- **Auto-save** -- The agent saves progress silently when the conversation context is getting heavy, the user is wrapping up, or 2+ steps have been completed without saving. Updates progress markers, files modified, and resume context.
-- **Auto-resume** -- When the user picks an existing task (by number, name, or keyword), the agent loads context and resumes automatically.
-- **Suggest complete** -- When all plan steps are marked COMPLETE, the agent suggests finalizing: "All steps for '`{task}`' look done. Want me to finalize it?" It never auto-invokes completion. The complete flow validates readiness, cleans the doc (strips resume context, removes progress markers, targets 200-400 lines), determines destination in `docs/`, confirms with user, moves, and verifies.
+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.
 
-**Directory conventions for `docs/in-progress/`:**
+When these command families overlap conceptually, use this boundary:
 
-```
-docs/in-progress/
-├── crm-integration/
-│   ├── index.mdx          # Main task doc
-│   └── attio-schema.mdx   # Supporting analysis
-├── email-templates.mdx    # Small standalone task
-└── ui-dashboard/
-    ├── index.mdx          # Main task doc
-    └── component-list.mdx # Supporting analysis
-```
-
-The numbered list is derived from scanning this directory. `index.mdx` is treated as the primary task doc for a directory. On complete, destination in `docs/` is determined by scanning for related existing directories.
+- `/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
 
-### `/tutorial` Command
+**`/dsp`** -- Dispatches subagents in parallel for implementation tasks that can run concurrently.
 
-The `/tutorial` command shows a track menu on every invocation and runs a progressive learning path adapted to the user's skill profile. Three tracks: Orchestration Concepts (7 lessons), Examples & Advanced Modules (9 standalone modules), and Meta-Framework (5 lessons). Two skill dimensions tracked: `automation` (none / low-code / custom) and `platformNavigation` (none / oriented / comfortable).
+**`/sync`** -- Pulls latest changes, wipes all `node_modules` and caches, and runs a fresh reinstall.
 
 ## Developer Profile
 
@@ -138,14 +126,26 @@ The agent does not prompt for confirmation on minor updates. Major changes (leve
 
 ## Rules System
 
-Six 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.
+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/`):
 
-The two files you will interact with directly:
+- **`docs.md`** -- Documentation structure, frontmatter conventions, auto-generated files.
+- **`task-tracking.md`** -- Task doc conventions, injected for in-progress files.
 
-- **`sdk-patterns.md`** (MANAGED) -- Injected when editing `src/`. Covers SDK imports, source structure, runtime, and typed adapter patterns. Updated by `elevasis-sdk update`.
-- **`workspace-patterns.md`** (INIT_ONLY) -- Injected project-wide. Starts empty; grows via error promotion (3+ recurrences of the same error become a rule). Never overwritten by updates.
+Additional contextual rules:
 
-Four additional MANAGED rules (`docs-authoring.md`, `memory-conventions.md`, `project-map.md`, `task-tracking.md`) are injected contextually for docs, memory, and task files. These are maintained by the SDK and require no user action.
+- **`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
 
@@ -153,4 +153,4 @@ The `CLAUDE.md` Interaction Guidance section translates skill dimensions from `m
 
 ---
 
-**Last Updated:** 2026-03-03
+**Last Updated:** 2026-04-17

package/reference/framework/index.mdx

@@ -14,22 +14,25 @@ Running `elevasis-sdk init my-project` produces the following agent infrastructu
 
 ```
 .claude/
-├── settings.json               # autoCompact: false
-├── commands/
-│   ├── meta.md                 # Project lifecycle (init, fix, deploy, health)
-│   ├── docs.md                 # Browse, create, and verify permanent docs
-│   ├── tutorial.md             # Progressive learning path (3 tracks)
-│   └── work.md                 # Task tracking
+├── settings.json               # Hook registrations (PostToolUse, PostToolUseFailure)
 ├── hooks/
-│   └── enforce-sdk-boundary.mjs  # Blocks file modifications outside project boundary
+│   ├── post-edit-validate.mjs    # Formatting/type-check hook (after Write/Edit/MultiEdit)
+│   └── tool-failure-recovery.mjs # Error recovery hook (after Bash failures)
 ├── skills/
-│   └── creds/SKILL.md          # Credential management (auto-triggers)
+│   ├── work/SKILL.md           # Task tracking across sessions
+│   ├── elevasis/SKILL.md       # SDK operations (check, deploy, exec)
+│   ├── deploy/skill.md         # Deploy pipeline
+│   ├── setup/SKILL.md          # First-time project setup
+│   ├── status/SKILL.md         # Project health check
+│   └── ...                     # Additional skills (dsp, continue, project, sync, explore, save)
+├── scripts/
+│   └── statusline-command.js   # Status line command
 └── rules/
     ├── sdk-patterns.md         # SDK patterns (auto-loaded for src/ files)
     ├── docs-authoring.md       # MDX conventions (auto-loaded for docs/ files)
-    ├── memory-conventions.md   # Memory conventions (auto-loaded)
-    ├── project-map.md          # Project map conventions (auto-loaded)
     ├── task-tracking.md        # Task tracking conventions (auto-loaded)
+    ├── platform.md             # Platform tool patterns
+    ├── error-handling.md       # Error handling patterns
     └── workspace-patterns.md   # Project-specific patterns (grows over time)
 ```