From 7eef52776cee20c0b3cb2e38076ea9b1bacd31c4 Mon Sep 17 00:00:00 2001 From: Albrecht Degering Date: Mon, 20 Jul 2026 20:48:47 +0200 Subject: [PATCH] docs: link product vision to technical roadmap --- docs/GOVOPLAN_MASTER_ROADMAP.md | 28 ++++++++++++++++++++-------- 1 file changed, 20 insertions(+), 8 deletions(-) diff --git a/docs/GOVOPLAN_MASTER_ROADMAP.md b/docs/GOVOPLAN_MASTER_ROADMAP.md index 7cb72ab..64a7023 100644 --- a/docs/GOVOPLAN_MASTER_ROADMAP.md +++ b/docs/GOVOPLAN_MASTER_ROADMAP.md @@ -1,13 +1,21 @@ # GovOPlaN Master Roadmap -This roadmap is the durable product north star and sequencing guide for -GovOPlaN as a modular platform for administrative operations. It keeps the -product moving without turning every possible public-sector need into an -immediate implementation track. +This roadmap is the technical and module-sequencing companion for GovOPlaN as +a modular platform for administrative operations. It translates the +cross-product outcome horizons into dependency waves without turning every +possible public-sector need into an immediate implementation track. -Use this document for product direction, sequencing, and module routing. Issues -are the active backlog; this document is durable planning context and should be -mirrored to the Gitea wiki. +Use this document for technical sequencing, module routing, and implementation +gates. Issues are the active backlog; this document is durable architecture +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 @@ -530,7 +538,11 @@ Before a module becomes release-included, it needs: - smoke test or permutation test - 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. 2. Deliver permit-to-payment MVP.