ObliviOS Developer portal Project site

Home / Decisions / ADR-257

Correct ADR-256 after the owner's second read of the same day.

Accepted, recorded 18 November 2026.

Decision
ADR-257
Date
2026-11-18
Status
AcceptedAccepted (owner, 2026-11-18: the menu is far too much and must look like the rest of the site; Compartments is on the Pixel 10a; SIM, camera, calls and the rest work; \"real data\" must be on the site and the wrong data replaced at once; issues are welcome; a contact page without encryption).
Mentions
ADR-256
Mentioned by
ADR-258, ADR-260

1Decision

Correct ADR-256 after the owner's second read of the same day. (1) The mobile menu is only an icon button that opens the page links as a plain list, in the style of the rest of the site: no word Menu before it, no numbers, dotted leaders, source list or ownership text in it (they stay in the footer).

(2) Every statement about what runs or works on a phone is taken off the site: the page Devices says only that the Pixel 10a is the owner's daily phone, the Pixel 7a his development phone, that no device is supported, what supported means and the image intention; the homepage cards no longer name a phone; the lines about the installed parts, the open bring-up rows, the update path and the 7a's upstream support date are gone.

(3) The page Get involved is replaced by Contact: an issue on GitHub is the way the owner likes best, for a bug, a question or a criticism of his code, and he takes the responsibility for it; for anything private an email to the address of SECURITY.md, in plain text, with encryption optional; a vulnerability is better sent by email, and the page still points to the key.

(4) The decision that the owner's phones are described only by the owner is added to the rules of the site: a state of a device is written on the site only from the owner's own statement or from a record that is newer than the build under discussion.

2Why and evidence

The records that ADR-256 read are older than the phone. docs/devices/support-policy.md still says for the Pixel 10a \"Mobile core, hardware, accessibility: not run, no SIM was inserted\", and docs/product/status-stallion-and-memory.md and docs/product/status.md still say that Compartments goes to stallion when its remaining lynx rows are shown; the owner states that Compartments is on the Pixel 10a and that calls, SIM and camera work.

The agent copied the old state onto the site as a present fact, which is the failure the public launch design names as an anti-goal (a site that claims more or other than the records support, here less than is true). A wrong sentence on a public site is worse than a missing one, so the sentences are removed first and replaced when the owner states the facts.

Rejected: keeping the old rows with a date, and asking the owner to confirm each row before removing it.

3Consequences

Done and read on 2026-11-18: the build of eleven pages and its check (307 internal links, css 18.9 KB); the menu rendered open and closed at 390 px, light and dark; no text about the state of a phone remains in site/ except the two phones' roles.

Not done: the owner's statement of what runs and works on each phone, which is the basis of the page that is missing; the correction of the three stale records; the same check of every other sentence of the site against the owner's knowledge (C-1): the line None is met of the five gates on Status, the descriptions of the nine parts and the FAQ answers come from records of October and November and are not re-confirmed; the page of one part per phone or part is not written; the issue settings of the four repositories (issues on) are the owner's action at the flip (R-3, O-7), and SECURITY.md, which still says not to open a public issue for a vulnerability, is unchanged.

4Review when

The owner states the facts of the phones; a sentence of the site is found to state an old fact; the owner changes the rule for vulnerabilities in public issues.

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