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 Response Surface MapThis note documents the recurring response shapes in the densest svc-tenders route modules after Cleanup Sprint 36.
Focus:
Labels used here:
VERIFIEDREALTRANSITIONALregisterTenderDeclarationRoutes.tsRoute module:
Response cluster:
Dominant response shape:
{ ok, declaration }Classification:
Response cluster:
Dominant response shape:
{ ok, declaration, validation, preview }Classification:
Notes:
VERIFIEDResponse cluster:
Dominant response shape:
{ ok, declaration, validation, preview }{ ok, declaration, validation, preview, event }Classification:
Response cluster:
Dominant response shape:
{ ok, evidence, reference }{ ok, evidence }Classification:
Notable asymmetry:
VERIFIEDregisterAuctionDeclarationRoutes.tsRoute module:
Response cluster:
Dominant response shape:
{ ok, allocations }{ ok, allocation }Classification:
Response cluster:
Dominant response shape:
{ ok, declaration }Classification:
Response cluster:
Dominant response shape:
{ ok, evidence, reference }{ ok, evidence }Classification:
Response cluster:
Dominant response shape:
{ ok, declaration, validation, preview }Classification:
Response cluster:
Dominant response shape:
{ ok, declaration, validation, preview }{ ok, declaration, validation, preview, event }Classification:
Notable asymmetry:
VERIFIEDallocation response family in the same moduleUnresolved or transitional notes:
TRANSITIONALregisterKesRoutes.tsRoute module:
Response cluster:
Dominant response shape:
{ ok, caseId, detail }Classification:
Response cluster:
Dominant response shape:
{ ok, cases, meta }{ ok, detail }{ ok, projection }{ ok, map }{ ok, snapshot }{ ok, suggestions, meta }Classification:
Response cluster:
Dominant response shape:
{ ok, map }Classification:
Response cluster:
Dominant response shape:
{ ok, detail }Classification:
Notes:
VERIFIED201, but the payload family stays detail-orientedResponse cluster:
Dominant response shape:
{ ok, detail }Classification:
Response cluster:
Dominant response shape:
{ ok, detail }Classification:
Notable asymmetry:
VERIFIEDvalidation + preview response family at allsnapshot, meta, and projectionUnresolved or transitional notes:
TRANSITIONALVERIFIED
The dense response surfaces are intentionally different:
declaration + validation + preview familyallocation response payloads in the same moduledetail action results and aggregate read payloads instead of preview/validation responses