Sync Repo-docs-MODULE-ARCHITECTURE from project files
@@ -1,4 +1,4 @@
|
|||||||
<!-- codex-wiki-sync:0b250b14c736a0cc7e27f2c5 -->
|
<!-- codex-wiki-sync:ae32ddb4aae0c28290f2031d -->
|
||||||
|
|
||||||
> 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`.
|
||||||
@@ -110,6 +110,12 @@ Current live table ownership:
|
|||||||
- `govoplan-audit`: `audit_log`
|
- `govoplan-audit`: `audit_log`
|
||||||
- `govoplan-core`: `system_settings`
|
- `govoplan-core`: `system_settings`
|
||||||
|
|
||||||
|
Current admin route ownership follows the same boundary: access contributes
|
||||||
|
users, groups, roles, system accounts/roles, auth, sessions, and API-key
|
||||||
|
administration; tenancy contributes tenant registry/settings routes; admin
|
||||||
|
contributes system settings, overview, and governance-template routes; audit
|
||||||
|
contributes audit-log routes.
|
||||||
|
|
||||||
Cross-module feature contracts live under focused kernel contract modules. For
|
Cross-module feature contracts live under focused kernel contract modules. For
|
||||||
example, `govoplan_core.core.campaigns` defines
|
example, `govoplan_core.core.campaigns` defines
|
||||||
`campaigns.access`, `campaigns.mailPolicyContext`,
|
`campaigns.access`, `campaigns.mailPolicyContext`,
|
||||||
|
|||||||
Reference in New Issue
Block a user