svc-tenders Support Consumption Map

Purpose

This note documents how the densest route modules in svc-tenders consume support helpers at call sites after Cleanup Sprint 33.

Focus:

• where broader visibility helpers are used
• where stricter mutation helpers are used
• where readiness/state-machine sequencing consumes support helpers
• where evidence upload/read helpers are used
• where KES ingress/security helpers become active

Labels used here:

• VERIFIED
• REAL
• TRANSITIONAL

registerTenderDeclarationRoutes.ts

Route module:

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

Support/helper consumed:

• support.canCheckTenderDeclaration(...)

Purpose at call site:

• broader visibility/read usage for admin read, readiness check, and evidence read/download

Classification:

• broader

Support/helper consumed:

• support.hasTenderDeclarationCapability(...)
• support.getTenderDeclarationCapabilities(...)

Purpose at call site:

• stricter mutation/command usage for draft create/update, mark-ready, and declare

Classification:

• stricter
• readiness/state transition

Notes:

• VERIFIED
• capability snapshot is reused in readiness/preview/state derivation, not only gating

Support/helper consumed:

• support.resolveIntentId(...)

Purpose at call site:

• shared request-intent consumption before mark-ready/declare persistence

Classification:

• transitional/shared

Support/helper consumed:

• support.runMulterSingle(...)
• support.parseTenderDeclarationEvidenceGroupKey(...)
• support.parseOptionalString(...)

Purpose at call site:

• evidence parsing/upload usage

Classification:

• evidence

registerAuctionDeclarationRoutes.ts

Route module:

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

Support/helper consumed:

• support.canCheckAuctionDeclaration(...)

Purpose at call site:

• broader visibility/read usage for output-allocation reads, admin declaration read, readiness check, and evidence read/download

Classification:

• broader

Support/helper consumed:

• support.hasAuctionDeclarationCapability(...)
• support.getAuctionDeclarationCapabilities(...)

Purpose at call site:

• stricter mutation/command usage for output-allocation writes, evidence upload, draft create/update, mark-ready, and declare

Classification:

• stricter
• readiness/state transition

Notes:

• VERIFIED
• route remains more transitional than tender declaration because helper consumption sits inside a composition-heavy module

Support/helper consumed:

• support.resolveIntentId(...)

Purpose at call site:

• shared request-intent consumption before mark-ready/declare persistence

Classification:

• transitional/shared

Support/helper consumed:

• support.runMulterSingle(...)
• support.parseAuctionDeclarationEvidenceGroupKey(...)
• support.parseOptionalString(...)

Purpose at call site:

• evidence parsing/upload usage

Classification:

• evidence

registerKesRoutes.ts

Route module:

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

Support/helper consumed:

• support.parsePositiveInt(...)
• support.parseOptionalInt(...)
• support.parseOptionalString(...)
• support.parseOptionalUpper(...)
• support.clampPositiveInt(...)

Purpose at call site:

• general read/list/action normalization across KES route flow

Classification:

• broader parser usage

Support/helper consumed:

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

Purpose at call site:

• strictest payment-request ingress/security usage

Classification:

• ingress
• payment-sensitive stricter

Notes:

• VERIFIED
• payment request is stricter than approve/settle because it applies both KYC boundary enforcement and signature verification

Support/helper consumed:

• support.verifyIncomingSignatureGate(...)

Purpose at call site:

• stricter payment approve/settle ingress usage

Classification:

• ingress
• payment-sensitive stricter

Notes:

• VERIFIED
• stricter than ordinary KES actions, narrower than payment request

Current Asymmetry

VERIFIED

The route/support consumption pattern is intentionally asymmetric:

• declaration routes pivot between broader visibility helpers and stricter mutation helpers
• KES mostly consumes general parser helpers and only activates stricter ingress helpers on payment-sensitive paths
• auction declaration remains additionally transitional because support consumption happens inside a composition-heavy route boundary