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 Cluster Intro MapThis note documents the one-line explanatory text immediately under the cluster headers in the densest route modules after Cleanup Sprint 42.
svc-tendersFocus:
Labels used here:
VERIFIEDREALTRANSITIONALregisterTenderDeclarationRoutes.tsRoute module:
Cluster header:
ADMIN READ SURFACEIntro text:
Broader declaration visibility gates this read cluster.Where wording was tightened/aligned:
Cluster header:
DRAFT AUTHORING SURFACEIntro text:
Create/update draft flows stay on the dedicated declaration write path.Where wording was tightened/aligned:
Create/update draft flows stay ...Cluster header:
READINESS / DECLARE TRANSITION SURFACEIntro text:
Readiness check, mark-ready, and declare keep the core declaration state machine together.Where wording was tightened/aligned:
Readiness check, mark-ready, and ... keep the core declaration state machine together.Cluster header:
EVIDENCE SURFACEIntro text:
Upload, list, and download keep shell storage plus declaration evidence logic together.Where wording was tightened/aligned:
Upload, list, and download keep ... togetherregisterAuctionDeclarationRoutes.tsRoute module:
Cluster header:
OUTPUT-ALLOCATION ADMIN SURFACEIntro text:
Colocated admin routes over the composed output-allocation/declaration boundary.Where wording was tightened/aligned:
Where wording intentionally stayed different:
output-allocation/declaration boundary language because this cluster is genuinely more transitional than the othersCluster header:
ADMIN READ SURFACEIntro text:
Broader declaration visibility gates this read cluster.Where wording was tightened/aligned:
Cluster header:
EVIDENCE SURFACEIntro text:
Upload, list, and download keep shell storage plus declaration evidence logic together in the composed boundary.Where wording was tightened/aligned:
Upload, list, and download keep ... togetherWhere wording intentionally stayed different:
in the composed boundary because auction evidence still lives on a more transitional route surfaceCluster header:
DRAFT AUTHORING SURFACEIntro text:
Create/update draft flows stay on the declaration-owned write path inside the composed boundary.Where wording was tightened/aligned:
Create/update draft flows stay ...Where wording intentionally stayed different:
inside the composed boundary because auction draft flows still depend on the mixed boundaryCluster header:
READINESS / ANNOUNCE TRANSITION SURFACEIntro text:
Readiness check, mark-ready, and announce keep the core declaration state machine together.Where wording was tightened/aligned:
Readiness check, mark-ready, and ... keep the core declaration state machine together.Where wording intentionally stayed different:
announce instead of declare because that is the real auction verbAsymmetry/transitional notes:
TRANSITIONALregisterKesRoutes.tsRoute module:
Cluster header:
CASE ENTRY SURFACEIntro text:
Authenticated case creation is the main KES write entry point.Where wording was tightened/aligned:
Cluster header:
OPERATOR READ / CONTROL-PLANE SURFACEIntro text:
Public reads keep list, detail, projection, suggestions, and control-plane access together.Where wording was tightened/aligned:
Where wording intentionally stayed different:
control-plane and public reads explicit because this cluster is not equivalent to the admin read surfaces in declaration modulesCluster header:
PROCESS-MAP MUTATION SURFACEIntro text:
Authenticated process-map writes stay separate from payment ingress rules.Where wording was tightened/aligned:
Cluster header:
CASE / TASK / INSPECTION ACTION SURFACEIntro text:
Authenticated orchestration actions stay separate from payment ingress rules.Where wording was tightened/aligned:
stay separate from payment ingress rulesCluster header:
PAYMENT-SENSITIVE ACTION SURFACEIntro text:
Payment actions add stricter ingress checks than ordinary KES writes.Where wording was tightened/aligned:
Where wording intentionally stayed different:
payment and stricter ingress explicit because this cluster is materially differentCluster header:
CASE CLOSURE ACTIONIntro text:
Terminal close stays separate from broader orchestration and payment actions.Where wording was tightened/aligned:
Where wording intentionally stayed different:
Asymmetry/transitional notes:
VERIFIEDVERIFIED
These intro lines intentionally stayed different:
announce versus declarepublic reads / control-plane wording in KESpayment ingress wording in KESterminal close wording in KESReason: