- Decision
- ADR-030
- Date
- 2026-08-04
- Status
- AcceptedAccepted
- Mentions
- ADR-026, ADR-027, ADR-028, ADR-029
- Mentioned by
- ADR-029, ADR-035, ADR-046, ADR-268
Shown as written
This entry has 8 columns where the log has seven, because a cell holds the separator of the table or a column is missing. The cells follow in their order, under the label of their place.
1Decision
Generate and use the first AegisOS alpha-channel signing key to re-sign the accepted candidate's (ADR-029) vbmeta.img, replacing the development-channel key, after flashing the 8 partitions that candidate actually changed.
2Why and evidence
docs/release/supply-chain-and-signing.md requires alpha candidates to be reproducible and have recorded approvals before promotion. ADR-029 recorded that reproduction (root-caused, candidate replaced, corroborated by a clean single-module spot-check). Task 5 found the device's prior boot evidence did not transfer to the new candidate and required a fresh check; Task 7 performed the actual signing, flashing, and that fresh check. ADR-028 records the single-operator role model this ceremony ran under.
3Further text
RSA 4096 alpha key generated on the build server at <build-root>/keys/alpha/ (private key never left the server), fingerprint 265ade399a0f3ee65003e56daef26a8f4d70e6a4, confirmed distinct from the development key's 7cf180b00535d72a70396995ab68b580aae05648.
Because the accepted candidate changed 8 of 12 partition images (not just vbmeta.img, unlike ADR-026's development-key ceremony), Task 7 first flashed init_boot, product, system_dlkm, system_ext, system, vendor, vendor_boot, vendor_dlkm — the 6 dynamic/logical partitions among these initially failed with Invalid command resize-logical-partition in plain bootloader-fastboot and required rebooting to fastbootd first, corrected before any partition write occurred.
vbmeta-alpha-signed.img was then built with avbtool make_vbmeta_image against all 12 partitions' descriptors, verified 13/13 on the server and independently on a separate local machine with a different avbtool binary (fingerprint cross-checked and matched).
A first signing attempt omitted --rollback_index and produced 0 instead of the original's 1783209600 — caught by the required descriptor diff (not silently passed) and corrected; the corrected image's only remaining difference from the original is Prop entry order (identical keys and values), confirmed cosmetic by reading AvbPropertyDescriptor in external/avb/avbtool.py, which parses and verifies each descriptor as an independent, self-contained struct rather than by position.
Flashed via fastboot flash vbmeta vbmeta-alpha-signed.img.
Fresh post-flash evidence for this specific candidate (not reused from any prior boot, per Task 5): fingerprint unchanged (google/lynx/lynx:17/CP2A.260705.006/2026073100:userdebug/test-keys), sys.boot_completed=1, verifiedbootstate=orange, vbmeta.device_state=unlocked (unchanged — relock explicitly out of scope), 392 total Dropbox entries (persisted across this partition-only reflash — no data wipe), 76 from this boot specifically (45 system_app_strictmode, 30 system_server_strictmode, 1 SYSTEM_BOOT), zero crash/ANR/tombstone matches across all 392.
4Further text
The device now boots under an independently-reproduced, alpha-signed AegisOS artifact — docs/devices/support-policy.md's "Production trust" row's stated blocker (missing Phase 1 execution plan) is resolved for the alpha tier. Bootloader remains unlocked; the key is not yet an enforced root of trust, same posture as ADR-027 described for the development key.
5Last cell
Before any beta-channel key is proposed, before this alpha key is exposed/rotated, or when bootloader relock / avb_custom_key enrollment (support-policy step 6 / LYNX-001) is proposed — that is its own future decision, not an extension of this one.
Read from docs/governance/decision-log.md, entry ADR-030.