GovOPlaN/govoplan
1
0
Fork 0
Code Issues 10 Pull Requests Actions 3 Packages Projects Releases Wiki Activity

docs: define system administrator lifecycle story

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-21 12:24:32 +02:00
parent f1b07354a0
commit 397c87a012
3 changed files with 210 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/CONNECTED_GOVERNANCE_PLATFORM_ROADMAP.md
View File

@@ -253,6 +253,12 @@ Operational access is distinct from permission to read all business content.
Diagnostics minimize personal data and link to governed evidence when deeper
inspection is authorized.
The complete installation and lifecycle journey is specified in the
[System Administrator Lifecycle User Story](SYSTEM_ADMINISTRATOR_LIFECYCLE_USER_STORY.md):
one-command Core-only bootstrap, signed online module installation and updates,
stateless scale-out, versioned configuration transfer, undo, and reproducible
environment-promotion recipes.
### Integration owner and enterprise architect
> As an integration owner, I can inventory external systems, declare direction
@@ -871,23 +877,27 @@ checkouts.
Priorities:
1. Pin and publish a compatible Core/WebUI/module composition and first
1. Deliver the first slices of the
[System Administrator Lifecycle User Story](SYSTEM_ADMINISTRATOR_LIFECYCLE_USER_STORY.md):
a verified Core-only distribution, first-run control plane, read-only online
module directory, and durable plan/confirm/install progress.
2. Pin and publish a compatible Core/WebUI/module composition and first
reference configuration package.
2. Complete database, files, configuration, secrets, and audit backup/restore
3. Complete database, files, configuration, secrets, and audit backup/restore
drills with measured recovery objectives.
3. Prove the providers required by the selected reference configurations,
4. Prove the providers required by the selected reference configurations,
beginning with SMTP/IMAP, CalDAV, and the relevant broker/worker and file or
directory adapters, including reconciliation behavior.
4. Add external monitoring, alerting, audit export/retention, deployment
5. Add external monitoring, alerting, audit export/retention, deployment
hardening, and incident/runbook evidence.
5. Apply the interface pattern language first to Campaign, scheduling, and
6. Apply the interface pattern language first to Campaign, scheduling, and
admin/configuration. Existing central components are mandatory; any custom
control needs prior product-owner authorization and a narrow recorded scope.
Extend central contracts only after a repeated need is demonstrated.
6. Align executable WebUI contributions with manifest/configured-system
7. Align executable WebUI contributions with manifest/configured-system
metadata and make focused views manually/default selectable without waiting
for Workflow.
7. Refresh the capability/infrastructure assessment and distinguish code-tested,
8. Refresh the capability/infrastructure assessment and distinguish code-tested,
target-tested, package-integrated, pilot-approved, and production-approved
evidence.