# GovOPlaN Access Codex Guide

## Documentation Contract

- Treat documentation as part of every behavior change. Update this module's manifest-driven `DocumentationTopic` contributions for affected user and administrator behavior.
- Keep feature content here; `govoplan-docs` projects it without importing Access internals.
- Maintain a static user/admin baseline and run `/mnt/DATA/git/govoplan/tools/checks/check-manifest-shapes.py` after behavior or manifest changes.

## 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.