@elevasis/sdk 1.8.2 → 1.8.3

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

@@ -1,147 +1,147 @@
-# Configure: goals
-
-Guides the user through reviewing and updating the `goals` domain of the organization model.
-
-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 reference
-
-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)
-})
-```
-
-Cross-reference constraint: `periodEnd` must be strictly after `periodStart`. Enforced at parse
-time by `OrganizationModelSchema.superRefine()`.
-
-The field name in the schema is `objectives` (not `goals`) and the measurable-outcome array is
-`keyResults` (not `outcomes`) — these are internal field names, not user-facing vocabulary.
-
-Where this lands in the adapter: `foundations/config/organization-model.ts` under the `goals`
-key of `defineOrganizationModel({...})`.
-
----
-
-## Process
-
-### Step 1: Read current state
-
-Read `foundations/config/organization-model.ts` and extract the current `goals.objectives` array.
-Present as a plain-language summary:
-
-```
-Current goals (N):
-  1. "{description truncated to 80 chars}" ({id})
-     Period: {periodStart} → {periodEnd}
-     Measurable outcomes: {count}
-  (no goals defined yet)
-```
-
-### Step 2: Establish intent
-
-Ask whether the user wants to:
-
-- **Add** a new goal
-- **Edit** an existing goal (by description or number)
-- **Remove** a goal
-- **Update progress** on a measurable outcome (update `currentValue`)
-
-### Step 3: Gather goal details
-
-For each goal being added or edited:
-
-**Core goal:**
-
-- "What is the organization working toward? Describe the goal in plain language — one or two sentences."
-- "Give it a stable ID — lowercase with hyphens, e.g. `goal-grow-arr-q1-2026`."
-- "What period does this goal cover? (Start date and end date — e.g. 2026-01-01 to 2026-03-31)"
-
-Validate that the end date is strictly after the start date before proceeding.
-
-**Measurable outcomes (optional but recommended):**
-
-- "Do you want to add any measurable outcomes under this goal? These help track whether you're
-  on track."
-- For each outcome: "What are you measuring? (e.g. monthly revenue, NPS score, trial-to-paid
-  conversion rate)"
-- "What's the target value? (Optional — leave blank if the outcome is directional.)"
-- "What's the current value?"
-- "Give this outcome an ID — e.g. `kr-revenue-q1`."
-
-Capture as many outcomes as the user wants. One at a time is fine.
-
-### Step 4: Confirm before writing
-
-Present a diff:
-
-```
-Proposed goals change:
-
-ADD goal "Reach $50K MRR by end of Q1 2026" (goal-arr-q1-2026):
-  period:  2026-01-01 → 2026-03-31
-  outcomes:
-    kr-mrr-q1: "Grow monthly recurring revenue"
-      metric:  "monthly recurring revenue (MRR)"
-      current: 32000
-      target:  50000
-    kr-churn-q1: "Reduce churn rate"
-      metric:  "monthly churn rate (%)"
-      current: 4.2
-      target:  2.5
-
-Apply? (yes/no)
-```
-
-### Step 5: Codify
-
-Execute `.claude/skills/configure/operations/codify-level-a.md` with the proposed `goals` block.
-Only the `objectives` array is written — no other keys in the adapter are touched.
-
-When updating progress only (updating `currentValue` on an existing outcome), make a targeted
-edit rather than rewriting the entire goals block.
-
-### Step 6: Report
-
-After successful validation:
-
-```
-Goals updated.
-  Goals: {total count} ({N added / N edited / N removed})
-  foundations/config/organization-model.ts — goals.objectives updated
-  Type-check: PASS
-  Schema validation: PASS
-```
-
-If validation failed and rollback occurred:
-
-```
-Goals update rolled back.
-  Reason: {error message}
-  foundations/config/organization-model.ts — restored to previous state
-  No changes persisted.
-```
+# Configure: goals
+
+Guides the user through reviewing and updating the `goals` domain of the organization model.
+
+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 reference
+
+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)
+})
+```
+
+Cross-reference constraint: `periodEnd` must be strictly after `periodStart`. Enforced at parse
+time by `OrganizationModelSchema.superRefine()`.
+
+The field name in the schema is `objectives` (not `goals`) and the measurable-outcome array is
+`keyResults` (not `outcomes`) — these are internal field names, not user-facing vocabulary.
+
+Where this lands in the adapter: `foundations/config/organization-model.ts` under the `goals`
+key of `defineOrganizationModel({...})`.
+
+---
+
+## Process
+
+### Step 1: Read current state
+
+Read `foundations/config/organization-model.ts` and extract the current `goals.objectives` array.
+Present as a plain-language summary:
+
+```
+Current goals (N):
+  1. "{description truncated to 80 chars}" ({id})
+     Period: {periodStart} → {periodEnd}
+     Measurable outcomes: {count}
+  (no goals defined yet)
+```
+
+### Step 2: Establish intent
+
+Ask whether the user wants to:
+
+- **Add** a new goal
+- **Edit** an existing goal (by description or number)
+- **Remove** a goal
+- **Update progress** on a measurable outcome (update `currentValue`)
+
+### Step 3: Gather goal details
+
+For each goal being added or edited:
+
+**Core goal:**
+
+- "What is the organization working toward? Describe the goal in plain language — one or two sentences."
+- "Give it a stable ID — lowercase with hyphens, e.g. `goal-grow-arr-q1-2026`."
+- "What period does this goal cover? (Start date and end date — e.g. 2026-01-01 to 2026-03-31)"
+
+Validate that the end date is strictly after the start date before proceeding.
+
+**Measurable outcomes (optional but recommended):**
+
+- "Do you want to add any measurable outcomes under this goal? These help track whether you're
+  on track."
+- For each outcome: "What are you measuring? (e.g. monthly revenue, NPS score, trial-to-paid
+  conversion rate)"
+- "What's the target value? (Optional — leave blank if the outcome is directional.)"
+- "What's the current value?"
+- "Give this outcome an ID — e.g. `kr-revenue-q1`."
+
+Capture as many outcomes as the user wants. One at a time is fine.
+
+### Step 4: Confirm before writing
+
+Present a diff:
+
+```
+Proposed goals change:
+
+ADD goal "Reach $50K MRR by end of Q1 2026" (goal-arr-q1-2026):
+  period:  2026-01-01 → 2026-03-31
+  outcomes:
+    kr-mrr-q1: "Grow monthly recurring revenue"
+      metric:  "monthly recurring revenue (MRR)"
+      current: 32000
+      target:  50000
+    kr-churn-q1: "Reduce churn rate"
+      metric:  "monthly churn rate (%)"
+      current: 4.2
+      target:  2.5
+
+Apply? (yes/no)
+```
+
+### Step 5: Codify
+
+Execute `.claude/skills/configure/operations/codify-level-a.md` with the proposed `goals` block.
+Only the `objectives` array is written — no other keys in the adapter are touched.
+
+When updating progress only (updating `currentValue` on an existing outcome), make a targeted
+edit rather than rewriting the entire goals block.
+
+### Step 6: Report
+
+After successful validation:
+
+```
+Goals updated.
+  Goals: {total count} ({N added / N edited / N removed})
+  foundations/config/organization-model.ts — goals.objectives updated
+  Type-check: PASS
+  Schema validation: PASS
+```
+
+If validation failed and rollback occurred:
+
+```
+Goals update rolled back.
+  Reason: {error message}
+  foundations/config/organization-model.ts — restored to previous state
+  No changes persisted.
+```

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

@@ -1,133 +1,133 @@
-# Configure: identity
-
-Guides the user through reviewing and updating the `identity` domain of the organization model.
-
-The `identity` domain captures legal identity, purpose, and operational anchors — distinct from
-`branding` (display identity: logos, product names). Editing identity fields here does not touch
-any visual or branding configuration.
-
-## Schema reference
-
-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.
-
-Where this lands in the adapter: `foundations/config/organization-model.ts` under the `identity`
-key of `defineOrganizationModel({...})`.
-
----
-
-## Process
-
-### Step 1: Read current state
-
-Read `foundations/config/organization-model.ts` and extract the current `identity` block. Present
-it to the user as a plain-language summary, not a raw code dump:
-
-```
-Current identity:
-  Mission:          {value or "(not set)"}
-  Vision:           {value or "(not set)"}
-  Legal name:       {value or "(not set)"}
-  Entity type:      {value or "(not set)"}
-  Jurisdiction:     {value or "(not set)"}
-  Industry:         {value or "(not set)"}
-  Geographic focus: {value or "(not set)"}
-  Time zone:        {value}
-  Business hours:   {configured days or "not configured"}
-```
-
-### Step 2: Ask conversationally
-
-Work through the fields in natural conversation. You do not need to ask every field in a single
-message — group related ones together and react to what the user shares.
-
-**Group A — Purpose:**
-
-- "What's the organization's mission? (Why does it exist — one or two sentences.)"
-- "What's the vision? (Where is the organization headed long-term?)"
-
-**Group B — Legal identity:**
-
-- "What's the legal registered name of the organization?"
-- "What type of legal entity is it? (e.g. LLC, Corporation, Sole Proprietor, Non-profit)"
-- "What jurisdiction is it registered in? (e.g. United States – Delaware, Canada – Ontario)"
-
-**Group C — Industry and geography:**
-
-- "What industry or category best describes the organization? (e.g. Marketing Agency, SaaS, Professional Services)"
-- "Where does it primarily operate or serve? (e.g. North America, Global, Southeast Asia)"
-
-**Group D — Temporal anchors:**
-
-- "What time zone does the team primarily operate in? I'll use an IANA identifier like
-  America/Los_Angeles or Europe/London."
-- "Do you want to capture standard business hours? (e.g. Mon–Fri 09:00–17:00)"
-
-If a field already has a non-empty value, show the current value and ask whether to keep or change it.
-Never silently overwrite existing values without confirmation.
-
-### Step 3: Confirm before writing
-
-Present a diff-style summary of all proposed changes:
-
-```
-Proposed identity changes:
-  mission:          "" → "We help SMBs automate complex operations using AI."
-  vision:           (unchanged) "(not set)"
-  legalName:        "" → "Acme Operations LLC"
-  entityType:       "" → "LLC"
-  jurisdiction:     "" → "United States – Delaware"
-  industryCategory: "" → "AI Automation / Professional Services"
-  geographicFocus:  "" → "North America"
-  timeZone:         "UTC" → "America/Chicago"
-  businessHours:    {} → { monday–friday: 09:00–17:00 }
-
-Apply these changes? (yes/no)
-```
-
-If the user says no, abort without writing anything.
-
-### Step 4: Codify
-
-Execute `.claude/skills/configure/operations/codify-level-a.md` with these changes targeting the
-`identity` key inside the `defineOrganizationModel({...})` call in
-`foundations/config/organization-model.ts`.
-
-Only write the fields the user confirmed. Do not add or remove other top-level keys in the adapter.
-
-### Step 5: Report
-
-After successful validation:
-
-```
-Identity updated.
-  Fields changed: {list}
-  foundations/config/organization-model.ts — identity block updated
-  Type-check: PASS
-  Schema validation: PASS
-```
-
-If validation failed and rollback occurred, report:
-
-```
-Identity update rolled back.
-  Reason: {error message}
-  foundations/config/organization-model.ts — restored to previous state
-  No changes persisted.
-```
+# Configure: identity
+
+Guides the user through reviewing and updating the `identity` domain of the organization model.
+
+The `identity` domain captures legal identity, purpose, and operational anchors — distinct from
+`branding` (display identity: logos, product names). Editing identity fields here does not touch
+any visual or branding configuration.
+
+## Schema reference
+
+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.
+
+Where this lands in the adapter: `foundations/config/organization-model.ts` under the `identity`
+key of `defineOrganizationModel({...})`.
+
+---
+
+## Process
+
+### Step 1: Read current state
+
+Read `foundations/config/organization-model.ts` and extract the current `identity` block. Present
+it to the user as a plain-language summary, not a raw code dump:
+
+```
+Current identity:
+  Mission:          {value or "(not set)"}
+  Vision:           {value or "(not set)"}
+  Legal name:       {value or "(not set)"}
+  Entity type:      {value or "(not set)"}
+  Jurisdiction:     {value or "(not set)"}
+  Industry:         {value or "(not set)"}
+  Geographic focus: {value or "(not set)"}
+  Time zone:        {value}
+  Business hours:   {configured days or "not configured"}
+```
+
+### Step 2: Ask conversationally
+
+Work through the fields in natural conversation. You do not need to ask every field in a single
+message — group related ones together and react to what the user shares.
+
+**Group A — Purpose:**
+
+- "What's the organization's mission? (Why does it exist — one or two sentences.)"
+- "What's the vision? (Where is the organization headed long-term?)"
+
+**Group B — Legal identity:**
+
+- "What's the legal registered name of the organization?"
+- "What type of legal entity is it? (e.g. LLC, Corporation, Sole Proprietor, Non-profit)"
+- "What jurisdiction is it registered in? (e.g. United States – Delaware, Canada – Ontario)"
+
+**Group C — Industry and geography:**
+
+- "What industry or category best describes the organization? (e.g. Marketing Agency, SaaS, Professional Services)"
+- "Where does it primarily operate or serve? (e.g. North America, Global, Southeast Asia)"
+
+**Group D — Temporal anchors:**
+
+- "What time zone does the team primarily operate in? I'll use an IANA identifier like
+  America/Los_Angeles or Europe/London."
+- "Do you want to capture standard business hours? (e.g. Mon–Fri 09:00–17:00)"
+
+If a field already has a non-empty value, show the current value and ask whether to keep or change it.
+Never silently overwrite existing values without confirmation.
+
+### Step 3: Confirm before writing
+
+Present a diff-style summary of all proposed changes:
+
+```
+Proposed identity changes:
+  mission:          "" → "We help SMBs automate complex operations using AI."
+  vision:           (unchanged) "(not set)"
+  legalName:        "" → "Acme Operations LLC"
+  entityType:       "" → "LLC"
+  jurisdiction:     "" → "United States – Delaware"
+  industryCategory: "" → "AI Automation / Professional Services"
+  geographicFocus:  "" → "North America"
+  timeZone:         "UTC" → "America/Chicago"
+  businessHours:    {} → { monday–friday: 09:00–17:00 }
+
+Apply these changes? (yes/no)
+```
+
+If the user says no, abort without writing anything.
+
+### Step 4: Codify
+
+Execute `.claude/skills/configure/operations/codify-level-a.md` with these changes targeting the
+`identity` key inside the `defineOrganizationModel({...})` call in
+`foundations/config/organization-model.ts`.
+
+Only write the fields the user confirmed. Do not add or remove other top-level keys in the adapter.
+
+### Step 5: Report
+
+After successful validation:
+
+```
+Identity updated.
+  Fields changed: {list}
+  foundations/config/organization-model.ts — identity block updated
+  Type-check: PASS
+  Schema validation: PASS
+```
+
+If validation failed and rollback occurred, report:
+
+```
+Identity update rolled back.
+  Reason: {error message}
+  foundations/config/organization-model.ts — restored to previous state
+  No changes persisted.
+```