@elevasis/sdk 1.24.0 → 1.26.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.24.0",
+  "version": "1.26.0",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -58,7 +58,7 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/core": "0.26.0",
+    "@repo/core": "0.31.0",
     "@repo/eslint-config": "0.0.0",
     "@repo/typescript-config": "0.0.0"
   },

package/reference/_navigation.md

@@ -4,7 +4,13 @@
 
 Auto-generated from the package reference manifests.
 
-Package entries indexed: 55.
+Package entries indexed: 60.
+
+## @elevasis/core / Auth
+
+| Resource | Location | Description | When to Load |
+| --- | --- | --- | --- |
+| Auth | `packages/core/src/README.md` | Published browser-safe auth contracts, AccessKeys, and Access Model primitives. | (not specified) |
 
 ## @elevasis/core / Core
 
@@ -93,6 +99,8 @@ Package entries indexed: 55.
 | Features Settings | `packages/ui/src/features/README.md` | Published settings feature surface for downstream shells. | (not specified) |
 | Features Knowledge | `packages/ui/src/features/README.md` | Published knowledge feature manifest for downstream shells. | (not specified) |
 | Features Clients | `packages/ui/src/features/README.md` | Published clients feature surface for downstream shells. | (not specified) |
+| Features Notes | `packages/ui/src/features/README.md` | Published Notes panel view and supporting note components for shared right-panel integrations. | (not specified) |
+| Features Right Panel Host | `packages/ui/src/features/README.md` | Published right-panel host provider, layer, trigger, keyboard shortcut, store, and view contract. | (not specified) |
 
 ## @elevasis/ui / Foundation
 
@@ -118,7 +126,9 @@ Package entries indexed: 55.
 | Resource | Location | Description | When to Load |
 | --- | --- | --- | --- |
 | Hooks | `packages/ui/src/hooks/README.md` | Headless hooks surface for executions, sessions, observability, and operations. | (not specified) |
+| Hooks Access | `packages/ui/src/hooks/README.md` | Published Access Model hook surface for checking route, section, and action access. | (not specified) |
 | Hooks Delivery | `packages/ui/src/hooks/README.md` | Published delivery hooks for projects, milestones, tasks, and notes. | (not specified) |
+| Hooks User Notes | `packages/ui/src/hooks/README.md` | Published user-notes query and mutation hooks used by shared Notes surfaces. | (not specified) |
 | Transform Command View Data | `packages/ui/src/hooks/README.md` | Utility that transforms backend CommandViewData arrays into a unified frontend CommandViewGraph with nodes and edges. | (not specified) |
 
 ## @elevasis/ui / Provider

package/reference/_reference-manifest.json

@@ -1,6 +1,20 @@
 {
   "schemaVersion": 1,
   "entries": [
+    {
+      "packageName": "@elevasis/core",
+      "packageDir": "packages/core",
+      "subpath": "./auth",
+      "kind": "subpath",
+      "title": "Auth",
+      "description": "Published browser-safe auth contracts, AccessKeys, and Access Model primitives.",
+      "group": "Auth",
+      "order": 1,
+      "sourcePath": "packages/core/src/auth/index.ts",
+      "docPath": "packages/core/src/README.md",
+      "referencePath": "packages/core/src/README.md",
+      "publishedExportPath": "./dist/auth/index.js"
+    },
     {
       "packageName": "@elevasis/core",
       "packageDir": "packages/core",
@@ -393,6 +407,34 @@
       "referencePath": "packages/ui/src/features/README.md",
       "publishedExportPath": "./dist/features/clients/index.js"
     },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./features/notes",
+      "kind": "subpath",
+      "title": "Features Notes",
+      "description": "Published Notes panel view and supporting note components for shared right-panel integrations.",
+      "group": "Features",
+      "order": 13,
+      "sourcePath": "packages/ui/src/features/notes/index.ts",
+      "docPath": "packages/ui/src/features/README.md",
+      "referencePath": "packages/ui/src/features/README.md",
+      "publishedExportPath": "./dist/features/notes/index.js"
+    },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./features/right-panel-host",
+      "kind": "subpath",
+      "title": "Features Right Panel Host",
+      "description": "Published right-panel host provider, layer, trigger, keyboard shortcut, store, and view contract.",
+      "group": "Features",
+      "order": 14,
+      "sourcePath": "packages/ui/src/features/right-panel-host/index.ts",
+      "docPath": "packages/ui/src/features/README.md",
+      "referencePath": "packages/ui/src/features/README.md",
+      "publishedExportPath": "./dist/features/right-panel-host/index.js"
+    },
     {
       "packageName": "@elevasis/ui",
       "packageDir": "packages/ui",
@@ -603,6 +645,20 @@
       "referencePath": "packages/ui/src/hooks/README.md",
       "publishedExportPath": "./dist/hooks/published.js"
     },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./hooks/access",
+      "kind": "subpath",
+      "title": "Hooks Access",
+      "description": "Published Access Model hook surface for checking route, section, and action access.",
+      "group": "Hooks",
+      "order": 2,
+      "sourcePath": "packages/ui/src/hooks/access/index.ts",
+      "docPath": "packages/ui/src/hooks/README.md",
+      "referencePath": "packages/ui/src/hooks/README.md",
+      "publishedExportPath": "./dist/hooks/access/index.js"
+    },
     {
       "packageName": "@elevasis/ui",
       "packageDir": "packages/ui",
@@ -617,6 +673,20 @@
       "referencePath": "packages/ui/src/hooks/README.md",
       "publishedExportPath": "./dist/hooks/delivery/index.js"
     },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./hooks/user-notes",
+      "kind": "subpath",
+      "title": "Hooks User Notes",
+      "description": "Published user-notes query and mutation hooks used by shared Notes surfaces.",
+      "group": "Hooks",
+      "order": 3,
+      "sourcePath": "packages/ui/src/hooks/user-notes/index.ts",
+      "docPath": "packages/ui/src/hooks/README.md",
+      "referencePath": "packages/ui/src/hooks/README.md",
+      "publishedExportPath": "./dist/hooks/user-notes/index.js"
+    },
     {
       "packageName": "@elevasis/ui",
       "packageDir": "packages/ui",

package/reference/claude-config/rules/organization-model.md

@@ -8,4 +8,15 @@ Canonical rule source:
 
 `node_modules/@elevasis/sdk/reference/rules/organization-model.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/organization-model.md`
+
+If the generated fallback is stale or missing, use the source:
+
+`packages/sdk/docs/agent-rules/organization-model.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/organization-os.md

@@ -8,4 +8,15 @@ Canonical rule source:
 
 `node_modules/@elevasis/sdk/reference/rules/organization-os.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/organization-os.md`
+
+If the generated fallback is stale or missing, use the source:
+
+`packages/sdk/docs/agent-rules/organization-os.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/skills/om/SKILL.md

@@ -10,8 +10,8 @@ description: |
   - The user asks "what governs X?", "what does X control?", "system governs", "what is our
     identity set to?", "what's our timezone?", "show me all reference docs", "list my roles",
     "where does outreach-cadence apply?", or similar.
-  - An agent is editing files matching: core/config/organization-model.ts or
-    core/config/knowledge/**.
+  - An agent is editing files matching: core/config/organization-model.ts,
+    core/config/organization-model/**, or core/config/knowledge/**.
   SKIP this skill when the task is purely UI layout, workflow authoring, or infrastructure
   work with no reference to org-model or knowledge-graph entities.
 
@@ -19,6 +19,7 @@ description: |
 metadata:
   pathPatterns:
     - "core/config/organization-model.ts"
+    - "core/config/organization-model/**"
     - "core/config/knowledge/**"
     - "core/config/extensions/**"
   promptSignals:
@@ -77,7 +78,8 @@ This skill auto-invokes whenever:
 - The user asks to read, list, find, show, query, navigate, describe, codify, add, edit,
   update, toggle, enable, or disable any of those
 - An agent is editing files matching `core/config/organization-model.ts`,
-  `core/config/extensions/**`, or `core/config/knowledge/**`
+  `core/config/organization-model/**`, `core/config/extensions/**`, or
+  `core/config/knowledge/**`
 
 Auto-invocation is driven by frontmatter `description`, `metadata.pathPatterns`, and
 `metadata.promptSignals` -- no explicit prefix is required.
@@ -238,7 +240,11 @@ safety ceremony preserved verbatim from the legacy `/configure` flow.
 
 ### Step 1: Snapshot
 
-Read `core/config/organization-model.ts` into memory before any edit. This is the rollback target.
+Determine the target file for the domain being edited (see the domain reference file for
+"Where it lives" guidance). Read that file into memory before any edit. This is the rollback
+target. For unsplit projects the target is `core/config/organization-model.ts`; for split projects
+use the appropriate sub-file (`profile.ts`, `systems.ts`, or `navigation.ts` under
+`core/config/organization-model/`).
 
 ### Step 2: Propose
 
@@ -275,7 +281,9 @@ The rollback is mandatory -- never leave the project in a broken state.
 
 **Two-level ceremony:**
 
-- **Level A** -- config-only edits to existing schema fields in `core/config/organization-model.ts`.
+- **Level A** -- config-only edits to existing schema fields in a single config file under
+  `core/config/` (the entry `organization-model.ts` for unsplit projects, or the appropriate
+  sub-file for split projects — see the domain reference for the correct target).
   Execute: `.claude/skills/om/operations/codify-level-a.md`
 - **Level B** -- new Zod extension files in `core/config/extensions/`. Gated to explicit user
   ask. On casual second mentions of a new type, suggest Level B and wait for confirmation rather

package/reference/claude-config/skills/om/operations/codify-level-a.md

@@ -1,100 +1,109 @@
-# Codify Pipeline: Level A (Config-Only Edits)
-
-Level A is the codify pipeline for changes that land exclusively in
-`core/config/organization-model.ts`. No new TypeScript files are created. The entire
-ceremony is: snapshot current file, propose the edit, write the edit, validate, and roll back on
-failure.
-
-This pipeline is called by domain operations (identity, customers, offerings, roles, goals,
-techStack, systems, actions, labels, and legacy feature compatibility) after the user has confirmed the proposed change. The caller provides
-the specific field/block being changed and the proposed new value.
-
----
-
-## Pipeline
-
-### Step 1: Snapshot
-
-Before any write, read `core/config/organization-model.ts` and keep the full file content
-in memory as the rollback snapshot. Do not write any file during this step.
-
-```
-Read("core/config/organization-model.ts")
--- store as ROLLBACK_SNAPSHOT
-```
-
-### Step 2: Apply the edit
-
-Use the Edit tool to apply the caller's proposed change to
-`core/config/organization-model.ts`.
-
-Rules for the edit:
-
-- Edit only the specific field or block the caller specified. Do not reformat or restructure
-  unrelated sections.
-- Preserve all other keys in `defineOrganizationModel({...})` exactly as they are.
-- Maintain the existing code style (trailing commas, quote style, indentation) of the file.
-- If the target field does not yet exist in the adapter call, add it as a new property in the
-  appropriate position (following the declared domain order in the schema).
-
-### Step 3: TypeScript type-check
-
-Run the type-check for the operations package:
-
-```bash
-pnpm -C operations check-types
-```
-
-Capture stdout and stderr. If the command exits non-zero, proceed to Step 5 (rollback).
-
-### Step 4: Runtime schema validation
-
-Confirm that the adapter's output passes `OrganizationModelSchema.parse()`. The adapter calls
-`resolveOrganizationModel()` internally, which merges defaults with overrides and then parses the
-result. A successful `check-types` pass is strong evidence that the schema is valid, but
-cross-reference checks (segment ID refs in offerings, role reporting refs, period ordering in
-goals) are runtime-only.
-
-If the project exposes a validation script (e.g. `pnpm -C operations check`), run that too:
-
-```bash
-pnpm -C operations check
-```
-
-If either validation step fails, proceed to Step 5 (rollback).
-
-### Step 5: Rollback (on failure only)
-
-If Step 3 or Step 4 failed:
-
-1. Write the ROLLBACK_SNAPSHOT content back to `core/config/organization-model.ts`
-   verbatim (use the Write tool with the exact snapshot content).
-2. Confirm the file has been restored by checking that the content matches the snapshot.
-3. Return the error message to the caller.
-
-The caller is responsible for reporting the rollback to the user.
-
-### Step 6: Success signal
-
-If Steps 3 and 4 both passed, return a success signal to the caller with:
-
-- The fields changed
-- `Type-check: PASS`
-- `Schema validation: PASS`
-
-The caller formats and presents the final report.
-
----
-
-## Caller Contract
-
-Callers must provide before invoking this pipeline:
-
-- **Target file:** always `core/config/organization-model.ts`
-- **Target block:** the specific domain key or sub-key being changed (e.g. `identity`,
-  `customers.segments`, `roles.roles`, `resources.hubspot`)
-- **Proposed value:** the new TypeScript literal to write for that block
-- **Confirmed:** the user has already said yes to the proposed change
-
-This pipeline does not ask the user any questions. All confirmation happens in the domain
-operation before this pipeline is invoked.
+# Codify Pipeline: Level A (Config-Only Edits)
+
+Level A is the codify pipeline for changes that land in a single config file inside
+`core/config/`. No new TypeScript files are created. The entire ceremony is: snapshot the target
+file, propose the edit, write the edit, validate, and roll back on failure.
+
+This pipeline is called by domain operations (identity, customers, offerings, roles, goals,
+techStack, systems, actions, labels, and legacy feature compatibility) after the user has confirmed the proposed change. The caller provides
+the specific field/block being changed, the proposed new value, and the target file.
+
+---
+
+## Pipeline
+
+### Step 1: Snapshot
+
+Before any write, read `TARGET_FILE` and keep the full file content in memory as the rollback
+snapshot. Do not write any file during this step.
+
+```
+Read(TARGET_FILE)
+-- store as ROLLBACK_SNAPSHOT
+```
+
+`TARGET_FILE` is the value the caller provides in the Caller Contract (see below). When the
+project has not been split yet, callers pass the default
+`core/config/organization-model.ts`.
+
+### Step 2: Apply the edit
+
+Use the Edit tool to apply the caller's proposed change to `TARGET_FILE`.
+
+Rules for the edit:
+
+- Edit only the specific field or block the caller specified. Do not reformat or restructure
+  unrelated sections.
+- For edits targeting `profile.ts`: preserve all other keys in `defineOrganizationModel({...})`
+  exactly as they are.
+- Maintain the existing code style (trailing commas, quote style, indentation) of the file.
+- If the target field does not yet exist in the file, add it as a new property in the appropriate
+  position (following the declared domain order in the schema).
+
+### Step 3: TypeScript type-check
+
+Run the type-check for the operations package:
+
+```bash
+pnpm -C operations check-types
+```
+
+Capture stdout and stderr. If the command exits non-zero, proceed to Step 5 (rollback).
+
+### Step 4: Runtime schema validation
+
+Confirm that the adapter's output passes `OrganizationModelSchema.parse()`. The adapter calls
+`resolveOrganizationModel()` internally, which merges defaults with overrides and then parses the
+result. A successful `check-types` pass is strong evidence that the schema is valid, but
+cross-reference checks (segment ID refs in offerings, role reporting refs, period ordering in
+goals) are runtime-only.
+
+If the project exposes a validation script (e.g. `pnpm -C operations check`), run that too:
+
+```bash
+pnpm -C operations check
+```
+
+If either validation step fails, proceed to Step 5 (rollback).
+
+### Step 5: Rollback (on failure only)
+
+If Step 3 or Step 4 failed:
+
+1. Write the ROLLBACK_SNAPSHOT content back to `TARGET_FILE` verbatim (use the Write tool with
+   the exact snapshot content).
+2. Confirm the file has been restored by checking that the content matches the snapshot.
+3. Return the error message to the caller.
+
+The caller is responsible for reporting the rollback to the user.
+
+### Step 6: Success signal
+
+If Steps 3 and 4 both passed, return a success signal to the caller with:
+
+- The file edited (`TARGET_FILE`)
+- The fields changed
+- `Type-check: PASS`
+- `Schema validation: PASS`
+
+The caller formats and presents the final report.
+
+---
+
+## Caller Contract
+
+Callers must provide before invoking this pipeline:
+
+- **Target file:** the sub-file path to snapshot and edit. Default (unsplit projects):
+  `core/config/organization-model.ts`. Split-project routing:
+  - `core/config/organization-model/profile.ts` for identity, customers, offerings, roles, goals
+    (and techStack/labels when those keys exist in `profile.ts`)
+  - `core/config/organization-model/systems.ts` for systems, actions, resources
+  - Callers use the default entry path when the domain does not yet have a dedicated sub-file
+- **Target block:** the specific domain key or sub-key being changed (e.g. `identity`,
+  `customers.segments`, `roles.roles`, `resources.hubspot`)
+- **Proposed value:** the new TypeScript literal to write for that block
+- **Confirmed:** the user has already said yes to the proposed change
+
+This pipeline does not ask the user any questions. All confirmation happens in the domain
+operation before this pipeline is invoked.

package/reference/claude-config/skills/om/operations/customers.md

@@ -89,19 +89,23 @@ customers: {
 
 ## Where it lives in the adapter
 
-`core/config/organization-model.ts` under the `customers` key of
+**Split projects:** `core/config/organization-model/profile.ts` under the `customers` key of
 `defineOrganizationModel({...})`.
 
-To read current segments: open the adapter file and inspect the `customers.segments` array, or
-use `pnpm exec elevasis-sdk om:cat customers` (external project).
+**Unsplit projects:** `core/config/organization-model.ts` under the same key.
+
+To read current segments: open the appropriate file and inspect the `customers.segments` array,
+or use `pnpm exec elevasis-sdk om:cat customers` (external project).
 
 ## Write path
 
 To add, edit, or remove a segment, the `/om` skill runs the codify ceremony
 (`operations/codify-level-a.md`): snapshot → propose → confirm → write → typecheck → Zod parse →
-rollback on failure. Only the `segments` array is written; no other keys in the adapter are
-touched. When adding, append to the array. When editing, replace the matching entry by `id`.
-When removing, filter it out — and surface any dangling `targetSegmentIds` references first.
+rollback on failure. Pass `targetFile` as `core/config/organization-model/profile.ts` for split
+projects, or `core/config/organization-model.ts` for unsplit projects. Only the `segments` array
+is written; no other keys in the target file are touched. When adding, append to the array. When
+editing, replace the matching entry by `id`. When removing, filter it out — and surface any
+dangling `targetSegmentIds` references first.
 
 ---
 

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

@@ -31,10 +31,14 @@ guidance that depends on it; prefer `by-system` everywhere.
 For natural-language requests like "turn on lead gen", "disable SEO", or "enable CRM":
 
 1. Treat the request as a System availability/routing change.
-2. Read `core/config/organization-model.ts` and find the matching System entry or platform
-   default constant exposed by `@elevasis/core/organization-model`.
+2. Read the Systems config file to find the matching System entry or platform default constant
+   exposed by `@elevasis/core/organization-model`. For split projects this is
+   `core/config/organization-model/systems.ts`; for unsplit projects use
+   `core/config/organization-model.ts`.
 3. Propose the exact availability/routing change in plain language.
-4. After confirmation, run the Level A codify ceremony in `operations/codify-level-a.md`.
+4. After confirmation, run the Level A codify ceremony in `operations/codify-level-a.md`, passing
+   `targetFile` as `core/config/organization-model/systems.ts` (split) or
+   `core/config/organization-model.ts` (unsplit).
 
 Do not create new extension files for a simple on/off change.
 

package/reference/claude-config/skills/om/operations/goals.md

@@ -98,19 +98,23 @@ goals: {
 
 ## Where it lives in the adapter
 
-`core/config/organization-model.ts` under the `goals` key of
+**Split projects:** `core/config/organization-model/profile.ts` under the `goals` key of
 `defineOrganizationModel({...})`.
 
-To read current goals: open the adapter file and inspect the `goals.objectives` array, or use
-`pnpm exec elevasis-sdk om:cat goals` (external project).
+**Unsplit projects:** `core/config/organization-model.ts` under the same key.
+
+To read current goals: open the appropriate file and inspect the `goals.objectives` array, or
+use `pnpm exec elevasis-sdk om:cat goals` (external project).
 
 ## Write path
 
 To add, edit, remove, or update progress on a goal, the `/om` skill runs the codify
 ceremony (`operations/codify-level-a.md`): snapshot → propose → confirm → write → typecheck →
-Zod parse → rollback on failure. Only the `objectives` array is written; no other keys in the
-adapter are touched. For progress-only updates (changing `currentValue` on an existing outcome),
-a targeted edit is preferred over rewriting the entire goals block.
+Zod parse → rollback on failure. Pass `targetFile` as
+`core/config/organization-model/profile.ts` for split projects, or
+`core/config/organization-model.ts` for unsplit projects. Only the `objectives` array is written;
+no other keys in the target file are touched. For progress-only updates (changing `currentValue`
+on an existing outcome), a targeted edit is preferred over rewriting the entire goals block.
 
 ---
 

package/reference/claude-config/skills/om/operations/identity.md

@@ -74,18 +74,21 @@ identity: {
 
 ## Where it lives in the adapter
 
-`core/config/organization-model.ts` under the `identity` key of
+**Split projects:** `core/config/organization-model/profile.ts` under the `identity` key of
 `defineOrganizationModel({...})`.
 
-To read the current values: open the adapter file and inspect the `identity` block directly, or
-use `pnpm exec elevasis-sdk om:cat identity` (external project).
+**Unsplit projects:** `core/config/organization-model.ts` under the same key.
+
+To read the current values: open the appropriate file and inspect the `identity` block directly,
+or use `pnpm exec elevasis-sdk om:cat identity` (external project).
 
 ## Write path
 
 To edit any field, the `/om` skill runs the codify ceremony
 (`operations/codify-level-a.md`): snapshot → propose → confirm → write → typecheck → Zod parse →
-rollback on failure. Only the confirmed fields are written; no other top-level keys in the adapter
-are touched.
+rollback on failure. Pass `targetFile` as `core/config/organization-model/profile.ts` for split
+projects, or `core/config/organization-model.ts` for unsplit projects. Only the confirmed fields
+are written; no other top-level keys in the target file are touched.
 
 ---
 

package/reference/claude-config/skills/om/operations/labels.md

@@ -4,7 +4,7 @@
 knowledge nodes, registry entries, and sidebar surfaces in the OrganizationModel. Labels control what users see in the UI and what
 agents say when narrating state. Editing a label does not change the entry's `id` or
 `semanticClass` -- only the human-readable display string. This is Level A only (config-only
-edits to `core/config/organization-model.ts`).
+edits to a single file under `core/config/`).
 
 ## What carries labels
 
@@ -76,6 +76,22 @@ navigation.sidebar.primary:
   sales.crm:     label "Pipeline"       -> "Deal Pipeline"
 ```
 
+## Where it lives
+
+**Split projects:** the target file depends on what carries the label being edited:
+
+- Status/stage entries and System entries -- `core/config/organization-model/systems.ts`
+- Sidebar navigation surfaces -- `core/config/organization-model/navigation.ts`
+- Business-profile domain entries (customers, offerings, roles, goals) -- `core/config/organization-model/profile.ts`
+
+**Unsplit projects:** `core/config/organization-model.ts` for all label edits.
+
+Pass the appropriate path as `targetFile` when invoking `operations/codify-level-a.md`.
+
+**Note:** `labels` is not currently authored as a standalone top-level domain key in either the
+template or reference tenant model. Label fields are inline properties on the entries listed
+above. Do not invent a top-level `labels` key in `profile.ts`.
+
 ## Validation gate
 
 Every label change must pass before codify completes:

package/reference/claude-config/skills/om/operations/offerings.md

@@ -88,20 +88,24 @@ offerings: {
 
 ## Where it lives in the adapter
 
-`core/config/organization-model.ts` under the `offerings` key of
+**Split projects:** `core/config/organization-model/profile.ts` under the `offerings` key of
 `defineOrganizationModel({...})`.
 
-To read current products: open the adapter file and inspect the `offerings.products` array, or
-use `pnpm exec elevasis-sdk om:cat offerings` (external project).
+**Unsplit projects:** `core/config/organization-model.ts` under the same key.
+
+To read current products: open the appropriate file and inspect the `offerings.products` array,
+or use `pnpm exec elevasis-sdk om:cat offerings` (external project).
 
 ## Write path
 
 To add, edit, or remove a product, the `/om` skill runs the codify ceremony
 (`operations/codify-level-a.md`): snapshot → propose → confirm → write → typecheck → Zod parse →
-rollback on failure. Only the `products` array is written; no other keys in the adapter are
-touched. Before writing, the skill verifies all `targetSegmentIds` and `deliverySystemId`
-references resolve. When adding, append to the array. When editing, replace by `id`. When
-removing, filter out — and surface any dangling references first.
+rollback on failure. Pass `targetFile` as `core/config/organization-model/profile.ts` for split
+projects, or `core/config/organization-model.ts` for unsplit projects. Only the `products` array
+is written; no other keys in the target file are touched. Before writing, the skill verifies all
+`targetSegmentIds` and `deliverySystemId` references resolve. When adding, append to the array.
+When editing, replace by `id`. When removing, filter out — and surface any dangling references
+first.
 
 ---