# GovOPlaN Identity

<!-- govoplan-repository-type:start -->
**Repository type:** module (platform).
<!-- govoplan-repository-type:end -->

`govoplan-identity` is the canonical identity directory module for GovOPlaN.

It owns identities and links between identities and platform accounts. This is
separate from IDM connectors and from access control.

## Boundary

Identity owns:

- identity records for people, services, and other internal subjects
- account links for identities that can use multiple accounts
- primary account selection for display and explainability
- accepted normalized identity facts after import or manual administration

Identity does not own:

- password authentication, sessions, API keys, or CSRF
- roles, rights, permission evaluation, or access decisions
- organization units, functions, or function assignments
- external directory connector internals

## Module Contract

The module registers the `identity.directory` capability from
`govoplan_core.core.identity`.

Feature modules should consume the capability instead of importing identity ORM
models.

## Development Install

From the core checkout:

```bash
cd /mnt/DATA/git/govoplan-core
./.venv/bin/python -m pip install -e ../govoplan-identity
```

## Git-source WebUI package

The repository root exposes `@govoplan/identity-webui` for Git-tagged release
dependencies. It mirrors the owning `webui/package.json` version, public
TypeScript/CSS exports and peer requirements, with entry paths under
`webui/src`. Consumers provide the shared Core/React peers; the facade runs no
development or install scripts. The source archive contains `webui/src`, this
README and any repository license file. Run module development checks from `webui/`; Python
installation remains governed by `pyproject.toml`.

Das Repository stellt `@govoplan/identity-webui` am Wurzelpfad für versionierte
Git-Abhängigkeiten bereit. Version, öffentliche TypeScript-/CSS-Exporte und
Peer-Anforderungen entsprechen `webui/package.json`; die Einstiegspfade liegen
unter `webui/src`. Gemeinsame Core-/React-Peers stellt die einbindende Anwendung
bereit. Die Fassade führt keine Entwicklungs- oder Installationsskripte aus.
Entwicklungsprüfungen bleiben in `webui/`, die Python-Installation weiterhin in
`pyproject.toml` definiert.