- Decision
- ADR-089
- Date
- 2026-09-17
- Status
- AcceptedAccepted — closes ADR-087's item 3, no code change
- Mentions
- ADR-060, ADR-061, ADR-085, ADR-087
1Decision
Formally close ADR-087's item 3: credential_capture (android.multiuser.credential_capture) stays permanently DISABLED for this product; no redesign is undertaken.
2Why and evidence
ADR-060/061 found enabling this generic AOSP mechanism caused a real device-wide keyguard bypass for ordinary PIN-protected secondary users and reverted it to inert (build/release's aconfig/cp2a/android.multiuser/credential_capture_flag_values.textproto, patch 0004, state: DISABLED, permission: READ_ONLY).
The 2026-09-07 seamless-unlock design (docs/superpowers/specs/2026-09-07-duress-decoy-seamless-unlock-design.md:105-107) built Component B specifically to avoid ever re-enabling it, and ADR-085/086/087 hardware-confirmed Component B's own three-grant authorization primitive delivers the original single-credential-entry goal without it.
No task, ADR, or spec reviewed for this closure identifies any capability credential_capture's redesign would add that Component B does not already provide.
3Consequences
None — no behavior, code, or build change. This entry only updates the record: credential_capture is not merely "untouched," it is deliberately and permanently retired in favor of Component B.
4Review when
Re-open only as its own brainstorming/spec/plan cycle, per ADR-061's own instruction, if a future requirement surfaces that Component B's three-grant primitive genuinely cannot satisfy — never as a reactive patch, and never without re-testing the exact ADR-061 non-decoy regression case.
Read from docs/governance/decision-log.md, entry ADR-089.