[Task] Access extraction Stage 2: Create govoplan-access #42

Closed
opened 2026-07-06 11:32:54 +02:00 by zemion · 1 comment
Owner

Imported from the GovOPlaN access extraction plan.

  • Source: /mnt/DATA/git/govoplan-core/docs/ACCESS_EXTRACTION_PLAN.md
  • Line: 211
  • Section: Stage 2: Create govoplan-access``

Plan excerpt:

### Stage 2: Create `govoplan-access`

Create the new repository/package and move the access seed package into it.

Tasks:

- Create package metadata and entry points for `govoplan-access`.
- Move `govoplan_core/access` implementation into the new package.
- Publish `ModuleManifest(id="access")`.
- Register access permissions, role templates, routers, and migrations.
- Add compatibility imports in core where needed.
- Add release/dev dependency entries in core.

Acceptance criteria:

- `govoplan-core + govoplan-access` starts through normal module discovery.
- `govoplan-core` compatibility imports still work during transition.
- access manifest, migrations, and route contributions are discovered by core.

<!-- codex-backlog-fingerprint:e5955d414b1484919f764b64 --> Imported from the GovOPlaN access extraction plan. - Source: `/mnt/DATA/git/govoplan-core/docs/ACCESS_EXTRACTION_PLAN.md` - Line: `211` - Section: `Stage 2: Create `govoplan-access`` Plan excerpt: ```markdown ### Stage 2: Create `govoplan-access` Create the new repository/package and move the access seed package into it. Tasks: - Create package metadata and entry points for `govoplan-access`. - Move `govoplan_core/access` implementation into the new package. - Publish `ModuleManifest(id="access")`. - Register access permissions, role templates, routers, and migrations. - Add compatibility imports in core where needed. - Add release/dev dependency entries in core. Acceptance criteria: - `govoplan-core + govoplan-access` starts through normal module discovery. - `govoplan-core` compatibility imports still work during transition. - access manifest, migrations, and route contributions are discovered by core. ```
zemion added this to the Access Extraction milestone 2026-07-06 12:53:12 +02:00
Author
Owner

Codex status: done.

Completed evidence:

  • govoplan-access exists as an installable package with pyproject.toml and govoplan.modules entry point.
  • The access module publishes ModuleManifest(id="access"), owns access metadata/migrations, registers permissions/role templates, and contributes auth/admin routes.
  • Core dev/release dependency files include the access package.

Verification:

  • ./.venv/bin/python -m unittest tests.test_access_contracts tests.test_module_system -> 66 tests OK

  • ./.venv/bin/python scripts/check_dependency_boundaries.py -> passed, 0 transitional exceptions

  • ./.venv/bin/python -m govoplan_core.devserver --smoke --no-reload with ENABLED_MODULES=access -> startup OK

Closing because the access module repository/package and manifest discovery acceptance criteria are met.

Codex status: done. Completed evidence: - `govoplan-access` exists as an installable package with `pyproject.toml` and `govoplan.modules` entry point. - The access module publishes `ModuleManifest(id="access")`, owns access metadata/migrations, registers permissions/role templates, and contributes auth/admin routes. - Core dev/release dependency files include the access package. Verification: - `./.venv/bin/python -m unittest tests.test_access_contracts tests.test_module_system` -> 66 tests OK - `./.venv/bin/python scripts/check_dependency_boundaries.py` -> passed, 0 transitional exceptions - `./.venv/bin/python -m govoplan_core.devserver --smoke --no-reload` with `ENABLED_MODULES=access` -> startup OK Closing because the access module repository/package and manifest discovery acceptance criteria are met.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-core#42
No description provided.