@elevasis/sdk 1.36.5 → 1.38.0

package/dist/test-utils/index.js

@@ -7561,17 +7561,13 @@ var AcqListMetadataSchema = z.object({
 }).catchall(z.unknown());
 var ProspectingBuildTemplateIdSchema = z.string().trim().min(1).max(100);
 var ListStageCountsSchema = z.object({
-  // Attempted counts by canonical lead-gen stage. The detailed status
-  // distribution lives on ListProgress; telemetry keeps the overview payload small.
-  stageCounts: z.object({
-    populated: z.number().int(),
-    extracted: z.number().int(),
-    qualified: z.number().int(),
-    discovered: z.number().int(),
-    verified: z.number().int(),
-    personalized: z.number().int(),
-    uploaded: z.number().int()
-  }),
+  // Attempted counts keyed by the tenant's declared lead-gen stage catalog IDs.
+  // The catalog is tenant-owned and OM-derived at compute time; the schema
+  // validates the transport shape (string keys → integer values) rather than
+  // a fixed key set, so tenants with custom stages receive complete telemetry.
+  // Canonical Elevasis stages (populated, extracted, qualified, discovered,
+  // verified, personalized, uploaded) are included when declared in the catalog.
+  stageCounts: z.record(z.string().min(1), z.number().int()),
   deliverability: z.object({
     valid: z.number().int(),
     risky: z.number().int(),
@@ -8775,17 +8771,48 @@ var SYSTEM_INTERFACE_PROFILES = [
 var SYSTEM_INTERFACE_READINESS_PROFILES = SYSTEM_INTERFACE_PROFILES.map(
   (profile) => profile.readinessProfile
 );
-var SystemInterfaceReadinessProfileSchema = z.enum(SYSTEM_INTERFACE_READINESS_PROFILES);
+var SystemInterfaceReadinessProfileSchema = z.string().trim().min(1);
 var SystemInterfaceResourceScopeSchema = z.array(ModelIdSchema).default([]);
+var SystemApiInterfaceReadinessContractSchema = z.object({
+  /** Ontology IDs of object types the interface depends on. */
+  requiredObjects: z.array(z.string().trim().min(1)).default([]),
+  /** Ontology IDs of catalog types the interface requires (must be non-empty). */
+  requiredCatalogs: z.array(z.string().trim().min(1)).default([]),
+  /** Optional ontology kind filters (reserved for future profile extensions). */
+  requiredKinds: z.array(z.string().trim().min(1)).optional()
+}).strict();
 var SystemApiInterfaceSchema = z.object({
   lifecycle: SystemInterfaceLifecycleSchema.default("active"),
+  /**
+   * Open-string profile id. Built-in platform presets are looked up through
+   * the profile registry; custom ids are validated structurally via
+   * `readinessContract`. Optional — `profileForInterface` provides a default.
+   */
   readinessProfile: SystemInterfaceReadinessProfileSchema.optional(),
   /**
    * Resource ids that participate in this API interface. This scopes readiness
    * derivation without duplicating authored required/provided contract refs.
    */
-  resourceIds: SystemInterfaceResourceScopeSchema.optional()
+  resourceIds: SystemInterfaceResourceScopeSchema.optional(),
+  /**
+   * Tenant-authorable readiness declaration. Required for custom
+   * (non-built-in) profile ids so structural validation can proceed. Built-in
+   * profiles ignore this field (requirements are derived from platform code).
+   */
+  readinessContract: SystemApiInterfaceReadinessContractSchema.optional()
 }).strict();
+var _profileRegistry = new Map(
+  SYSTEM_INTERFACE_READINESS_PROFILES.map((profileId) => [
+    profileId,
+    { profileId, kind: "built-in" }
+  ])
+);
+function profileForInterface(systemPath, interfaceKey, readinessProfile) {
+  return readinessProfile ?? `${systemPath}.${interfaceKey}`;
+}
+function isBuiltInReadinessProfile(profileId) {
+  return _profileRegistry.get(profileId)?.kind === "built-in";
+}
 z.object({
   systemPath: SystemPathSchema,
   interfaceKey: SystemInterfaceKeySchema
@@ -8926,6 +8953,7 @@ function getLeadGenStageCatalog(model) {
       );
       const recordEntity = entry.recordEntity === "company" || entry.recordEntity === "contact" ? entry.recordEntity : void 0;
       const recordStageKey = stringValue(entry.recordStageKey);
+      const readinessTarget = entry.readinessTarget === true ? true : void 0;
       results[entryId] = {
         key: entryId,
         label: stringValue(entry.label) ?? entryId,
@@ -8934,7 +8962,8 @@ function getLeadGenStageCatalog(model) {
         entity,
         ...additionalEntities.length > 0 ? { additionalEntities } : {},
         ...recordEntity ? { recordEntity } : {},
-        ...recordStageKey ? { recordStageKey } : {}
+        ...recordStageKey ? { recordStageKey } : {},
+        ...readinessTarget ? { readinessTarget } : {}
       };
     }
   }
@@ -9032,14 +9061,11 @@ function addReadinessIssue(issues, family, code, message, details = {}) {
 function formatInterfaceIdentity(systemPath, interfaceKey) {
   return `${systemPath}/${interfaceKey}`;
 }
-function profileForInterface(systemPath, interfaceKey, readinessProfile) {
-  return readinessProfile ?? `${systemPath}.${interfaceKey}`;
-}
 function readinessMarkerPath(context) {
   return context.interfaceKey === "api" ? `systems.${context.systemPath}.apiInterface` : `systems.${context.systemPath}.derivedCrmHandoffReadiness`;
 }
 function formatSupportedReadinessProfiles() {
-  return SYSTEM_INTERFACE_READINESS_PROFILES.map((profile) => `"${profile}"`).join(", ");
+  return SYSTEM_INTERFACE_PROFILES.map((p3) => `"${p3.readinessProfile}"`).join(", ");
 }
 function getActiveScopedResources(model, resourceIds, issues, context) {
   const resources = [];
@@ -9231,9 +9257,6 @@ function getLeadGenCrmHandoffResourceIds(model) {
 function getSystemInterfaceReadinessMarker(model, request) {
   const system = getSystem(model, request.systemPath);
   if (system === void 0) return void 0;
-  if (request.interfaceKey === LEAD_GEN_API_INTERFACE.interfaceKey) {
-    return system.apiInterface;
-  }
   if (request.systemPath === LEAD_GEN_CRM_HANDOFF_INTERFACE.systemPath && request.interfaceKey === LEAD_GEN_CRM_HANDOFF_INTERFACE.interfaceKey) {
     return {
       lifecycle: "active",
@@ -9241,6 +9264,9 @@ function getSystemInterfaceReadinessMarker(model, request) {
       resourceIds: getLeadGenCrmHandoffResourceIds(model)
     };
   }
+  if (request.interfaceKey === "api" && system.apiInterface !== void 0) {
+    return system.apiInterface;
+  }
   return void 0;
 }
 function mergeLeadGenDerivedCatalogs(model) {
@@ -9285,6 +9311,18 @@ function tryCompileBusinessOntology(model, readinessProfile, issues) {
     return void 0;
   }
 }
+function requireContractReadiness(issues, index2, resources, contract, context) {
+  const reads = resourceBindingIds(resources, "reads");
+  const catalogs = resourceBindingIds(resources, "usesCatalogs");
+  for (const objectId of contract.requiredObjects) {
+    requireObjectReadiness(issues, index2, objectId, context);
+    requireScopedBinding(issues, reads, "reads", objectId, context);
+  }
+  for (const catalogId of contract.requiredCatalogs) {
+    requireCatalogReadiness(issues, index2, catalogId, context);
+    requireScopedBinding(issues, catalogs, "usesCatalogs", catalogId, context);
+  }
+}
 function computeInterfaceReadiness(model, request) {
   const issues = [];
   const system = getSystem(model, request.systemPath);
@@ -9332,20 +9370,22 @@ function computeInterfaceReadiness(model, request) {
       { path: `${readinessMarkerPath(request)}.lifecycle` }
     );
   }
-  const supportedProfile = readinessProfile !== void 0 && SYSTEM_INTERFACE_PROFILES.some((profile) => profile.readinessProfile === readinessProfile);
-  if (!supportedProfile) {
+  const checkedReadinessProfile = readinessProfile ?? profileForInterface(request.systemPath, request.interfaceKey);
+  const isBuiltIn = isBuiltInReadinessProfile(checkedReadinessProfile);
+  const readinessContract = systemInterface.readinessContract;
+  if (!isBuiltIn && readinessContract === void 0) {
     addReadinessIssue(
       issues,
       "SYSTEM_INTERFACE_INVALID",
-      "unknown-readiness-profile",
-      `System Interface "${formatInterfaceIdentity(request.systemPath, request.interfaceKey)}" references unknown readiness profile "${readinessProfile}". Supported profiles: ${formatSupportedReadinessProfiles()}. Custom Systems should not declare apiInterface; route custom behavior through workflows/operations plus ontology, resources, and topology.`,
-      { path: `${readinessMarkerPath(request)}.readinessProfile`, ref: readinessProfile }
+      "missing-readiness-contract",
+      `System Interface "${formatInterfaceIdentity(request.systemPath, request.interfaceKey)}" uses custom readiness profile "${checkedReadinessProfile}" but declares no readinessContract. Built-in profiles: ${formatSupportedReadinessProfiles()}.`,
+      { path: `${readinessMarkerPath(request)}.readinessContract`, ref: checkedReadinessProfile }
     );
     return {
       ready: false,
       systemPath: request.systemPath,
       interfaceKey: request.interfaceKey,
-      readinessProfile,
+      readinessProfile: checkedReadinessProfile,
       scopedResourceIds,
       issues
     };
@@ -9359,10 +9399,6 @@ function computeInterfaceReadiness(model, request) {
       { path: `${readinessMarkerPath(request)}.resourceIds` }
     );
   }
-  const checkedReadinessProfile = readinessProfile;
-  if (checkedReadinessProfile === void 0) {
-    throw new Error("Supported readiness profile unexpectedly resolved to undefined");
-  }
   const resources = getActiveScopedResources(model, scopedResourceIds, issues, request);
   const index2 = tryCompileBusinessOntology(model, checkedReadinessProfile, issues);
   if (index2 !== void 0) {
@@ -9374,13 +9410,15 @@ function computeInterfaceReadiness(model, request) {
       requireLeadGenInterfaceReadiness(issues, index2, resources, request);
       requireCrmInterfaceReadiness(issues, index2, resources, { ...request, allowForeignOwner: true });
       requireHandoffBridgeReadiness(issues, model, request);
+    } else if (readinessContract !== void 0) {
+      requireContractReadiness(issues, index2, resources, readinessContract, request);
     }
   }
   return {
     ready: issues.length === 0,
     systemPath: request.systemPath,
     interfaceKey: request.interfaceKey,
-    readinessProfile,
+    readinessProfile: checkedReadinessProfile,
     scopedResourceIds,
     issues
   };

package/dist/worker/index.js

@@ -5537,17 +5537,13 @@ var AcqListMetadataSchema = z.object({
 }).catchall(z.unknown());
 var ProspectingBuildTemplateIdSchema = z.string().trim().min(1).max(100);
 var ListStageCountsSchema = z.object({
-  // Attempted counts by canonical lead-gen stage. The detailed status
-  // distribution lives on ListProgress; telemetry keeps the overview payload small.
-  stageCounts: z.object({
-    populated: z.number().int(),
-    extracted: z.number().int(),
-    qualified: z.number().int(),
-    discovered: z.number().int(),
-    verified: z.number().int(),
-    personalized: z.number().int(),
-    uploaded: z.number().int()
-  }),
+  // Attempted counts keyed by the tenant's declared lead-gen stage catalog IDs.
+  // The catalog is tenant-owned and OM-derived at compute time; the schema
+  // validates the transport shape (string keys → integer values) rather than
+  // a fixed key set, so tenants with custom stages receive complete telemetry.
+  // Canonical Elevasis stages (populated, extracted, qualified, discovered,
+  // verified, personalized, uploaded) are included when declared in the catalog.
+  stageCounts: z.record(z.string().min(1), z.number().int()),
   deliverability: z.object({
     valid: z.number().int(),
     risky: z.number().int(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.36.5",
+  "version": "1.38.0",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -58,9 +58,9 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/core": "0.51.0",
-    "@repo/typescript-config": "0.0.0",
-    "@repo/eslint-config": "0.0.0"
+    "@repo/eslint-config": "0.0.0",
+    "@repo/core": "0.54.0",
+    "@repo/typescript-config": "0.0.0"
   },
   "scripts": {
     "lint": "eslint src --max-warnings 0",

package/reference/claude-config/Overview.md

@@ -7,15 +7,21 @@ This file is a routing map for the skill and rule inventories. For live CLI capa
 
 ## What Lives Here
 
-| Surface | Purpose                       | Source of truth                                |
-| ------- | ----------------------------- | ---------------------------------------------- |
-| Skills  | Slash-command entry points    | `.claude/skills/*/SKILL.md`                    |
-| Rules   | Path-scoped operating context | `node_modules/@elevasis/sdk/reference/rules/`  |
-| Hooks   | Claude lifecycle automation   | `.claude/hooks/*.mjs`, `.claude/settings.json` |
-| CLI     | Live command + domain surface | `elevasis-sdk cli` (authoritative, run it)     |
+| Surface | Purpose                       | Source of truth                                          |
+| ------- | ----------------------------- | -------------------------------------------------------- |
+| Skills  | Slash-command entry points    | `.claude/skills/*/SKILL.md`                              |
+| Rules   | Path-scoped operating context | `operations/node_modules/@elevasis/sdk/reference/rules/` |
+| Hooks   | Claude lifecycle automation   | `.claude/hooks/*.mjs`, `.claude/settings.json`           |
+| CLI     | Live command + domain surface | `elevasis-sdk cli` (authoritative, run it)               |
 
 For CLI capability, run `elevasis-sdk cli` — it is the authoritative surface for what commands
-and domains are available. For architecture context, read `CLAUDE.md` first.
+and domains are available.
+
+**This file is template-owned and replaced by sync.** It holds guidance that is true for every
+project built from this template: structure, stack, commands, and the skill surface. Project-specific
+facts (identity, client context, user preferences) live in `CLAUDE.md`, which sync never overwrites.
+Tenant-specific operational quirks live in `OPERATIONS.md`. Do not copy content between them — each
+fact should exist in exactly one of the three, owned by whoever can correct it.
 
 ---
 
@@ -23,16 +29,109 @@ and domains are available. For architecture context, read `CLAUDE.md` first.
 
 This project is skill-first with an always-on ambient vibe layer:
 
-1. Load `CLAUDE.md` for project rules, stack, and the Ambient Vibe Layer contract.
+1. Read `operations/node_modules/@elevasis/sdk/reference/rules/agent-start-here.md` — it owns session
+   bootstrap and task-class routing. Then read `CLAUDE.md` for this project's identity and preferences,
+   and `OPERATIONS.md` for tenant-specific quirks that override generic guidance.
 2. Every natural-language message is silently classified into an intent (Capture, Query, Describe,
    Transition, Navigate, Codify, Toggle, Operate) before the agent responds — no slash command needed.
+   The classifier and intent definitions live in the bundled `vibe.md` rule.
 3. For explicit work, match intent to a skill in `.claude/skills/{name}/SKILL.md`.
-4. Load the relevant bundled rule from `node_modules/@elevasis/sdk/reference/rules/` for the area
+4. Load the relevant bundled rule from `operations/node_modules/@elevasis/sdk/reference/rules/` for the area
    being changed (the local `.claude/rules/*.md` files are thin pointers to these).
 5. Use `elevasis-sdk cli` for the live command/domain surface — do not answer "what can I do" from memory.
 
 ---
 
+## Project Structure
+
+```
+├── ui/                  # React frontend app
+├── operations/          # Platform workflows + agents
+├── core/                # Cross-runtime organization model, types, Zod schemas, constants
+├── .claude/             # Claude Code config (this file, skills, hooks)
+├── pnpm-workspace.yaml  # Workspace definition
+└── .env                 # Environment variables
+```
+
+| Resource             | Path                            |
+| -------------------- | ------------------------------- |
+| Source — Routes      | `ui/src/routes/`                |
+| Source — Features    | `ui/src/features/`              |
+| Source — Lib         | `ui/src/lib/`                   |
+| Source — Assets      | `ui/src/assets/`                |
+| Platform — Workflows | `operations/src/`               |
+| Platform — Config    | `operations/elevasis.config.ts` |
+| Core Types           | `core/`                         |
+
+**Standalone repo** — this project is NOT part of the Elevasis monorepo pnpm workspace. Git, gh, and
+CLI commands work directly here (the monorepo boundary hook does not apply).
+
+- Use `pnpm` exclusively — never `npm`
+- Path aliases: `@/*` maps to `ui/src/*`, `@core/*` maps to `core/*`
+- Frontend and platform code are separate runtimes — share only types via `core/`
+- Release-train migration guidance lands in `.claude/sync-notes/`; run `/git-sync` to pull and surface
+  new notes before doing any manual reconciliation
+
+---
+
+## Stack
+
+> **Package surface:** this project consumes `@elevasis/{sdk,ui,core}` from npm. The monorepo's
+> workspace-internal `@repo/elevasis-{core,operations}` packages are NOT installable here. See the
+> bundled `package-taxonomy.md` rule.
+
+### Frontend (`ui/`)
+
+| Layer        | Tech                                |
+| ------------ | ----------------------------------- |
+| UI           | React 19 + Mantine 8.2.7            |
+| Build        | Vite 8                              |
+| Language     | TypeScript 5.9 (strict)             |
+| Routing      | TanStack Router (file-based)        |
+| Server State | TanStack React Query                |
+| Client State | Zustand + Immer                     |
+| Charts       | Recharts via @mantine/charts        |
+| Graph Viz    | @xyflow/react (ReactFlow)           |
+| Icons        | @tabler/icons-react                 |
+| Testing      | Vitest                              |
+| Auth         | @elevasis/ui + AuthKit (WorkOS)     |
+| API Access   | `@elevasis/ui/api` (`useApiClient`) |
+
+### Platform (`operations/`)
+
+| Layer    | Tech                                              |
+| -------- | ------------------------------------------------- |
+| SDK      | @elevasis/sdk (workflows, agents, typed adapters) |
+| Language | TypeScript (strict, Node target)                  |
+| Schemas  | Zod                                               |
+| Deploy   | Elevasis Platform — see bundled `deployment.md`   |
+
+### Core (`core/`)
+
+Types and constants shared between frontend and platform workflows. Runtime-agnostic only — no
+React, no Node APIs, no SDK worker imports.
+
+---
+
+## Commands
+
+| Command                          | Purpose                                                       |
+| -------------------------------- | ------------------------------------------------------------- |
+| `pnpm -C ui dev`                 | Dev server (port 4300, `strictPort` — fails fast if occupied) |
+| `pnpm -C ui build`               | Type-check + production build                                 |
+| `pnpm -C ui test`                | Run frontend tests                                            |
+| `pnpm -C ui lint`                | Type-check only (no emit)                                     |
+| `pnpm -C operations check`       | Validate SDK resource definitions                             |
+| `pnpm -C operations deploy`      | Deploy resources — **targets production by default**          |
+| `pnpm -C operations deploy:prod` | Deploy resources to production (explicit `--prod`)            |
+
+> **Deploy targets are safety-critical and the resolution order has exceptions.** The authoritative
+> rule is the bundled `deployment.md`, which ships with the CLI version this project actually runs.
+> Read it before deploying — and check `OPERATIONS.md`, which records whether this specific tenant
+> has a working dev target at all.
+
+---
+
 ## Skills
 
 **Location:** `.claude/skills/`
@@ -41,6 +140,7 @@ Skills are the slash-command surface. Each skill is `.claude/skills/{name}/SKILL
 
 <!-- @generated:start:sync-overview-skills -->
 - **client** -- Client portfolio management -- list, resolve, inspect, and maintain client records and their lineage to companies, contacts, and source deals -- via the elevasis-sdk client:* CLI.
+- **deploy** -- Test, build, fix issues, then commit and push
 - **dsp** -- Dispatch subagents in parallel for implementation tasks
 - **elevasis** -- Elevasis platform operations -- check, deploy, execute, inspect, and debug SDK resources
 - **explore** -- Codebase exploration anchored to project documentation
@@ -60,29 +160,29 @@ Skills are the slash-command surface. Each skill is `.claude/skills/{name}/SKILL
 
 ## Rules
 
-**Location:** `node_modules/@elevasis/sdk/reference/rules/` (bundled with `@elevasis/sdk`)
+**Location:** `operations/node_modules/@elevasis/sdk/reference/rules/` (bundled with `@elevasis/sdk`)
 
 Path-scoped operating context loaded for substantial work in their areas. The project's local
 `.claude/rules/*.md` files are thin compatibility pointers; the authoritative content ships with
 the SDK and is listed here:
 
 <!-- @generated:start:sync-overview-rules -->
-- `node_modules/@elevasis/sdk/reference/rules/active-change-index.md` -- Bridge between stable scaffold docs and higher-volatility in-progress architecture work that may override assumptions for agents working in the template
-- `node_modules/@elevasis/sdk/reference/rules/agent-start-here.md` -- Canonical first-read for agents entering the template scaffold -- project continuity, task-class routing, and boundary resolution
-- `node_modules/@elevasis/sdk/reference/rules/deployment.md` -- Deployment workflow -- check-first, dev vs prod, version bumping, common errors
-- `node_modules/@elevasis/sdk/reference/rules/error-handling.md` -- Error handling -- ExecutionError vs PlatformToolError, retry logic, no auto-retry
-- `node_modules/@elevasis/sdk/reference/rules/execution.md` -- Execution model -- timeouts, memory, concurrency, org isolation, runtime constraints
-- `node_modules/@elevasis/sdk/reference/rules/frontend.md` -- Frontend conventions -- React, routing, state, styling, testing, pages
-- `node_modules/@elevasis/sdk/reference/rules/observability.md` -- Observability -- context.logger API, execution inspection, step-level context
-- `node_modules/@elevasis/sdk/reference/rules/operations.md` -- Platform workflows, agents, resource definitions, and deployment for the operations/ surface
-- `node_modules/@elevasis/sdk/reference/rules/organization-model.md` -- Edits to the canonical organization model go through /om
-- `node_modules/@elevasis/sdk/reference/rules/organization-os.md` -- Organization OS orientation -- the semantic contract layer relating Systems, Actions, ontology, resources, policies, roles, goals, and knowledge; consumed via published @elevasis/core / @elevasis/sdk
-- `node_modules/@elevasis/sdk/reference/rules/package-taxonomy.md` -- Package taxonomy (consumer view) -- external projects consume the published @elevasis/* surface only; workspace-internal @repo/elevasis-* packages are not installable here
-- `node_modules/@elevasis/sdk/reference/rules/platform.md` -- Platform conventions -- SDK workflows, agents, deployment, resource registry
-- `node_modules/@elevasis/sdk/reference/rules/shared-types.md` -- Core type boundary -- what belongs in core/types, import rules, schema conventions
-- `node_modules/@elevasis/sdk/reference/rules/task-tracking.md` -- In-progress task conventions -- doc format, status values, auto-save behavior
-- `node_modules/@elevasis/sdk/reference/rules/ui.md` -- UI shell, route structure, auth flow, API access, and template customization points for the ui/ surface
-- `node_modules/@elevasis/sdk/reference/rules/vibe.md` -- Ambient intent classifier -- routes natural-language input to intent buckets without a slash command; Codify and Toggle delegate to /om, Operate delegates to /elevasis
+- `operations/node_modules/@elevasis/sdk/reference/rules/active-change-index.md` -- Bridge between stable scaffold docs and higher-volatility in-progress architecture work that may override assumptions for agents working in the template
+- `operations/node_modules/@elevasis/sdk/reference/rules/agent-start-here.md` -- Canonical first-read for agents entering the template scaffold -- project continuity, task-class routing, and boundary resolution
+- `operations/node_modules/@elevasis/sdk/reference/rules/deployment.md` -- Deployment workflow -- check-first, dev vs prod, version bumping, common errors
+- `operations/node_modules/@elevasis/sdk/reference/rules/error-handling.md` -- Error handling -- ExecutionError vs PlatformToolError, retry logic, no auto-retry
+- `operations/node_modules/@elevasis/sdk/reference/rules/execution.md` -- Execution model -- timeouts, memory, concurrency, org isolation, runtime constraints
+- `operations/node_modules/@elevasis/sdk/reference/rules/frontend.md` -- Frontend conventions -- React, routing, state, styling, testing, pages
+- `operations/node_modules/@elevasis/sdk/reference/rules/observability.md` -- Observability -- context.logger API, execution inspection, step-level context
+- `operations/node_modules/@elevasis/sdk/reference/rules/operations.md` -- Platform workflows, agents, resource definitions, and deployment for the operations/ surface
+- `operations/node_modules/@elevasis/sdk/reference/rules/organization-model.md` -- Edits to the canonical organization model go through /om
+- `operations/node_modules/@elevasis/sdk/reference/rules/organization-os.md` -- Organization OS orientation -- the semantic contract layer relating Systems, Actions, ontology, resources, policies, roles, goals, and knowledge; consumed via published @elevasis/core / @elevasis/sdk
+- `operations/node_modules/@elevasis/sdk/reference/rules/package-taxonomy.md` -- Package taxonomy (consumer view) -- external projects consume the published @elevasis/* surface only; workspace-internal @repo/elevasis-* packages are not installable here
+- `operations/node_modules/@elevasis/sdk/reference/rules/platform.md` -- Platform conventions -- SDK workflows, agents, deployment, resource registry
+- `operations/node_modules/@elevasis/sdk/reference/rules/shared-types.md` -- Core type boundary -- what belongs in core/types, import rules, schema conventions
+- `operations/node_modules/@elevasis/sdk/reference/rules/task-tracking.md` -- In-progress task conventions -- doc format, status values, auto-save behavior
+- `operations/node_modules/@elevasis/sdk/reference/rules/ui.md` -- UI shell, route structure, auth flow, API access, and template customization points for the ui/ surface
+- `operations/node_modules/@elevasis/sdk/reference/rules/vibe.md` -- Ambient intent classifier -- routes natural-language input to intent buckets without a slash command; Codify and Toggle delegate to /om, Operate delegates to /elevasis
 <!-- @generated:end:sync-overview-rules -->
 
 ---
@@ -113,10 +213,18 @@ Use the owning skill instead of guessing from the name alone:
 
 ## Scaffold Maintenance
 
-| Action                                 | Command or file                             |
-| -------------------------------------- | ------------------------------------------- |
-| Refresh the Skills + Rules lists above | `pnpm gen:overview` (run from the monorepo) |
+This file is maintained upstream in the Elevasis monorepo template
+(`external/_template/.claude/Overview.md`) and delivered to this project via template
+sync (`/git-sync`). **The whole file is replace-managed** -- not just the generated blocks.
+Any local edit here is overwritten on the next sync, so corrections belong upstream, where
+every project receives them.
+
+The blocks marked `<!-- @generated:start:... -->` / `<!-- @generated:end -->` are additionally
+machine-written by `pnpm gen:overview` in the monorepo; do not hand-edit them even upstream.
+
+There is no monorepo command to run from inside this project; refreshes happen upstream and
+arrive through the normal sync flow.
 
-The Skills section is generated from `external/_template/.claude/skills/*/SKILL.md` frontmatter, and
-the Rules section from the bundled rule source `packages/sdk/docs/agent-rules/*.md`, both by the
-monorepo `pnpm gen:overview` generator. Do not hand-edit the generated blocks.
+**If you were about to add project-specific detail to this file, stop** -- it will be lost.
+Project identity and preferences go in `CLAUDE.md`; tenant operational quirks go in
+`OPERATIONS.md`. Both are project-owned and never overwritten.

package/reference/claude-config/rules/active-change-index.md

@@ -6,6 +6,17 @@ description: Compatibility pointer for the canonical Active Change Index rule bu
 
 Canonical rule source:
 
-`node_modules/@elevasis/sdk/reference/rules/active-change-index.md`
+`operations/node_modules/@elevasis/sdk/reference/rules/active-change-index.md`
 
-Read that bundled rule before applying this rule. This local file is intentionally kept as a thin compatibility pointer for existing local rule references in skills, sync notes, and older prompts.
+When working in the monorepo template snapshot before dependencies are installed,
+use the repo-local generated fallback:
+
+`packages/sdk/reference/rules/active-change-index.md`
+
+If the generated fallback is stale or missing, use the source:
+
+`packages/sdk/docs/agent-rules/active-change-index.md`
+
+Read the bundled rule first when available. This local file is intentionally kept
+as a thin compatibility pointer for existing local rule references in skills,
+sync notes, and older prompts.

package/reference/claude-config/rules/agent-start-here.md

@@ -6,6 +6,17 @@ description: Compatibility pointer for the canonical Agent Start Here rule bundl
 
 Canonical rule source:
 
-`node_modules/@elevasis/sdk/reference/rules/agent-start-here.md`
+`operations/node_modules/@elevasis/sdk/reference/rules/agent-start-here.md`
 
-Read that bundled rule before applying this rule. This local file is intentionally kept as a thin compatibility pointer for existing local rule references in skills, sync notes, and older prompts.
+When working in the monorepo template snapshot before dependencies are installed,
+use the repo-local generated fallback:
+
+`packages/sdk/reference/rules/agent-start-here.md`
+
+If the generated fallback is stale or missing, use the source:
+
+`packages/sdk/docs/agent-rules/agent-start-here.md`
+
+Read the bundled rule first when available. This local file is intentionally kept
+as a thin compatibility pointer for existing local rule references in skills,
+sync notes, and older prompts.

package/reference/claude-config/rules/deployment.md

@@ -6,6 +6,17 @@ description: Compatibility pointer for the canonical Deployment rule bundled wit
 
 Canonical rule source:
 
-`node_modules/@elevasis/sdk/reference/rules/deployment.md`
+`operations/node_modules/@elevasis/sdk/reference/rules/deployment.md`
 
-Read that bundled rule before applying this rule. This local file is intentionally kept as a thin compatibility pointer for existing local rule references in skills, sync notes, and older prompts.
+When working in the monorepo template snapshot before dependencies are installed,
+use the repo-local generated fallback:
+
+`packages/sdk/reference/rules/deployment.md`
+
+If the generated fallback is stale or missing, use the source:
+
+`packages/sdk/docs/agent-rules/deployment.md`
+
+Read the bundled rule first when available. This local file is intentionally kept
+as a thin compatibility pointer for existing local rule references in skills,
+sync notes, and older prompts.

package/reference/claude-config/rules/error-handling.md

@@ -6,6 +6,17 @@ description: Compatibility pointer for the canonical Error Handling rule bundled
 
 Canonical rule source:
 
-`node_modules/@elevasis/sdk/reference/rules/error-handling.md`
+`operations/node_modules/@elevasis/sdk/reference/rules/error-handling.md`
 
-Read that bundled rule before applying this rule. This local file is intentionally kept as a thin compatibility pointer for existing local rule references in skills, sync notes, and older prompts.
+When working in the monorepo template snapshot before dependencies are installed,
+use the repo-local generated fallback:
+
+`packages/sdk/reference/rules/error-handling.md`
+
+If the generated fallback is stale or missing, use the source:
+
+`packages/sdk/docs/agent-rules/error-handling.md`
+
+Read the bundled rule first when available. This local file is intentionally kept
+as a thin compatibility pointer for existing local rule references in skills,
+sync notes, and older prompts.

package/reference/claude-config/rules/execution.md

@@ -6,6 +6,17 @@ description: Compatibility pointer for the canonical Execution rule bundled with
 
 Canonical rule source:
 
-`node_modules/@elevasis/sdk/reference/rules/execution.md`
+`operations/node_modules/@elevasis/sdk/reference/rules/execution.md`
 
-Read that bundled rule before applying this rule. This local file is intentionally kept as a thin compatibility pointer for existing local rule references in skills, sync notes, and older prompts.
+When working in the monorepo template snapshot before dependencies are installed,
+use the repo-local generated fallback:
+
+`packages/sdk/reference/rules/execution.md`
+
+If the generated fallback is stale or missing, use the source:
+
+`packages/sdk/docs/agent-rules/execution.md`
+
+Read the bundled rule first when available. This local file is intentionally kept
+as a thin compatibility pointer for existing local rule references in skills,
+sync notes, and older prompts.

package/reference/claude-config/rules/frontend.md

@@ -6,6 +6,17 @@ description: Compatibility pointer for the canonical Frontend rule bundled with
 
 Canonical rule source:
 
-`node_modules/@elevasis/sdk/reference/rules/frontend.md`
+`operations/node_modules/@elevasis/sdk/reference/rules/frontend.md`
 
-Read that bundled rule before applying this rule. This local file is intentionally kept as a thin compatibility pointer for existing local rule references in skills, sync notes, and older prompts.
+When working in the monorepo template snapshot before dependencies are installed,
+use the repo-local generated fallback:
+
+`packages/sdk/reference/rules/frontend.md`
+
+If the generated fallback is stale or missing, use the source:
+
+`packages/sdk/docs/agent-rules/frontend.md`
+
+Read the bundled rule first when available. This local file is intentionally kept
+as a thin compatibility pointer for existing local rule references in skills,
+sync notes, and older prompts.

package/reference/claude-config/rules/observability.md

@@ -6,6 +6,17 @@ description: Compatibility pointer for the canonical Observability rule bundled
 
 Canonical rule source:
 
-`node_modules/@elevasis/sdk/reference/rules/observability.md`
+`operations/node_modules/@elevasis/sdk/reference/rules/observability.md`
 
-Read that bundled rule before applying this rule. This local file is intentionally kept as a thin compatibility pointer for existing local rule references in skills, sync notes, and older prompts.
+When working in the monorepo template snapshot before dependencies are installed,
+use the repo-local generated fallback:
+
+`packages/sdk/reference/rules/observability.md`
+
+If the generated fallback is stale or missing, use the source:
+
+`packages/sdk/docs/agent-rules/observability.md`
+
+Read the bundled rule first when available. This local file is intentionally kept
+as a thin compatibility pointer for existing local rule references in skills,
+sync notes, and older prompts.