ObliviOS Developer portal Project site

Home / Decisions / ADR-248

Amend the source-only stage (ADR-171, ADR-241) with the owner decisions of 2026-11-17.

Accepted, recorded 17 November 2026.

Decision
ADR-248
Date
2026-11-17
Status
AcceptedAccepted (owner, 2026-11-17: the design read and approved; at most two domains, a framework, Vercel, quiet publication; the key to be replaced because its private half is believed lost). Done: the design, committed; the new key (fingerprint 7F16 E467 18B2 3814 59B8 E694 4F84 B523 8F58 7493, made by the owner on 2026-11-17) replaced the old one in the five SECURITY.md and the five key files, committed locally in oblivios-manifest, oblivios-platform, oblivios-services and this repository, and the SBOM and the snapshot were rebuilt on those commits; the owner decrypted a message that was encrypted to the new key (read 2026-11-17); both SBOM documents validate against the CycloneDX 1.6 and SPDX 2.3 schemas (ajv 8.17.1; a copy with a wrong specVersion fails); oblivios-manifest d511728, oblivios-platform 27f358a and oblivios-services c83b5c2 are pushed (owner, 2026-11-17: default branches only, the remote of each lists that one head) and oblivios-docs follows with the snapshot of this entry. Also done: the owner registered oblivios.org and oblivios.dev on 2026-11-17 (RDAP: registered 14:18 and 14:19 UTC, transfer lock set, the nameservers of the registrar, no DNS records, so dig answers NXDOMAIN), and the logo variants are made (ADR-249). Not done: the DNS records, the Vercel account, the owner's approval of the logo variants, the mockups, the sites, the extension of the SBOM build to site/, every row of the checklist, the visibility, the announcement.
Mentions
ADR-171, ADR-227, ADR-241, ADR-243, ADR-245, ADR-249
Mentioned by
ADR-171, ADR-256, ADR-262

1Decision

Amend the source-only stage (ADR-171, ADR-241) with the owner decisions of 2026-11-17, as designed in 2026-11-17-public-launch-design.md. (1) Order: the four repositories and the sites go public without an announcement, a week of checks follows, and the announcement needs the owner's word (approach A of the design).

(2) Two sites replace the single site of ADR-171: oblivios.org (the project site) and oblivios.dev (a portal for reviewers and developers: the searchable decision log, the threat model, the SBOM and component quickstarts), built with Astro as static output and hosted on Vercel, two projects of one repository. The code is site/, authored here and published in oblivios-docs by tools/docs/build-public-docs.py.

(3) The deferral of the site until the logo is final (ADR-241 (1)) ends: the logo is the cloud with a server (branding/logo-cloud, owner, 2026-11-17); its variants (plain cut, favicons, wordmark, dark variant) are made and approved before a page uses them, and ADR-249 supersedes ADR-227. (4) The audience of this stage is reviewers and developers who reuse single components; no image is offered, because an image costs about 8 hours per update.

(5) The repositories stay under the owner's account and the history is accepted as it is (ADR-243 to ADR-245): the old commits stay reachable by id and the host of the private OTA server stays in older commits of oblivios-platform. (6) The disclosure key is rotated: a new key with the user id ObliviOS Security replaces the key of ADR-171 (design row O-5).

(7) The checklist of the design (60 rows in nine groups) is the gate list of the stage; a row is closed only with its evidence.

2Why and evidence

The owner wants other people to use ObliviOS. Reviewers and developers can start from the source today, and a site that makes the project findable and checkable is the lever; a portal makes the decision log (about 660 KB, one line per entry) readable. Astro with static output ships no client runtime by default, which fits a site without tracking; Vercel is the owner's choice. Rejected: announcing on the day of the flip (a mistake is then found when most people look), a fifth repository for the site (one commit pins the site and the documents it shows), one site with a redirect (the owner wants both domains used), a GitHub organisation (owner decision).

3Consequences

Vercel is a third party in the path and sees visitor IP addresses; the privacy page says so. The npm packages of the framework join the supply chain, so the SBOM build must cover site/. Two sites double the claim review. Both domains looked free by a DNS and RDAP read of 2026-11-17 and the owner registered them the same day; oblivios.com belongs to a person. Whether the free Vercel plan allows this use is not verified.

The legal notice (B-4), the export position for cryptographic source (B-5), a trademark filing (B-7), issues, pull requests and a code of conduct (O-7) are the owner's decisions and are open. The keyring still lists the old secret key; whether its passphrase is known is not read.

4Review when

A registrar reports a domain as taken; the terms of Vercel exclude the use; a package of site/ is compromised or yanked; the quiet week finds a mistake that the checklist should have caught; the owner offers an image.

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