# OM Deployment Drift Detection

## Why this note exists

The platform API now persists deployed Organization Model snapshots and validates tenant
lead-gen and CRM catalogs against the requesting tenant's active deployed model. The
template does not need source changes for this server-side fix, but template-derived
projects should accept the `@elevasis/core` package baseline when this release train
publishes it so generated database and shared type surfaces stay aligned.

## Applies to

Template-derived projects that use SDK deployments, lead-gen list creation, CRM stages,
or CRM actions through the hosted Elevasis API.

## Required actions

1. Pull the package baseline update produced by this ship train.
2. Redeploy or verify tenant operations resources if the project has recently changed its
   Organization Model catalogs.
3. After the API deployment stage completes, smoke lead-gen list creation with a
   project-owned build template ID.

## Verification

Run the normal template-derived project gates after syncing:

```powershell
pnpm -C core test
pnpm -C operations check-types
pnpm -C operations check
pnpm -C ui check-types
pnpm -C ui build
```

For projects using lead-gen, also verify list creation against the hosted API with a
tenant-owned build template ID.

## Not handled by /git-sync

`/git-sync` cannot apply the production database change or deploy the hosted API. It also
does not create project-specific Organization Model catalogs or workflow resources.
