svc-tenders Error Surface Map
Purpose
This note documents the recurring error families in the densest svc-tenders route modules after Cleanup Sprint 37.
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 Error Surface MapThis note documents the recurring error families in the densest svc-tenders route modules after Cleanup Sprint 37.
Focus:
400 validation/input failures403 visibility/capability/ingress denials404 not-found surfaces409 state/conflict/domain-transition failuresLabels used here:
VERIFIEDREALTRANSITIONALregisterTenderDeclarationRoutes.tsRoute module:
Error cluster:
Dominant status family:
400403404Classification:
Notes:
VERIFIEDError cluster:
Dominant status family:
400403404409Classification:
Notes:
VERIFIED404 missing draft target and 409 draft-state or ID-mismatch conflictsError cluster:
Dominant status family:
400403404409Classification:
Notes:
VERIFIED409 here is primarily readiness/state-machine conflict rather than repository uniqueness conflictError cluster:
Dominant status family:
400403404409Classification:
Notes:
VERIFIED400 upload/evidence-group failures and 409 draft-state conflict before persistenceregisterAuctionDeclarationRoutes.tsRoute module:
Error cluster:
Dominant status family:
400403404Classification:
Notes:
VERIFIED409 state-machine pattern as declaration transitionsError cluster:
Dominant status family:
400403404Classification:
Error cluster:
Dominant status family:
400403404409Classification:
Notes:
VERIFIEDauction:create-draftError cluster:
Dominant status family:
400403404409Classification:
Notes:
VERIFIEDError cluster:
Dominant status family:
400403404409Classification:
Notes:
VERIFIED409 here is the announce/readiness conflict family rather than a generic repository failureUnresolved or transitional notes:
TRANSITIONALregisterKesRoutes.tsRoute module:
Error cluster:
Dominant status family:
400500Classification:
Notes:
VERIFIED500 create failure rather than the more common 409 action conflict familyError cluster:
Dominant status family:
400404Classification:
Notes:
VERIFIEDError cluster:
Dominant status family:
400409Classification:
Error cluster:
Dominant status family:
400404409Classification:
Notes:
VERIFIED404 missing case, while lifecycle transitions skew toward 409 invalid stateError cluster:
Dominant status family:
400403404409Classification:
Notes:
VERIFIEDError cluster:
Dominant status family:
400409Classification:
Notable asymmetry:
VERIFIED403 denial patterns in this dense cluster409 familiesUnresolved or transitional notes:
TRANSITIONALVERIFIED
The recurring error families remain intentionally different:
400 / 403 / 404 / 409 family, but auction additionally mixes in output-allocation-specific not-found/input paths403 denial and a 500 case-create failure surface that declaration routes do not use