Congregation territory operations
The repository identifies a 5.0 Alpha core milestone, while signed device beta and public distribution remain separate release gates.
Downloads + releases
Release truth before the download button.
Developer, Beta, and Stable are deliberate promotion states. A public acquisition link appears only after a real artifact has approved version metadata, release notes, integrity information, and an official distribution URL.
Manifest-backedMachine-readable release state stays separate from marketing copy.
Integrity-awarePublished artifacts require integrity metadata such as a SHA-256 checksum.
No fabricated linksUnpublished products remain visibly in development instead of exposing placeholder installers.
Product fleet
Current release state.
These surfaces report only what the repository currently declares. The absence of a download button is intentional when a verified public artifact does not exist.
Receive. Work. Return.
The local-first companion remains under active engineering. No public App Store or installer artifact is declared by this site.
Power on demand
Workflow, diagnostics, packaging, update, and clean-machine lifecycle work remain part of the release gate before a supported installer is published.
Evidence-safe recovery
Standalone recovery validation, packaging, evidence handling, and independent launch behavior must be proven before a public installer is promoted.
A missing installer link is a release-safety state, not a broken page. Product manifests remain the machine-readable source for publication state.
Distribution architecture
Metadata first. Artifacts second.
The release contract separates what update clients need to know from the binary packages themselves. That keeps version checks deterministic and prevents the public HTML from becoming an accidental source of release truth.
Describe the release
Product ID, channel, version, publication state, release notes, artifact metadata, and integrity information.
Store the artifact
Approved versioned installers and packages are intended to live in Cloudflare R2 without coupling binary storage to page markup.
Check deterministically
Applications can compare channel metadata without scraping the website or guessing which file is current.
Promotion channels
A build existing does not make it a release.
Developer, Beta, and Stable represent increasingly strong distribution commitments. Promotion remains an explicit release decision.
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 current product and validation work while manifests remain the machine-readable source for published release state.