- Decision
- ADR-060
- Date
- 2026-08-29
- Status
- AcceptedAccepted (qualified — see ADR-061 for a real defect found in Component A during validation)
- Part
- Duress Unlock
- Mentions
- ADR-061, ADR-062
- Mentioned by
- ADR-061, ADR-066, ADR-068, ADR-082, ADR-089
1Decision
Approve docs/superpowers/specs/2026-08-28-duress-decoy-session-indistinguishability-design.md and land Tasks 1-9 of its implementation plan (docs/superpowers/plans/2026-08-28-duress-decoy-session-indistinguishability.md) across four AOSP repositories under the established local-first patch-authoring discipline, executed via subagent-driven-development with an independent task review for every task.
2Why and evidence
The design was approved after a source-verified audit inventoried every real way the decoy session fails the threat model's "a decoy unlock is, from every observable signal, a normal unlock" requirement (docs/security/threat-model.md:54): a P0 double-PIN-prompt bug (reproduced on physical hardware before this plan), P1 identity leaks (SystemUI's user switcher and power menu, Settings' Storage screen, the com.android.multiuser widget), a P2 setup-incomplete behavioral cascade (screenshot/clipboard overlays, full-screen intents, the alarm icon, Material You theming, the QS gear), and minor P3 inconsistencies.
Task 1 (research) confirmed STRONG_AUTH_REQUIRED_AFTER_USER_LOCKDOWN is lockdown-only, not reachable by an ordinary wrong-PIN attempt (independently re-verified by a second subagent before being trusted), and found one new unscoped, decoy-reachable call site (packages/SettingsLib/.../StorageMeasurement.java:148) the original audit had missed.
Tasks 2-8 landed one new shared API (UserManager.getUsersForUiDisplay, frameworks/base patch 0019) and migrated every real leaking call site onto it (SystemUI 0020, Settings 0001+0021, the multiuser widget's own new 0001 patch package), added the decoy setup-complete write (0022, plus a same-session fix 0023 after the controller independently found and confirmed a missing Binder.clearCallingIdentity() around the new Settings.Secure write — the real invocation path lacks WRITE_SECURE_SETTINGS, a defect the task's own reviewer had missed), and Component A's own two patches (0018 on frameworks/base, 0001 on a newly created build/release package) — later found broken, see ADR-061.
Task 9's consolidated m systemimage build across all four repositories' final state passed clean: ninja: 1h20m55.67s Build Succeeded: 4272 steps, #### build completed successfully (01:21:01) ####.
3Consequences
All four repositories' patches exported to aegisos-platform/credential/duress-unlock-decoy/patches/{frameworks-base,build-release,packages-apps-settings,packages-apps-multiuser}/, SOURCE.md updated for each, including two new patch packages (build-release, packages-apps-multiuser) receiving their first-ever AegisOS patches. Components B, C, and D are functionally sound per this build and Task 10's subsequent emulator validation (ADR-061); Component A is not.
4Review when
See ADR-061 for Component A's real, confirmed defect and its resolution, and ADR-062 for physical-hardware validation of the components that do work.
Read from docs/governance/decision-log.md, entry ADR-060.