@elevasis/sdk 1.7.0 → 1.8.0

package/reference/claude-config/settings.json

@@ -4,17 +4,6 @@
     "command": "node .claude/scripts/statusline-command.js"
   },
   "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "Write|Edit|MultiEdit",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node .claude/hooks/pre-edit-vibe-gate.mjs"
-          }
-        ]
-      }
-    ],
     "PostToolUse": [
       {
         "matcher": "Write|Edit|MultiEdit",
@@ -22,6 +11,10 @@
           {
             "type": "command",
             "command": "node .claude/hooks/post-edit-validate.mjs"
+          },
+          {
+            "type": "command",
+            "command": "node .claude/hooks/scaffold-registry-reminder.mjs"
           }
         ]
       }

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

@@ -22,8 +22,6 @@ Recurring, safe-to-re-run org model editor for external projects. Reads the orga
 - `/configure features` -- Enable, disable, or add features; Level A (defaults) or Level B (new extension TS files)
 - `/configure labels` -- Edit inline display labels on enum entries (statuses, stages, categories)
 
-**Distinction from `/org-os manage`:** `/configure` edits structural organizational reality (who the org is, who it serves, what it offers). `/org-os manage` controls feature gating (what platform capabilities are enabled). Use `/configure` for org-model content; use `/org-os manage` for feature flags.
-
 **Distinction from `/setup`:** `/setup` is for first-time bootstrap (placeholder replacement, dependency install, build verification). `/configure` is for recurring org-model updates. After first run, `/setup` delegates here.
 
 ---

package/reference/claude-config/skills/configure/operations/features.md

@@ -7,9 +7,7 @@ items and routes visible; disabling hides them without removing the feature from
 a new feature may require only a config edit (Level A) or a new extension TypeScript file
 (Level B), depending on whether the feature already exists in the platform defaults.
 
-This operation handles both toggling existing features and introducing custom features. For
-surface-level toggles (hiding one sub-section within an already-enabled feature), use
-`/org-os manage` instead.
+This operation handles both toggling existing features and introducing custom features.
 
 ## Background: Level A vs Level B
 

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

@@ -38,17 +38,6 @@ Read the current version from `package.json`, then bump it:
 
 Use the Edit tool to update the `"version"` field in `package.json` directly. Do not use `npm version` or any CLI command.
 
-### Step 1c: Regenerate Documentation
-
-Run both doc generators in sequence (resources first so the nav index picks up `resources.md`):
-
-```bash
-pnpm exec elevasis-sdk generate-resources
-pnpm exec elevasis-sdk generate-docs
-```
-
-This ensures autogenerated files (`docs/resources.md`, `docs/index.md`) reflect the current resource state before they are committed. These must run after the version bump so any version references in generated output are correct.
-
 ### Step 2: Run Tests
 
 ```bash
@@ -133,8 +122,9 @@ After a successful push, mark any linked project task as `submitted`. This is a
    - The most recent in-progress task on the most-recently-touched project, via:
 
      ```bash
-     pnpm -C operations exec elevasis-sdk project:list --status active,blocked --format brief
-     pnpm -C operations exec elevasis-sdk project:task:list --project <project-id> --status in_progress
+     pnpm elevasis-sdk project:list --status active --pretty
+     pnpm elevasis-sdk project:list --status blocked --pretty
+     pnpm elevasis-sdk project:task:list --project <project-id> --status in_progress --pretty
      ```
 
    - If the session produced an ambiguous or empty result, PROMPT the user once: "Mark a project task as submitted? (task UUID, or 'skip')". Default is skip.

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

@@ -13,13 +13,13 @@ Parallel agent dispatch for implementation tasks. Orchestrate, then delegate to
 
 1. **Always dispatch, never self-execute** -- the purpose is to offload work to subagents
 2. **Parallel within waves** -- all agents in a wave dispatched in a SINGLE message
-3. **Read docs first** -- always read `docs/index.md` before planning to understand project structure
+3. **Orient first** -- read `.claude/rules/agent-start-here.md` before planning to understand project structure and task routing
 
 ## Process
 
 ### Step 1: Understand Context
 
-1. Read `docs/index.md` for project structure and navigation
+1. Read `.claude/rules/agent-start-here.md` for project structure, task-class routing, and boundary resolution
 2. Read relevant architecture/feature docs based on the task domain
 3. If the task touches code, explore the relevant `src/` directories
 

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

@@ -49,11 +49,7 @@ Reports: resource count, validation errors, schema serialization warnings. Exit
 
 Bundle and deploy resources to the Elevasis platform.
 
-Before calling the SDK deploy, run both doc generators in sequence so the uploaded docs reflect the current resource state (resources first, then nav so `docs/index.md` picks up `resources.md`):
-
 ```bash
-pnpm exec elevasis-sdk generate-resources
-pnpm exec elevasis-sdk generate-docs
 pnpm -C operations exec elevasis-sdk deploy [--prod]
 ```
 

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

@@ -26,11 +26,11 @@ Before orienting, scan the user's query for Organization OS terminology. If any
 
 **If OS-relevant:**
 
-1. Read `docs/reference/active-change-index.md` immediately. If the target area is flagged as under active refactor, surface the watch-area warning to the user before proceeding — include the "Load:" doc paths listed in that entry so investigation does not rely on stale scaffold prose.
+1. Read `.claude/rules/active-change-index.md` immediately. If the target area is flagged as under active refactor, surface the watch-area warning to the user before proceeding — include the "Load:" doc paths listed in that entry so investigation does not rely on stale scaffold prose.
 2. Build the OS context bundle to pass into Step 3:
-   - Always: `node_modules/@elevasis/sdk/reference/scaffold/reference/glossary.md`, `docs/reference/active-change-index.md`, `docs/agent-start-here.md`
+   - Always: `node_modules/@elevasis/sdk/reference/scaffold/reference/glossary.md`, `.claude/rules/active-change-index.md`, `.claude/rules/agent-start-here.md`
    - Features / Shell / Gating queries: add `node_modules/@elevasis/sdk/reference/scaffold/ui/feature-flags-and-gating.md` + `node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md`
-   - Workflow / Operations queries: add `docs/operations/index.md` + `docs/resources.md`
+   - Workflow / Operations queries: add `.claude/rules/operations.md` + glob `operations/resources/**`
    - Organization-model queries: add `node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md` + `foundations/config/README.md`
 
 **OS layer → query intent map** (guides which reference docs the investigator loads first):
@@ -40,12 +40,12 @@ Before orienting, scan the user's query for Organization OS terminology. If any
 | "Why doesn't my feature show up?"        | Features + UI Shell Runtime      | `glossary.md` (accessFeatureKey, FEATURE_KEY_ALIASES), `feature-flags-and-gating.md`     |
 | "How do I add a nav item?"               | Features + Toolkit               | `feature-flags-and-gating.md`, `contracts.md`                                            |
 | "How does admin gating work?"            | Features + UI Shell Runtime      | `glossary.md` (AdminGuard, requiresAdmin, ProtectedRoute), `feature-flags-and-gating.md` |
-| "What runs when this workflow triggers?" | Platform Public API + Operations | `operations/index.md`, `resources.md`                                                    |
+| "What runs when this workflow triggers?" | Platform Public API + Operations | `.claude/rules/operations.md`, `resources.md`                                            |
 | "Why does the foundations adapter fail?" | Foundations                      | `glossary.md` (domain vs surface, settings asymmetry), `foundations/config/README.md`    |
 
 ### Step 1: Orient
 
-1. Read `docs/index.md` for the full project structure
+1. Read `.claude/rules/agent-start-here.md` for project structure, task-class routing, and boundary resolution
 2. Determine which domain the user's question falls into
 
 ### Step 2: Load Domain Context

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

@@ -317,7 +317,7 @@ For progress detail (milestones/tasks), follow up with `project:milestone:list`
 Wraps `project:work` for fuzzy-matched resume. Used by intent-detection "resume" classification.
 
 ```bash
-pnpm elevasis-sdk project:work <query> --pretty
+pnpm elevasis-sdk project:work <query>
 ```
 
 Prints the matched project/task brief with current `resume_context`. If multiple matches, show top 3 and ask which.

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

@@ -88,10 +88,6 @@ No other fields. Do NOT add `resume_context`, `files_modified`, or `next_steps`
 
 **Doc structure rules:**
 
-- `docs/ui/` -- frontend features, auth, components, hooks, charts, pages
-- `docs/operations/` -- platform workflows, agents, deployment, resource registry
-- `docs/knowledge/` -- project knowledge, research, reference material, domain context
-- New sections auto-detected -- any subdirectory of `docs/` becomes a section
 - All docs are `.md` (not .mdx)
 - Keep docs focused -- one topic per file
 - Use markdown tables for structured data
@@ -115,11 +111,11 @@ Dispatch a `general-purpose` subagent with the plan, conversation context, and t
 If Step 1 resolved a task ID, save the current state to `prj_tasks.resume_context` via the SDK CLI. This is the canonical persistence step and must run every `/save` invocation that has a task in scope:
 
 ```bash
-pnpm exec elevasis-sdk project:task:save <task-uuid> \
+pnpm elevasis-sdk project:task:save <task-uuid> \
   --current-state "<concise prose summary of where we are>" \
   --next-steps "<concise prose of the next concrete action>" \
   --files-modified '["path/one.ts","path/two.tsx"]' \
-  --key-docs '["docs/knowledge/foo.md"]' \
+  --key-docs '["operations/resources/foo/index.ts"]' \
   --tools '["project:task:save","project:note:create"]'
 ```
 
@@ -138,7 +134,7 @@ The endpoint is `PATCH /api/external/tasks/<id>/resume-context` and merges (does
 For each signal event identified in Step 2, create a typed `prj_note`. One CLI call per note:
 
 ```bash
-pnpm exec elevasis-sdk project:note:create \
+pnpm elevasis-sdk project:note:create \
   --project <project-uuid> \
   --task <task-uuid>          # optional, omit if not scoped to a task \
   --type <note-type> \
@@ -169,17 +165,7 @@ Rules:
 - **Idempotent** -- if the task is already `blocked`, the update is a no-op. Fire it anyway; do not pre-check.
 - **Order** -- the `blocker` note (Step 5) creates first; this transition follows. Keeps the note attached to the task even if the status update later fails.
 
-### Step 6: Regenerate Docs Index
-
-After the Step 3 subagent completes all doc file changes, regenerate `docs/index.md`:
-
-```bash
-pnpm exec elevasis-sdk generate-docs
-```
-
-This deterministically scans `docs/`, reads frontmatter, and rebuilds the navigation hub. Never edit `docs/index.md` manually.
-
-### Step 7: Report
+### Step 6: Report
 
 Summarize:
 
@@ -194,4 +180,4 @@ Summarize:
 
 - **No task in scope + user declines to provide one:** proceed with Steps 2, 3, 6, 7; skip Step 4; still allow Step 5 if a `--project` UUID is available.
 - **`project:task:save` returns non-2xx:** surface the error in the report, do not retry silently; Step 5 and Step 6 still run.
-- **`generate-docs` fails:** surface the error; doc edits from Step 3 are already on disk, so they are not lost -- the operator can re-run the index regeneration manually.
+- **Knowledge doc edits fail to write:** surface the error; any edits already applied are on disk and not lost.

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

@@ -143,29 +143,44 @@ After all replacements, re-scan the four key files from State Detection to verif
 
 If the user skipped any knowledge questions, fill in what was provided and omit what wasn't -- don't leave placeholder text behind.
 
-### Step 5: Create Client Knowledge Doc
+### Step 5: Write Client Brief to Org Model
 
-**Idempotency check:** Check whether `docs/knowledge/client.md` already exists. If it exists and is non-empty, skip this step entirely -- do not overwrite.
+**Idempotency check:** Read `foundations/config/organization-model.ts` and inspect `identity.clientBrief`. If the field is already a non-empty string, skip this step entirely — do not overwrite.
 
-If it does not exist, create `docs/knowledge/client.md`:
+If the field is empty or absent, compose the client brief from the information gathered in Step 2:
 
 ```markdown
----
-title: Client Context
-description: Company background, industry, stakeholders, and business goals
----
-
-# Client Context
-
 **Company:** {company name}
 **Industry:** {industry}
 **Description:** {what they do}
 
 ## Additional Context
 
-{any additional context shared -- key stakeholders, business goals, constraints, etc. If nothing was shared, write "No additional context provided yet. Update this as the project evolves."}
+{any additional context shared — key stakeholders, business goals, constraints, etc. If nothing was shared, write "No additional context provided yet. Update this as the project evolves."}
+```
+
+Propose the composed content to the user before writing (read → propose → confirm → write — the same ceremony `/configure` uses):
+
+```
+Here's the client brief I'll write into identity.clientBrief:
+
+---
+{composed content}
+---
+
+Write this? (yes/no)
 ```
 
+On confirmation, use the Edit tool to replace the `clientBrief: ''` value in `foundations/config/organization-model.ts` with a template literal containing the composed markdown. Use a regular string (backtick or single-quoted multi-line) — ensure the closing quote and trailing comma are correct TypeScript.
+
+After the edit, run:
+
+```bash
+pnpm -C foundations check-types
+```
+
+If type-check fails, report the error and do not proceed to Step 6 until it is resolved.
+
 ### Step 6: Install and Verify
 
 #### Step 6a: Install Dependencies
@@ -242,8 +257,8 @@ Running `/setup` more than once is safe:
 
 - **Placeholder replacement** only runs when placeholders are detected (State A). It is skipped entirely in States B and C.
 - **CLAUDE.md knowledge sections** (`{CLIENT_CONTEXT}`, `{USER_PREFERENCES}`) are checked before writing. If already replaced, the write is skipped.
-- **`docs/knowledge/client.md`** is only created if it does not exist. An existing file is never overwritten by `/setup`.
-- **Org-model fields** (`foundations/config/organization-model.ts`) are never written by `/setup`. All org-model edits go through `/configure`, which has its own diff-preview and confirm ceremony.
+- **`identity.clientBrief`** is only written when the field is empty. A non-empty field is never overwritten by `/setup`. The write uses a read → propose → confirm ceremony before touching the file.
+- **All other org-model fields** (`foundations/config/organization-model.ts`) are never written by `/setup`. All other org-model edits go through `/configure`, which has its own diff-preview and confirm ceremony.
 
 ---
 
@@ -253,7 +268,8 @@ Running `/setup` more than once is safe:
 
 1. Replaces scaffold placeholders (project name, slug, description)
 2. Fills lightweight CLAUDE.md knowledge sections (user and client basics, idempotent)
-3. Installs dependencies and verifies the build
-4. Hands off to `/configure` for org-model configuration
+3. Writes the client brief into `identity.clientBrief` in the org model (confirm-before-write, idempotent)
+4. Installs dependencies and verifies the build
+5. Hands off to `/configure` for full org-model configuration
 
-`/configure` owns all structural org-model editing (identity, customers, offerings, roles, goals, techStack, features, labels). It is idempotent, confirm-before-overwrite, and includes a runtime validation gate. Re-run `/configure` any time organizational reality changes — no need to re-run `/setup`.
+`/configure` owns all other structural org-model editing (identity fields beyond clientBrief, customers, offerings, roles, goals, techStack, features, labels). It is idempotent, confirm-before-overwrite, and includes a runtime validation gate. Re-run `/configure` any time organizational reality changes — no need to re-run `/setup`.

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

@@ -20,10 +20,9 @@ Run in parallel:
 3. `pnpm test` - test results
 4. `pnpm lint` - type check
 
-### Step 2: Check Docs + Active Work
+### Step 2: Check Active Work
 
-1. Read `docs/index.md` - verify doc structure is current
-2. Query active project work via `pnpm -C operations exec elevasis-sdk project:list --status active,blocked --format brief` - active project/task count lives in the DB, not in `docs/in-progress/`
+1. Query active project work via `pnpm elevasis-sdk project:list --status active --pretty` and `pnpm elevasis-sdk project:list --status blocked --pretty` - active project/task count lives in the DB
 
 ### Step 3: Report
 

package/reference/claude-config/skills/submit-request/SKILL.md

@@ -154,7 +154,7 @@ Once confirmed (or `--auto`), write the assembled JSON body to a temp file then
 # Write the report body to a temp file
 # (Use the Write tool to create request-report.json at the project root)
 
-pnpm exec elevasis-sdk request:submit --input-file ./request-report.json --pretty
+pnpm elevasis-sdk request:submit --input-file ./request-report.json --pretty
 ```
 
 Delete the temp file after submission succeeds or fails.

package/reference/deployment/command-center.mdx

@@ -14,7 +14,6 @@ The Command Center is the browser UI for interacting with deployed resources. Af
 | -------------------------------------------------- | -------------- | ----------------------- |
 | Browse deployed resources, view the resource graph | Command View   | `/command-view`         |
 | Approve or reject pending HITL requests            | Command Queue  | `/queue`                |
-| Browse deployed documentation                      | Knowledge Base | `/knowledge-base`       |
 | Search execution history across all resources      | Execution Logs | `/logs`                 |
 | Create API key and OAuth credentials               | Credentials    | `/settings/credentials` |
 | View deployment history and active version         | Deployments    | `/settings/deployments` |
@@ -147,22 +146,6 @@ const task = await approval.create({
 
 ---
 
-## Knowledge Base
-
-The Knowledge Base renders the `docs/` directory of your deployed workspace as browsable documentation.
-
-**What you can do here:**
-
-- Browse pages you created in `docs/*.mdx`
-- Search across all documentation
-- Share links to specific pages with team members
-
-**How it connects to your code:** Every `.mdx` file in your workspace's `docs/` directory is bundled at deploy time and rendered here.
-
-> **SDK takeaway:** Write `docs/*.mdx` pages for your team -- business process docs, schema references, usage guides. They appear here automatically after each deploy.
-
----
-
 ## Execution Logs
 
 The Execution Logs page shows the history of all executions across every deployed resource.

package/reference/framework/project-structure.mdx

@@ -45,7 +45,7 @@ Cross-runtime types, schemas, constants, and organization-model configuration sh
 
 ### `operations/elevasis.config.ts`
 
-Project-level configuration. The scaffolded file includes commented-out options (`defaultStatus`, `dev.port`) and sets `docsDir` to point at the workspace-level `docs/` directory:
+Project-level configuration. The scaffolded file includes commented-out options (`defaultStatus`, `dev.port`):
 
 ```ts
 import type { ElevasConfig } from '@elevasis/sdk'
@@ -53,13 +53,9 @@ import type { ElevasConfig } from '@elevasis/sdk'
 export default {
   // defaultStatus: 'dev',     // Default status for new resources ('dev' | 'prod')
   // dev: { port: 5170 },      // Local API port (internal development only)
-
-  docsDir: '../docs' // Scan the template's top-level docs/ directory
 } satisfies ElevasConfig
 ```
 
-The `docsDir` option (relative to CWD) overrides where the CLI scans for documentation files. Use `false` to disable documentation scanning entirely.
-
 ---
 
 ## Documentation

package/reference/packages/ui/src/hooks/README.md

@@ -8,7 +8,7 @@ The hooks barrel is the published headless hook surface for the UI package.
 - Scheduling hooks
 - Monitoring, observability, and notification hooks
 - Session and SSE hooks
-- Operations hooks, including command-view and knowledge-base helpers
+- Operations hooks, including command-view helpers
 - Feature access, table state, and service helpers
 - Acquisition and delivery hooks
 
@@ -21,4 +21,3 @@ The hooks barrel is the published headless hook surface for the UI package.
 ## Notes
 
 - This barrel is intentionally headless. It should not pull in the visual component layer.
-

package/reference/scaffold/operations/propagation-pipeline.md

@@ -30,11 +30,11 @@ Layer 3: Sync Verification (pnpm sync:verify)
 
 `pnpm scaffold:sync` is the meta-script that regenerates all derived documentation and validates the output. It chains three sub-scripts:
 
-| Script                                  | Input                                                                                                                                         | Output                                                                                                                    |
-| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
-| `generate-scaffold-contracts.js`        | `packages/core/src/organization-model/types.ts`, `packages/ui/src/features/registry/types.ts`, `packages/core/src/platform/registry/types.ts` | `packages/core/src/reference/_generated/contracts.md`                                                                     |
-| `generate-scaffold-feature-registry.js` | `packages/ui/src/features/*/manifest.ts`, `packages/core/src/organization-model/domains/features.ts`                                          | `packages/ui/src/scaffold/_generated/feature-registry.md`                                                                 |
-| `generate-reference-artifacts.js`       | SDK manifest, navigation sources                                                                                                              | `packages/sdk/reference/_reference-manifest.json`, `_navigation.md`, `external/_template/docs/platform-navigation-map.md` |
+| Script                                  | Input                                                                                                                                         | Output                                                              |
+| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
+| `generate-scaffold-contracts.js`        | `packages/core/src/organization-model/types.ts`, `packages/ui/src/features/registry/types.ts`, `packages/core/src/platform/registry/types.ts` | `packages/core/src/reference/_generated/contracts.md`               |
+| `generate-scaffold-feature-registry.js` | `packages/ui/src/features/*/manifest.ts`, `packages/core/src/organization-model/domains/features.ts`                                          | `packages/ui/src/scaffold/_generated/feature-registry.md`           |
+| `generate-reference-artifacts.js`       | SDK manifest, navigation sources                                                                                                              | `packages/sdk/reference/_reference-manifest.json`, `_navigation.md` |
 
 After generation, `validate-reference-artifacts.js` checks that the outputs are consistent. Exit 1 if drifted.
 
@@ -55,11 +55,11 @@ Drift is healed at the moment it would otherwise leak downstream. This is cheape
 
 `/external sync` propagates the `external/_template` to downstream projects. It uses a three-tier model:
 
-| Tier                           | Policy                                    | Examples                                                            |
-| ------------------------------ | ----------------------------------------- | ------------------------------------------------------------------- |
+| Tier                           | Policy                                    | Examples                                                              |
+| ------------------------------ | ----------------------------------------- | --------------------------------------------------------------------- |
 | **Tier 1 (Infrastructure)**    | Always replaced from template             | Configs, shared runtime surfaces, `lib/`, `test-utils/`, entry points |
-| **Tier 2 (Standard Features)** | Synced unless project has customized them | Standard UI features, common patterns                               |
-| **Tier 3 (Project-Specific)**  | Never touched                             | `nav-items.ts`, `operations/src/`, `docs/`, `CLAUDE.md`             |
+| **Tier 2 (Standard Features)** | Synced unless project has customized them | Standard UI features, common patterns                                 |
+| **Tier 3 (Project-Specific)**  | Never touched                             | `nav-items.ts`, `operations/src/`, `docs/`, `CLAUDE.md`               |
 
 The sync skill doc (`.claude/skills/external/SKILL.md`) defines the full tier model and phase sequence.
 
@@ -78,8 +78,7 @@ The sync skill doc (`.claude/skills/external/SKILL.md`) defines the full tier mo
 | `org-os`       | Organization model exists, exports canonical symbols, imports from `@elevasis/core/organization-model`, calls `defineOrganizationModel` + `resolveOrganizationModel`, app-config references org model, `__root.tsx` uses `ElevasisFeaturesProvider` + `canonicalOrganizationModel`, `main.tsx` uses `ElevasisUIProvider`, all 3 CSS subpath imports present |
 | `placeholders` | No unresolved `__PROJECT_SLUG__`, `__PROJECT_NAME__`, `__PROJECT_DESCRIPTION__` in key config files                                                                                                                                                                                                                                                         |
 | `scripts`      | `ui` and `operations` `package.json` have required npm scripts                                                                                                                                                                                                                                                                                              |
-| `generated-docs` | `docs/index.md` and `docs/resources.md` are current with `pnpm exec elevasis-sdk generate-docs` and `pnpm exec elevasis-sdk generate-resources`; `pnpm exec elevasis-sdk validate-docs` passes                                                                                                                                                                                                            |
-| `lib`          | `ui/src/lib/`, `lib/`, `test-utils/` exist with minimum file counts                                                                                                                                                                                                                                                                                      |
+| `lib`          | `ui/src/lib/`, `lib/`, `test-utils/` exist with minimum file counts                                                                                                                                                                                                                                                                                         |
 | `tier3`        | `nav-items.ts` has project-specific customization (not overwritten by template)                                                                                                                                                                                                                                                                             |
 | `conflicts`    | No merge conflict markers in source files                                                                                                                                                                                                                                                                                                                   |
 | `git`          | Working tree is clean                                                                                                                                                                                                                                                                                                                                       |

package/reference/scaffold/operations/scaffold-maintenance.md

@@ -71,7 +71,6 @@ Generated by `scripts/monorepo/generate-reference-artifacts.js`:
 
 - `packages/sdk/reference/_reference-manifest.json` -- machine-readable catalog of all reference entries
 - `packages/sdk/reference/_navigation.md` -- navigation table
-- `external/_template/docs/platform-navigation-map.md` -- cross-package reference map for external projects
 
 ### Running Generators
 
@@ -120,6 +119,4 @@ The output lands in `packages/sdk/reference/` which is included in the npm packa
 
 ## Freshness Validation
 
-External projects validate generated docs with `pnpm check:autogenerated-docs`, which now calls `pnpm exec elevasis-sdk validate-docs`. The legacy `scripts/validate-autogenerated-docs.mjs` file may still exist as a temporary compatibility shim in the template, but the SDK CLI is the canonical path.
-
-At the monorepo level, `pnpm scaffold:sync` followed by `pnpm sync:verify` confirms that all artifacts are current and all downstream projects are consistent.
+At the monorepo level, `pnpm scaffold:sync` followed by `pnpm sync:verify` confirms that all artifacts are current and all downstream projects are consistent. The SDK no longer ships doc validation because external projects no longer carry a `docs/` tree.

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

@@ -109,7 +109,7 @@ const org: DeploymentSpec = {
 }
 ```
 
-Full relationship and checkpoint types are defined in `@elevasis/sdk` (`DeploymentSpec`). The generated `docs/resources.md` topology map will reflect these in the Topology Relationships, Triggers, and Human Checkpoints sections after regeneration.
+Full relationship and checkpoint types are defined in `@elevasis/sdk` (`DeploymentSpec`). Resources are discovered live via `pnpm elevasis-sdk project:list` or by globbing `operations/resources/**` directly.
 
 ---
 
@@ -133,18 +133,9 @@ See `OrganizationModelResourceMapping` in [contracts.md](../reference/contracts.
 
 ---
 
-## 5. Regenerate the topology map
+## 5. Verify resource inventory
 
-```bash
-pnpm exec elevasis-sdk generate-resources
-```
-
-Open `docs/resources.md` and confirm:
-
-- Section 1 (Workflows table) lists the new resource with correct `resourceId`, `version`, and `status`.
-- Section 2 (Topology Relationships) shows any declared `relationships` edges.
-- Sections 3-6 (Triggers, Integrations, Human Checkpoints, External Resources) show any relevant declarations.
-- Section 7 (Schema Signatures) includes the new resource's input/output field list.
+Resources are discovered live via `pnpm elevasis-sdk project:list` or by globbing `operations/resources/**` directly. Confirm the new resource appears with the correct `resourceId`, `version`, and `status`.
 
 ---
 

package/reference/scaffold/reference/contracts.md

@@ -1,4 +1,4 @@
-<!-- Auto-generated on 2026-04-20T23:27:16.482Z by scripts/monorepo/generate-scaffold-contracts.js -->
+<!-- Auto-generated on 2026-04-21T05:52:18.229Z by scripts/monorepo/generate-scaffold-contracts.js -->
 ---
 title: Reference Contracts
 description: Auto-generated TypeScript contracts for SDK consumers. Do not edit manually.