1Decision
Authorize an owner-performed OEM bootloader unlock on the physical Pixel 7a (lynx) engineering unit, to proceed past bring-up sequence step 2 (docs/devices/support-policy.md).
2Why and evidence
The unit's retail identity and locked state were verified read-only (stock fingerprint google/lynx/lynx:15/BP1A.250505.005.B1/13277630:user/release-keys, ro.boot.vbmeta.device_state=locked, ro.boot.verifiedbootstate=green); GrapheneOS vendor blobs for lynx were generated via adevtool; an ARM64 lynx-cur-userdebug build carrying the ADR-019 boot-identity patch layer is in progress. Unlocking is the mandatory prerequisite to flash any test-key image (support-policy step 3) and cannot be skipped or emulated.
3Consequences
Unlocking irreversibly wipes all data on the device and moves its verified-boot state from locked/green to unlocked, losing the stock trust chain until AegisOS completes its own signing/relocking path (support-policy steps 5–6). Per ADR-007, the assistant has no flashing/bootloader authority; the owner enables OEM unlocking in Developer Options and performs the fastboot unlock and its on-device physical confirmation personally. Developer Options and USB debugging reset with the wipe and must be re-enabled before ADB access returns.
4Review when
The unlock fails or produces an unexpected device state, the device needs to return to a locked/stock state for any reason, or the AegisOS release-key signing design (support-policy step 5) is proposed.
Read from docs/governance/decision-log.md, entry ADR-020.