Model role-based service directory and availability explanations #1

Open
opened 2026-07-09 15:05:00 +02:00 by zemion · 0 comments
Owner

Define the portal service directory as the user-facing map of configured services, filtered by role/function, tenant, policy, installed modules, and package contributions.

Source concept/wiki doc: govoplan-portal/docs/SERVICE_DIRECTORY_CONCEPT.md.

Acceptance criteria:

  • Service entries describe audience, required capabilities/modules, entry point, blockers, and evidence expectations.
  • Unavailable services can explain missing role, policy, capability, maintenance mode, or external provider state when useful.
  • Portal consumes service contributions through core contracts instead of importing domain module internals.

Context recovered from previous GovOPlaN planning chats and consolidated into the roadmap/docs on 2026-07-09.

Define the portal service directory as the user-facing map of configured services, filtered by role/function, tenant, policy, installed modules, and package contributions. Source concept/wiki doc: `govoplan-portal/docs/SERVICE_DIRECTORY_CONCEPT.md`. Acceptance criteria: - [ ] Service entries describe audience, required capabilities/modules, entry point, blockers, and evidence expectations. - [ ] Unavailable services can explain missing role, policy, capability, maintenance mode, or external provider state when useful. - [ ] Portal consumes service contributions through core contracts instead of importing domain module internals. Context recovered from previous GovOPlaN planning chats and consolidated into the roadmap/docs on 2026-07-09. <!-- govoplan-recovered-concept:d1ceb3e27729fa77 -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-portal#1
No description provided.