ObliviOS Developer portal Project site

Home / Decisions / ADR-226

Build the first ObliviOS image, lynx 2026111101.

Accepted, recorded 11 November 2026.

Decision
ADR-226
Date
2026-11-11
Status
AcceptedAccepted (owner, 2026-11-11: the owner agreed to the build and to the renumbering). Done and read back: built (IMG-031, build-lynx-2026111101.sh, exit 0 and every check of the script), the flashset of 37 files copied to the workstation with 37 of 37 hashes equal. Not done: signing, the flash read back on the device (the owner flashes), every DUR and CMP row of round-gate.py 2026111101.
Mentions
ADR-222, ADR-225

1Decision

Build the first ObliviOS image, lynx 2026111101, as one build with every open Duress and Compartments change (owner, 2026-11-11: land frameworks-base/0014 and 0015 of ADR-222, build them with the other open Duress patches, and verify the new Compartments work in the same round).

The patches of the duress-unlock-decoy package are numbered in the order of the branch: 0012 and 0013 are the two build-tree commits of lynx 2026110502 that no package file held (ef65610d1f1b, the finger can be chosen for any biometric id; afc9ac07440e, the decoy administration accepts only the owner's own credential), 0014 and 0015 are the decoy memory patches of ADR-222 (numbered 0012 and 0013 until the same day), 0016 sorts the renamed decoy user type in core/api/system-current.txt.

2Why and evidence

The build tree held two patches that were built into an image and exported nowhere; a search for their identifiers in the five repositories found none. tools/rename/package-check-all.sh cannot find such a gap for frameworks/base because it already fails there (ADR-225).

The first build after the rename stopped after 2 h 18 min at 99 % in check_current_api: the renamed constant sorts after USER_TYPE_FULL_GUEST and the listing is compared line by line; the second run was incremental and took 1 h 58 min.

Rejected, each with its reason: exporting the two missing patches as 0014 and 0015 and keeping 0012 and 0013 (the series replays the branch in order, and the owner check and the memory patches both edit DecoyProfileHelper; only the order of the branch is proven by the equal trees); building with DISABLE_STUB_VALIDATION=true (the notice says it does not bypass checkapi, and the listing would stay wrong).

3Consequences

The decoy users are deleted at the first boot of the image and a vault of the old identity does not open (ADR-225): the DUR rows start with a new set-up. A 0012 or 0013 in a record written before 2026-11-11 means the decoy memory patches (corrected where found).

4Review when

The first device round of 2026111101; the cause of the frameworks/base package check.

Read from docs/governance/decision-log.md, entry ADR-226.