@elevasis/sdk 1.15.1 → 1.16.0

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

@@ -1,139 +0,0 @@
-# Configure: techStack
-
-Guides the user through reviewing and updating the tech stack metadata on resource mapping entries
-in the organization model.
-
-Tech stack information lives as an optional `techStack` extension field on each `ResourceMapping`
-entry -- not as a standalone top-level domain. This keeps all integration metadata co-located with
-the resource mapping that represents it, while adding fields that agents need for cross-integration
-automation and system-of-record resolution.
-
-## Schema reference
-
-Source: `packages/core/src/organization-model/domains/shared.ts`
-
-```typescript
-TechStackEntrySchema = z.object({
-  platform:         z.string().trim().min(1).max(200),
-  purpose:          z.string().trim().min(1).max(500),
-  credentialStatus: z.enum(['configured', 'pending', 'expired', 'missing']),
-  isSystemOfRecord: z.boolean().default(false)
-})
-```
-
-`credentialStatus` values:
-
-- `configured` -- credential present and valid
-- `pending` -- not yet set up
-- `expired` -- credential existed but has lapsed
-- `missing` -- expected but not present
-
-`isSystemOfRecord: true` means this integration is the authoritative data source for its domain
-(e.g. HubSpot is the system of record for contacts).
-
-`techStack` is an optional field on `ResourceMappingSchema`. It is added to individual resource
-mapping entries whose `resourceType` is `'integration'` or `'external'`.
-
-Where this lands in the adapter: `foundations/config/organization-model.ts` inside the
-`resourceMappings` array of `defineOrganizationModel({...})`. The `techStack` field is set on the
-matching `ResourceMapping` object.
-
----
-
-## Process
-
-### Step 1: Read current state
-
-Read `foundations/config/organization-model.ts` and extract the `resourceMappings` array. Filter
-to entries that either already have a `techStack` field or have `resourceType: 'integration'` or
-`'external'`. Present as a summary:
-
-```
-Resource mappings with integration context (N):
-  {label} ({id}) -- resourceType: {type}
-    techStack: {platform} | {credentialStatus} | SoR: {yes/no}
-    (no techStack yet)
-
-Other resource mappings (M total, K without techStack):
-  {list by label}
-```
-
-If there are no resource mappings at all, note that the user should add resource mappings through
-the SDK deployment process before configuring tech stack metadata here.
-
-### Step 2: Establish intent
-
-Ask whether the user wants to:
-
-- **Add or update** tech stack metadata on an existing resource mapping
-- **Update credential status** on an existing tech stack entry
-- **Mark or unmark** an integration as the system of record
-- **Review all** integration health
-
-For adding or updating, the user selects a resource mapping from the list.
-
-### Step 3: Gather tech stack details
-
-For each resource mapping being updated:
-
-**If no `techStack` field yet:**
-
-- "What external platform does this resource mapping represent? (e.g. 'HubSpot', 'Stripe',
-  'Notion', 'Apify')"
-- "What is this integration used for? (free-form description)"
-- "What is the current credential status? Options: configured, pending, expired, missing."
-- "Is this the system of record for its domain? (e.g. HubSpot is SoR for contacts)"
-
-**If `techStack` already exists:**
-
-Show the current values and ask which fields to update.
-
-Credential status shortcut: if the user only wants to mark a credential as configured or expired,
-skip directly to that field.
-
-### Step 4: Confirm before writing
-
-Present a diff scoped to the affected resource mapping entry:
-
-```
-Proposed techStack change:
-
-UPDATE resourceMapping "HubSpot CRM Integration" (rm-hubspot):
-  techStack:
-    platform:         "HubSpot"
-    purpose:          "CRM for contacts, companies, and deal pipeline"
-    credentialStatus: "pending" -> "configured"
-    isSystemOfRecord: false -> true
-
-Apply? (yes/no)
-```
-
-### Step 5: Codify
-
-Execute `.claude/skills/configure/operations/codify-level-a.md` with the proposed change to the
-`resourceMappings` array. Only the targeted entry (matched by `id`) is modified -- all other
-entries are left unchanged.
-
-The write edits the `techStack` field on the matching `ResourceMapping` object inside the
-`defineOrganizationModel({...})` call.
-
-### Step 6: Report
-
-After successful validation:
-
-```
-Tech stack updated.
-  Integrations: {total with techStack} ({N updated})
-  foundations/config/organization-model.ts -- resourceMappings updated
-  Type-check: PASS
-  Schema validation: PASS
-```
-
-If validation failed and rollback occurred:
-
-```
-Tech stack update rolled back.
-  Reason: {error message}
-  foundations/config/organization-model.ts -- restored to previous state
-  No changes persisted.
-```