ICPI Rollback Window Status

Status

Rollback to legacy colocated ICPI hosting is closed.

What Closed

Closed rollback elements:

• legacy ICPI route mounting inside svc-tenders
• legacy ICPI route/support/repository fallback path
• explicit gateway fallback startup script dev:api:icpi-fallback

Rollback Implications

Current implication:

• svc-icpi is the only supported ICPI runtime
• rollback no longer means pointing the gateway back at colocated svc-tenders ICPI hosting
• recovery now means fixing or redeploying svc-icpi while keeping the gateway route shape unchanged

Why Closure Is Acceptable Now

Rollback closure is justified because:

1. parity was verified for reads, protected-write denials, and successful authenticated writes
2. a live env-only cutover window was executed successfully
3. svc-icpi has already been operating as the active primary runtime
4. the team explicitly requested a non-indefinite decision

Current Gateway Posture

The gateway contract remains unchanged in services/api/src/routes/icpi.ts:

• ICPI_SERVICE_URL ?? TENDERS_SERVICE_URL ?? "http://localhost:4020"

Operationally:

• ICPI_SERVICE_URL should point to svc-icpi
• TENDERS_SERVICE_URL remains part of the existing gateway shape, but it is no longer a supported ICPI rollback path

Remaining Risk

The main remaining ICPI-specific cleanup risk is no longer route/runtime fallback or migration-path ambiguity.

Notes

• Gateway behavior is unchanged.
• Auth behavior is unchanged.
• svc-tenders still remains required for other domains; only its ICPI runtime slice was retired.
• Migration invocation is now explicit through migrate:all including migrate:icpi.