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 Support And Gate MapThis note documents the support/gate responsibilities of the two densest support modules in after Cleanup Sprint 24:
svc-tendersThe goal is to make it obvious:
Labels used here:
VERIFIEDREALTRANSITIONALdeclarationRouteSupport.tsSupport module:
Consumed by route modules:
Status:
VERIFIEDTRANSITIONALWhy transitional:
Purpose:
Helpers:
getTenderDeclarationCapabilities(...)hasTenderDeclarationCapability(...)canCheckTenderDeclaration(...)getAuctionDeclarationCapabilities(...)hasAuctionDeclarationCapability(...)canCheckAuctionDeclaration(...)What it does:
*, admin:*, tender:*, auction:*Broader vs stricter gate note:
canCheckTenderDeclaration(...)canCheckAuctionDeclaration(...)hasTenderDeclarationCapability(...)hasAuctionDeclarationCapability(...)This distinction matters because declaration read/check endpoints are intentionally broader than state-changing endpoints.
Purpose:
Helpers:
parseTenderDeclarationEvidenceGroupKey(...)parseAuctionDeclarationEvidenceGroupKey(...)What it does:
undefinedTender evidence groups:
supportingDocumentsspecificationEvidencecomplianceEvidenceAuction evidence groups:
supportingDocumentsqualityEvidencesubjectEvidencetransportEvidenceThis is intentionally asymmetric because tender and auction declarations do not share the exact same evidence buckets.
Purpose:
server.tsInputs forwarded:
requireServiceAuthparseOptionalStringresolveIntentIdrunMulterSingleNotes:
resolveIntentId(...) is shared request-intent normalization, not declaration-specific business logicrunMulterSingle(...) is a declaration upload bridge, but still built from shell-owned upload middlewarekesRouteSupport.tsSupport module:
Consumed by route modules:
Status:
VERIFIEDTRANSITIONALWhy transitional:
Purpose:
Helpers forwarded:
parsePositiveIntparseOptionalIntparseOptionalStringparseOptionalUpperclampPositiveIntWhat it does not do:
Purpose:
Helpers forwarded:
ensureThirdPartyKycBoundary(...)verifyIncomingSignatureGate(...)What it does:
What it does not do:
This is the key distinction for KES:
requireServiceAuthrequireServiceAuthensureThirdPartyKycBoundary(...)verifyIncomingSignatureGate(...)requireServiceAuthverifyIncomingSignatureGate(...)That stricter branching lives in:
This is important: kesRouteSupport.ts exposes ingress helpers, but the route module is where stricter payment gating actually becomes active.
VERIFIED
These two support modules are not symmetric, and that is correct:
Trying to force symmetry here would hide the real support boundary.
VERIFIED
Declaration support still depends on shell-owned auth and upload inputs.
KES support still depends on shell-owned parser and ingress helpers.
KES route support is structurally clear, but the repository input behind the route remains transitional because KES persistence still lives behind the mixed root repository.