@elevasis/sdk 0.5.10 → 0.5.12

package/dist/worker/index.js

@@ -4997,15 +4997,20 @@ function resolveNext(next, data) {
   }
   return next.default;
 }
+function serializeNext(next) {
+  if (next === null) return null;
+  if (next.type === "linear") return { type: "linear", target: next.target };
+  return { type: "conditional", routes: next.routes.map((r) => ({ target: r.target })), default: next.default };
+}
 async function executeWorkflow(workflow, input, context) {
   const logs = [];
-  const postLog = (level, message) => {
+  const postLog = (level, message, logContext) => {
     const timestamp = (/* @__PURE__ */ new Date()).toISOString();
-    const entry = { level, message, timestamp };
+    const entry = { level, message, timestamp, context: logContext };
     logs.push(entry);
     parentPort.postMessage({
       type: "log",
-      entry: { level, message, timestamp, executionId: context.executionId }
+      entry: { level, message, timestamp, executionId: context.executionId, context: logContext }
     });
   };
   const origLog = console.log;
@@ -5026,26 +5031,71 @@ async function executeWorkflow(workflow, input, context) {
       if (!step) {
         throw new Error(`Step '${stepId}' not found in workflow '${workflow.config.resourceId}'`);
       }
+      const stepStartTime = Date.now();
       const stepInput = step.inputSchema.parse(currentData);
-      const rawOutput = await step.handler(stepInput, {
-        executionId: context.executionId,
-        organizationId: context.organizationId,
-        organizationName: context.organizationName,
-        resourceId: workflow.config.resourceId,
-        sessionId: context.sessionId,
-        sessionTurnNumber: context.sessionTurnNumber,
-        parentExecutionId: context.parentExecutionId,
-        executionDepth: context.executionDepth,
-        store: /* @__PURE__ */ new Map(),
-        logger: {
-          debug: (msg) => console.log(`[debug] ${msg}`),
-          info: (msg) => console.log(`[info] ${msg}`),
-          warn: (msg) => console.warn(`[warn] ${msg}`),
-          error: (msg) => console.error(`[error] ${msg}`)
-        }
+      postLog("info", `Step '${step.name}' started`, {
+        type: "workflow",
+        contextType: "step-started",
+        stepId: step.id,
+        stepStatus: "started",
+        input: stepInput,
+        startTime: stepStartTime
       });
-      currentData = step.outputSchema.parse(rawOutput);
-      stepId = resolveNext(step.next, currentData);
+      try {
+        const rawOutput = await step.handler(stepInput, {
+          executionId: context.executionId,
+          organizationId: context.organizationId,
+          organizationName: context.organizationName,
+          resourceId: workflow.config.resourceId,
+          sessionId: context.sessionId,
+          sessionTurnNumber: context.sessionTurnNumber,
+          parentExecutionId: context.parentExecutionId,
+          executionDepth: context.executionDepth,
+          store: /* @__PURE__ */ new Map(),
+          logger: {
+            debug: (msg) => console.log(`[debug] ${msg}`),
+            info: (msg) => console.log(`[info] ${msg}`),
+            warn: (msg) => console.warn(`[warn] ${msg}`),
+            error: (msg) => console.error(`[error] ${msg}`)
+          }
+        });
+        currentData = step.outputSchema.parse(rawOutput);
+        const stepEndTime = Date.now();
+        const nextStepId = resolveNext(step.next, currentData);
+        postLog("info", `Step '${step.name}' completed (${stepEndTime - stepStartTime}ms)`, {
+          type: "workflow",
+          contextType: "step-completed",
+          stepId: step.id,
+          stepStatus: "completed",
+          output: currentData,
+          duration: stepEndTime - stepStartTime,
+          isTerminal: nextStepId === null,
+          startTime: stepStartTime,
+          endTime: stepEndTime
+        });
+        if (step.next?.type === "conditional" && nextStepId !== null) {
+          postLog("info", `Routing from '${step.name}' to '${nextStepId}'`, {
+            type: "workflow",
+            contextType: "conditional-route",
+            stepId: step.id,
+            target: nextStepId
+          });
+        }
+        stepId = nextStepId;
+      } catch (err) {
+        const stepEndTime = Date.now();
+        postLog("error", `Step '${step.name}' failed: ${String(err)}`, {
+          type: "workflow",
+          contextType: "step-failed",
+          stepId: step.id,
+          stepStatus: "failed",
+          error: String(err),
+          duration: stepEndTime - stepStartTime,
+          startTime: stepStartTime,
+          endTime: stepEndTime
+        });
+        throw err;
+      }
     }
     if (workflow.contract.outputSchema) {
       currentData = workflow.contract.outputSchema.parse(currentData);
@@ -5122,7 +5172,14 @@ function startWorker(org) {
           status: w.config.status,
           description: w.config.description,
           version: w.config.version,
-          domains: w.config.domains
+          domains: w.config.domains,
+          steps: Object.values(w.steps).map((step) => ({
+            id: step.id,
+            name: step.name,
+            description: step.description,
+            next: serializeNext(step.next)
+          })),
+          entryPoint: w.entryPoint
         })),
         agents: (org.agents ?? []).map((a) => ({
           resourceId: a.config.resourceId,

package/package.json

@@ -1,11 +1,9 @@
 {
   "name": "@elevasis/sdk",
-  "version": "0.5.10",
+  "version": "0.5.12",
   "description": "SDK for building Elevasis organization resources",
-  "comment:bin": "IMPORTANT: This package shares the 'elevasis' binary name with @repo/cli. They never conflict because @elevasis/sdk must NEVER be added as a dependency of any workspace package (apps/*, packages/*, organizations/*). Workspace projects use @repo/cli for the 'elevasis' binary. External developers (outside the workspace) get this SDK's binary via npm install.",
   "type": "module",
   "bin": {
-    "elevasis": "./dist/cli.cjs",
     "elevasis-sdk": "./dist/cli.cjs"
   },
   "exports": {

package/reference/_navigation.md

@@ -14,7 +14,7 @@ All paths are relative to `node_modules/@elevasis/sdk/reference/`.
 
 | Resource | Location | Description | When to Load |
 | --- | --- | --- | --- |
-| CLI Reference | `cli/index.mdx` | Full reference for every elevasis CLI command -- scaffold, validate, deploy, execute, and inspect resources | Running CLI operations |
+| CLI Reference | `cli/index.mdx` | Full reference for every elevasis-sdk CLI command -- scaffold, validate, deploy, execute, and inspect resources | Running CLI operations |
 
 ## Concepts
 
@@ -29,7 +29,7 @@ All paths are relative to `node_modules/@elevasis/sdk/reference/`.
 | Execution API | `deployment/api.mdx` | REST endpoints for executing resources, querying execution history, and managing deployments via the Elevasis external API | Calling the API directly or debugging API responses |
 | Command Center UI | `deployment/command-center-ui.mdx` | Reference for the Elevasis Command Center -- what each page does, when to use it post-deployment, and how SDK concepts map to UI actions | User asks about the Command Center UI, post-deployment workflow, or monitoring deployed resources |
 | Command View | `deployment/command-view.mdx` | How the Command View graph works -- node types, relationships, what is enforced vs decorative, and what the platform needs to render your resource graph | Deploying resources or building resources that invoke other resources |
-| Deploying Resources | `deployment/index.mdx` | How to deploy your Elevasis SDK resources to the platform using elevasis deploy, including configuration, validation, and environment setup | Preparing to deploy or debugging deploy failures |
+| Deploying Resources | `deployment/index.mdx` | How to deploy your Elevasis SDK resources to the platform using elevasis-sdk deploy, including configuration, validation, and environment setup | Preparing to deploy or debugging deploy failures |
 
 ## Developer
 
@@ -45,7 +45,7 @@ All paths are relative to `node_modules/@elevasis/sdk/reference/`.
 | Resource Documentation | `framework/documentation.mdx` | Write and deploy MDX documentation alongside your Elevasis resources | Writing or updating project documentation |
 | Development Framework | `framework/index.mdx` | The SDK scaffolds a complete development environment for Claude Code -- project instructions, slash commands, cross-session memory, and template versioning | Understanding the agent framework structure |
 | Memory System | `framework/memory.mdx` | Cross-session project knowledge stored in .claude/memory/ -- deployment state, environment, decisions, and error patterns that persist between Claude Code sessions | Working with agent memory or session state |
-| Project Structure | `framework/project-structure.mdx` | Each file scaffolded by elevasis init and its purpose in the development workflow | Understanding scaffolded files or project layout |
+| Project Structure | `framework/project-structure.mdx` | Each file scaffolded by elevasis-sdk init and its purpose in the development workflow | Understanding scaffolded files or project layout |
 
 ## Getting-started
 

package/reference/cli/index.mdx

@@ -1,29 +1,29 @@
 ---
 title: CLI Reference
-description: Full reference for every elevasis CLI command -- scaffold, validate, deploy, execute, and inspect resources
+description: Full reference for every elevasis-sdk CLI command -- scaffold, validate, deploy, execute, and inspect resources
 loadWhen: "Running CLI operations"
 ---
 
-The `elevasis` CLI is the primary interface for working with your Elevasis SDK project. Install it as part of `@elevasis/sdk` and use it to scaffold projects, validate resource definitions, deploy to the platform, and inspect execution history.
+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 scaffold projects, validate resource definitions, deploy to the platform, and inspect execution history.
 
 **Installation:**
 
 ```bash
-npm install @elevasis/sdk
+pnpm add @elevasis/sdk
 ```
 
-After installation, the `elevasis` binary is available in your project's `node_modules/.bin/`. Most commands require `ELEVASIS_API_KEY` to be set in your environment or a `.env` file.
+After installation, the `elevasis-sdk` binary is available in your project's `node_modules/.bin/`. Most commands require `ELEVASIS_API_KEY` to be set in your environment or a `.env` file.
 
 ---
 
-## elevasis init
+## elevasis-sdk init
 
 Scaffold a new Elevasis SDK project in the specified directory.
 
 **Synopsis:**
 
 ```
-elevasis init [directory]
+elevasis-sdk init [directory]
 ```
 
 **Behavior:**
@@ -42,7 +42,13 @@ elevasis init [directory]
 **Example:**
 
 ```bash
-elevasis init my-project
+elevasis-sdk init my-project
+```
+
+You can also run `init` without a global install using `pnpm dlx`:
+
+```bash
+pnpm dlx @elevasis/sdk init my-project
 ```
 
 ```
@@ -52,20 +58,20 @@ elevasis init my-project
 
   Next steps:
     cd my-project
-    npm install
-    elevasis check
+    pnpm install
+    elevasis-sdk check
 ```
 
 ---
 
-## elevasis check
+## elevasis-sdk check
 
 Validate all resource definitions in your project without deploying.
 
 **Synopsis:**
 
 ```
-elevasis check
+elevasis-sdk check
 ```
 
 **Behavior:**
@@ -88,7 +94,7 @@ elevasis check
 **Example output (success):**
 
 ```
-$ elevasis check
+$ elevasis-sdk check
 
   Validating...    done (4 resources, 0 errors)
 ```
@@ -96,7 +102,7 @@ $ elevasis check
 **Example output (failure):**
 
 ```
-$ elevasis check
+$ elevasis-sdk check
 
   Validating...
     ERROR  Duplicate resource ID 'onboard-client' in organization 'Acme Corp'
@@ -107,20 +113,20 @@ $ elevasis check
 
 ---
 
-## elevasis deploy
+## elevasis-sdk deploy
 
 Bundle your project with esbuild and deploy it to the Elevasis platform.
 
 **Synopsis:**
 
 ```
-elevasis deploy
+elevasis-sdk deploy
 ```
 
 **Behavior:**
 
 - Authenticates with `ELEVASIS_API_KEY` and resolves your organization name
-- Runs the same `ResourceRegistry` validation as `elevasis check`
+- Runs the same `ResourceRegistry` validation as `elevasis-sdk check`
 - Bundles your `src/index.ts` and all dependencies into a single self-contained JS file (`dist/bundle.js`, approximately 50-200 KB)
 - Uploads the bundle plus resource metadata to `POST /api/external/deploy`
 - Streams deploy status and prints the result
@@ -143,7 +149,7 @@ elevasis deploy
 **Example output (success):**
 
 ```
-$ elevasis deploy
+$ elevasis-sdk deploy
 
   Authenticating...          done (acme-corp)
   Validating...              done (4 resources, 0 errors)
@@ -157,7 +163,7 @@ $ elevasis deploy
 **Example output (validation failure):**
 
 ```
-$ elevasis deploy
+$ elevasis-sdk deploy
 
   Authenticating...          done (acme-corp)
   Validating...
@@ -169,14 +175,14 @@ $ elevasis deploy
 
 ---
 
-## elevasis exec
+## elevasis-sdk exec
 
 Execute a deployed resource by ID.
 
 **Synopsis:**
 
 ```
-elevasis exec <resource> --input '{...}'
+elevasis-sdk exec <resource> --input '{...}'
 ```
 
 **Behavior:**
@@ -198,7 +204,7 @@ elevasis exec <resource> --input '{...}'
 **Example:**
 
 ```bash
-elevasis exec onboard-client --input '{"clientName": "Jane", "email": "jane@example.com"}'
+elevasis-sdk exec onboard-client --input '{"clientName": "Jane", "email": "jane@example.com"}'
 ```
 
 ```
@@ -218,24 +224,24 @@ elevasis exec onboard-client --input '{"clientName": "Jane", "email": "jane@exam
 **Async example:**
 
 ```bash
-elevasis exec onboard-client --input '{"clientName": "Jane"}' --async
+elevasis-sdk exec onboard-client --input '{"clientName": "Jane"}' --async
 ```
 
 ```
   Execution started: exec_550e8400
-  Poll with: elevasis execution onboard-client exec_550e8400
+  Poll with: elevasis-sdk execution onboard-client exec_550e8400
 ```
 
 ---
 
-## elevasis resources
+## elevasis-sdk resources
 
 List all deployed resources for your organization.
 
 **Synopsis:**
 
 ```
-elevasis resources
+elevasis-sdk resources
 ```
 
 **Behavior:**
@@ -254,7 +260,7 @@ elevasis resources
 **Example output:**
 
 ```
-$ elevasis resources
+$ elevasis-sdk resources
 
   onboard-client    workflow   Onboard Client       prod
   send-report       workflow   Send Weekly Report   prod
@@ -264,14 +270,14 @@ $ elevasis resources
 
 ---
 
-## elevasis executions
+## elevasis-sdk executions
 
 View execution history for a resource.
 
 **Synopsis:**
 
 ```
-elevasis executions [resource]
+elevasis-sdk executions [resource]
 ```
 
 **Behavior:**
@@ -292,7 +298,7 @@ elevasis executions [resource]
 **Example:**
 
 ```bash
-elevasis executions onboard-client --limit 5
+elevasis-sdk executions onboard-client --limit 5
 ```
 
 ```
@@ -305,14 +311,14 @@ elevasis executions onboard-client --limit 5
 
 ---
 
-## elevasis execution
+## elevasis-sdk execution
 
 View full detail for a single execution.
 
 **Synopsis:**
 
 ```
-elevasis execution <resource> <id>
+elevasis-sdk execution <resource> <id>
 ```
 
 **Behavior:**
@@ -330,7 +336,7 @@ elevasis execution <resource> <id>
 **Example:**
 
 ```bash
-elevasis execution onboard-client exec_abc001
+elevasis-sdk execution onboard-client exec_abc001
 ```
 
 ```
@@ -360,14 +366,14 @@ elevasis execution onboard-client exec_abc001
 
 ---
 
-## elevasis deployments
+## elevasis-sdk deployments
 
 List all deployments for your organization.
 
 **Synopsis:**
 
 ```
-elevasis deployments
+elevasis-sdk deployments
 ```
 
 **Behavior:**
@@ -385,7 +391,7 @@ elevasis deployments
 **Example output:**
 
 ```
-$ elevasis deployments
+$ elevasis-sdk deployments
 
   deploy_abc123   active    2026-02-25 14:00:00   4 resources
   deploy_abc122   stopped   2026-02-24 09:30:00   3 resources
@@ -394,14 +400,14 @@ $ elevasis deployments
 
 ---
 
-## elevasis describe
+## elevasis-sdk describe
 
 Show the definition of a deployed resource.
 
 **Synopsis:**
 
 ```
-elevasis describe <resource>
+elevasis-sdk describe <resource>
 ```
 
 **Behavior:**
@@ -420,7 +426,7 @@ elevasis describe <resource>
 **Example:**
 
 ```bash
-elevasis describe onboard-client
+elevasis-sdk describe onboard-client
 ```
 
 ```
@@ -444,16 +450,16 @@ elevasis describe onboard-client
 
 ---
 
-## elevasis env
+## elevasis-sdk env
 
 Manage environment variables for your project.
 
 **Synopsis:**
 
 ```
-elevasis env list
-elevasis env set <key> <value>
-elevasis env remove <key>
+elevasis-sdk env list
+elevasis-sdk env set <key> <value>
+elevasis-sdk env remove <key>
 ```
 
 **Behavior:**
@@ -471,9 +477,9 @@ elevasis env remove <key>
 **Examples:**
 
 ```bash
-elevasis env list
-elevasis env set OPENAI_API_KEY sk-proj-***
-elevasis env remove OPENAI_API_KEY
+elevasis-sdk env list
+elevasis-sdk env set OPENAI_API_KEY sk-proj-***
+elevasis-sdk env remove OPENAI_API_KEY
 ```
 
 ---

package/reference/concepts/index.mdx

@@ -23,7 +23,7 @@ This page covers core Elevasis concepts in plain English. It is the teaching voc
 | Handler | The function inside a step that does the actual work. It receives input data and returns output data. |
 | Entry Point | The first step that runs when a workflow is executed. Every workflow must have one. |
 | Resource ID | A unique lowercase name for your resource (e.g., `lead-scorer`, `send-welcome-email`). Must be unique within your organization. |
-| Workspace | Your Elevasis project directory. Contains resources (workflows and agents), documentation, and optionally a database connection and custom apps. Created by `elevasis init`. |
+| Workspace | Your Elevasis project directory. Contains resources (workflows and agents), documentation, and optionally a database connection and custom apps. Created by `elevasis-sdk init`. |
 | Data Table | A table in your database (e.g., Supabase) that stores structured data your workflows can read and write. Defined in `data/schema.ts` as documentation for the agent. |
 
 ---
@@ -94,7 +94,7 @@ type MyInput = z.infer<typeof myInput>;
 
 ### What Happens When You Run a Workflow
 
-1. A request arrives at the Elevasis platform (someone runs `elevasis exec` or a schedule triggers)
+1. A request arrives at the Elevasis platform (someone runs `elevasis-sdk exec` or a schedule triggers)
 2. The platform creates a temporary server just for this execution
 3. Your code runs on that server
 4. The result is sent back

package/reference/deployment/api.mdx

@@ -245,7 +245,7 @@ Upload a resource bundle and deploy it. Accepts a multipart request with the com
 }
 ```
 
-Use `elevasis deploy` from the CLI rather than calling this endpoint directly -- the CLI handles bundling, metadata generation, and status streaming automatically.
+Use `elevasis-sdk deploy` from the CLI rather than calling this endpoint directly -- the CLI handles bundling, metadata generation, and status streaming automatically.
 
 ### GET /api/external/deployments
 
@@ -284,13 +284,13 @@ The SDK CLI wraps all execution endpoints. Use these commands instead of calling
 
 | Command | API call | Purpose |
 | ------- | -------- | ------- |
-| `elevasis resources` | `GET /api/external/resources` | List all resources |
-| `elevasis describe <resource>` | `GET /api/external/resources/:id/definition` | Show resource definition |
-| `elevasis exec <resource> --input '...'` | `POST /api/external/execute` | Execute synchronously |
-| `elevasis exec <resource> --input '...' --async` | `POST /api/external/execute-async` | Execute asynchronously |
-| `elevasis executions <resource>` | `GET /api/external/executions/:id` | List execution history |
-| `elevasis execution <resource> <id>` | `GET /api/external/executions/:id/:execId` | Get execution detail |
-| `elevasis deployments` | `GET /api/external/deployments` | List deployments |
+| `elevasis-sdk resources` | `GET /api/external/resources` | List all resources |
+| `elevasis-sdk describe <resource>` | `GET /api/external/resources/:id/definition` | Show resource definition |
+| `elevasis-sdk exec <resource> --input '...'` | `POST /api/external/execute` | Execute synchronously |
+| `elevasis-sdk exec <resource> --input '...' --async` | `POST /api/external/execute-async` | Execute asynchronously |
+| `elevasis-sdk executions <resource>` | `GET /api/external/executions/:id` | List execution history |
+| `elevasis-sdk execution <resource> <id>` | `GET /api/external/executions/:id/:execId` | Get execution detail |
+| `elevasis-sdk deployments` | `GET /api/external/deployments` | List deployments |
 
 ---
 

package/reference/deployment/command-center-ui.mdx

@@ -4,7 +4,7 @@ description: Reference for the Elevasis Command Center -- what each page does, w
 loadWhen: "User asks about the Command Center UI, post-deployment workflow, or monitoring deployed resources"
 ---
 
-The Command Center is the browser UI for interacting with deployed resources. After you run `elevasis deploy`, this is where you run workflows, monitor executions, manage approvals, schedule tasks, and review logs. This reference covers each page and how it connects to your SDK code.
+The Command Center is the browser UI for interacting with deployed resources. After you run `elevasis-sdk deploy`, this is where you run workflows, monitor executions, manage approvals, schedule tasks, and review logs. This reference covers each page and how it connects to your SDK code.
 
 ---
 
@@ -103,7 +103,7 @@ The Execution Logs page shows the history of all executions across every deploye
 - Filter by `failed` status to triage production issues
 - Use date range to narrow down incidents
 
-> **SDK takeaway:** Every `elevasis exec` and every scheduled run appears here. Use this page to verify behavior after deploy and to diagnose failures before opening code.
+> **SDK takeaway:** Every `elevasis-sdk exec` and every scheduled run appears here. Use this page to verify behavior after deploy and to diagnose failures before opening code.
 
 ---
 
@@ -142,9 +142,9 @@ The Deployments page shows the history of all deployments for your organization.
 - Identify the currently active version
 - Compare resource counts across deployments
 
-**How it connects to your code:** Each `elevasis deploy` run creates a new deployment entry. The platform activates the new version atomically -- in-flight executions complete against the previous version while new executions start against the new one.
+**How it connects to your code:** Each `elevasis-sdk deploy` run creates a new deployment entry. The platform activates the new version atomically -- in-flight executions complete against the previous version while new executions start against the new one.
 
-> **SDK takeaway:** Check this page after `elevasis deploy` to confirm your resources are active. If something behaves unexpectedly, look here to confirm the latest version is live.
+> **SDK takeaway:** Check this page after `elevasis-sdk deploy` to confirm your resources are active. If something behaves unexpectedly, look here to confirm the latest version is live.
 
 ---
 

package/reference/deployment/command-view.mdx

@@ -16,8 +16,8 @@ Every resource you deploy becomes a node in the Command View. Some nodes are exe
 
 | Type | What It Does | Deployed By |
 | ---- | ------------ | ----------- |
-| Workflow | Runs step handlers in sequence or branching paths | `elevasis deploy` |
-| Agent | Autonomous LLM-powered resource with tools | `elevasis deploy` |
+| Workflow | Runs step handlers in sequence or branching paths | `elevasis-sdk deploy` |
+| Agent | Autonomous LLM-powered resource with tools | `elevasis-sdk deploy` |
 
 ### Visual-Only Nodes
 
@@ -108,7 +108,7 @@ This means the graph can drift from reality:
 
 ## Deploy-Time Validation
 
-When you run `elevasis deploy` or `elevasis check`, the SDK validates your resource definitions locally using the same `ResourceRegistry` the platform uses.
+When you run `elevasis-sdk deploy` or `elevasis-sdk check`, the SDK validates your resource definitions locally using the same `ResourceRegistry` the platform uses.
 
 ### What Gets Checked
 

package/reference/deployment/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Deploying Resources
-description: How to deploy your Elevasis SDK resources to the platform using elevasis deploy, including configuration, validation, and environment setup
+description: How to deploy your Elevasis SDK resources to the platform using elevasis-sdk deploy, including configuration, validation, and environment setup
 loadWhen: "Preparing to deploy or debugging deploy failures"
 ---
 
@@ -10,7 +10,7 @@ Deploying your resources makes them live on the Elevasis platform and immediatel
 
 ## How Deployment Works
 
-When you run `elevasis deploy`, the CLI performs these steps in order:
+When you run `elevasis-sdk deploy`, the CLI performs these steps in order:
 
 1. **Authenticate** -- calls the API with your `ELEVASIS_API_KEY` to verify credentials and resolve your organization name
 2. **Validate** -- runs your `src/index.ts` through `ResourceRegistry`, catching the same errors as the platform
@@ -25,7 +25,7 @@ There is no local dev server and no separate staging environment. Deployed resou
 ## Running a Deploy
 
 ```bash
-elevasis deploy
+elevasis-sdk deploy
 ```
 
 **Successful deploy output:**
@@ -40,7 +40,7 @@ elevasis deploy
   Deployment: deploy_abc123
 ```
 
-Each deploy creates a new deployment record. The previous active deployment is automatically stopped. You can view all deployments with `elevasis deployments`.
+Each deploy creates a new deployment record. The previous active deployment is automatically stopped. You can view all deployments with `elevasis-sdk deployments`.
 
 ---
 
@@ -67,7 +67,7 @@ The CLI validates your resources before bundling. Validation uses the same `Reso
   2 errors. Deploy aborted.
 ```
 
-Run `elevasis check` at any time to validate without deploying.
+Run `elevasis-sdk check` at any time to validate without deploying.
 
 ---
 
@@ -113,7 +113,7 @@ Place `.env` in your project root. The CLI reads it automatically. Never commit
 
 ## Deployment Lifecycle
 
-Each call to `elevasis deploy` creates a new deployment. The platform tracks all deployments for your organization.
+Each call to `elevasis-sdk deploy` creates a new deployment. The platform tracks all deployments for your organization.
 
 | Status | Meaning |
 | ------ | ------- |
@@ -127,7 +127,7 @@ Only one deployment can be `active` at a time. Deploying again automatically mov
 **View deployment history:**
 
 ```bash
-elevasis deployments
+elevasis-sdk deployments
 ```
 
 ```