PyBLE keeps public contracts, design rationale, validation evidence, and maintainer guidance beside the source they govern.
- Product scope
- Architecture
- PBLE/1 protocol
- App contract
- Firmware contract
- Hardware compatibility
- Public roadmap
specifications/App/— app requirements, test design, and the Signal visual systemspecifications/firmware/— firmware requirements, test design, browser flashing, release integrity, and HIL gates- Website — public routes, privacy, compatibility, installer, and deployment contracts
PBLE/1 is the interoperability source of truth. Changes to wire behavior must update the protocol specification, app and firmware implementations, and the shared conformance corpus in one pull request.
- Architecture Decision Records
validation/— retained release and hardware qualification evidence
Internal sprint notes and automated-agent orchestration are intentionally kept outside the public source repository. Public work is planned through the roadmap and GitHub issues.