- Decision
- ADR-240
- Date
- 2026-11-16
- Status
- AcceptedAccepted (owner, 2026-11-16). Done in the sources:
oblivios-platform,oblivios-services,oblivios-manifestand this repository, committed locally. Not done: landing the regenerated patches on the build-servervendor/adevtoolanddevice/generic/goldfishtrees withgit am, the pin update ofadevtool-version-check.mk, removal ofvendor/oblivios/guardianfrom the build-server tree, the next image, and the read on the phone. - Mentions
- ADR-011, ADR-013, ADR-015, ADR-016, ADR-032, ADR-033, ADR-034, ADR-035, ADR-036, ADR-044, ADR-051, ADR-057, ADR-070
- Mentioned by
- ADR-011, ADR-013, ADR-015, ADR-016, ADR-032, ADR-033, ADR-034, ADR-035, ADR-036, ADR-044, ADR-051, ADR-057, ADR-070, ADR-242, ADR-246
1Decision
Remove Guardian from ObliviOS completely, in the sources and on the phone. (1) Sources: the guardian package of oblivios-platform (app, core jar, test fixture, emulator and vendor patches), the three Guardian modules of oblivios-services, the Guardian documents and their tests are removed.
The nine vendor/adevtool patches whose context carried the Guardian block in device-common.mk (AirPods 0001, Data Map 0001 and 0002, zram 0001 and 0003, decoy-stop-on-switch 0001 and 0002, Passwords 0001, Compartments 0001) are regenerated without it. The git history keeps Guardian and is not rewritten. (2) Device: the next software update leaves no Guardian on the phone: no GuardianApp, no privapp allowlist, no location fixture.
check-required-packages.sh no longer requires them and refuses all three in every build type, so a tree that still builds Guardian fails the gate. (3) It supersedes ADR-013, ADR-015, ADR-016, ADR-032, ADR-033, ADR-034, ADR-035, ADR-036, ADR-044, ADR-051, ADR-057 and ADR-070, and ADR-011 in part.
Closed records (dated specs, plans, reviews, research, the one-shot rename scripts and their tests, the upstream provenance records of oblivios-manifest) keep their text; the decision log keeps the rows above as history.
2Why and evidence
The owner decided that Guardian leaves the product. The patch stack is the reason the removal is not a directory delete: the AirPods patch carries the Guardian lines as context, so git am of the old series without Guardian's patch fails. The chain of twelve patches was rebuilt offline: the old landed order applies, and the new chain ends in the old device-common.mk minus the Guardian block (diff read 2026-11-16). [assumption] Whether Android deletes the data of a system app that disappears in an update is not verified; the device read decides.
3Consequences
The regenerated patches carry no index lines, because the blobs of the new chain are unknown until it is landed; the records of each package say so. Features that used Guardian's remediations are gone, and the product direction that ADR-011 and the product compass built on Guardian's loop is open for the owner to restate. The threat model and the capability boundaries must lose the Guardian rows.
4Review when
The device read after the next flash finds GuardianApp or its data; git am of the regenerated chain on the build server does not give the tree of the offline chain; a Guardian feature is wanted again.
Read from docs/governance/decision-log.md, entry ADR-240.