@elevasis/sdk 1.22.1 → 1.23.0

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

@@ -1,30 +1,30 @@
-# TechStack Context
-
-Tech stack information is no longer modeled through `resourceMappings`. Resource identity and governance metadata live in OM Resources descriptors under the id-keyed `organizationModel.resources` map; external platform context belongs on the relevant integration descriptor or in project knowledge when the descriptor schema does not expose a dedicated field yet.
-
-## Current Resource-Governance Contract
-
-- Resource IDs are authored once in `core/config/organization-model.ts`.
-- Runtime workflows, agents, and integrations derive `resourceId` / `type` from OM descriptors during deployment assembly.
-- `DeploymentSpec` remains the runtime/deploy bundle, not an independent identity catalog.
-- `pnpm -C operations check` validates descriptor/code alignment before deploy.
-
-## Where To Look
-
-- `core/config/organization-model.ts` -- Systems and Resources descriptors.
-- `operations/src/index.ts` -- deployment assembly that binds executable behavior to descriptors.
-- `pnpm elevasis-sdk project:list --pretty` -- live deployed resource surface.
-- Project knowledge nodes -- narrative details such as credential owner, setup notes, and system-of-record rationale when they do not fit the descriptor shape.
-
-## Write Path
-
-When the user wants to document or change integration ownership, credential status, or system-of-record context:
-
-1. Inspect `core/config/organization-model.ts` for the relevant integration Resource descriptor.
-2. If the descriptor identity, System membership, owner role, or status is wrong, update the descriptor through the `/knowledge` ceremony where possible.
-3. If the requested detail is operational narrative rather than descriptor schema, capture it in a knowledge node or project documentation instead of recreating `resourceMappings`.
-4. Run `pnpm -C operations check` after descriptor or deployment assembly changes.
-
----
-
-**Read via `/knowledge`** -- natural-language queries like "what integrations are configured?" or "is HubSpot our system of record for contacts?" route here for inspection and recommendation.
+# TechStack Context
+
+Tech stack information is no longer modeled through `resourceMappings`. Resource identity and governance metadata live in OM Resources descriptors under the id-keyed `organizationModel.resources` map; external platform context belongs on the relevant integration descriptor or in project knowledge when the descriptor schema does not expose a dedicated field yet.
+
+## Current Resource-Governance Contract
+
+- Resource IDs are authored once in `core/config/organization-model.ts`.
+- Runtime workflows, agents, and integrations derive `resourceId` / `type` from OM descriptors during deployment assembly.
+- `DeploymentSpec` remains the runtime/deploy bundle, not an independent identity catalog.
+- `pnpm -C operations check` validates descriptor/code alignment before deploy.
+
+## Where To Look
+
+- `core/config/organization-model.ts` -- Systems and Resources descriptors.
+- `operations/src/index.ts` -- deployment assembly that binds executable behavior to descriptors.
+- `pnpm elevasis-sdk project:list --pretty` -- live deployed resource surface.
+- Project knowledge nodes -- narrative details such as credential owner, setup notes, and system-of-record rationale when they do not fit the descriptor shape.
+
+## Write Path
+
+When the user wants to document or change integration ownership, credential status, or system-of-record context:
+
+1. Inspect `core/config/organization-model.ts` for the relevant integration Resource descriptor.
+2. If the descriptor identity, System membership, owner role, or status is wrong, update the descriptor through the `/om` ceremony where possible.
+3. If the requested detail is operational narrative rather than descriptor schema, capture it in a knowledge node or project documentation instead of recreating `resourceMappings`.
+4. Run `pnpm -C operations check` after descriptor or deployment assembly changes.
+
+---
+
+**Read via `/om`** (legacy `/knowledge` alias also accepted) -- natural-language queries like "what integrations are configured?" or "is HubSpot our system of record for contacts?" route here for inspection and recommendation.