Choose a reproducible-build and bundled-license strategy

[eimexdev]

Part of OpenBeat v0.1.0 public launch map.

Question

What release-dependency constraint strategy and third-party notice format should OpenBeat adopt so a release can be rebuilt from a known dependency set and redistributed responsibly?

Research scope

• Compare practical constraints/lock approaches for Python 3.11 release builds across macOS and Windows.
• Decide how PyInstaller and runtime dependencies are pinned and deliberately updated.
• Decide where resolved versions are recorded.
• Inventory bundled dependency licenses and determine the notice or source-offer obligations relevant to the installer.
• Identify platform-specific differences that prevent one identical lock set.

Research artifact

Use $research and primary package/license sources. Link a repository Markdown summary from the resolution comment with the selected approach and rejected alternatives.

Handoff

Implement reproducible release dependencies and third-party notices implements the resolved strategy.