Sync Repo-docs-MODULE-ARCHITECTURE from project files

2026-07-07 01:01:14 +02:00
parent 2aeb236c4b
commit 6cbe4b501f

@@ -1,4 +1,4 @@
<!-- codex-wiki-sync:145a1efa1dc4580d1870eef3 --> <!-- codex-wiki-sync:ac612f4a103c52d994713144 -->
> Mirrored from `/mnt/DATA/git/govoplan-core/docs/MODULE_ARCHITECTURE.md`. > Mirrored from `/mnt/DATA/git/govoplan-core/docs/MODULE_ARCHITECTURE.md`.
> Origin: `repository`. > Origin: `repository`.
@@ -44,10 +44,11 @@ During the staged split, `govoplan-core` still contains compatibility surfaces
for access, auth, tenancy, RBAC, governance, audit, CSRF/API helpers, and for access, auth, tenancy, RBAC, governance, audit, CSRF/API helpers, and
secret helpers. The extracted access implementation now lives in secret helpers. The extracted access implementation now lives in
`govoplan-access`; live legacy ORM table definitions have been split across `govoplan-access`; live legacy ORM table definitions have been split across
their platform owners while retaining historical table names, and core keeps their platform owners while retaining historical table names. The old core
import shims until all callers move to module-owned imports or kernel model, route, admin-service, and access-security import shims have been
capabilities. These paths are temporary compatibility surfaces until the removed; callers must use module-owned imports or kernel capabilities. The
matching platform modules are fully self-contained: remaining compatibility surfaces are temporary until the matching platform
modules are fully self-contained:
- `govoplan-access` - `govoplan-access`
- `govoplan-tenancy` - `govoplan-tenancy`