svc-tenders Status Code Map
Purpose
This note documents the recurring status-code families in the densest svc-tenders route modules after Cleanup Sprint 38.
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 Status Code MapThis note documents the recurring status-code families in the densest svc-tenders route modules after Cleanup Sprint 38.
Focus:
200 successful read/update/action responses201 create-style responses400 invalid input/request errors403 capability or ingress denials404 not-found cases409 state/conflict/domain-transition errorsLabels used here:
VERIFIEDREALTRANSITIONALregisterTenderDeclarationRoutes.tsRoute module:
Route cluster:
Dominant status families:
200400403404Classification:
Route cluster:
Dominant status families:
201200400 / 403 / 404 / 409Classification:
Route cluster:
Dominant status families:
200400 / 403 / 404 / 409Classification:
Route cluster:
Dominant status families:
201200200-style headers400 / 403 / 404 / 409Classification:
Notable asymmetry:
VERIFIEDregisterAuctionDeclarationRoutes.tsRoute module:
Route cluster:
Dominant status families:
200201400 / 403 / 404Classification:
Route cluster:
Dominant status families:
200400403404Classification:
Route cluster:
Dominant status families:
201200200-style headers400 / 403 / 404 / 409Classification:
Route cluster:
Dominant status families:
201200400 / 403 / 404 / 409Classification:
Route cluster:
Dominant status families:
200400 / 403 / 404 / 409Classification:
Notable asymmetry:
VERIFIEDUnresolved or transitional notes:
TRANSITIONALregisterKesRoutes.tsRoute module:
Route cluster:
Dominant status families:
201400 / 500Classification:
Route cluster:
Dominant status families:
200400 / 404Classification:
Route cluster:
Dominant status families:
200400 / 409Classification:
Route cluster:
Dominant status families:
200201400 / 404 / 409Classification:
Route cluster:
Dominant status families:
201200400 / 403 / 404 / 409Classification:
Route cluster:
Dominant status families:
200400 / 409Classification:
Notable asymmetry:
VERIFIED500 outlier among the dense modulesUnresolved or transitional notes:
TRANSITIONALVERIFIED
The status-code families remain intentionally different:
200 / 201 / 400 / 403 / 404 / 409 family, with evidence download breaking into stream/header behavior500 create-failure outlier and has no stream/download branch in this dense cluster