- Decision
- ADR-147
- Date
- 2026-10-07
- Status
- AcceptedAccepted
- Mentions
- ADR-140, ADR-144, ADR-145
- Mentioned by
- ADR-149
1Decision
The Duress Unlock Settings UI of ADR-145 ships to stallion under Personal Stable, in the same candidate as the app drawer and the AirPods review fixes (ADR-144): 2026100701, a user build with OFFICIAL_BUILD=true, signed in the ceremony with the Personal Stable key, published as stallion stable and installed through the Updater, with the steps of ADR-140. It decides what Task 8, Step 1 of the Duress Unlock Settings UI plan left open: a user build for stallion as a separate decision.
2Why and evidence
Owner decision 2026-10-07 (chat): the owner wants the Duress Unlock Settings UI in the same update as the drawer and the review fixes, after the content of the candidate was listed per repository (three change sets, the framework change and the open Duress items named). ADR-145 is accepted with part of its device rows waived; the screen replaces shell-command provisioning of the decoy on the daily phone.
3Consequences
The candidate adds ILockSettings#isDuressWipeCredential to frameworks/base on the daily phone (appended last, write permission and owner credential required, no wipe and no routing). Open and accepted by the owner: the decoy session's lock screen and notifications differ from the owner's, and a wipe PIN can still be set equal to a decoy PIN (ADR-145, status.md); the waived rows DUR-006, DUR-008 to DUR-011 and DUR-013. A downgrade is rejected by the Updater, so a rollback is a new build with a higher number (ADR-140). Evidence: STALLION-006.
4Review when
A Duress row fails on stallion; the owner decides on the decoy's resemblance; a defect in the lock settings path after the update.
Read from docs/governance/decision-log.md, entry ADR-147.