[Task] Decide: Is govoplan-access required for any authenticated deployment, while core-only remains a diagnostics/settings shell? #53

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

Imported from the GovOPlaN access extraction plan open decisions.

  • Source: /mnt/DATA/git/govoplan-core/docs/ACCESS_EXTRACTION_PLAN.md
  • Line: 352
  • Section: Open Decisions
  • Source status: decision needed

Imported backlog item:

- [ ] Is `govoplan-access` required for any authenticated deployment, while core-only remains a diagnostics/settings shell?
<!-- codex-backlog-fingerprint:b1dfd7d88c2ea69f455c074c --> Imported from the GovOPlaN access extraction plan open decisions. - Source: `/mnt/DATA/git/govoplan-core/docs/ACCESS_EXTRACTION_PLAN.md` - Line: `352` - Section: `Open Decisions` - Source status: `decision needed` Imported backlog item: ```markdown - [ ] Is `govoplan-access` required for any authenticated deployment, while core-only remains a diagnostics/settings shell? ```
zemion added this to the Access Extraction milestone 2026-07-06 12:49:46 +02:00
zemion added the
status
needs-info
label 2026-07-08 03:00:33 +02:00
Author
Owner

Codex State: decision recorded 2026-07-09

Decision: govoplan-access is required for authenticated deployments. Core-only remains a diagnostics/settings shell shape, not an authenticated product composition.

Current state: this is already implemented in the registry/module-management layer. REQUIRED_PLATFORM_MODULES is tenancy+access, startup candidates include both, and the registry inserts tenancy before access when needed.

Effects: module install/uninstall flows should keep access and tenancy protected; feature modules may assume authenticated deployments have access capabilities available.

## Codex State: decision recorded 2026-07-09 Decision: govoplan-access is required for authenticated deployments. Core-only remains a diagnostics/settings shell shape, not an authenticated product composition. Current state: this is already implemented in the registry/module-management layer. REQUIRED_PLATFORM_MODULES is tenancy+access, startup candidates include both, and the registry inserts tenancy before access when needed. Effects: module install/uninstall flows should keep access and tenancy protected; feature modules may assume authenticated deployments have access capabilities available.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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