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

I want to...	Start here
Use or reflash a badge	Get Started, then ignition/README.md
Write a MicroPython badge app	Developer Guide, Apps, and firmware/initial_filesystem/apps/README.md
Submit or share a Community App	Add an app folder under community_apps/, then follow community_apps/README.md
Change firmware	firmware/README.md and firmware/src/README.md
Understand flashing and storage	ignition/README.md and firmware/docs/STORAGE-MODEL.md
Work with hardware files	hardware/README.md
Update public schedule, floor, or speaker data	data/README.md
Update the docs site	docs/README.md
Review release artifacts or OTA	release-assets/README.md and .github/workflows/release-firmware.yml
Check licensing and third-party terms	THIRD_PARTY_NOTICES.md and licenses/
Contribute a fix	Open a pull request against temporal-community/badge.temporal.io; see Contributing below.

Repository Map

Path	What It Contains	Start Here
docs/	Static public documentation site for badge users and contributors.	Visit badge.temporal.io or open docs/index.html locally.
firmware/	PlatformIO firmware project for the ESP32-S3 badge, including native C++ screens, MicroPython embedding, OTA, Doom, and the badge filesystem source.	firmware/README.md
community_apps/	Installable MicroPython community app folders that are published in the Community Apps registry but not preloaded into the factory filesystem.	community_apps/README.md
ignition/	Temporal-powered build and flashing system built to bulk flash the badge fleet, also useful for one badge.	ignition/README.md
hardware/	Public KiCad projects, fabrication outputs, mechanical references, artwork, and board renders from the final hardware package.	hardware/README.md
data/	Public schedule, speaker, and floor data plus the generated bundle embedded by firmware.	data/README.md
release-assets/	Notes for OTA and factory image release artifacts.	release-assets/README.md
licenses/	Third-party license texts and notices for bundled non-MIT components.	THIRD_PARTY_NOTICES.md
.github/workflows/	CI release workflow that builds firmware.bin and replay2026-factory-16MB.bin.	.github/workflows/release-firmware.yml
CONTRIBUTING.md	Pull request guidance and change-type checks.	CONTRIBUTING.md

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:

Path	Source of truth	Commit?
data/out/	data/in/ via data/build-data.py	Yes, commit all generated public data outputs
firmware/data/	firmware/initial_filesystem/ via firmware/scripts/generate_startup_files.py	No, it is a local build mirror
firmware/build/community_apps.json	community_apps/ via firmware/scripts/generate_startup_files.py	No, generated in CI and uploaded as a release asset
firmware/.pio/, ignition/.venv/, local logs, and WiFi files	Local machine state	No
firmware.bin and replay2026-factory-16MB.bin	GitHub release workflow	Release assets only

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.