ICPI Legacy Retirement Decision

Decision

Legacy ICPI hosting inside svc-tenders is approved for retirement and retired in Sprint 55.

Retirement Approval Status

• Current decision: closed and retired
• Retirement approved now: yes
• Reason class: primary runtime stable enough and rollback explicitly closed

Why Retirement Is Now Approved

1. The extracted runtime is already the proven primary host

The active primary runtime is services/svc-icpi, and the repo has already verified:

• read parity
• protected-write denial parity
• successful authenticated write parity
• live env-only cutover behavior

So the old colocated ICPI host is no longer needed to prove basic runtime correctness.

2. The rollback window is now intentionally closed

The team asked for a non-indefinite answer. Sprint 55 closes the rollback window explicitly rather than leaving fallback posture open-ended.

What closed:

• legacy ICPI route mounting in svc-tenders
• legacy fallback route/support/repository slice
• explicit fallback startup script for the gateway

3. Migration ownership is clear enough to separate runtime retirement from migration cleanup

ICPI migrations now have a clear canonical owner in services/svc-icpi/migrations.

The duplicate legacy copies have now been removed, so both runtime ownership and migration ownership point to svc-icpi.

What Is Safe To Say Now

• svc-icpi is the active primary ICPI runtime.
• legacy ICPI hosting in svc-tenders has been retired.
• gateway and auth behavior do not need further changes for retirement preparation.
• migration ownership is now explicit.

Legacy Removal Package Executed

Sprint 55 removes:

• services/svc-tenders/src/routes/registerIcpiRoutes.ts
• services/svc-tenders/src/routes/support/icpiRouteSupport.ts
• services/svc-tenders/src/icpi/contracts.ts
• services/svc-tenders/src/icpi/validation.ts
• services/svc-tenders/src/icpi/queryParsers.ts
• services/svc-tenders/src/icpi/repository.ts
• the registerIcpiRoutes(...) mount inside services/svc-tenders/src/server.ts
• package.json dev:api:icpi-fallback

Migration-file cleanup is intentionally treated as a separate follow-up cut.

What Still Remains After Retirement

The following still remain by design:

• unchanged gateway route shape in services/api/src/routes/icpi.ts
• unchanged auth behavior
• canonical ICPI migrations in services/svc-icpi/migrations

Verdict

Sprint 55 is the sprint that actually closes the rollback window and retires the legacy ICPI host runtime slice.