Resolving locale, route permissions, and workspace projection.
Current scope: Gest
Category: 10_normative | Version: v1.0.0
Owner: DOCUMENT_CUSTODIAN | Review cycle: 90 days
Approval Authority: GOVERNANCE_ADMIN
Read-only Documentation Portal. Editing and mutation endpoints are disabled.
METADATA INCOMPLETE: Document ID, Version, Status, Owner Role, Last Review Date, Next Review Date, Change Log
The canonical owner for ICPI migrations is now:
This matches the extracted ICPI runtime being the active primary host.
The current ICPI migration set is:
The duplicate ICPI migration copies have now been removed from svc-tenders.
svc-icpiremovedyes, already deletedruntime and migration transfer completeThe active primary ICPI runtime is services/svc-icpi/src/server.ts, not svc-tenders.
The repo now exposes:
migrate:icpi in package.jsonmigrate:all including migrate:icpi in package.jsonThat makes ICPI migration invocation explicit rather than implied by old colocated migration copies.
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-icpi0008_icpi_latest_lookup_index.sql: same checksum in svc-tenders and svc-icpiSo this was not a divergence problem. It was a cleanup-timing problem.
The migration invocation decision is now explicit:
migrate:all includes migrate:icpiCanonical operator command paths:
migrate:allmigrate:icpiOperator meaning:
npm run migrate:all for the full local/platform migration sweepnpm run migrate:icpi only for ICPI-only schema workAfter deleting the old svc-tenders ICPI migration copies, current scripts, docs, and bootstraps should point to:
svc-icpimigrate:all for full platform setupmigrate:icpi only for ICPI-only operational work