- Decision
- ADR-132
- Date
- 2026-10-04
- Status
- AcceptedAccepted
- Part
- AirPods
- Mentions
- ADR-128, ADR-129
- Mentioned by
- ADR-133, ADR-134
1Decision
The own AirPods pages support every control the AirPods expose. No control is dropped for lack of a captured protocol: each one is captured on the owner's pair with the probe first, then built and proven on the device. A control for which the pair gives no frame stays on the page's list as Open with the capture result as its reason and is never hidden. Supersedes the sentence of ADR-129 and of Plan 7B decision P4 that moves Equalizer and Find (Last seen, Play sound) off the page, and the spec's "leaves the page" rows. ADR-128 (no scan, no BLUETOOTH_SCAN) is unchanged.
2Why and evidence
Owner decision 2026-10-04: full AirPods support, repeated several times; a page that drops controls for lack of a protocol does not meet it. Press and hold and Name were also only third-party documented until the probe captured them, and are now built. The third-party control table lists about 40 settings and the owner's burst already carries 14 of them (docs/research/airpods-aap-protocol-facts.md).
3Consequences
A larger page and more frames sent to the pair, each bounded and validated like the existing ones; a security review of every new frame and permission before code; the case location (Find My) may turn out to be Apple's network and impossible here, which is then recorded per row, not assumed.
4Review when
A capture that shows a control the pair does not implement; a control that needs a permission the security rules forbid (then an owner decision with the evidence).
Read from docs/governance/decision-log.md, entry ADR-132.