ICPI Root Compatibility Layer Status
Current Root Compatibility Hosting
The root repository.ts still contains ICPI runtime delegation methods on :
Loading module
Resolving locale, route permissions, and workspace projection.
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
The root repository.ts still contains ICPI runtime delegation methods on :
TendersRepositoryupsertIcpiPricePoints(...)countIcpiPricePoints(...)listIcpiPricePoints(...)suggestIcpiItems(...)findLatestIcpiPricePoint(...)These methods still forward to the dedicated ICPI child repository and therefore remain a temporary runtime compatibility layer.
The root repository no longer re-exports ICPI contract types from src/icpi/contracts.
That means root hosting has been narrowed from:
to:
TendersRepository still truthfully hosts multiple legacy domain slices in one runtimeThis is a better extraction posture than Sprint 45 because the root repository no longer presents itself as the authoritative home of ICPI types. The remaining root edge is operational compatibility only.
TendersRepositoryTendersRepository alongside the dedicated IcpiRepository