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 Cluster Stack Order MapThis note documents the comment-stack ordering used under the dense route-cluster headers in after Cleanup Sprint 43.
svc-tendersFocus:
Labels used here:
VERIFIEDREALTRANSITIONALVERIFIED
Where the full stack exists, the dominant order is now:
Why this order:
registerTenderDeclarationRoutes.tsRoute module:
Route cluster:
ADMIN READ SURFACEDRAFT AUTHORING SURFACEREADINESS / DECLARE TRANSITION SURFACEEVIDENCE SURFACEStack order:
Where wording/order was aligned:
registerAuctionDeclarationRoutes.tsRoute module:
Route cluster:
OUTPUT-ALLOCATION ADMIN SURFACEADMIN READ SURFACEEVIDENCE SURFACEDRAFT AUTHORING SURFACEREADINESS / ANNOUNCE TRANSITION SURFACEStack order:
Where wording/order was aligned:
Where wording/order intentionally stayed different:
OUTPUT-ALLOCATION ADMIN SURFACE still keeps the OWNERSHIP NOTE after the shared stack because it is a transitional note, not part of the common explanatory layersAsymmetry/transitional notes:
TRANSITIONALregisterKesRoutes.tsRoute module:
Route cluster:
CASE ENTRY SURFACEOPERATOR READ / CONTROL-PLANE SURFACEPROCESS-MAP MUTATION SURFACECASE / TASK / INSPECTION ACTION SURFACEPAYMENT-SENSITIVE ACTION SURFACECASE CLOSURE ACTIONStack order:
Where wording/order was aligned:
Where wording/order intentionally stayed different:
Asymmetry/transitional notes:
VERIFIEDVERIFIED
These items intentionally remain outside the shared stack:
OWNERSHIP NOTE under OUTPUT-ALLOCATION ADMIN SURFACEVALIDATION STACK and SUPPORT CONSUMPTION comments inside handlersReason: