- Decision
- ADR-140
- Date
- 2026-10-06
- Status
- AcceptedAccepted
- Part
- AirPods
- Mentions
- ADR-117, ADR-139
- Mentioned by
- ADR-144, ADR-147, ADR-149
1Decision
The AirPods stack (the AirPods commits of packages/modules/Bluetooth on sovereignos-airpods-identity, the app and its package, ADR-117 to ADR-139) ships to stallion under Personal Stable as candidate 2026100501, with the matrix rows AIR-136, AIR-138, AIR-191, the second-user part of AIR-196 and the rows listed in status.md still open. This supersedes the exclusion of the AirPods commit from stallion builds in tasks 5, 7 and 10 of the stallion plan.
2Why and evidence
Owner decision 2026-10-06 (chat): the owner wants to use the AirPods on the daily phone. The risk is the one the open rows name: the Bluetooth module change reaches every peer (AIR-138 no second peer was available), a call with both pods out was never run (AIR-136), and the binder tests of patch 0012 were not run (AIR-191).
3Consequences
The candidate is a user build (ro.debuggable=0), signed in the ceremony with the Personal Stable key and checked independently (hash equal to the log, otacert fingerprint equal to the OTA already installed, post-timestamp newer). A downgrade is rejected by the Updater, so a rollback is a new build without the AirPods commits and a higher number. The owner can stop using the AirPods without a rollback by not connecting them. Evidence: AIR-197.
4Review when
A defect in another Bluetooth peer, a call or the update path on stallion; the closing of the open rows (then the Proposed ADRs 125, 126, 127, 135 to 139 can be accepted).
Read from docs/governance/decision-log.md, entry ADR-140.