OpenBeat v0.1.0 public launch map

[eimexdev]

Destination

Publish OpenBeat v0.1.0 as a licensed open-source project whose macOS and Windows installers are downloaded from GitHub Releases, signed and independently verifiable, honestly documented, and smoke-tested in DaVinci Resolve.

Notes

This map explicitly carries execution through the public release. That overrides Wayfinder's planning-only default: wayfinder:task children may implement the resolved route and deliver the destination.

Standing preferences:

• GitHub Releases is the canonical binary distribution channel.
• Ko-fi may support or announce the project, but it does not gate downloads or host a second canonical copy.
• Preserve the May 21 reliability and release work; change direction with forward commits rather than rewriting main.
• Target v0.1.0 for the first public launch.
• Treat signing as a launch gate unless the signing research resolves a narrower, explicitly accepted exception.

Session guidance:

• Use $research and primary sources for wayfinder:research tickets; link the Markdown research artifact from the resolution comment.
• Use $grilling with $domain-modeling for wayfinder:grilling tickets. The maintainer must answer for their own preferences.
• Use $prototype for wayfinder:prototype tickets and obtain live maintainer reaction before resolution.
• Claim a ticket by assignment before working it. Resolve it with an answer comment, close it, and add only a one-line named context pointer below.
• Native GitHub dependencies define the frontier; do not infer sequencing from issue numbers.

Decisions so far

• Choose the project license for the public launch — Use MIT for OpenBeat's own source with Copyright © 2026 Parker Eimerl; preserve the separate licenses and notices of bundled dependencies.

• Make GitHub Releases the canonical download channel — GitHub Releases is the sole installer channel; Ko-fi is optional support and never gates or duplicates downloads.

• Correct Build Installers artifact-upload documentation — Automatic builds upload nothing; manual builds provide temporary test artifacts, while draft GitHub Release assets are smoke-tested and published.

• Choose the Windows installer destination contract — Default to the standard per-user Fusion root, support an explicit custom-root chooser, and defer automatic discovery.

• Research the signing and notarization strategy for macOS and Windows — Use existing Apple Developer ID credentials for macOS; prefer free SignPath Foundation signing on Windows, with Azure Artifact Signing used only during release months as the fallback.

Not yet specified

• Additional installer or compatibility work that may emerge from the Windows destination decision or exact-artifact smoke testing.
• The final compatibility claims and release caveats supported by the exact v0.1.0 artifacts.

Out of scope

• Extract the embedded Windows installer application into a testable module — useful maintenance work, but not required to reach the v0.1.0 launch destination unless smoke testing exposes a blocking defect.
• Improving automatic click-track or subtitle placement beyond the current documented best-effort behavior.
• Building a second binary distribution system, Ko-fi checkout flow, or standalone marketing-site release infrastructure.