- Decision
- ADR-100
- Date
- 2026-09-26
- Status
- AcceptedAccepted. Deviation from
docs/release/supply-chain-and-signing.md("Alpha requires a reproducible candidate") recorded here, not waived silently; ADR-099 stays Proposed until the candidate has booted on the reallynx. - Mentions
- ADR-029, ADR-097, ADR-099
- Mentioned by
- ADR-102
1Decision
Sign the lynx candidate 2026092501 (manifest 2026091900, ADR-099) as an alpha internal-test artifact without an independent reproduction run, and update the owner's device by OTA with the decoy user removed first, not by fastboot -w. The owner delegated the choice ("whatever is fastest and best") and set the data rule: the decoy user may be wiped, the owner's normal profile must not be.
2Why and evidence
An independent reproduction needs a second full source tree and build (/srv has ~63 GB free, a tree is ~400 GB, a full build about 8.5 h) and ADR-029 already showed that ext4 image generation carries wall-clock values with no build-input origin, so byte reproducibility of the images is not expected even then.
What was verified instead (see sovereignos-manifest/provenance/2026091900.md): the four official apps present, identical build identity, and 0 content differences over the SYSTEM/SYSTEM_EXT/VENDOR/PRODUCT trees between the target-files zip and the build output.
The persisted decoy user type string changed from org.aegisos.usertype.full.DECOY to org.sovereignos.usertype.full.DECOY (ADR-097); UserManagerService in this tree has no upgrade path for an unknown persisted type and I could not rule out a null dereference at boot, so the decoy user is removed on the running old build before the update and an OTA (which keeps /data) is used.
3Consequences
The candidate must not be described as reproducible or promoted beyond internal alpha testing. The new baseband (g5300q-260604-260807-B-16036236) has not been confirmed to be carried by the OTA payload. sign-ota.sh on the signing host has been hand-edited before (2026-08-21-the signing host-storage-rootcause-report.md), so its live copy must match the repo copy before the ceremony.
4Review when
Any claim of reproducibility or promotion beyond internal alpha; the OTA install fails or the device does not boot; the live signing script differs from the repo copy.
Read from docs/governance/decision-log.md, entry ADR-100.