ICPI Rollback Window Status
Status
Rollback to legacy colocated ICPI hosting is closed.
What Closed
Closed rollback elements:
Resolving locale, route permissions, and workspace projection.
Current scope: Guest
Category: 10_normative | Version: v1.0.0
Owner: DOCUMENT_CUSTODIAN | Review cycle: 90 days
Approval authority: GOVERNANCE_ADMIN
Documentation portal is read-only. Editing and mutation endpoints are disabled.
Kvary platform is originally created in Georgian. Where a Georgian version exists, Georgian is authoritative for platform UI, documentation, and legal interpretation.
Translations into other languages are provided for convenience. Some records may originate in other languages and carry their own source or legal locale for a specific flow, but where a Georgian version is available, the Georgian version prevails for platform-level wording and interpretation.
Metadata incomplete: Document ID, Version, Status, Owner Role, Last Review Date, Next Review Date, Change Log
Rollback to legacy colocated ICPI hosting is closed.
Closed rollback elements:
svc-tendersdev:api:icpi-fallbackCurrent implication:
svc-icpi is the only supported ICPI runtimesvc-tenders ICPI hostingsvc-icpi while keeping the gateway route shape unchangedRollback closure is justified because:
svc-icpi has already been operating as the active primary runtimeThe 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-icpiTENDERS_SERVICE_URL remains part of the existing gateway shape, but it is no longer a supported ICPI rollback pathThe main remaining ICPI-specific cleanup risk is no longer route/runtime fallback or migration-path ambiguity.
svc-tenders still remains required for other domains; only its ICPI runtime slice was retired.migrate:all including migrate:icpi.