# 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

- **Systems and Resources descriptors** -- `core/config/organization-model/systems.ts` (split
  projects) or `core/config/organization-model.ts` (unsplit projects).
- `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.

**Note:** `techStack` is not currently authored as a top-level key in either the template or
reference tenant model. Integration context lives in Resource descriptors (`systems.ts`) and
project knowledge nodes rather than a dedicated `techStack` domain block. Do not invent a
`techStack` key in `profile.ts`; if the schema adds one in a future SDK release, this note will
be updated.

## 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.
