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
output_allocations Ownership DossierDate: 2026-03-17 Sprint: Cleanup Sprint 11
This is a founder-facing ownership dossier for .
output_allocationsIt does not force a decision.
It records the evidence currently visible in code.
Persistence implementation:
Root compatibility / ownership surface:
HTTP route exposure:
services/svc-tenders/src/routes/registerAuctionDeclarationRoutes.ts
GET /admin/output-allocationsGET /admin/output-allocations/:idPOST /admin/output-allocationsPUT /admin/output-allocations/:idCurrent server wiring:
services/svc-tenders/src/server.ts
Web client surface:
The table shape, as seen from code, carries:
allocation_idstakeholder_idproductive_asset_idasset_typeallocation_stateThis looks more like a registry / inventory allocation record than a narrow auction bid record.
Evidence:
Why it points toward auction:
allocationId while building auction announcement draftsStrength:
VERIFIEDLimit:
Evidence:
findOutputAllocationById(...) is used by auction declaration draft/update/declare path checks in
services/svc-tenders/src/routes/registerAuctionDeclarationRoutes.tsWhy it points toward auction:
Strength:
VERIFIEDLimit:
Evidence:
Why it points toward settlement/financial side:
Strength:
INFERREDLimit:
Evidence:
Why it points toward shared registry:
Strength:
INFERREDLimit:
It does not prove that output_allocations are:
Ownership verdict today:
VERIFIED: currently hosted with auction declaration admin flowINFERRED: conceptually closer to shared registry / pre-settlement allocation capabilityUNVERIFIEDSystem state:
REALUse this question:
Is
output_allocationsmeant to exist only to feed auction declarations, or is it meant to be a reusable record of allocatable productive output across multiple commercial flows?
If answer is:
“only auction preparation”
“reusable output registry for multiple flows”
“it will drive entitlement/release/payment mechanics”
Do not decide only from route colocation.
Safer next step: