svc-tenders Auth Surface Map
Purpose
This note documents the route-cluster auth and gate surfaces in the densest svc-tenders route modules after Cleanup Sprint 39.
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 Auth Surface MapThis note documents the route-cluster auth and gate surfaces in the densest svc-tenders route modules after Cleanup Sprint 39.
Focus:
requireServiceAuth boundariesLabels used here:
VERIFIEDREALTRANSITIONALregisterTenderDeclarationRoutes.tsRoute module:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthcanCheckTenderDeclaration(...)Classification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthhasTenderDeclarationCapability(..., "tender:create-draft")Classification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthClassification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthDRAFT state guardClassification:
Notable asymmetry:
VERIFIEDregisterAuctionDeclarationRoutes.tsRoute module:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthClassification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthcanCheckAuctionDeclaration(...)Classification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthClassification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthhasAuctionDeclarationCapability(..., "auction:create-draft")Classification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthClassification:
Notable asymmetry:
VERIFIEDUnresolved or transitional notes:
TRANSITIONALregisterKesRoutes.tsRoute module:
Route cluster:
Dominant auth/gate surface:
requireServiceAuth onlyClassification:
Route cluster:
Dominant auth/gate surface:
Classification:
Notes:
VERIFIEDrequireServiceAuthRoute cluster:
Dominant auth/gate surface:
requireServiceAuth onlyClassification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuth onlyClassification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuthClassification:
Route cluster:
Dominant auth/gate surface:
requireServiceAuth onlyClassification:
Notable asymmetry:
VERIFIEDUnresolved or transitional notes:
TRANSITIONALVERIFIED
The auth surfaces remain intentionally different: