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

Guide module installer lifecycle

Browse Source
This commit is contained in:
zemion
2026-08-03 08:44:51 +02:00
parent fef4e10afd
commit 6dbccd5e08
7 changed files with 434 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+9
View File
@@ -48,6 +48,15 @@ admin UI records operator intent and queues or renders commands for the trusted
installer process described in
`/mnt/DATA/git/govoplan-core/docs/MODULE_ARCHITECTURE.md`.
The WebUI presents the lifecycle as five derived stages: plan, preflight,
installer request, daemon execution, and run evidence. The projection resets
when the saved plan changes and associates evidence only with an installer
request created at or after the current plan revision. It therefore cannot make
an old successful run look like evidence for a new plan. The earliest queue
blocker is shown through Core's actionable blocker pattern with the required
action, responsible operator or administrator, and destination. Contextual help
uses the stable `admin.module-lifecycle-workflow` documentation topic.
## Package Surfaces
The admin UI intentionally exposes two different package concepts: