ObliviOS Developer portal Project site

Home / Decisions / ADR-021

Execute Phase 1 Task 5 (independent reproducibility comparison), owner-directed after ADR-018's waiver, and record the result honestly rather than re-waiving it.

Accepted, recorded 1 August 2026.

Decision
ADR-021
Date
2026-08-01
Status
AcceptedAccepted
Mentions
ADR-018, ADR-019
Mentioned by
ADR-022, ADR-023, ADR-024, ADR-026, ADR-073

1Decision

Execute Phase 1 Task 5 (independent reproducibility comparison), owner-directed after ADR-018's waiver, and record the result honestly rather than re-waiving it.

2Why and evidence

The owner requested the deferred reproducibility rebuild. A second, fully independent workspace (<build-root>/platform-repro: own repo init/repo sync, own CCACHE_DIR, nothing shared with platform-primary) was built on the same remote build server from the same verified manifest tag 2026071500 (signature re-verified, commit 8903f9d28abc61da0928d32b653ba4f9a88afd8c) and the same target sdk_phone64_x86_64-cp2a-userdebug. SHA-256 of every target/product/emu64x/*.img was compared against the primary build's recorded table in docs/reviews/phase-1-emulator-baseline-review.md, verified with a scripted join.

3Consequences

18 of 25 images differ; 7 match exactly (full table in the review record). Per the Phase 1 plan's own Task 5 Step 3 rule, a difference blocks baseline acceptance until an evidence-backed cause is documented and resolved — this has not been root-caused.

The failure pattern (fixed-content/empty-container images match; every image built from a live filesystem or containing vbmeta/verity metadata differs) is consistent with ordinary unpinned build non-determinism (image timestamps, UUIDs, verity salts) rather than tampering, but that is an unverified hypothesis, not a confirmed cause.

docs/reviews/phase-1-emulator-baseline-review.md's exit decision is downgraded from Accepted baseline (Task 5 waived per ADR-018) to Rejected baseline (Task 5 executed, reproducibility failed, root cause unknown).

This reopens the single-build-provenance caveat already carried by ADR-019 (boot-identity patches) and the ARM64 lynx bring-up work in progress on physical hardware; neither is retroactively invalidated by this entry, but neither should be treated as resting on confirmed-reproducible provenance until root-caused.

4Review when

A root cause is established (e.g. unpinned image timestamps/UUIDs/verity salts confirmed and fixed) and a follow-up comparison matches, or the owner otherwise reviews and accepts the difference with a documented reason; or evidence of actual build-environment compromise surfaces, per ADR-018's own trigger.

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