Butkhuzi Code Boundary Hardening
Sprint 76 performed the first real Butkhuzi code-boundary hardening pass.
The goal was not extraction yet. The goal was to reduce dependence on mixed surfaces where ownership was already clear.
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
Sprint 76 performed the first real Butkhuzi code-boundary hardening pass.
The goal was not extraction yet. The goal was to reduce dependence on mixed surfaces where ownership was already clear.
svc-tendersMoved out of the mixed service-wide validator:
butkhuziComponentSchemabutkhuziReferenceMetaSchemaupsertButkhuziNormSchemarebuildButkhuziChunksSchemaNew Butkhuzi-owned validation module:
Updated route dependency:
Result:
Sprint 75 already moved Butkhuzi contracts into:
Sprint 76 preserved and used that harder boundary:
Reduced in Sprint 76:
Still mixed after Sprint 76:
services/svc-tenders/migrationsStill shared on purpose:
/auth/meMain remaining blockers:
svc-tenderssvc-tenders host shellSprint 76 did the first low-risk Butkhuzi boundary cleanup that directly helps extraction: