{
  "site": "universal",
  "plugins": [
    "backups",
    "computers",
    "employees",
    "geenforce",
    "knowledgebase",
    "machines",
    "measuringtools",
    "network",
    "notifications",
    "printedparts",
    "printers",
    "slides",
    "usb",
    "warranty"
  ],
  "locked": [],
  "_comment": "The profile the released Windows installer is built from. Every bundled plugin that carries a manifest, so ONE exe serves any site: the wizard offers all of them and the operator ticks what that site uses. Plugins left unticked are never installed, and 'flask plugin prune-schema' drops their tables at provisioning (ADR-014). 'applications' is deliberately absent - it is manifest-less core and always ships. Build with: deploy/windows/installer/build-installer.sh deploy/site-profile-universal.json <repo>. Use site-profile.example.json instead only when a site genuinely needs a lean build; see ADR-013."
}
