Downloads

Documents first. Software only when validated.

This page is the future home for RelayHub documents, media assets, community resources, hardware resources, validation artefacts, and eventual RelayOS software releases.

Documentation Status

Documents

Foundational documents and future public artefacts.

RelayHub begins with architecture, product requirements, governance, values, policy, validation, and branding documents. Public download links can be added here as documents are prepared for release.

Document available

System Architecture Specification

Canonical architecture source for hardware classes, policy, recovery, validation, operational modes, and ecosystem design.

Document available

Product Requirements Document

Product-facing requirements for appliance behaviour, onboarding, recovery, support, validation, and user experience.

Document available

Purpose, Mission, Values & Principles

Foundational purpose and principles guiding the RelayHub ecosystem.

Document available

Governance & Policy Framework

Policy hierarchy, policy domains, enforcement expectations, validation, and governance lifecycle.

Document available

Branding & Identity Specification

Canonical RelayHub, RelayOS, product, application, community, federation, compatibility, and certification language.

Planned

Validation Plan

Future public validation plan covering evidence, release gates, hardware classes, recovery drills, and support readiness.

Media assets

Brand and media resources.

Media assets should help journalists, presenters, community organisers, and partners describe RelayHub consistently.

Media kit
  • Logo package
  • Brand colour palette
  • OpenGraph images
  • Product screenshots
  • Hardware photographs
  • Media kit

Community resources

Practical resources for future pilots and communities.

Community resources should help groups start small, test onboarding, document lessons, practise recovery, and avoid false confidence before scaling.

Community guides
  • Community Quick Start
  • Community Pilot Checklist
  • Deployment Worksheet
  • Recovery Drill Worksheet
  • Trust and Membership Worksheet
  • Marketplace Steward Guide
  • Presentation Slides
  • Workshop Handouts

Future software

No RelayOS images are available yet.

Software downloads should not appear until builds, recovery, update, hardware compatibility, documentation, and validation boundaries are ready.

Planned

RelayOS Images

Future appliance images for validated hardware classes.

Planned

Home Node Images

Future Home Node builds after recovery, onboarding, and validation gates are satisfied.

Planned

Infrastructure Node Images

Future infrastructure builds for validated bridge, gateway, DTN, and operator workflows.

Planned

Recovery Images

Future recovery-focused images or bundles for safe restore and repair.

Planned

Offline Update Packages

Future signed offline update bundles after compatibility and rollback behaviour are validated.

Planned

Validation Tools

Future test tools for boot, setup, Reticulum, recovery, update, support export, and hardware validation.

Validation Recovery

Hardware resources

Hardware files must not imply support before validation.

Future hardware resources should clearly identify whether they are concept, experimental, compatible, verified, certified, or officially supported.

Hardware Certification
  • Bills of materials
  • Assembly guides
  • Hardware compatibility lists
  • Capability manifests
  • Power and thermal notes
  • Radio policy notes
  • Certification documents
  • Manufacturing test checklists

Download rules

Every download should carry status and scope.

RelayHub should avoid publishing files that create false expectations. Downloads should explain their version, maturity, hardware class, support boundary, and recovery implications.

Downloads should be versioned.

Downloads should clearly show status.

Experimental files must be labelled experimental.

Product-supported files require validation evidence.

Software images must preserve recovery paths.

Offline updates must be signed and validated.

Hardware resources must not imply certification unless certified.

Documents should distinguish current, planned, experimental, and supported material.

Current status

Downloads are being prepared as the project matures.

The downloads hub is ready as a public structure. Documents, assets, guides, software, and hardware resources can be added as they become appropriate for public release.