Install once
Start with Raysor Hub instead of collecting unrelated installer links.
Windows control center
Raysor Hub is the Windows product center for discovery, installation, updates, repair, recovery, Developer builds, health evidence, and existing-machine migration.
Start with Raysor Hub instead of collecting unrelated installer links.
Acquisition, package trust, health checks, side-by-side versions, and rollback are separate failure boundaries.
Developer Mode can build explicit branches while Stable remains isolated and fail-closed.
Lifecycle
Organizer, RAYSOR AI, TerritoryHub, StriveLoop, Tactical Tower, and future managed products share one lifecycle authority.
Stable candidates require signed catalog evidence, exact release identity, SHA-256, architecture, package kind, and publisher policy before installation authorization.
Candidates must pass health before activation. Failed candidates preserve or restore the prior known-good version.
Existing machines
Upgrade Hub first. Hub can inventory declared Raysor installations, verify their identity, preserve external data boundaries, adopt them as legacy baselines, and migrate lifecycle control one product at a time.
Privacy
Platform telemetry is designed around versions, crashes, health, lifecycle failures, typed errors, and correlation IDs. Product content and user-created data are outside the default telemetry contract.
Requirements
Production acquisition is native to Hub.
PowerShell remains a Developer/CI tool, not a consumer requirement.
Users receive built packages rather than source checkouts.
FAQ
Public distribution fails closed until an owner-promoted release has an approved HTTPS host, version, architecture, and exact SHA-256. Workflow artifacts are not silently substituted.
No. It allows unfinished Raysor builds under explicit developer control while keeping package and data boundaries intact.
Binary lifecycle and user-data lifecycle are intentionally separate. Product data remains outside disposable version directories.