ObliviOS Developer portal Project site

Home / Decisions / ADR-253

Record the owner answers of 2026-11-17 to the open points of ADR-251 and the calls made while building oblivios.org.

Accepted, recorded 17 November 2026.

Decision
ADR-253
Date
2026-11-17
Status
AcceptedAccepted (owner, 2026-11-17) for (1) to (4); the calls are the agent's and the owner may overrule each.
Mentions
ADR-171, ADR-242, ADR-249, ADR-251, ADR-252
Mentioned by
ADR-252, ADR-254, ADR-255

1Decision

Record the owner answers of 2026-11-17 to the open points of ADR-251 and the calls made while building oblivios.org (ADR-252).

Owner answers: (1) the light lockup in the header and the dark lockup in the footer are approved as shown on the mockup pages (ADR-249, lockups); (2) the sentence under the home headline is descriptive and does not repeat the thesis of ADR-242: `ObliviOS is a privacy-focused Android build based on GrapheneOS, published as source: patches, decisions, a threat model and a bill of materials you can check.

There is no image, no update and no supported device yet. (the lede of What it does was not asked about and stays as in the mockup); (3) the contact address stays the one of SECURITY.md (O-6; the test message stays open) and the sample security.txt is real: Encryption is https://oblivios.org/security-contact.asc, served from the repository file, and Expires is a fixed date one year out in site/org/src/lib/securitytxt.mjs, which fails the build when fewer than 60 days remain or when it is more than a year ahead; (4) fonts: Roboto Flex (SIL OFL 1.1) may be downloaded for self-hosting, and because it has no serif and the accepted headings are serif, Noto Serif (SIL OFL 1.1) too, both through the npm packages @fontsource-variable/roboto-flex and @fontsource-variable/noto-serif` 5.3.0, Latin files only; code blocks use the system monospace stack.

Calls of the agent, not yet seen by the owner on a served page: the application is site/org and the shared package site/shared with one lockfile in site/ (npm workspaces); Astro is pinned to 5.18.2 because Astro 6 and 7 need Node 22 or later and the workstation has Node 20.19.2 (site/.nvmrc, engines 20.x); output is one file per page with Vercel cleanUrls; the pages use no inline style, no data: URI and no script, so that Content-Security-Policy: default-src 'self' holds; the dark scheme follows the system and has no toggle (a toggle needs script and storage); the header button and the footer entry for the developer portal are hidden until oblivios.dev exists, because the link would be dead (portal in site/org/src/lib/site.mjs); the Privacy page no longer claims scripts and a search index (this site has neither) and says that it runs no script; the Trademark page says that the site serves Roboto Flex and Noto Serif and links their licence texts at /licenses.txt; the stamp on the home page has a paper background (axe measured 2.22 and 1.84 against the plate); the date on the pages is the newest entry of the decision log; the sources of each page are written to site/org/.build/claims/ at build time and never shown.

2Why and evidence

The four questions were the open points of ADR-251 that only the owner can answer. The descriptive sentence is every clause of the README and the stage line of ADR-171, with nothing from ADR-242, whose wording the owner had not read. Roboto Flex alone would have left the accepted serif headings to whatever serif a visitor has.

Rejected: the first sentence with the control thesis (unreviewed agent wording), security@oblivios.org now (no DNS zone, so a dead address), Expires as the build date plus a year (two builds of one commit would differ), the plain cloud cut instead of the lockups, Roboto Serif (changes the accepted headings), a system serif only (differs per device), Astro 7 (needs Node 22.23), a developer-portal link to a host with no site.

3Consequences

site/ is in this repository and builds nine pages. Done and read on 2026-11-17 (evidence in site-engineering-notes.md): the build and its own output check, axe with no violation in both schemes at 390, 798 and 1440 px after three fixes, contrast of 418 text nodes per scheme from 5.22.

Not done: the extension of tools/sbom/build-sbom.py (W-7) and tools/docs/build-public-docs.py (W-8) to site/, so the SBOM and the snapshot do not cover site/ yet; the readings at 390, 798 and 1920 px of every page by eye and the flag round with the owner; layout shift, the network capture of every page in a clean browser profile and the open menu at 390 px; the Vercel project and its settings (the owner's account, W-3), where the empty Permissions-Policy value is unverified; the claim review (C-1); the NOTICE of site/ (B-6); oblivios.dev.

The Privacy page states Vercel settings that are plans until the owner sets them. Node 20 is the version the workstation has and the lockfile resolves a package (undici 8, only for an Astro feature the site does not use) that needs Node 22: moving the pin needs a download of Node and a new run.

4Review when

The owner rejects the descriptive sentence, the fonts or a call of the agent; the pin of Node 20 is no longer accepted by Vercel; a sentence of a page is found unsupported in the claim review; the SBOM extension cannot express site/.

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