TerritoryHub
Maps, territory records, publishers, assignments, campaigns, S-13 history, search, recovery, and administration.
Product documentation →Documentation
Public documentation for the Raysor ecosystem.
Start with product scope, understand release status, then use the version manifests and support routes for the current public state.
Products
Choose the product boundary first.
TerritoryHub owns congregation-side territory management. Territory Field owns the field-user assignment workflow. PowerShell Principal owns broader automation and developer workflows. Deep Orbit remains a distinct recovery and reconstruction product.
Territory Field
Request, receive, understand, work, track, and return territory assignments with local-first behavior.
Product documentation →PowerShell Principal
Reusable automation, pipelines, runtime profiles, controlled execution, logs, artifacts, diagnostics, and lifecycle tooling.
Product documentation →Deep Orbit
Evidence-safe recovery missions, provenance, confidence, reconstruction, diagnostics, SAFE STOP, and reporting.
Product documentation →Release channels
Developer, Beta, Stable.
Every manifest uses the same three channel names. The presence of a channel does not mean it is published. The published field is authoritative for whether the website recognizes an approved artifact in that channel.
Developer is for active engineering. Beta is controlled distribution. Stable is the supported public release line.
Downloads
Version data before installer links.
The public downloads page reads from the same release architecture that update clients can consume. A release record should include a product ID, channel, version, published state, release notes, artifact URL when available, and integrity metadata such as a SHA-256 checksum.
Product manifests live under /releases/. The catalog is available at /releases/catalog.json.
Security
Public downloads must be verifiable.
Stable distribution is expected to use HTTPS, versioned artifacts, integrity metadata, deliberate release-channel promotion, and product-specific validation. Website administration remains protected through the existing Cloudflare Access and application authorization system.
Support
Use the route that matches the issue.
General product or company questions belong on the Contact route. The Support route contains the current voluntary-support flow and its payment disclosures. Security reports should use the security reporting guidance rather than a public form containing sensitive details.
Website platform
The redesign does not replace the backend.
The website remains served by the existing Cloudflare Worker with static assets, D1, protected administration, Stripe, Turnstile integration points, Resend integration boundaries, API routes, security headers, and explicit feature-readiness gates. Website v1.0 changes the public experience around those existing contracts.
Backend infrastructure remains independently versioned and validated. Public redesign work must not weaken Worker routing, authorization, request validation, data separation, or deployment safeguards.
Current state
Need to know what is actually shipping?
Use the downloads hub and product manifests. A disabled channel is intentionally different from a missing or implied release.