GovOPlaN/govoplan-core
1
0
Fork 0
Code Issues 43 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: link product vision to technical roadmap

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-20 20:48:47 +02:00
parent c50ce58ad8
commit 7eef52776c
1 changed files with 20 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/GOVOPLAN_MASTER_ROADMAP.md
View File

@@ -1,13 +1,21 @@
# GovOPlaN Master Roadmap # GovOPlaN Master Roadmap
This roadmap is the durable product north star and sequencing guide for This roadmap is the technical and module-sequencing companion for GovOPlaN as
GovOPlaN as a modular platform for administrative operations. It keeps the a modular platform for administrative operations. It translates the
product moving without turning every possible public-sector need into an cross-product outcome horizons into dependency waves without turning every
immediate implementation track. possible public-sector need into an immediate implementation track.
Use this document for product direction, sequencing, and module routing. Issues Use this document for technical sequencing, module routing, and implementation
are the active backlog; this document is durable planning context and should be gates. Issues are the active backlog; this document is durable architecture
mirrored to the Gitea wiki. planning context and should be mirrored to the Gitea wiki.
The meta repository's
[Connected Governance Platform Roadmap](https://git.add-ideas.de/add-ideas/govoplan/src/branch/main/docs/CONNECTED_GOVERNANCE_PLATFORM_ROADMAP.md)
describes the corresponding cross-product stakeholder visions, configurable
service and operating configurations, connected outcome stories, and
capability horizons. Its product horizons are canonical; the waves below give
their technical dependency order. This Core roadmap remains the technical
sequencing and module-routing companion.
## Product Thesis ## Product Thesis
@@ -530,7 +538,11 @@ Before a module becomes release-included, it needs:
- smoke test or permutation test - smoke test or permutation test
- no required imports from optional modules - no required imports from optional modules
## Priority Order Summary ## Technical Dependency Order Summary
When the meta roadmap selects one of these product programs, use this order to
respect shared-spine dependencies. The list is not an active schedule or a
decision to start every program horizontally.
1. Stabilize the platform spine. 1. Stabilize the platform spine.
2. Deliver permit-to-payment MVP. 2. Deliver permit-to-payment MVP.