svc-tenders Service Shell Composition
Purpose
This note records the current service-shell composition of services/svc-tenders/src/server.ts after Cleanup Sprint 21.
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 Service Shell CompositionThis note records the current service-shell composition of services/svc-tenders/src/server.ts after Cleanup Sprint 21.
It is not an ownership document for all domains in svc-tenders.
It is a shell-composition map:
Labels used here:
VERIFIEDREALTRANSITIONALUNRESOLVEDStatus:
VERIFIEDREALPurpose:
What is wired here:
resolveConfig() from services/svc-tenders/src/config.tscreatePool(...) from services/svc-tenders/src/db.tsDeclarationEvidenceStorage from services/svc-tenders/src/evidenceStorage.tsmulter(...) declaration evidence upload middlewareexpress.json(...)Future planning implication:
Status:
VERIFIEDREALPurpose:
What is wired here:
new TendersRepository(...)new TenderRepository(...)new AuctionRepository(...)new DeclarationRepository(...)new IcpiRepository(...)new ButkhuziRepository(...)new OutputAllocationsRepository(...)new VacancyCommandHandlers(...)new AccommodationCommandHandlers(...)new VacancyReadRepository(...)new AccommodationReadRepository(...)new AccommodationOwnerReadRepository(...)What is stable:
What is still transitional:
TendersRepository is still instantiated because:
Future planning implication:
TendersRepository use, not hide itStatus:
VERIFIEDREALPurpose:
What is wired here:
Why this stays shell-owned:
Future planning implication:
Status:
VERIFIEDTRANSITIONALPurpose:
What is wired here:
declarationEvidenceUploadRunnermulter instance via services/svc-tenders/src/routes/support/declarationUploadSupport.tsauctionDeclarationRepositoryWhy this is transitional:
output_allocations methodsFuture planning implication:
Status:
VERIFIEDREALPurpose:
What is wired here:
vacancyRouteSupportaccommodationRouteSupporticpiRouteSupportbutkhuziRouteSupportkesRouteSupporttenderRouteSupporttenderDeclarationRouteSupportauctionRouteSupportauctionDeclarationRouteSupportBacked by:
Why this matters:
Future planning implication:
Status:
VERIFIEDREALPurpose:
What is registered here:
What is now clearer:
Status:
VERIFIEDREALPurpose:
Sub-boundaries:
/auth/me principal resolutionReference:
Future planning implication:
TendersRepository hosting for KES and compatibility residueserver.tsOpen services/svc-tenders/src/server.ts in this order:
That order reflects the real shell composition more truthfully than reading it as one flat file.