Revenue Service Multi-Tenant Preparation
What exists today
- A normalized tenant/company authority connection model
Loading module
Resolving locale, route permissions, and workspace projection.
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-rs backend slice with persistence and audit eventsNothing in this slice calls a live Revenue Service API yet.
Each tenant/company gets its own connection record:
tenantIdprovider = RSDocuments are stored with normalized internal states:
DRAFTREADY_FOR_SUBMISSIONSUBMISSION_PENDINGSUBMITTEDCONFIRMEDREJECTEDCANCELLEDSYNC_ERROREach record keeps:
The live RS adapter will plug into the same interface:
createDraftDocumentsubmitDocumentfetchDocumentStatuslistDocumentscancelDocumentThe profile surface only consumes normalized internal state. It does not know about:
That separation is intentional to minimize future refactor.