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
- PyBLE — canonical app, PBLE/1, firmware, product documentation, tests, and release tooling
- PyBLE Examples — separately governed official user-facing runnable-example collection; its initial catalog plan records the founding scope
The current primary-maintainer sibling checkout for the examples collection is
/Users/vyv/Working/SciLabPro/PyBLE-Examples. This machine-local path is an
informational organization convention, not a contributor, build, application,
CI, or release requirement. ADR-0041
defines the boundary: official example implementation happens in that separate
repository and history, while this repository retains only the fixtures and
bundled offline examples required by its own product contracts.
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.