@elevasis/sdk 1.22.1 → 1.24.0

package/reference/claude-config/skills/{knowledge → om}/operations/features.md

@@ -1,76 +1,77 @@
-# Features Compatibility Notes
-
-`features` is legacy organization-model wording. Current Organization OS vocabulary is
-System/Action oriented:
-
-- **Systems** describe availability, routing, ownership, navigation grouping, and knowledge
-  mounts.
-- **Actions** describe invokable operations such as workflows, agents, commands, and UI-triggered
-  tasks.
-
-Use this file only when older prompts, browser copy text, SDK references, or scaffold recipes still
-say "feature". For current tenant organization-model work, route the user to Systems and Actions
-wording and use `/by-system/<id>` knowledge paths.
-
-## Compatibility Mapping
-
-| Legacy wording                     | Current wording                                      |
-| ---------------------------------- | ---------------------------------------------------- |
-| Feature toggle                     | System availability or routing toggle                |
-| Feature ID                         | System ID when discussing Organization OS            |
-| Add a custom feature               | Add or extend a System, then define any Actions      |
-| Feature governs X                  | System governs X                                     |
-| `/knowledge read-folder feature:x` | `/knowledge read-folder system:x`                    |
-| `/by-feature/x`                    | `/by-system/x`                                       |
-
-`by-feature` may still exist as a legacy compatibility axis in older tools. Do not introduce new
-guidance that depends on it; prefer `by-system` everywhere.
-
-## What To Do With Toggle Requests
-
-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`.
-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`.
-
-Do not create new extension files for a simple on/off change.
-
-## When Level B Applies
-
-Level B applies only when the user explicitly asks for a new structural concept that cannot be
-represented as an existing System or Action configuration. In current vocabulary this usually
-means adding a project-owned extension under `core/config/extensions/` and wiring it into the
-organization model.
-
-Older references may call this "adding a custom feature"; translate it to "add or extend a
-System and define any Actions it owns" before invoking `operations/codify-level-b.md`.
-
-## UI Package Exception
-
-Keep the word `features` only for legacy frontend source paths that still use that directory
-name, such as `ui/src/features/`. Current published shell APIs are System-oriented:
-`SystemShell`, `SystemModule`, and `ElevasisSystemsProvider`.
-
-## Read Examples
-
-Use current system paths:
-
-```bash
-pnpm exec elevasis-sdk knowledge:ls /by-system/<id> --ids-only
-pnpm exec elevasis-sdk knowledge:cat <node-id>
-```
-
-Legacy browser output:
-
-```text
-/knowledge read-folder feature:<id>
-```
-
-Resolve as:
-
-```bash
-pnpm exec elevasis-sdk knowledge:ls /by-system/<id> --ids-only
-```
+# Features Compatibility Notes
+
+`features` is legacy organization-model wording. Current Organization OS vocabulary is
+System/Action oriented:
+
+- **Systems** describe availability, routing, ownership, navigation grouping, and knowledge
+  mounts.
+- **Actions** describe invokable operations such as workflows, agents, commands, and UI-triggered
+  tasks.
+
+Use this file only when older prompts, browser copy text, SDK references, or scaffold recipes still
+say "feature". For current tenant organization-model work, route the user to Systems and Actions
+wording and use `/by-system/<id>` knowledge paths.
+
+## Compatibility Mapping
+
+| Legacy wording                                                                        | Current wording                                 |
+| ------------------------------------------------------------------------------------- | ----------------------------------------------- |
+| Feature toggle                                                                        | System availability or routing toggle           |
+| Feature ID                                                                            | System ID when discussing Organization OS       |
+| Add a custom feature                                                                  | Add or extend a System, then define any Actions |
+| Feature governs X                                                                     | System governs X                                |
+| `/om read-folder feature:x` (legacy `/knowledge read-folder feature:x` also accepted) | `/om read-folder system:x`                      |
+| `/by-feature/x`                                                                       | `/by-system/x`                                  |
+
+`by-feature` may still exist as a legacy compatibility axis in older tools. Do not introduce new
+guidance that depends on it; prefer `by-system` everywhere.
+
+## What To Do With Toggle Requests
+
+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`.
+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`.
+
+Do not create new extension files for a simple on/off change.
+
+## When Level B Applies
+
+Level B applies only when the user explicitly asks for a new structural concept that cannot be
+represented as an existing System or Action configuration. In current vocabulary this usually
+means adding a project-owned extension under `core/config/extensions/` and wiring it into the
+organization model.
+
+Older references may call this "adding a custom feature"; translate it to "add or extend a
+System and define any Actions it owns" before invoking `operations/codify-level-b.md`.
+
+## UI Package Exception
+
+Keep the word `features` only for legacy frontend source paths that still use that directory
+name, such as `ui/src/features/`. Current published shell APIs are System-oriented:
+`SystemShell`, `SystemModule`, and `ElevasisSystemsProvider`.
+
+## Read Examples
+
+Use current system paths:
+
+```bash
+pnpm exec elevasis-sdk om:ls /by-system/<id> --ids-only
+pnpm exec elevasis-sdk om:cat <node-id>
+```
+
+Legacy browser output (the `/knowledge` slash form is preserved as a permanent alias for `/om`):
+
+```text
+/knowledge read-folder feature:<id>
+/om read-folder feature:<id>
+```
+
+Resolve as:
+
+```bash
+pnpm exec elevasis-sdk om:ls /by-system/<id> --ids-only
+```

package/reference/claude-config/skills/{knowledge → om}/operations/goals.md

@@ -1,118 +1,119 @@
-# Goals domain
-
-The `goals` domain captures what the organization is working toward — time-bounded goals with
-measurable outcomes. The schema shape is OKR-inspired (objectives + key results) but all
-user-facing language must say "goals" and "measurable outcomes". Never say "OKR", "objective",
-or "key result" to the user.
-
-Agents use this domain for quarterly planning, priority routing, and understanding which outcomes
-matter most right now.
-
-## Schema
-
-Source: `packages/core/src/organization-model/domains/goals.ts`
-
-```typescript
-GoalsDomainSchema = z.object({
-  objectives: z.array(ObjectiveSchema).default([])
-})
-
-ObjectiveSchema = z.object({
-  id:          z.string().trim().min(1).max(100),   // stable ID, e.g. "goal-grow-arr-q1-2026"
-  description: z.string().trim().min(1).max(1000),  // plain-language goal statement
-  periodStart: z.string().regex(ISO_DATE),          // YYYY-MM-DD — must be before periodEnd
-  periodEnd:   z.string().regex(ISO_DATE),          // YYYY-MM-DD — enforced in superRefine
-  keyResults:  z.array(KeyResultSchema).default([]) // measurable outcomes under this goal
-})
-
-KeyResultSchema = z.object({
-  id:           z.string().trim().min(1).max(100),  // e.g. "kr-revenue-q1"
-  description:  z.string().trim().min(1).max(500),  // e.g. "Increase trial-to-paid conversion"
-  targetMetric: z.string().trim().min(1).max(200),  // what is being measured, e.g. "monthly revenue"
-  currentValue: z.number().default(0),              // current tracked value
-  targetValue:  z.number().optional()               // target to hit (omit if directional)
-})
-```
-
-## Field reference
-
-| Field         | Type          | Notes                                                      |
-| ------------- | ------------- | ---------------------------------------------------------- |
-| `id`          | string (100)  | Stable key; e.g. `"goal-grow-arr-q1-2026"`                 |
-| `description` | string (1000) | Plain-language goal statement; min 1 char required         |
-| `periodStart` | string        | ISO date `YYYY-MM-DD`; must be strictly before `periodEnd` |
-| `periodEnd`   | string        | ISO date `YYYY-MM-DD`; enforced by `superRefine`           |
-| `keyResults`  | array         | Measurable outcomes under this goal; defaults to `[]`      |
-
-Key result fields:
-
-| Field          | Type         | Notes                                               |
-| -------------- | ------------ | --------------------------------------------------- |
-| `id`           | string (100) | Stable key; e.g. `"kr-revenue-q1"`                  |
-| `description`  | string (500) | What is being tracked; min 1 char required          |
-| `targetMetric` | string (200) | The metric name; e.g. `"monthly recurring revenue"` |
-| `currentValue` | number       | Current value; defaults to `0`                      |
-| `targetValue`  | number       | Optional target; omit if the outcome is directional |
-
-## Validation rules
-
-- `periodEnd` must be strictly after `periodStart`; enforced at parse time by
-  `OrganizationModelSchema.superRefine()`; setting equal dates is also invalid
-- Both `periodStart` and `periodEnd` must match `YYYY-MM-DD` ISO date format exactly
-- The internal field name for the goals array is `objectives` (not `goals`) — this is a
-  schema-level name, not user-facing vocabulary; always say "goals" to users
-- The internal field name for measurable outcomes is `keyResults` (not `outcomes`) — same
-  convention applies; say "measurable outcomes" to users
-- `targetValue` is optional for directional goals where there is no specific number target
-
-## Examples
-
-```typescript
-goals: {
-  objectives: [
-    {
-      id:          "goal-arr-q1-2026",
-      description: "Reach $50K MRR by end of Q1 2026",
-      periodStart: "2026-01-01",
-      periodEnd:   "2026-03-31",
-      keyResults: [
-        {
-          id:           "kr-mrr-q1",
-          description:  "Grow monthly recurring revenue",
-          targetMetric: "monthly recurring revenue (MRR)",
-          currentValue: 32000,
-          targetValue:  50000
-        },
-        {
-          id:           "kr-churn-q1",
-          description:  "Reduce monthly churn rate",
-          targetMetric: "monthly churn rate (%)",
-          currentValue: 4.2,
-          targetValue:  2.5
-        }
-      ]
-    }
-  ]
-}
-```
-
-## Where it lives in the adapter
-
-`core/config/organization-model.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 knowledge:cat goals` (external project).
-
-## Write path
-
-To add, edit, remove, or update progress on a goal, the `/knowledge` 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.
-
----
-
-**Read via `/knowledge`** — natural-language queries like "what are our goals this quarter?" or
-"what's the current MRR against target?" route to this domain via the skill's intent classifier.
+# Goals domain
+
+The `goals` domain captures what the organization is working toward — time-bounded goals with
+measurable outcomes. The schema shape is OKR-inspired (objectives + key results) but all
+user-facing language must say "goals" and "measurable outcomes". Never say "OKR", "objective",
+or "key result" to the user.
+
+Agents use this domain for quarterly planning, priority routing, and understanding which outcomes
+matter most right now.
+
+## Schema
+
+Source: `packages/core/src/organization-model/domains/goals.ts`
+
+```typescript
+GoalsDomainSchema = z.object({
+  objectives: z.array(ObjectiveSchema).default([])
+})
+
+ObjectiveSchema = z.object({
+  id:          z.string().trim().min(1).max(100),   // stable ID, e.g. "goal-grow-arr-q1-2026"
+  description: z.string().trim().min(1).max(1000),  // plain-language goal statement
+  periodStart: z.string().regex(ISO_DATE),          // YYYY-MM-DD — must be before periodEnd
+  periodEnd:   z.string().regex(ISO_DATE),          // YYYY-MM-DD — enforced in superRefine
+  keyResults:  z.array(KeyResultSchema).default([]) // measurable outcomes under this goal
+})
+
+KeyResultSchema = z.object({
+  id:           z.string().trim().min(1).max(100),  // e.g. "kr-revenue-q1"
+  description:  z.string().trim().min(1).max(500),  // e.g. "Increase trial-to-paid conversion"
+  targetMetric: z.string().trim().min(1).max(200),  // what is being measured, e.g. "monthly revenue"
+  currentValue: z.number().default(0),              // current tracked value
+  targetValue:  z.number().optional()               // target to hit (omit if directional)
+})
+```
+
+## Field reference
+
+| Field         | Type          | Notes                                                      |
+| ------------- | ------------- | ---------------------------------------------------------- |
+| `id`          | string (100)  | Stable key; e.g. `"goal-grow-arr-q1-2026"`                 |
+| `description` | string (1000) | Plain-language goal statement; min 1 char required         |
+| `periodStart` | string        | ISO date `YYYY-MM-DD`; must be strictly before `periodEnd` |
+| `periodEnd`   | string        | ISO date `YYYY-MM-DD`; enforced by `superRefine`           |
+| `keyResults`  | array         | Measurable outcomes under this goal; defaults to `[]`      |
+
+Key result fields:
+
+| Field          | Type         | Notes                                               |
+| -------------- | ------------ | --------------------------------------------------- |
+| `id`           | string (100) | Stable key; e.g. `"kr-revenue-q1"`                  |
+| `description`  | string (500) | What is being tracked; min 1 char required          |
+| `targetMetric` | string (200) | The metric name; e.g. `"monthly recurring revenue"` |
+| `currentValue` | number       | Current value; defaults to `0`                      |
+| `targetValue`  | number       | Optional target; omit if the outcome is directional |
+
+## Validation rules
+
+- `periodEnd` must be strictly after `periodStart`; enforced at parse time by
+  `OrganizationModelSchema.superRefine()`; setting equal dates is also invalid
+- Both `periodStart` and `periodEnd` must match `YYYY-MM-DD` ISO date format exactly
+- The internal field name for the goals array is `objectives` (not `goals`) — this is a
+  schema-level name, not user-facing vocabulary; always say "goals" to users
+- The internal field name for measurable outcomes is `keyResults` (not `outcomes`) — same
+  convention applies; say "measurable outcomes" to users
+- `targetValue` is optional for directional goals where there is no specific number target
+
+## Examples
+
+```typescript
+goals: {
+  objectives: [
+    {
+      id:          "goal-arr-q1-2026",
+      description: "Reach $50K MRR by end of Q1 2026",
+      periodStart: "2026-01-01",
+      periodEnd:   "2026-03-31",
+      keyResults: [
+        {
+          id:           "kr-mrr-q1",
+          description:  "Grow monthly recurring revenue",
+          targetMetric: "monthly recurring revenue (MRR)",
+          currentValue: 32000,
+          targetValue:  50000
+        },
+        {
+          id:           "kr-churn-q1",
+          description:  "Reduce monthly churn rate",
+          targetMetric: "monthly churn rate (%)",
+          currentValue: 4.2,
+          targetValue:  2.5
+        }
+      ]
+    }
+  ]
+}
+```
+
+## Where it lives in the adapter
+
+`core/config/organization-model.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).
+
+## 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.
+
+---
+
+**Read via `/om`** (legacy `/knowledge` alias also accepted) — natural-language queries like
+"what are our goals this quarter?" or "what's the current MRR against target?" route to this
+domain via the skill's intent classifier.

package/reference/claude-config/skills/{knowledge → om}/operations/identity.md

@@ -1,93 +1,94 @@
-# Identity domain
-
-The `identity` domain captures the organization's legal identity, purpose, and operational anchors.
-It is distinct from `branding` (display identity: logos, product names) — editing identity fields
-here does not touch any visual or branding configuration.
-
-## Schema
-
-Source: `packages/core/src/organization-model/domains/identity.ts`
-
-```typescript
-IdentityDomainSchema = z.object({
-  mission:          z.string().trim().max(1000).default(''),
-  vision:           z.string().trim().max(1000).default(''),
-  legalName:        z.string().trim().max(200).default(''),
-  entityType:       z.string().trim().max(100).default(''),    // e.g. "LLC", "Corporation"
-  jurisdiction:     z.string().trim().max(200).default(''),    // e.g. "United States – Delaware"
-  industryCategory: z.string().trim().max(200).default(''),    // e.g. "Marketing Agency"
-  geographicFocus:  z.string().trim().max(200).default(''),    // e.g. "North America"
-  timeZone:         z.string().trim().max(100).default('UTC'), // IANA identifier
-  businessHours:    BusinessHoursSchema                        // per-day { open, close } in HH:MM
-})
-```
-
-`BusinessHoursSchema` is an object with optional keys `monday` through `sunday`, each holding
-`{ open: "HH:MM", close: "HH:MM" }`. An empty object `{}` means not configured.
-
-## Field reference
-
-| Field              | Type   | Max  | Notes                                                    |
-| ------------------ | ------ | ---- | -------------------------------------------------------- |
-| `mission`          | string | 1000 | Why the organization exists                              |
-| `vision`           | string | 1000 | Where the organization is headed long-term               |
-| `legalName`        | string | 200  | Registered legal name                                    |
-| `entityType`       | string | 100  | e.g. "LLC", "Corporation", "Sole Proprietor"             |
-| `jurisdiction`     | string | 200  | e.g. "United States – Delaware", "Canada – Ontario"      |
-| `industryCategory` | string | 200  | e.g. "Marketing Agency", "SaaS", "Professional Services" |
-| `geographicFocus`  | string | 200  | e.g. "North America", "Global", "Southeast Asia"         |
-| `timeZone`         | string | 100  | IANA identifier, e.g. `America/Los_Angeles`              |
-| `businessHours`    | object | --   | Per-day `{ open: "HH:MM", close: "HH:MM" }`              |
-
-## Validation rules
-
-- All string fields default to empty string `''`; none are required to be non-empty at schema level
-- `timeZone` defaults to `"UTC"` when not set; agents should treat a value of `"UTC"` as
-  potentially unconfigured and surface it for review
-- `businessHours` defaults to `{}` (not configured); an empty object is valid
-- Per-day entries must follow `"HH:MM"` 24-hour format; the schema does not enforce range bounds
-  but convention is `00:00`–`23:59`
-- `jurisdiction` should use the format `"Country – Region"` (em dash, not hyphen) for
-  consistency across agents that parse it
-
-## Examples
-
-```typescript
-identity: {
-  mission:          "We help SMBs automate complex operations using AI.",
-  vision:           "A world where every business operates at the efficiency of a Fortune 500.",
-  legalName:        "Acme Operations LLC",
-  entityType:       "LLC",
-  jurisdiction:     "United States – Delaware",
-  industryCategory: "AI Automation / Professional Services",
-  geographicFocus:  "North America",
-  timeZone:         "America/Chicago",
-  businessHours: {
-    monday:    { open: "09:00", close: "17:00" },
-    tuesday:   { open: "09:00", close: "17:00" },
-    wednesday: { open: "09:00", close: "17:00" },
-    thursday:  { open: "09:00", close: "17:00" },
-    friday:    { open: "09:00", close: "17:00" }
-  }
-}
-```
-
-## Where it lives in the adapter
-
-`core/config/organization-model.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 knowledge:cat identity` (external project).
-
-## Write path
-
-To edit any field, the `/knowledge` 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.
-
----
-
-**Read via `/knowledge`** — natural-language queries like "what's our identity set to?" or
-"what timezone are we in?" route to this domain via the skill's intent classifier.
+# Identity domain
+
+The `identity` domain captures the organization's legal identity, purpose, and operational anchors.
+It is distinct from `branding` (display identity: logos, product names) — editing identity fields
+here does not touch any visual or branding configuration.
+
+## Schema
+
+Source: `packages/core/src/organization-model/domains/identity.ts`
+
+```typescript
+IdentityDomainSchema = z.object({
+  mission:          z.string().trim().max(1000).default(''),
+  vision:           z.string().trim().max(1000).default(''),
+  legalName:        z.string().trim().max(200).default(''),
+  entityType:       z.string().trim().max(100).default(''),    // e.g. "LLC", "Corporation"
+  jurisdiction:     z.string().trim().max(200).default(''),    // e.g. "United States – Delaware"
+  industryCategory: z.string().trim().max(200).default(''),    // e.g. "Marketing Agency"
+  geographicFocus:  z.string().trim().max(200).default(''),    // e.g. "North America"
+  timeZone:         z.string().trim().max(100).default('UTC'), // IANA identifier
+  businessHours:    BusinessHoursSchema                        // per-day { open, close } in HH:MM
+})
+```
+
+`BusinessHoursSchema` is an object with optional keys `monday` through `sunday`, each holding
+`{ open: "HH:MM", close: "HH:MM" }`. An empty object `{}` means not configured.
+
+## Field reference
+
+| Field              | Type   | Max  | Notes                                                    |
+| ------------------ | ------ | ---- | -------------------------------------------------------- |
+| `mission`          | string | 1000 | Why the organization exists                              |
+| `vision`           | string | 1000 | Where the organization is headed long-term               |
+| `legalName`        | string | 200  | Registered legal name                                    |
+| `entityType`       | string | 100  | e.g. "LLC", "Corporation", "Sole Proprietor"             |
+| `jurisdiction`     | string | 200  | e.g. "United States – Delaware", "Canada – Ontario"      |
+| `industryCategory` | string | 200  | e.g. "Marketing Agency", "SaaS", "Professional Services" |
+| `geographicFocus`  | string | 200  | e.g. "North America", "Global", "Southeast Asia"         |
+| `timeZone`         | string | 100  | IANA identifier, e.g. `America/Los_Angeles`              |
+| `businessHours`    | object | --   | Per-day `{ open: "HH:MM", close: "HH:MM" }`              |
+
+## Validation rules
+
+- All string fields default to empty string `''`; none are required to be non-empty at schema level
+- `timeZone` defaults to `"UTC"` when not set; agents should treat a value of `"UTC"` as
+  potentially unconfigured and surface it for review
+- `businessHours` defaults to `{}` (not configured); an empty object is valid
+- Per-day entries must follow `"HH:MM"` 24-hour format; the schema does not enforce range bounds
+  but convention is `00:00`–`23:59`
+- `jurisdiction` should use the format `"Country – Region"` (em dash, not hyphen) for
+  consistency across agents that parse it
+
+## Examples
+
+```typescript
+identity: {
+  mission:          "We help SMBs automate complex operations using AI.",
+  vision:           "A world where every business operates at the efficiency of a Fortune 500.",
+  legalName:        "Acme Operations LLC",
+  entityType:       "LLC",
+  jurisdiction:     "United States – Delaware",
+  industryCategory: "AI Automation / Professional Services",
+  geographicFocus:  "North America",
+  timeZone:         "America/Chicago",
+  businessHours: {
+    monday:    { open: "09:00", close: "17:00" },
+    tuesday:   { open: "09:00", close: "17:00" },
+    wednesday: { open: "09:00", close: "17:00" },
+    thursday:  { open: "09:00", close: "17:00" },
+    friday:    { open: "09:00", close: "17:00" }
+  }
+}
+```
+
+## Where it lives in the adapter
+
+`core/config/organization-model.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).
+
+## 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.
+
+---
+
+**Read via `/om`** (legacy `/knowledge` alias also accepted) — natural-language queries like
+"what's our identity set to?" or "what timezone are we in?" route to this domain via the skill's
+intent classifier.