# Schema migration ownership change

**Date:** 2026-09-28

## What changed

1. New task **`AST-SCHEMA-MIG` — Asset V1 Full Schema Migrations — Backend**
   - Branch: `feature-asset-v1-schema-migrations`
   - Depends on: `AST-1.1.1` (module skeleton) + `AST-SCHEMA-1` (DDL lock)
   - Creates **all** V1 Asset tables listed in `ASSET_MANAGEMENT_DATABASE_SCHEMA.md`

2. All other feature BE cards were updated so they:
   - **Do not** create domain table migrations
   - Depend on `AST-SCHEMA-MIG` where they need those tables
   - Build models / repos / services / APIs on existing tables

## Exceptions (still allowed later)

| Task | Allowed schema change |
|------|------------------------|
| AST-1.4.2 | Optional `ALTER employee_assets ADD serialized_asset_id` + data copy |
| AST-1.11.6 | Measured `ADD INDEX` only |

## Order

```text
AST-SCHEMA-1 (DDL lock)
  → AST-1.1.1 (module skeleton)
  → AST-SCHEMA-MIG (all CREATE TABLE)
  → feature BE/FE cards
```

## SQL seed

`ASSET_MANAGEMENT_TASKS_INSERT.sql` now has **99** tasks × **3.00** hours.
If an older 98-row seed was already inserted for project_id=1 / module_id=24, delete those Asset module tasks (or truncate carefully) before re-running, or insert only the new `feature-asset-v1-schema-migrations` row and update descriptions manually.