Version manifest
Product ID, channel, version, publication state, release notes, artifact metadata, and integrity information.
Downloads + releases
One place for the release state of Raysor software.
Each product uses Developer, Beta, and Stable channels. A download button appears only after an approved artifact has a real version, release notes, integrity metadata, and an official distribution URL.
Products
Current release state.
All four products are currently represented conservatively as active development work. No unverified public installer is linked from Website v1.0.
TerritoryHub · iPhone + iPad
Development
The repository identifies a 5.0 Alpha core milestone, while signed device beta and public distribution remain separate release gates.
Territory Field · iPhone + iPad
Development
The local-first companion remains under active engineering. No public App Store or installer artifact is declared by this site.
PowerShell Principal · Windows
Development
Workflow, diagnostics, packaging, update, and clean-machine lifecycle work remain part of the release gate before a supported installer is published.
Deep Orbit · Windows
Development
Standalone recovery validation, packaging, evidence handling, and independent launch behavior must be proven before a public installer is promoted.
Distribution architecture
R2 holds artifacts. Manifests describe releases.
The Website v1.0 distribution contract separates the metadata clients need from the binary artifacts themselves. Release artifacts are intended to live in Cloudflare R2 once a product is approved for distribution.
Artifact storage
Versioned installers and packages can be stored in Cloudflare R2 without coupling release metadata to the public HTML pages.
Update checks
Applications can read channel metadata and compare versions without scraping the website or guessing which file is current.
Channels
Promotion is deliberate.
Moving an artifact from Developer to Beta or Stable is a release decision. The manifest model does not automatically promote a build because it exists.
Fast-moving engineering
Internal and closely controlled validation builds.
Controlled candidates
Signed artifacts distributed to a defined testing audience after product-specific gates pass.
Supported public builds
Approved artifacts with public acquisition, release notes, version metadata, and integrity checks.
Release notes
Follow the milestone before the installer.
Company updates explain the current product and validation work while manifests remain the machine-readable source for published release state.