Loading module
Resolving locale, route permissions, and workspace projection.
Resolving locale, route permissions, and workspace projection.
Текущая область: Гость
Категория: 10_normative | Версия: v1.0.0
Владелец: DOCUMENT_CUSTODIAN | Цикл пересмотра: 90 дней
Утверждающий орган: GOVERNANCE_ADMIN
Портал документации доступен только для чтения. Редактирование и mutation endpoints отключены.
Платформа Kvary изначально создана на грузинском языке. Там, где существует грузинская версия, именно грузинский язык является авторитетным для UI платформы, документации и юридического толкования.
Переводы на другие языки предоставляются только для удобства. Отдельные записи и flow могут изначально существовать на других языках и иметь собственный source/legal locale, но там, где доступна грузинская версия, для формулировок и толкования на уровне платформы приоритет имеет грузинский текст.
Метаданные неполные: Document ID, Version, Status, Owner Role, Last Review Date, Next Review Date, Change Log
svc-tenders Route Sequence MapThis note documents the repeated handler-stage patterns in the densest svc-tenders route modules after Cleanup Sprint 34.
Focus:
Labels used here:
VERIFIEDREALTRANSITIONALregisterTenderDeclarationRoutes.tsRoute module:
Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDsupport.canCheckTenderDeclaration(...) is the broader helper for read/check routesRepository/dependency touchpoint:
findTenderDeclarationById(...)saveTenderDeclarationAssessment(...)Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDsupport.hasTenderDeclarationCapability(...) is narrower than the broader read/check helpersupport.getTenderDeclarationCapabilities(...) feeds readiness/state derivation before the final guardRepository/dependency touchpoint:
findTenderDeclarationById(...)markTenderDeclarationReady(...)declareTender(...)Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDDRAFT state guard before persistenceRepository/dependency touchpoint:
findTenderDeclarationById(...)support.runMulterSingle(...)registerAuctionDeclarationRoutes.tsRoute module:
Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDsupport.canCheckAuctionDeclaration(...) carries the broader read/check surfaceRepository/dependency touchpoint:
findAuctionDeclarationById(...)saveAuctionDeclarationAssessment(...)Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDsupport.hasAuctionDeclarationCapability(...) gates writes more narrowly than the broader read/check helperRepository/dependency touchpoint:
updateAuctionDeclarationDraft(...)markAuctionDeclarationReady(...)declareAuction(...)Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDRepository/dependency touchpoint:
support.runMulterSingle(...)Unresolved or transitional notes:
TRANSITIONALregisterKesRoutes.tsRoute module:
Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDRepository/dependency touchpoint:
Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDRepository/dependency touchpoint:
Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDverifyIncomingSignatureGate(...)Repository/dependency touchpoint:
approveKesOrchestratorPayment(...)settleKesOrchestratorPayment(...)Repeated sequence pattern:
Purpose:
Broader vs stricter notes:
VERIFIEDRepository/dependency touchpoint:
requestKesOrchestratorPayment(...)Unresolved or transitional notes:
TRANSITIONALVERIFIED
The repeated route-sequence patterns are intentionally not uniform:
DRAFT state guard