ICPI Primary And Fallback Status

Current Primary Runtime

Primary ICPI runtime:

• services/svc-icpi

Primary bootstrap:

• server.ts

Primary route surface:

• registerIcpiRoutes.ts

Current intent:

• svc-icpi is the active primary runtime for ICPI reads and writes
• gateway traffic should resolve to svc-icpi first

Rollback Status

Rollback to legacy colocated ICPI hosting is now closed.

Current implication:

• there is no active svc-tenders ICPI fallback runtime anymore
• svc-icpi is the only supported ICPI service runtime
• any future rollback would need to target svc-icpi deployment/config itself, not the old colocated host

Current Gateway Seam

Gateway route surface:

• icpi.ts

Current seam:

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

Current operational expectation:

• ICPI_SERVICE_URL should point at svc-icpi
• TENDERS_SERVICE_URL remains part of the unchanged gateway shape, but it is no longer an operational ICPI rollback target

Current Script / Runtime Defaults

Primary-oriented defaults:

• package.json dev
• package.json dev:core
• package.json dev:api

These now point ICPI at:

• http://localhost:4021

Rollback Method

Legacy-host rollback no longer remains available.

Current rollback posture is narrower:

1. keep gateway route shape unchanged
2. keep ICPI_SERVICE_URL pointed at the active svc-icpi runtime
3. recover by fixing svc-icpi deployment/runtime issues rather than switching back to colocated ICPI hosting

Notes

• svc-tenders as a service is still required for many non-ICPI domains.
• Only the ICPI slice inside svc-tenders was retired in this context.
• The gateway seam stayed unchanged even though the legacy host was removed.