ObliviOS Developer portal Project site

Home / Decisions / ADR-225

Carry out phases 1 to 3 of ADR-224 on 2026-11-10.

Accepted, recorded 10 November 2026.

Decision
ADR-225
Date
2026-11-10
Status
AcceptedAccepted (owner, 2026-11-10). Done and read back on 2026-11-10: the five repositories renamed and committed locally (tools/rename verify finds 0 problems in each); the workstation directories are oblivios-*; the live AOSP tree of the build server is on the twin branches oblivios-2026110200 with vendor/oblivios; <build-root> on the build server and the signing host; 38 scripts of the build server and four of the signing host replaced by the renamed versions; the vendored jars and libvault_core.so rebuilt. Not done: GitHub names, a push of oblivios-services, oblivios-manifest and oblivios-docs (oblivios-foundation and oblivios-platform were pushed by the owner after their rename commits), the certificate renewal, the first build, an image, a flash, and the cause of the frameworks/base package-check failure (it predates the rename).
Mentions
ADR-223, ADR-224
Mentioned by
ADR-226

1Decision

Carry out phases 1 to 3 of ADR-224 on 2026-11-10, with the owner's answers to the open points of section 9 of 2026-11-10-oblivios-rename-design.md: (1) the decoy user type value follows the mapping (org.oblivios.usertype.full.DECOY); (2) masklist-easylist of the platform and services repositories is merged first (fast-forward into main and master) and the rename is applied on top; (3) the vault format labels of vault-core follow the mapping: the HKDF info and the AEAD associated data of the passphrase key, the wrapped vault key, the vault and the export, and the export format name change from freeholdos-passwords/... to oblivios-passwords/...; (4) the order against the certificate renewal is not decided: the OTA directory moved first and the renewal stays due on 2026-11-22.

Updates ADR-224: its status line "Not started" and its open points are superseded by this entry.

2Why and evidence

The owner took the full mapping over named exceptions for the decoy type and the vault labels: a grep for the old name stays a complete check and the project carries one name.

Rejected, with the reason of the owner's answers: keeping org.freeholdos.usertype.full.DECOY and the freeholdos-passwords/* labels as named exceptions (old decoy users and old vaults and exports would stay readable; the cost is one old name in a few strings); renaming from master or on the open branch (conflicts with ADR-223 when it lands).

[measured 2026-11-10] vault-core 169 tests pass after the known-answer value of the passphrase key changed; a scratch copy with the old label reproduces the old value, so the label alone differs. Two builds of libvault_core.so give 2f5d7f2f..., and of the two jars fcabf19f... and 8658fb35....

The OTA server answers 200 for lynx-alpha and stallion-stable from two hosts. 13 of 14 projects pass the package check against the twin branches; frameworks/base fails the same way before the rename.

3Consequences

A vault file or an export file written under the old labels does not open with the new core, and the old export cannot be imported. [assumption] The Passwords app of the new package id does not see the data of org.freeholdos.passwords on an upgraded device, and the new core rejects an export made under the old labels, so a vault cannot be carried over to the first ObliviOS image. Existing decoy users are deleted at the first boot of the first ObliviOS image (R3 of the previous rename). Rollback of the live tree: switch-live-tree-oblivios.sh rollback; the backups are *.pre-oblivios files and redeploy-backup-20261110 on the hosts.

4Review when

The owner needs old exports to open (add a read path for the old labels to vault-core before the first ObliviOS image); a conflicting operating system or a counsel objection (ADR-224); the cause of the frameworks/base failure turns out to be a rename defect.

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