add-ideas/govoplan-access
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Sync Repo-README from project files

zemion
2026-07-06 23:43:59 +02:00
parent ee024f0b07
commit b1b1ad162f
1 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Repo-README.-.md

@@ -1,4 +1,4 @@
<!-- codex-wiki-sync:acf75350b24f197bce28310a -->
<!-- codex-wiki-sync:27a8b95113b862e14a2d7c1c -->
> Mirrored from `/mnt/DATA/git/govoplan-access/README.md`.
> Origin: `repository`.
@@ -18,9 +18,11 @@ owned here and exposed through core compatibility imports while the staged
extraction continues. Access-side admin service helpers remain here for users,
groups, roles, system accounts, sessions, API keys, and tenant access
enforcement. Governance-template CRUD and materialization live in
`govoplan-admin`. The transitional administration WebUI lives under `webui/src`
as `@govoplan/access-webui`. Live access ORM models are defined here while
retaining their historical table names; tenant records live in
`govoplan-admin`. The transitional administration WebUI route shell and
access-owned panels live under `webui/src` as `@govoplan/access-webui`. Generic
system administration panels are contributed by `@govoplan/admin-webui` through
core's `admin.sections` UI capability. Live access ORM models are defined here
while retaining their historical table names; tenant records live in
`govoplan-tenancy`, governance templates in `govoplan-admin`, audit logs in
`govoplan-audit`, and system settings in `govoplan-core`. `govoplan-core` keeps
compatibility re-exports for older import paths. The staged extraction path is
@@ -56,8 +58,10 @@ before access for authenticated platform composition.
The repository root and `webui/` directory both expose the package
`@govoplan/access-webui`. The package contributes the `/admin` route and admin
nav item through core's module WebUI contract. Core supplies the shell,
shared components, route rendering, and icon resolution.
nav item through core's module WebUI contract. The route shell consumes
module-owned `admin.sections` contributions from installed platform modules and
continues to render access-owned tenant/user/group/role panels locally. Core
supplies shared admin components, route rendering, and icon resolution.
The kernel remains responsible for module discovery, route aggregation,
database/session lifecycle, migration orchestration, capability registry, and