V0-Replay-26 PCB A

Temporal Replay 2026 Badge

Public source for the Temporal Replay 2026 Badge at badge.temporal.io: firmware, hardware design files, flashing tools, badge apps, release metadata, and the static documentation site.

This repository is for people who want to flash a badge, build a badge app, study or modify the firmware, review the hardware package, or contribute fixes back through GitHub pull requests. Backend services and private event operations tooling are intentionally not part of this public repo.

Where To Start

Repository Map

Quick Start

Ignition is the Temporal-powered system we built to bulk flash the Replay 2026 badge fleet. It runs locally and is the default flashing path for one badge or a connected batch of badges:

cd ignition
./setup.sh
./doctor.sh
./start.sh --latest-release

--latest-release downloads replay2026-factory-16MB.bin from the latest GitHub Release, caches it locally, and flashes the badge through Ignition. A factory flash restores firmware and filesystem contents and wipes existing on-badge data.

To build from source and preload WiFi, pass credentials on the command line or create an ignored firmware/wifi.local.env from firmware/wifi.local.env.example:

./start.sh -e replay2026 --firmware-dir ../firmware \
  --wifi-ssid "YourNetwork" --wifi-pass "YourPassword"

Developers who want the lower-level path can use PlatformIO directly:

cd firmware
pio run -e replay2026
pio run -e replay2026 -t upload
pio run -e replay2026 -t uploadfs

For a specific prebuilt release, use the release tag:

cd ignition
./start.sh --release-tag v1.0.0

You can still flash a manually downloaded image with ./start.sh --no-build --factory-image ~/Downloads/replay2026-factory-16MB.bin. See release-assets/README.md for release artifact context.

Firmware Releases

Public releases include two firmware artifacts:

• firmware.bin: application image consumed by badge OTA.
• replay2026-factory-16MB.bin: complete factory image with bootloader, partition table, firmware, FAT filesystem, and bundled shareware Doom data.

The badge OTA updater checks GitHub Releases in temporal-community/badge.temporal.io for firmware.bin.

Licensing

Temporal-authored source, docs, firmware glue, website content, and hardware files use the MIT License unless a file or notice says otherwise.

Firmware builds that include Doom also include DoomGeneric engine code and the bundled doom1.wad shareware game data. Those components have separate terms; see THIRD_PARTY_NOTICES.md and licenses/.

Generated Artifacts

Some generated files are committed because the firmware or public release flow consumes them directly:

Contributing

Pull requests are welcome. Good public contributions include docs fixes, MicroPython examples, badge apps, firmware fixes, Ignition improvements, hardware documentation corrections, data updates, and Community App updates. See CONTRIBUTING.md for change-type checklists.

Before opening a PR:

• Keep changes focused and explain what you tested.
• Link related docs when you add or change a workflow.
• Do not commit credentials, local WiFi settings, virtualenvs, PlatformIO build output, caches, or private event operations context.
• For firmware changes, include the relevant PlatformIO build or flash command you ran.
• For docs-only changes, check that links resolve from the repo root and the static docs site still opens from docs/index.html.

Use GitHub issues or PR discussion for questions, bug reports, and proposed app or documentation changes.