- Decision
- ADR-256
- Date
- 2026-11-18
- Status
- AcceptedAccepted (owner, 2026-11-18, in the order of the six points of the message that asked for it and the answers to three questions: pages
DevicesandGet involved, the intention onStatusand the FAQ, and the ownership line without a third party's name). The wording, the page text, the menu design and the two new prints (a pair of phones and a branch) are the agent's calls; the owner may overrule each. - Mentions
- ADR-171, ADR-248, ADR-251
- Mentioned by
- ADR-257
1Decision
Change the public site oblivios.org after the owner's read of 2026-11-18, and record the owner's intention to publish Pixel 10a images. (1) The mobile menu, a bordered Menu button with a boxed list that overlapped the page, is replaced by a contents sheet under the header: the pages as large serif lines with dotted leaders and numbers, the four repositories, and the ownership line; it needs no script.
(2) Two pages are added, Devices and Get involved, which makes ten pages and the 404 page; of four candidates (Devices, one page per part, a Limits page, Get involved) the owner chose these two. (3) The four GitHub repositories are linked from the menu, a Source column of the footer, Get involved and Verify it.
(4) One line says on every page that only oblivios.org, oblivios.dev and the four repositories on github.com/Beau4201 are the owner's and that any other site, app, account or package that uses the name is not to be trusted; it is in the footer and the menu, and as a section on Security and Trademark and an FAQ answer. It names no other domain (the owner chose that over naming oblivios.com).
(5) The site named only the Pixel 7a (lynx); it now names both phones as the records state them: the Pixel 10a (stallion) is the owner's daily phone, the Pixel 7a the development phone, and no device is supported. (6) The owner intends to publish images for the Pixel 10a when real interest in the project shows.
This is an intention and not a change of stage: ADR-171 and ADR-248 stand, there is no date, and the site says on Devices, Status and the FAQ that nothing is promised and that the five gates of a public beta and the open rows of the Pixel 10a bring-up record come first.
2Why and evidence
The owner called the old menu extremely unprofessional, ill-fitting and ugly, and a flagged element is replaced by a better design (ADR-251), so the menu is redrawn in the direction Printed record, as the contents page of a book. The Devices page follows the bring-up record of the support policy and the status records, which say that stallion is the relocked daily phone and lynx the development phone.
The images sentence is the owner's words made conditional and dated, because the public launch design lists images as a non-goal of this stage and an anti-goal is a claim that the records do not support. Rejected: always-visible navigation instead of a menu, naming oblivios.com, a date or a count of interested people on the site, a mailing list or a form to register interest (the design excludes both).
3Consequences
Done and read on 2026-11-18: the build of eleven pages and its output check (309 internal links, css 20.0 KB); no horizontal overflow on any of the eleven pages at 320, 390, 798, 861, 1024 and 1920 px; the open menu rendered at 390 px in the light and the dark scheme; Devices at 390 and 1280 px and Get involved at 1280 px.
Not done: the owner's read of the menu and the new pages in the browser pane (the pane was hidden, so the menu was not clicked there: its open state was rendered from a copy with the open attribute, and the close-by-key behaviour, which a menu without script lacks, is not tested); the claim review of the new sentences (C-1), which the agent drafted from the status records; the other two candidates, one page per part and a Limits page; the four repositories are private until the flip (R-7), so the links lead nowhere before it, and the site is to go live after it.
4Review when
The owner rejects the menu or a page; a sentence of Devices is found unsupported by the records; the intention to publish images changes or lapses; an image is built for the public, which needs its own decision and the gates of ADR-171.
Read from docs/governance/decision-log.md, entry ADR-256.