@elevasis/sdk 0.5.10 → 0.5.11

package/dist/templates.js

@@ -1,7 +1,7 @@
 // package.json
 
 // src/cli/commands/templates/core/workspace.ts
-var TEMPLATE_VERSION = 23;
+var TEMPLATE_VERSION = 24;
 function configTemplate() {
   return `import type { ElevasConfig } from '@elevasis/sdk'
 
@@ -19,6 +19,7 @@ dist/
 __elevasis_worker.ts
 .claude/settings.local.json
 .claude/memory/
+package-lock.json
 `;
   if (ctx.hasUI) {
     content += `ui/node_modules/
@@ -273,13 +274,13 @@ All \`reference/\` paths resolve to \`node_modules/@elevasis/sdk/reference/\`.
 
 ## Elevasis CLI
 
-**MANDATORY:** Use the \`elevasis\` CLI for all execution/platform operations -- never \`npx\`, \`curl\`, or any other tool.
+**MANDATORY:** Use the \`elevasis-sdk\` CLI for all execution/platform operations -- never \`npx\`, \`curl\`, or any other tool.
 
-- \`elevasis exec <resource-id> --input '{...}'\` -- run a resource synchronously
-- \`elevasis exec <resource-id> --input '{...}' --async\` -- run async, returns execution ID
-- \`elevasis execution <resource-id> <execution-id>\` -- inspect execution detail
-- \`elevasis check\` -- validate resource definitions without deploying
-- \`elevasis deploy\` -- deploy to the platform
+- \`elevasis-sdk exec <resource-id> --input '{...}'\` -- run a resource synchronously
+- \`elevasis-sdk exec <resource-id> --input '{...}' --async\` -- run async, returns execution ID
+- \`elevasis-sdk execution <resource-id> <execution-id>\` -- inspect execution detail
+- \`elevasis-sdk check\` -- validate resource definitions without deploying
+- \`elevasis-sdk deploy\` -- deploy to the platform
 
 Organization is derived from your API key -- no org prefix needed in the resource ID.
 For full CLI reference: \`reference/cli/index.mdx\`
@@ -490,7 +491,7 @@ When automation is none:
 Skip the file tour. Start with what Elevasis does for their business -- use analogies
 from \`reference/developer/interaction-guidance.mdx\` (recipe, assembly line, kitchen
 appliance). Explain deployment plainly: "You write the recipe here, then deploy it so
-it's live." Deploy the starter echo workflow (\`elevasis check\` + \`elevasis deploy\`),
+it's live." Deploy the starter echo workflow (\`elevasis-sdk check\` + \`elevasis-sdk deploy\`),
 THEN tour the Command Center so the user sees populated pages, not empty ones. Tour:
 Command View (echo node), Execution Logs (result).
 Observation focus: automation value understanding, Command Center comfort.
@@ -499,7 +500,7 @@ When automation is low-code or custom:
 Tour project files: src/index.ts (registry), src/example/echo.ts (starter
 workflow), src/operations/platform-status.ts (platform API example),
 elevasis.config.ts, .env, docs/. Explain the execution model.
-Verify: run \`elevasis resources\`. Then open the Command Center and tour the
+Verify: run \`elevasis-sdk resources\`. Then open the Command Center and tour the
 main pages: Command View (resource graph), Execution Logs.
 Point out the echo workflow node in Command View.
 Observation focus: cloud deployment model, UI navigation comfort.
@@ -509,14 +510,14 @@ Observation focus: cloud deployment model, UI navigation comfort.
 When automation is none:
 Frame the workflow as "a recipe." Use plain language: "settings" not "config",
 "what data it needs" not "contract", "instructions" not "steps", "where it starts"
-not "entryPoint." Agent writes all code changes. Agent runs \`elevasis exec\` to verify
+not "entryPoint." Agent writes all code changes. Agent runs \`elevasis-sdk exec\` to verify
 and narrates the result in plain terms.
 Observation focus: recipe-to-result connection.
 
 When automation is low-code or custom:
 Modify the echo workflow. Walk through each part: config, contract, steps,
-entryPoint. Deploy: \`elevasis check\` then \`elevasis deploy\`. Test with
-\`elevasis exec echo --input '{"message":"hello"}'\`. Then open the Execution
+entryPoint. Deploy: \`elevasis-sdk check\` then \`elevasis-sdk deploy\`. Test with
+\`elevasis-sdk exec echo --input '{"message":"hello"}'\`. Then open the Execution
 Runner in the Command Center, find the echo workflow, fill out the form, and
 run it from the UI. Compare the result to the CLI output.
 Observation focus: deployment-to-execution loop, TypeScript syntax comfort.
@@ -527,20 +528,20 @@ When automation is none:
 Frame as "What information does your automation need?" Describe types in plain English:
 text, number, yes/no, a choice from a list. NO Zod, no z.string(), no z.infer(), no
 code shown. Agent reads identity.md goals and writes the workflow schema. Agent runs
-\`elevasis exec\` with sample input and narrates the result.
+\`elevasis-sdk exec\` with sample input and narrates the result.
 Observation focus: data-to-input connection, required vs optional understanding.
 
 When automation is low-code:
 "Field mapping like Zapier, but with validation." Show Zod types briefly. Demonstrate
 how \`.describe()\` documents each field. Build schema based on identity.md goals.
-After deploy, run with \`elevasis exec --input '{...}'\` to verify each field.
+After deploy, run with \`elevasis-sdk exec --input '{...}'\` to verify each field.
 Observation focus: schema-to-input mapping, optional fields, types.
 
 When automation is custom:
 Explain schemas in plain English (concepts page). Show common Zod types.
 Explain \`z.infer\`. Build a new workflow with real-world input schema based
 on the user's goals (read .claude/memory/profile/identity.md). After deploy,
-run with \`elevasis exec --input '{...}'\` to verify the schema and inspect
+run with \`elevasis-sdk exec --input '{...}'\` to verify the schema and inspect
 the execution output.
 Observation focus: schema-to-input mapping, optional fields, types.
 
@@ -571,7 +572,7 @@ Observation focus: credential setup (CLI + UI), async/await.
 When automation is none:
 Frame as "Step 1 passes its result to Step 2, like a relay race." Command View is
 PRIMARY teaching tool -- show the visual graph before explaining code. Agent builds
-the 2-step workflow. Agent runs \`elevasis exec\` to verify and shows output flow.
+the 2-step workflow. Agent runs \`elevasis-sdk exec\` to verify and shows output flow.
 User opens Command View to see the two nodes + arrow. Code is secondary.
 Observation focus: relay-race concept, visual graph comprehension.
 
@@ -587,7 +588,7 @@ Observation focus: data flow reasoning, relationship visualization.
 When automation is none:
 Frame as "If the customer is VIP, do this -- otherwise, do that." No StepType.CONDITIONAL
 jargon -- focus on the concept, not the implementation. Agent adds the condition.
-Agent runs \`elevasis exec\` for both paths. Open Execution Logs to see which
+Agent runs \`elevasis-sdk exec\` for both paths. Open Execution Logs to see which
 path ran. Guide log navigation step-by-step.
 Observation focus: branching concept understanding, log navigation.
 
@@ -612,7 +613,7 @@ Change status from dev to production. Cover error handling: try/catch,
 ExecutionError, PlatformToolError. Create a schedule in Task Scheduler (use
 Recurring type for a cron schedule). If docs/ has pages, show Knowledge Base.
 Open Deployments page to confirm the latest version is active. Show CLI
-monitoring: elevasis executions, elevasis execution. Suggest next steps.
+monitoring: elevasis-sdk executions, elevasis-sdk execution. Suggest next steps.
 Observation focus: readiness for independent operation (CLI + UI).
 
 ## Module Menu
@@ -700,7 +701,7 @@ Read: \`reference/framework/agent.mdx\`.
 Build: Create an agent definition with tools. Configure LLM tool calling.
 Compare agent vs workflow for a task.
 Key concepts: agent definition, tool registration, LLM tool calling, execution trace.
-Verify: Run agent with \`elevasis exec\`, review tool call trace in Execution Logs.
+Verify: Run agent with \`elevasis-sdk exec\`, review tool call trace in Execution Logs.
 
 ## Meta-Framework Track
 
@@ -823,7 +824,7 @@ Observation focus: customization concept, owned vs managed files.
 
 When automation is low-code:
 Show the \`.claude/rules/\` directory. Explain the two types: sdk-patterns.md (MANAGED --
-updated by elevasis update) and workspace-patterns.md (INIT_ONLY -- yours to edit).
+updated by elevasis-sdk update) and workspace-patterns.md (INIT_ONLY -- yours to edit).
 Explain path-scoping briefly: "These rules only activate when the agent is working on
 certain file types." Show an example rule with WRONG/RIGHT pattern. Explain error
 promotion: if something goes wrong 3+ times, add it here.
@@ -853,7 +854,7 @@ Next steps: point to reference docs in docs/, encourage using /work for new task
 Observation focus: update model concept, project map as navigation aid.
 
 When automation is low-code:
-Explain MANAGED (auto-updated by elevasis update) vs INIT_ONLY (set once, yours).
+Explain MANAGED (auto-updated by elevasis-sdk update) vs INIT_ONLY (set once, yours).
 Show how /meta fix applies SDK updates with conflict handling: "If a file changed,
 it shows you both versions and lets you decide."
 Show \`docs/project-map.mdx\` and explain what it contains: resources, commands,
@@ -877,7 +878,7 @@ Observation focus: full template lifecycle, conflict resolution pattern.
 
 **automation: none**
 Use the non-technical variant for each lesson. Agent writes all code -- user
-never types code. Agent runs \`elevasis exec\` for verification and narrates results.
+never types code. Agent runs \`elevasis-sdk exec\` for verification and narrates results.
 Avoid all jargon; use analogies. CLI is the primary verification tool.
 Always deploy before directing the user to the Command Center.
 
@@ -973,7 +974,7 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    \`\`\`
    No other keys (no \`NODE_ENV\`, no extras). The \`.env\` file must contain
    only \`ELEVASIS_PLATFORM_KEY\`.
-   Validate the key works: run \`elevasis resources\` (should return an empty
+   Validate the key works: run \`elevasis-sdk resources\` (should return an empty
    list, not an auth error). If auth fails, tell the user their key appears
    invalid and ask them to check it in the Elevasis dashboard.
 
@@ -1034,7 +1035,7 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    - If git remote exists: note remote URL in memory/profile/preferences.md
 
 5. **Verify project**
-   Run \`elevasis check\` to confirm the starter resource is valid.
+   Run \`elevasis-sdk check\` to confirm the starter resource is valid.
    Optionally deploy the echo workflow.
 
 6. **Report**
@@ -1063,7 +1064,7 @@ Detect and repair all drift. Optionally upgrades the SDK first.
 
 0. **SDK version check** -- Compare installed \`@elevasis/sdk\` against the latest
    available. If behind, offer to run \`pnpm update @elevasis/sdk\` before
-   continuing. If the user accepts, run it, then run \`elevasis update\` to add
+   continuing. If the user accepts, run it, then run \`elevasis-sdk update\` to add
    any new managed files and flag conflicts. For each flagged file:
    - Read the current project file and the new template from \`@elevasis/sdk/templates\`
    - Add new sections that don't exist; preserve user customizations
@@ -1092,7 +1093,7 @@ Detect and repair all drift. Optionally upgrades the SDK first.
    suggest adding patterns. Surface suggestions only -- do not auto-generate.
 8. **Project map freshness:** Check whether \`docs/project-map.mdx\` reflects the
    current project state (resources, commands, rules, skills, memory files).
-   Compare filesystem state against the map. If stale, run \`elevasis deploy\`
+   Compare filesystem state against the map. If stale, run \`elevasis-sdk deploy\`
    to regenerate, or patch inline for minor drift.
 
 Each step reports its result. Steps 1-8 run even if step 0 is skipped.
@@ -1102,11 +1103,11 @@ Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 0. Read \`reference/deployment/command-view.mdx\` -- understand the Command View
    model, relationship declarations, and what deploy-time validation checks.
    This context is essential for diagnosing validation failures in steps 1-2.
-1. Run \`elevasis check\` (validation)
+1. Run \`elevasis-sdk check\` (validation)
 2. Type check if \`tsconfig.json\` exists
 3. Verify docs reflect current resources
 4. If git configured: stage changes, commit with deploy message
-5. Run \`elevasis deploy\`
+5. Run \`elevasis-sdk deploy\`
 6. \`docs/project-map.mdx\` is auto-regenerated by deploy (no manual bump needed)
 7. Verify deployment via platform
 8. Update \`memory/deployment-state.md\` with count, timestamp, inventory
@@ -1668,10 +1669,10 @@ description: Project map conventions -- auto-generated, do not edit, maintained
 
 # Project Map
 
-- \`docs/project-map.mdx\` and \`docs/resource-map.mdx\` are fully auto-generated by \`elevasis deploy\`
+- \`docs/project-map.mdx\` and \`docs/resource-map.mdx\` are fully auto-generated by \`elevasis-sdk deploy\`
 - Do not edit either file manually -- changes are overwritten on next deploy
 - \`/meta fix\` step 8 checks for drift and patches the map
-- If a new command, rule, skill, or memory file is added, run \`/meta fix\` or \`elevasis deploy\` to update
+- If a new command, rule, skill, or memory file is added, run \`/meta fix\` or \`elevasis-sdk deploy\` to update
 `;
 }
 function claudeTaskTrackingRuleTemplate() {

package/package.json

@@ -1,11 +1,9 @@
 {
   "name": "@elevasis/sdk",
-  "version": "0.5.10",
+  "version": "0.5.11",
   "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.
 
 ---