Create access module package
This commit is contained in:
28
AGENTS.md
Normal file
28
AGENTS.md
Normal file
@@ -0,0 +1,28 @@
|
||||
# GovOPlaN Access Codex Guide
|
||||
|
||||
## Scope
|
||||
|
||||
This repository owns the GovOPlaN access platform module seed: identity,
|
||||
authentication, sessions, API keys, users, groups, roles, memberships, access
|
||||
administration, and access-owned migrations.
|
||||
|
||||
During the transition, some live routes and legacy ORM models still sit in
|
||||
`/mnt/DATA/git/govoplan-core` as compatibility code. Keep moving ownership here
|
||||
behind core compatibility imports and kernel capability contracts.
|
||||
|
||||
## Boundaries
|
||||
|
||||
- Depend on kernel contracts from `govoplan-core`.
|
||||
- Do not import feature-module internals from mail, files, or campaign.
|
||||
- Expose integration through manifests, capabilities, API routes, events, and
|
||||
typed DTOs.
|
||||
- Keep WebUI access administration as module route contributions once the
|
||||
frontend move begins.
|
||||
|
||||
## Local Workflow
|
||||
|
||||
Use Gitea issues as the canonical backlog and state log. The shared workflow is
|
||||
installed under `.gitea/`, with labels in `docs/gitea-labels.json`.
|
||||
|
||||
Focused verification is still driven from `/mnt/DATA/git/govoplan-core` for
|
||||
cross-repository behavior.
|
||||
Reference in New Issue
Block a user