From 89124d09ea3e5b8ad1ba19357097aa9c71e2dee1 Mon Sep 17 00:00:00 2001 From: zemion Date: Mon, 6 Jul 2026 21:45:13 +0200 Subject: [PATCH] Sync Repo-README from project files --- Repo-README.-.md | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/Repo-README.-.md b/Repo-README.-.md index 3406709..885ba79 100644 --- a/Repo-README.-.md +++ b/Repo-README.-.md @@ -1,4 +1,4 @@ - + > Mirrored from `/mnt/DATA/git/govoplan-access/README.md`. > Origin: `repository`. @@ -16,8 +16,13 @@ The repository contains the extracted access seed implementation under interactive auth routes, and the legacy administration router are already owned here and exposed through core compatibility imports while the staged extraction continues. The legacy admin service/governance helpers are also -owned here, while legacy ORM models still reside in `govoplan-core` as -compatibility code. The staged extraction path is documented in: +owned here, and 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-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 +documented in: - `/mnt/DATA/git/govoplan-core/docs/ACCESS_EXTRACTION_PLAN.md` - `/mnt/DATA/git/govoplan-core/docs/MODULE_ARCHITECTURE.md` @@ -39,6 +44,16 @@ This module will own: - access administration WebUI route contributions - access-owned migrations +`govoplan-access` depends on `govoplan-tenancy`; the registry loads tenancy +before access for authenticated platform composition. + +## WebUI Package + +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. + The kernel remains responsible for module discovery, route aggregation, database/session lifecycle, migration orchestration, capability registry, and stable contracts.