diff --git a/frontend/src/views/geenforce/ManifestEditor.vue b/frontend/src/views/geenforce/ManifestEditor.vue index 81e1b3d..8a52704 100644 --- a/frontend/src/views/geenforce/ManifestEditor.vue +++ b/frontend/src/views/geenforce/ManifestEditor.vue @@ -8,6 +8,25 @@ then Publish to ship it to PCs. Nothing reaches a PC until you publish.
+A manifest is the desired state for a PC type - the + list of what should be installed. shopdb serves it; each PC checks + itself every cycle and re-installs anything that drifted (uninstalled, + corrupted, or overwritten). That is the "self-heal".
+Each entry is one action (install an app, copy a + file, write a registry value, run a script) plus a detection + rule that tells the PC whether it is already correct - if not, the + action runs. Entry order is execution order.
+Targeting narrows an entry: the fleet-wide
+ common manifest uses PC types to hit a subset; a per-type
+ manifest already only runs on its own type, so it shows just the niche
+ gate it needs (CMM version, a bay number, a subtype).
Full guide: docs/GE-ENFORCE.md.