ICPI Migration Ownership Status

Canonical Owner

The canonical owner for ICPI migrations is now:

• services/svc-icpi/migrations

This matches the extracted ICPI runtime being the active primary host.

Canonical Migration Files

The current ICPI migration set is:

• services/svc-icpi/migrations/0007_icpi_price_points.sql
• services/svc-icpi/migrations/0008_icpi_latest_lookup_index.sql

Old-Host Copy Status

The duplicate ICPI migration copies have now been removed from svc-tenders.

Status Classification

• canonical owner: svc-icpi
• old-host copies: removed
• safe to delete now: yes, already deleted
• ownership transfer status: runtime and migration transfer complete

Evidence For Canonical Ownership

Runtime ownership

The active primary ICPI runtime is services/svc-icpi/src/server.ts, not svc-tenders.

Root workflow ownership

The repo now exposes:

• migrate:icpi in package.json
• migrate:all including migrate:icpi in package.json

That makes ICPI migration invocation explicit rather than implied by old colocated migration copies.

Duplicate-file parity before deletion

Before deletion, the old and new migration files were byte-for-byte identical:

• 0007_icpi_price_points.sql: same checksum in svc-tenders and svc-icpi
• 0008_icpi_latest_lookup_index.sql: same checksum in svc-tenders and svc-icpi

So this was not a divergence problem. It was a cleanup-timing problem.

Invocation Decision

The migration invocation decision is now explicit:

• migrate:all includes migrate:icpi

Canonical operator command paths:

• package.json migrate:all
• package.json migrate:icpi

Operator meaning:

1. use npm run migrate:all for the full local/platform migration sweep
2. use npm run migrate:icpi only for ICPI-only schema work

Old-Path Reference Safety

After deleting the old svc-tenders ICPI migration copies, current scripts, docs, and bootstraps should point to:

• services/svc-icpi/migrations/0007_icpi_price_points.sql
• services/svc-icpi/migrations/0008_icpi_latest_lookup_index.sql
• package.json migrate:all
• package.json migrate:icpi

Practical Interpretation

• evolve ICPI schema from svc-icpi
• run ICPI migrations through migrate:all for full platform setup
• use migrate:icpi only for ICPI-only operational work