Purpose

This note documents the recurring status-code families in the densest svc-tenders route modules after Cleanup Sprint 38.

Focus:

• 200 successful read/update/action responses
• 201 create-style responses
• 400 invalid input/request errors
• 403 capability or ingress denials
• 404 not-found cases
• 409 state/conflict/domain-transition errors
• stream/download paths that break the normal JSON response pattern

Labels used here:

• VERIFIED
• REAL
• TRANSITIONAL

registerTenderDeclarationRoutes.ts

Route module:

• services/svc-tenders/src/routes/registerTenderDeclarationRoutes.ts

Route cluster:

• admin read

Dominant status families:

• 200
• 400
• 403
• 404

Classification:

• read

Route cluster:

• draft authoring

Dominant status families:

• create: 201
• update: 200
• failures: 400 / 403 / 404 / 409

Classification:

• create
• mutate

Route cluster:

• readiness / declare transitions

Dominant status families:

• success: 200
• failures: 400 / 403 / 404 / 409

Classification:

• mutate

Route cluster:

• evidence surface

Dominant status families:

• upload: 201
• list: 200
• download: stream response with 200-style headers
• failures: 400 / 403 / 404 / 409

Classification:

• evidence
• stream-download

Notable asymmetry:

• VERIFIED
• tender evidence download is the clearest place where the module breaks the normal JSON response pattern and switches into header + stream behavior

registerAuctionDeclarationRoutes.ts

Route module:

• services/svc-tenders/src/routes/registerAuctionDeclarationRoutes.ts

Route cluster:

• output-allocation admin surface

Dominant status families:

• list/detail/update: 200
• create: 201
• failures: 400 / 403 / 404

Classification:

• read
• create
• mutate
• transitional

Route cluster:

• admin read

Dominant status families:

• 200
• 400
• 403
• 404

Classification:

• read

Route cluster:

• evidence surface

Dominant status families:

• upload: 201
• list: 200
• download: stream response with 200-style headers
• failures: 400 / 403 / 404 / 409

Classification:

• evidence
• stream-download

Route cluster:

• draft authoring

Dominant status families:

• create: 201
• update: 200
• failures: 400 / 403 / 404 / 409

Classification:

• create
• mutate
• transitional

Route cluster:

• readiness / announce transitions

Dominant status families:

• success: 200
• failures: 400 / 403 / 404 / 409

Classification:

• mutate
• transitional

Notable asymmetry:

• VERIFIED
• this module mixes allocation status-code patterns and declaration status-code patterns in the same route boundary
• evidence download, like tender, switches away from normal JSON payloads into stream response behavior

Unresolved or transitional notes:

• TRANSITIONAL
• the module remains composed because output-allocation administration still shares the declaration route boundary

registerKesRoutes.ts

Route module:

• services/svc-tenders/src/routes/registerKesRoutes.ts

Route cluster:

• case entry

Dominant status families:

• success: 201
• failures: 400 / 500

Classification:

• create

Route cluster:

• operator read / control-plane surface

Dominant status families:

• success: 200
• failures: 400 / 404

Classification:

• read
• aggregate

Route cluster:

• process-map mutation

Dominant status families:

• success: 200
• failures: 400 / 409

Classification:

• mutate

Route cluster:

• case / task / inspection actions

Dominant status families:

• ordinary lifecycle actions: 200
• task/inspection create-like writes: 201
• failures: 400 / 404 / 409

Classification:

• mutate
• create

Route cluster:

• payment-sensitive actions

Dominant status families:

• payment request: 201
• approve/settle: 200
• failures: 400 / 403 / 404 / 409

Classification:

• ingress
• create
• mutate

Route cluster:

• case closure

Dominant status families:

• success: 200
• failures: 400 / 409

Classification:

• mutate

Notable asymmetry:

• VERIFIED
• KES has no stream/download exception in this dense cluster
• KES case entry is also the main 500 outlier among the dense modules

Unresolved or transitional notes:

• TRANSITIONAL
• KES status-code patterns still sit over a root-repository-derived persistence slice rather than a fully isolated child repository

Current Asymmetry

VERIFIED

The status-code families remain intentionally different:

• tender and auction declarations share the same broad 200 / 201 / 400 / 403 / 404 / 409 family, with evidence download breaking into stream/header behavior
• auction declaration additionally exposes output-allocation create/read/update patterns inside the same module
• KES adds a 500 create-failure outlier and has no stream/download branch in this dense cluster