Resolving locale, route permissions, and workspace projection.
Current scope: Gest
Category: 10_normative | Version: v1.0.0
Owner: DOCUMENT_CUSTODIAN | Review cycle: 90 days
Approval Authority: GOVERNANCE_ADMIN
Read-only Documentation Portal. Editing and mutation endpoints are disabled.
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