- Decision
- ADR-239
- Date
- 2026-11-16
- Status
- ProposedProposed 2026-11-16 (owner's choice for review D10; plain-JVM harness, two mutants killed, type check
OK; not landed, not built, not on a device) - Part
- Duress Unlock
1Decision
Amend the failure path of the seamless decoy unlock (2026-09-07-duress-decoy-seamless-unlock-design.md, \"Failure path\"): the failure marker of DecoyRoutingFailureMarker is cleared when the real owner's own credential next unlocks user 0 on the primary domain (LockSettingsService, after DecoyFingerHelper.onOwnerSyntheticPasswordUnlocked). Patch credential/duress-unlock-decoy frameworks-base/0008.
2Why and evidence
Review D10 of 2026-11-duress-unlock-code-review.md. The marker was written for the owner to see a silent failure afterwards (LockSettingsShellCommand prints it) but nothing cleared it, so a read of the storage of user 0 after a boot showed that and when a decoy switch ran [verified-in-source]. Rejected: removing the marker (no later sign of a failed routing for the owner); keeping it as it was.
3Consequences
The owner sees the marker only until the next credential unlock; a read of the storage in the window between the failure and that unlock still shows it, and a finger unlock does not clear it.
4Review when
Reopen if the window is itself a leak the owner cares about (then the marker would have to be kept in memory only).
Read from docs/governance/decision-log.md, entry ADR-239.