Purpose

This note records the route-support cleanup through Sprint 17 inside services/svc-tenders.

The goal was narrow and structural:

• reduce broad inline support-bundle assembly in services/svc-tenders/src/server.ts
• keep route behavior unchanged
• make support responsibilities easier to inspect

Labels used here:

• VERIFIED
• REAL
• TRANSITIONAL

Current support modules

routes/support/vacancyRouteSupport.ts

File:

• services/svc-tenders/src/routes/support/vacancyRouteSupport.ts

Responsibility:

• assembles the vacancy route support bundle
• owns the vacancy top-level detail key set
• groups vacancy capability checks with the route-facing support shape

Used by route groups:

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

Status:

• VERIFIED
• TRANSITIONAL

Why transitional:

• underlying auth, parsing, and error mapping functions still live in the service shell
• this module narrows the assembly boundary, not the final ownership boundary

routes/support/accommodationRouteSupport.ts

File:

• services/svc-tenders/src/routes/support/accommodationRouteSupport.ts

Responsibility:

• assembles the accommodation route support bundle
• owns the accommodation top-level detail key set
• keeps public-mapping helpers grouped with the route-facing support shape

Used by route groups:

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

Status:

• VERIFIED
• TRANSITIONAL

routes/support/tenderRouteSupport.ts

File:

• services/svc-tenders/src/routes/support/tenderRouteSupport.ts

Responsibility:

• assembles the tender route support bundle
• keeps tender list parsing, declaration-check gating, portal/detail mapping, and intent-id support explicit at the route boundary

Used by route groups:

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

Status:

• VERIFIED
• TRANSITIONAL

routes/support/auctionRouteSupport.ts

File:

• services/svc-tenders/src/routes/support/auctionRouteSupport.ts

Responsibility:

• assembles the auction route support bundle
• keeps auction list parsing and declaration-check gating explicit at the route boundary

Used by route groups:

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

Status:

• VERIFIED
• TRANSITIONAL

routes/support/icpiRouteSupport.ts

File:

• services/svc-tenders/src/routes/support/icpiRouteSupport.ts

Responsibility:

• assembles the ICPI route support bundle
• keeps ICPI query parsing support explicit without merging it into generic shared helpers

Used by route groups:

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

Status:

• VERIFIED
• TRANSITIONAL

routes/support/butkhuziRouteSupport.ts

File:

• services/svc-tenders/src/routes/support/butkhuziRouteSupport.ts

Responsibility:

• assembles the Butkhuzi route support bundle
• keeps Butkhuzi query parsing support explicit without folding it into a generic route helper

Used by route groups:

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

Status:

• VERIFIED
• TRANSITIONAL

routes/support/kesRouteSupport.ts

File:

• services/svc-tenders/src/routes/support/kesRouteSupport.ts

Responsibility:

• assembles the KES route support bundle
• keeps KES parser support and KYC/signature gate support explicit at the route boundary

Used by route groups:

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

Status:

• VERIFIED
• TRANSITIONAL

routes/support/declarationRouteSupport.ts

File:

• services/svc-tenders/src/routes/support/declarationRouteSupport.ts

Responsibility:

• assembles tender declaration route support
• assembles auction declaration route support
• keeps shared declaration-route support shape explicit:
  • auth gate
  • intent parsing
  • upload middleware bridge
  • declaration capability checks
  • evidence group parsing

Used by route groups:

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

Status:

• VERIFIED
• TRANSITIONAL

What remains broad

Auth/session helper hosting

Still hosted in:

• services/svc-tenders/src/server.ts

Examples:

• requireServiceAuth(...)
• requireActivePrincipal(...)
• token verification / principal resolution helpers

Status:

• VERIFIED
• REAL

Reason still broad:

• these helpers are still shared across many route groups
• moving them this sprint would have been a bigger service-shell refactor than a support-bundle cleanup

Shared query/parser helpers

Still hosted in:

• services/svc-tenders/src/server.ts

Examples:

• parsePositiveInt(...)
• parseOptionalInt(...)
• parseOptionalString(...)
• parseOptionalUpper(...)
• clampPositiveInt(...)
• tender/auction list-option parsers

Used by:

• tender routes
• auction routes
• KES routes
• ICPI routes
• Butkhuzi routes
• declaration routes indirectly

Status:

• VERIFIED
• REAL

Reason still broad:

• these are still cross-route service-shell helpers
• they were not yet split into narrower support modules in this sprint

Signature / KYC boundary helpers

Still hosted in:

• services/svc-tenders/src/server.ts

Examples:

• ensureThirdPartyKycBoundary(...)
• verifyIncomingSignatureGate(...)

Used by:

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

Status:

• VERIFIED
• REAL

Reason still broad:

• KES remains the main consumer
• final KES/shared-backbone boundary is still transitional

What was removed or narrowed

Sprint 16-17 removed broad inline support-object assembly from server.ts for:

• vacancy routes
• accommodation routes
• tender routes
• auction routes
• ICPI routes
• Butkhuzi routes
• KES routes
• tender declaration routes
• auction declaration routes

This did not remove the underlying helpers themselves.

It narrowed:

• where route-facing support objects are assembled
• where route-specific key sets are defined
• how clearly route support responsibilities are named

What remains unresolved

• whether core auth/query helper hosting should later move into dedicated HTTP support modules
• whether KES-specific support should split further from the service shell
• whether tender/auction list-route support should also get dedicated builders later

Result

After Sprint 17:

• server.ts is less cluttered with inline support-object literals across all extracted route groups
• vacancy/accommodation/tender/auction/ICPI/Butkhuzi/KES/declaration support boundaries are more explicit
• route modules still behave exactly the same
• future extraction work has a cleaner support-layer starting point