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
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