@elevasis/sdk 1.23.0 → 1.25.0

package/reference/claude-config/rules/task-tracking.md

@@ -1,47 +1,11 @@
----
-description: In-progress task conventions -- doc format, status values, auto-save behavior
----
-
-# Task Tracking
-
-## Status Values
-
-Exactly three values for frontmatter `status`: `planned`, `in-progress`, `complete`.
-
-## Doc Format
-
-- Frontmatter: `title`, `description`, `status` only -- nothing else belongs in task-doc frontmatter; `resume_context` is DB-canonical on `prj_tasks`
-- Sections: Objective, Plan, Progress, Resume Context
-- Progress subsections use markers: `### Step N: Title -- PENDING`, `-- IN PROGRESS`, `-- COMPLETE`
-
-## Auto-Update Behavior
-
-- When working on a tracked task, update the Progress section when a plan step transitions:
-  - PENDING -> IN PROGRESS (starting work on a step)
-  - IN PROGRESS -> COMPLETE (finishing a step)
-- Do NOT update on every action -- only on step transitions
-
-## Auto-Save Behavior
-
-The agent auto-saves progress (no user action needed) when:
-
-- The conversation context is getting heavy (many tool calls, large file reads)
-- The user appears to be wrapping up (thanks, goodbye, switching topics)
-- Significant progress has been made (2+ steps completed without saving)
-- Before a context reset
-
-Auto-save updates the task doc's Progress and Resume Context sections silently, then briefly confirms. The canonical persistence path is `pnpm elevasis-sdk project:task:save` -- the CLI writes through to `prj_tasks.resume_context` (JSONB) so another agent can resume without re-deriving intent.
-
-## Completion Suggestions
-
-When all plan steps are marked COMPLETE, **suggest** completing the task -- never auto-invoke. Ask: "All steps for '{task}' look done. Want me to finalize it?"
-
-## Where Tasks Live
-
-Project tasks for this template live in the `prj_tasks` Supabase table, not in repo-local files. Operate on them via the SDK CLI:
-
-- `pnpm elevasis-sdk project:work` -- entrypoint for task work (resume / new intent detection)
-- `pnpm elevasis-sdk project:list` -- portfolio / task listing
-- `pnpm elevasis-sdk project:task:save` -- persist progress + `resume_context` to the DB
-
-The monorepo-side `/work` slash command still exists for monorepo task docs under `apps/docs/content/docs/in-progress/**`; that flow is unchanged. What went away is the external template's own `/work` skill and its `docs/in-progress/` directory -- external projects now route through the DB-backed `project:*` surface above.
+---
+description: Compatibility pointer for the canonical Task Tracking rule bundled with @elevasis/sdk
+---
+
+# Task Tracking
+
+Canonical rule source:
+
+`node_modules/@elevasis/sdk/reference/rules/task-tracking.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.

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

@@ -1,200 +1,11 @@
----
-description: UI shell, route structure, auth flow, API access, and template customization points for the ui/ surface
-paths:
-  - ui/**
----
-
-# UI Features
-
-**Status:** Stable
-
-## App Shell Overview
-
-The template frontend is a React 19 + TanStack Router app that composes a local dashboard shell with published System modules from `@elevasis/ui`.
-
-The main join points are:
-
-- `ui/src/main.tsx` -- boots the app with `ElevasisUIProvider`, query client, theme config, WorkOS AuthKit, notifications, and the generated route tree
-- `ui/src/routes/__root.tsx` -- composes the authenticated shell with `ElevasisSystemsProvider`, published System modules, app-local dashboard nav, shell runtime dependencies, and `SystemShell`
-- `ui/src/config/nav-items.ts` -- keeps the host-local dashboard entry separate from the published feature manifests
-- `core/config/organization-model.ts` -- is the template's semantic source of truth, adapting `@elevasis/core/organization-model` into the preserved branding, dashboard label, quick-access, System labels, resource descriptors, and shell helpers
-
-Published System modules mounted by the template shell:
-
-- `lead-gen`
-- `crm`
-- `delivery` at `/projects`
-- `operations`
-- `monitoring`
-- `settings`
-
-Important distinction:
-
-- shared modules gate on current org-model System keys such as `sales.lead-gen` and `projects`
-- template routes and local nav may still use legacy aliases such as `crm`, `lead-gen`, and `projects`
-- `core/config/organization-model.ts` and `ui/src/lib/hooks/useFeatureAccess.ts` are the bridge between those two vocabularies
-
-Dashboard remains a host-local route at `/`, not a shared feature manifest.
-
-This template should be treated as the downstream reference implementation for this composition:
-
-- `core/config/organization-model.ts` owns the organization/runtime semantics
-- `ui/src/config/nav-items.ts` preserves the host-local dashboard entry instead of pushing that concern into shared manifests
-- `ui/src/routes/__root.tsx` threads `canonicalOrganizationModel` from `@core/config/organization-model` into `ElevasisSystemsProvider` so the shared shell/runtime uses the same semantic source of truth as the local template helpers
-- host-local customizations still stay local: dashboard remains app-owned nav, branding stays in app config, and quick-access/dashboard UX stays in the template app
-
-## Auth and Initialization
-
-The app uses WorkOS AuthKit through `ElevasisUIProvider`. Authentication is enforced by the local `ProtectedRoute` wrapper in `ui/src/features/auth/ProtectedRoute.tsx`.
-
-**Sign-in flow:**
-
-1. Unauthenticated user hits a protected route -- `ProtectedRoute` redirects to `/login?returnTo=<path>`
-2. `/login` renders a sign-in card; user clicks Sign In, triggering `signIn({ returnTo })` from `useAuth()`
-3. User authenticates on the WorkOS-hosted sign-in page
-4. WorkOS redirects back to `/auth-redirect` -- `ui/src/routes/auth-redirect.tsx` waits for auth to complete, then navigates to the requested path or `/`
-5. User lands on the home page, fully authenticated
-
-**Route protection:**
-
-Wrap protected route components with the local `ProtectedRoute` from `@/features/auth`, which adds the full-screen loader and delegates to the shared guard from `@elevasis/ui/auth`:
-
-```tsx
-import { ProtectedRoute } from '@/features/auth'
-
-function HomePageGuarded() {
-  return (
-    <ProtectedRoute>
-      <HomePage />
-    </ProtectedRoute>
-  )
-}
-```
-
-**Initialization state:**
-
-Use `useInitialization()` from `@elevasis/ui/initialization` anywhere inside the app to read aggregated auth + org readiness:
-
-```ts
-const { allReady, userReady, isInitializing, error, retry, profile } = useInitialization()
-```
-
-**Organization context:**
-
-Use `useOrganization()` from `@elevasis/ui/organization` to access org-scoped IDs and memberships:
-
-```ts
-const { currentWorkOSOrganizationId, currentSupabaseOrganizationId, memberships, switchOrganization } = useOrganization()
-```
-
-## API and Streaming
-
-Use `useApiClient()` from `@/lib/hooks/useApiClient` in route components and feature hooks:
-
-```ts
-const { apiRequest, isOrganizationReady } = useApiClient()
-const data = await apiRequest('/executions', { method: 'GET' })
-```
-
-The template also re-exports `useApiClientContext()` and the shared API client types from `@/lib/hooks/useApiClient`.
-
-For real-time updates, feature surfaces use the local singleton wrapper:
-
-```ts
-import { sseConnectionManager } from '@/lib/sse/SSEConnectionManager'
-```
-
-**WorkOS config:**
-
-WorkOS `clientId`, `redirectUri`, and `signoutUri` are hardcoded in `ui/src/config/workos.ts` -- no UI env vars are required to run the template. Edit that file if a fork needs a different WorkOS client. The dev server runs on port `4300` with Vite `strictPort: true`, so a second `pnpm -C ui dev` on the same machine fails fast instead of drifting.
-
-The API URL is centralized in `ui/src/lib/constants/api.ts`. In the current template it is hard-coded to `https://api.elevasis.io`, so if the bootstrap is repointed to another API target, that file is the source of truth.
-
-## Route Structure
-
-Current top-level app sections:
-
-- `/` -- host-local dashboard entrypoint with quick links derived from `organizationModel.navigation.quickAccessSurfaceIds`
-- `/lead-gen/*` -- lead generation pages (`lists`, `companies`, `contacts`)
-- `/crm/*` -- CRM overview, pipeline, and deals
-- `/projects/*` -- delivery feature pages (projects, milestones, tasks, notes)
-- `/operations/*` -- operations overview, resources, command queue, command view, sessions, task scheduler
-- `/monitoring/*` -- execution logs, execution health, activity log, cost analytics, notifications
-- `/settings/*` -- account, organization, credentials, API keys, deployments, webhooks, and appearance
-- `/login` and `/auth-redirect` -- auth entry/callback routes
-
-Section guards currently follow this pattern:
-
-- `ProtectedRoute` for all authenticated sections
-- `SystemGuard` on sections that should hard-stop when a System is disabled: `crm`, `lead-gen`, `projects`, `operations`, and `monitoring`
-- provider-level shell gating for shared System nav and sub-shell behavior
-
-The app shell in `__root.tsx` derives visible nav from `shellModel.systems` and `getSidebarLinks()`, filters admin-only entries locally using the signed-in profile, and passes `canonicalOrganizationModel` into `ElevasisSystemsProvider` so shared nav labels, paths, and graph runtime behavior resolve from the same organization-model semantic source.
-
-## Dashboard and Feature Areas
-
-**Dashboard**
-
-`ui/src/features/dashboard/components/Dashboard.tsx` is intentionally lightweight. It acts as the host-owned landing page and renders quick access cards for the most important organization surfaces instead of duplicating the shared operations overview.
-
-**Operations**
-
-The operations area is the richest shared shell in the template. It includes:
-
-- resource inventory and detail pages
-- command queue and command view
-- sessions screens
-- the shared operations overview at `/operations/`
-
-**Monitoring**
-
-Monitoring is scaffolded as a shared feature area with route files for:
-
-- activity log
-- cost analytics
-- execution health
-- execution logs
-- notifications
-
-## Customization Points
-
-The main template-owned customization surfaces are:
-
-- `ui/src/config/app-config.ts` -- brand name, logos, and app version
-- `ui/src/config/theme.ts` -- theme presets and defaults
-- `ui/src/config/background.tsx` -- shared background treatment
-- `ui/src/config/loader.tsx` -- global loader element
-- `ui/src/config/nav-items.ts` -- app-local nav entries, including the preserved dashboard/home entry
-- `core/config/organization-model.ts` -- product labels, System availability, resource descriptors, semantic surfaces, canonical-to-legacy surface aliases, and quick-access behavior
-- `ui/src/config/README.md` -- the deeper guide for those config files
-
-## Customizing System Sidebars
-
-The template demonstrates one override pattern in `ui/src/routes/__root.tsx`: it extends `CRM_ITEMS` with a template-owned Reports link and replaces `crmManifest` with `customCrmManifest` in the System module array. The backing route lives at `ui/src/routes/crm/reports.tsx` -- delete both the nav item and the route if you don't need them.
-
-Two customization layers are available for every shared System sidebar:
-
-1. **Nav-item shortcut (`items` prop)** -- when you just need to swap or extend the nav array, spread the published items constant and pass the result to `*SidebarMiddle`. The template's CRM customization uses this path.
-
-   ```tsx
-   import { crmManifest, CrmSidebar, CrmSidebarMiddle, CRM_ITEMS } from '@elevasis/ui/features/crm'
-   import type { NavItem } from '@elevasis/ui/layout'
-
-   const customItems: NavItem[] = [...CRM_ITEMS, { label: 'Reports', to: '/crm/reports', icon: IconFileText, exact: false }]
-   const CustomCrmSidebar = () => <CrmSidebar><CrmSidebarMiddle items={customItems} /></CrmSidebar>
-   const customCrmManifest = { ...crmManifest, sidebar: CustomCrmSidebar }
-   ```
-
-2. **Compose-primitives (structural changes)** -- when you need to inject panels, reorder sections, or add a new section, drop down to `CrmSidebarTop` + `SubshellNavList` + `SubshellSidebarSection` + published panels (`MyTasksPanel`, `QuickCreateActions`) and compose your own Middle.
-
-`manifest.sidebar` accepts any component, so arbitrary customization is always available. The `items` prop is an abstraction barrier for the common case, not a limit.
-
-See `node_modules/@elevasis/sdk/reference/scaffold/ui/customization.md` for the decision tree, page-wrapping pattern, and delivery's three-section variant. For broader CRM extension work across pages, hooks, actions, workflows, and org-model boundaries, start with `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-crm.md`. For broader lead-gen extension work across pages, hooks, list/member state, artifacts, workflows, and org-model boundaries, start with `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-lead-gen.md`. See `node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md` for `NavItem`, `SystemModule`, CRM platform primitives, Lead Gen platform primitives, and related TypeScript shapes.
-
-For CRM deal action buttons, read `node_modules/@elevasis/sdk/reference/scaffold/recipes/customize-crm-actions.md` before changing `crmActions`, `DealDetailPage`, `DealDrawer`, or custom workflow buttons. Start with the shared `crmActions` provider path for action visibility, labels, ordering, and render-time configuration. In v1, platform-known/default action endpoint behavior is server-constrained; use project-owned UI that calls the workflow directly when a custom key sits outside that server-dispatched set.
-
-## Notes
-
-- `ui/src/routeTree.gen.ts` is generated by TanStack Router tooling. Do not hand-edit it.
-- The template ships a broad route surface so downstream projects can trim or reshape features without having to re-derive the shared shell contract from scratch.
-- For package-export discovery, glob `node_modules/@elevasis/sdk/reference/` or `node_modules/@repo/ui/dist/` for the current SDK/UI package surface.
+---
+description: Compatibility pointer for the canonical Ui rule bundled with @elevasis/sdk
+---
+
+# Ui
+
+Canonical rule source:
+
+`node_modules/@elevasis/sdk/reference/rules/ui.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.

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

@@ -1,235 +1,11 @@
 ---
-description: Ambient intent classifier -- routes natural-language input to 7 intent buckets without a slash command; Codify and Toggle delegate to /om
-paths:
-  - "**/*"
+description: Compatibility pointer for the canonical Vibe rule bundled with @elevasis/sdk
 ---
 
-# Vibe Layer
+# Vibe
 
-Vibe is an **ambient, always-on** intent classifier. It activates automatically whenever the user speaks in plain language -- no slash command, no activation phrase, no special syntax. Every natural-language message passes through vibe classification before the agent acts.
+Canonical rule source:
 
-This rule applies to all sessions inside external projects. It does NOT apply in the monorepo (ambient routing is off there by default).
+`node_modules/@elevasis/sdk/reference/rules/vibe.md`
 
-## What Vibe Is
-
-Vibe is the translation layer between the user's natural language and the correct agent action. The user describes reality -- "we track deals by Shopify platform", "I'm stuck on this task", "what should I work on next" -- and vibe determines which of the seven intent types the message represents. The agent then routes to the right behavior without the user ever knowing the classification happened.
-
-Vibe coders (non-technical builders) are the primary audience. They build by describing. They never memorize commands, IDs, or schema. The ambient layer closes the gap between what they say and what the system can act on.
-
-## The Seven Intent Types
-
-### 1. Capture
-
-The user wants to record something new -- a task, a note, a piece of information that should persist.
-
-**Recognize by:** action verbs like "add", "create", "remember", "track", "log", "note down", "write down", combined with a thing to record.
-
-**Fixture examples:**
-
-| Input                                             | Why it's Capture                            |
-| ------------------------------------------------- | ------------------------------------------- |
-| "Add a task to follow up with the Shopify client" | Explicit "add a task" with a described item |
-| "Remember to run the campaign report on Friday"   | "Remember to" signals something to persist  |
-| "Run the campaign report every Friday at 9am"     | Repeating schedule vocabulary to persist    |
-| "Track this conversation as a deal note"          | Explicit "track" with a described artifact  |
-
-**Agent action:** draft the capture in plain language, confirm with the user, then execute via `elevasis-sdk project:*` commands for project records or `elevasis-sdk schedule:create` for recurring automation. Use repetition vocabulary ("every", "daily", "weekly", "monthly") for schedules; one-shot future reminders stay project tasks with due dates. Never write without confirmation.
-
-### 2. Query
-
-The user wants to know something about current state -- task priorities, what is pending, what is running, what failed.
-
-**Recognize by:** questions about the current list, status, or queue of things. Includes both static-model queries ("what systems are on?") and runtime-entity queries ("what's pending in the queue?"). Route Query to static-model sources (org model, Systems/Actions config) or runtime sources (operations domain) based on the referenced entity.
-
-**Fixture examples:**
-
-| Input                                        | Why it's Query                              |
-| -------------------------------------------- | ------------------------------------------- |
-| "What should I work on next?"                | Asking for prioritized task list            |
-| "What's pending in the HITL queue?"          | Runtime-entity query about operations state |
-| "What runs this week?"                       | Runtime query about upcoming schedules      |
-| "What systems are enabled for this project?" | Static-model query about Systems config     |
-
-**Agent action:** read the relevant source and narrate the answer in plain language. Use org model or `project:*` for project state, `elevasis-sdk queue:list --status pending --pretty` and `queue:status --pretty` for HITL queue state, and `elevasis-sdk schedule:list --status active --pretty` for upcoming recurring automation. No writes.
-
-### 3. Describe
-
-The user wants the agent to explain something -- a scope, an entity, a concept within the project.
-
-**Recognize by:** "what is", "what does", "tell me about", "explain", "where am I", "what's going on", "describe", "show me" without an action intent attached.
-
-**Fixture examples:**
-
-| Input                                      | Why it's Describe                                     |
-| ------------------------------------------ | ----------------------------------------------------- |
-| "What's going on with the ZentaraHQ deal?" | Asking for a plain-language description of an entity  |
-| "Tell me about the CRM system"             | Asking the agent to narrate what a model element does |
-| "Where am I in this project?"              | Asking for current scope narration                    |
-
-**Agent action:** read the relevant org-model label, entity, or scope. Narrate in plain language using label fields from the model -- never invent vocabulary not present in the model. Phase-1 scope covers Model, Systems/Actions, and Foundations layers only.
-
-**Stage/state/catalog sub-routing:** when the noun being described is a stage, state, status
-bucket, catalog entry, progress step, pipeline column, or similarly closed business vocabulary,
-also show the cross-system impact before the normal description:
-
-1. Read `node_modules/@elevasis/sdk/reference/spine/spine-primer.md` for the layering pattern.
-2. Read the relevant domain in `core/config/organization-model.ts`.
-3. Explain the impact in vibe-coder language only: the business profile entry, the saved progress
-   on each record, the automations that produce updates, and the dashboard or reports that read it.
-4. Route follow-up changes through `/om <domain>`. Do not mention the technical pattern name
-   unless the user explicitly asks for internals.
-
-### 4. Transition
-
-The user wants to change the status of a task or entity.
-
-**Recognize by:** single-word or short-phrase state signals -- "done", "finished", "complete", "blocked", "stuck", "waiting", "in review", "cancelled" -- applied to a current task or named entity.
-
-**Fixture examples:**
-
-| Input                                         | Why it's Transition                         |
-| --------------------------------------------- | ------------------------------------------- |
-| "Done with the proposal draft"                | "Done" + named artifact = status transition |
-| "Stuck -- blocked waiting on client feedback" | "Stuck" + reason = blocked transition       |
-| "Mark the onboarding task as complete"        | Explicit status-change vocabulary           |
-| "Approve the pending checkpoint"              | Selects an action from the HITL queue       |
-| "Pause the Friday report"                     | Changes schedule state                      |
-
-**Agent action:** identify the task, queue item, schedule, or entity being transitioned, confirm the new status/action with the user, then apply it via `elevasis-sdk project:task:save`, `elevasis-sdk queue:select <id> --action-id <id>`, `elevasis-sdk queue:expire <id>`, `elevasis-sdk schedule:pause <id>`, `schedule:resume <id>`, or `schedule:cancel <id>` as appropriate. Never auto-transition without confirmation if the target entity is ambiguous.
-
-### 5. Navigate
-
-The user wants to shift focus -- to a different task, project, System, Action, or layer of the model.
-
-**Recognize by:** focus-shift vocabulary -- "focus on", "let's look at", "switch to", "back to", "move to", "open", "go to" -- followed by a scope target.
-
-**Fixture examples:**
-
-| Input                                        | Why it's Navigate                                   |
-| -------------------------------------------- | --------------------------------------------------- |
-| "Let's focus on the onboarding flow for now" | "Focus on" + scope target                           |
-| "Switch to the Shopify integration project"  | "Switch to" = navigate to a different project scope |
-| "Back to the CRM tasks"                      | "Back to" = return to a prior scope                 |
-
-**Agent action:** update the active scope in `prj_tasks.resume_context` (current project + task pointer), then narrate the new scope in plain language so the user knows where they are.
-
-### 6. Codify
-
-The user describes organizational reality that is not yet expressed in the model -- industry type, entity kinds, custom attributes, renamed stages, domain vocabulary.
-
-**Recognize by:** declarative "we are" / "we use" / "we track" statements, repeated attribute mentions (second time the same attribute appears), or explicit "add a type / add a field / model X as Y" requests.
-
-**Fixture examples:**
-
-| Input                                                                            | Why it's Codify                                          |
-| -------------------------------------------------------------------------------- | -------------------------------------------------------- |
-| "We're an e-commerce company -- all our deals come from Shopify or Amazon"       | Declares industry + platform attributes not yet in model |
-| "We track deal stage as discovery, scoping, proposal, closed"                    | Describes custom CRM stages that should replace defaults |
-| "Add a project type called 'retainer' with monthly billing and a contract field" | Explicit request to add a new entity extension           |
-
-**Agent action:** delegate immediately to `/om`. Do not attempt the ceremony yourself. Invoke with the relevant domain: `/om sales` for deal/contact changes, `/om projects` for project types, `/om systems` for availability/routing toggles, and `/om actions` for invokable operation changes. Plain-language summary of what was detected is acceptable before delegating, but the actual draft-confirm-write ceremony belongs to `/om`.
-
-**Stage/state/catalog impact preview:** if the Codify intent adds, renames, removes, reorders, or
-re-scopes a stage, state, status bucket, catalog member, pipeline step, or progress vocabulary,
-preview the cross-system impact before delegating:
-
-- Which business-profile entry changes.
-- Which saved record progress keys may already exist.
-- Which automations or templates reference the key.
-- Which dashboard, report, queue, or API reads may display or filter by it.
-
-Then delegate to `/om <domain>` with that preview as context. Vibe does not write the
-change and does not expose monorepo-only commands.
-
-This routing applies to both codify levels (decision #21 -- Codify ceremony delegated to `/om`):
-
-- **Level A** (config-only edits to `organization-model.ts`, System availability/routing toggles, label renames): delegate to `/om <domain>` immediately.
-- **Level B** (new Zod extension files in `core/config/extensions/`): also delegate to `/om <domain>`; `/om` gates Level B to explicit user asks before scaffolding a new TS file.
-
-Vibe detects the intent and delegates in both cases. It does not run either pipeline itself.
-
-For "build/extend the CRM" asks, classify the structural org-model portion as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-crm.md` before editing. CRM work often spans org-model sales semantics, shared UI routes, hooks, workflow adapters, and deal actions; do not reduce it to only `sales` config or only UI.
-
-For "build/extend lead gen" / "campaign creator" / "outbound list state" asks, classify the structural org-model portion as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-lead-gen.md` before editing. Lead-gen work often spans org-model prospecting semantics, shared UI routes, hooks, list/member state, artifacts, and workflow adapters; do not reduce it to only `prospecting` config or only UI.
-
-For "add a custom CRM action" / "Send Quote button" asks, classify as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/customize-crm-actions.md` before editing. Start with the shared `crmActions` provider path for action visibility, labels, ordering, and render-time configuration. In v1, platform-known/default action endpoint behavior is server-constrained; use project-owned UI that calls the workflow directly when a custom key sits outside that server-dispatched set.
-
-Heuristics for when to propose codification (passed to `/om` as context):
-
-- First mention of a new attribute: note to `resume_context`, do not propose yet
-- Second mention OR explicit declaration ("we're ecom"): propose extension
-- Explicit ask ("track ecom deals separately"): propose immediately with fuller scope
-- Attribute appearing across 3+ tasks: propose adding field to existing extension
-
-### 7. Toggle
-
-The user wants to enable or disable a System.
-
-**Recognize by:** system-control vocabulary -- "turn on", "enable", "disable", "turn off", "activate", "deactivate" -- followed by a System name or description.
-
-**Fixture examples:**
-
-| Input                           | Why it's Toggle                              |
-| ------------------------------- | -------------------------------------------- |
-| "Turn on the lead-gen system"   | Explicit "turn on" + System name             |
-| "Disable monitoring for now"    | "Disable" + System reference                 |
-| "We don't use SEO, turn it off" | Declarative + "turn it off" = System disable |
-
-**Agent action:** delegate to `/om systems`. The ceremony (confirm + edit `core/config/organization-model.ts` + typecheck) belongs to `/om`, not to the ambient rule.
-
-## Quick Reference Table
-
-| Intent     | Trigger signal                                                         | Routed to                                                               |
-| ---------- | ---------------------------------------------------------------------- | ----------------------------------------------------------------------- |
-| Capture    | "add", "remember", "track", "log" + a thing                            | Agent -- draft + confirm + `project:*` or `schedule:create` CLI         |
-| Query      | "what's next", "what's pending", "what failed", "what systems"         | Agent -- read with `project:*`, `queue:*`, or `schedule:*` + narrate    |
-| Describe   | "what is", "tell me about", "explain", "where am I"                    | Agent -- narrate from org model labels                                  |
-| Transition | "done", "stuck", "blocked", "finished", "complete", "approve", "pause" | Agent -- confirm + `project:task:save`, `queue:select`, or `schedule:*` |
-| Navigate   | "focus on", "switch to", "back to", "look at"                          | Agent -- update scope + narrate                                         |
-| Codify     | "we are X", "we track Y", repeated attribute, "add type/field"         | Delegate to `/om \<domain>`                                             |
-| Toggle     | "enable", "disable", "turn on/off" + system                            | Delegate to `/om systems`                                               |
-
-## Source of Truth for Plain Language
-
-All plain-language labels come from the OrganizationModel itself -- never from hardcoded strings in this rule file. Every status, entity kind, and layer name in the model carries an inline `label` field (e.g., `{ id: 'revision_requested', label: 'changes needed', semanticClass: 'blocked' }`). When narrating state or confirming an action, read the label from the model and use it verbatim. Do not invent synonyms or fallback vocabulary.
-
-The unified manifest (delivered via `@elevasis/core/organization-model`) is the canonical vocabulary surface. Vibe classifies against it -- Systems, Actions, statuses, operations entities, and resource kinds are all discoverable from the manifest without hardcoding.
-
-## Ambiguous Intent
-
-When the user's input does not clearly map to one of the seven types, ask one clarifying question. Do not guess. Do not apply a precedence rule. Do not route to the "closest" intent.
-
-Format: a single neutral question that presents the two (or three) plausible intents as options and asks which the user means.
-
-Example: "That could be a note to capture or a status update on the current task -- which did you mean?"
-
-Never ask more than one question per ambiguous input. If the user's reply is still ambiguous, ask once more, then surface the options explicitly.
-
-## Classifier Threshold
-
-Default threshold: `balanced`.
-
-The threshold controls how aggressively the classifier proposes codification from ambiguous signals:
-
-- `strict` -- only explicit declarations or repeat mentions trigger codify proposals
-- `balanced` -- second mention OR explicit declaration triggers; default
-- `loose` -- first strong signal triggers a proposal
-
-Override per project in `core/config/organization-model.ts` under `vibe.classifierThreshold`. The override is merge-aware (Tier 2 sync) and will not be overwritten by template sync operations.
-
-## Phase-1 Scope
-
-This rule covers Phase 1 of the vibe layer rollout. The layers the ambient classifier can narrate and codify in Phase 1 are:
-
-- Layer 1 (Model): narrate schema shape, propose codification edits via `/om`
-- Layer 4 (Systems/Actions): describe which Systems are on/off, propose enabling one via `/om`
-- Layer 7 (Foundations): explain and edit `organization-model.ts` and `extensions/` via `/om`
-
-Layers 2 (Public API), 3 (UI Shell Runtime), 5 (Toolkit), and 6 (Graph) require runtime read APIs that are not yet available. Do not attempt to narrate or classify against those layers in Phase 1. If the user's input clearly references one of those layers, acknowledge the scope and explain that full support arrives in a later phase.
-
-## What Vibe Is Not
-
-- Vibe is not a slash command. There is no `/vibe` invocation (decision #19 -- ambient rule, not a skill or command).
-- Vibe is not a skill. It lives in this rule file + CLAUDE.md + the PreToolUse hook -- not in `.claude/skills/`.
-- Vibe does not own the codify ceremony. `/om` owns draft, confirm, write, and typecheck for both Level A and Level B codify pipelines (decision #21 -- Codify ceremony delegated to `/om`). Vibe detects intent and hands off.
-- Vibe is not active in the monorepo. If working inside the monorepo (not an `external/` project), this ambient routing does not apply.
+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.