ObliviOS Developer portal Project site

Home / Decisions / ADR-273

Close what ADR-272 left open and keep the publication of both sites to one command with a live check.

Accepted, recorded 19 November 2026.

Decision
ADR-273
Date
2026-11-19
Status
AcceptedAccepted (owner, 2026-11-19: both sites must update fully automatically and always be current; analytics works on oblivios.dev; Google and Bing are set up). The command, the 480 s wait and the rule that a push stays asked are the agent's calls; the owner may overrule each.
Mentions
ADR-272

Shown as written

This entry has 8 columns where the log has seven, because a cell holds the separator of the table or a column is missing. The cells follow in their order, under the label of their place.

1Decision

Close what ADR-272 left open and keep the publication of both sites to one command with a live check. (1) The owner turned on Analytics in the Vercel project of oblivios.dev and says that it counts; the owner set up Google Search Console and Bing Webmaster Tools for oblivios.org and oblivios.dev and submitted both sitemaps (all on 2026-11-19).

(2) The footer of the portal said that it counts nothing, which ADR-272 made false; it now says that page views are counted without cookies.

(3) tools/docs/sync-site.py is the one command from the private repository to the live sites: it requires the five repositories clean, builds the snapshot and the SBOM and checks both, builds both sites as Vercel does (VERCEL=1), commits in oblivios-docs, pushes only with --push, and then compares every file of both live sites with the build, the headers of vercel.json and the 404 of a missing page, for up to 480 s, and exits non-zero on any difference or a domain that does not resolve; when the workstation's resolver has no answer it asks a public one.

(4) The owner's wish is that both sites are always up to date without a manual step, which the owner called very important; every push still waits for the owner's yes, as in the owner's rule for git, until the owner says that a push may be automatic.

2Why and evidence

The site is the project's public face and a push that did not reach it, or reached it wrong, is found by a visitor first. A byte comparison of every file with the build proves that the site equals the snapshot, which a reading of one page does not, and it needs no account of the host. A push to a public repository cannot be taken back, so the step that the owner's rule reserves stays a flag.

Rejected: a git hook that pushes (it publishes without a yes), a GitHub workflow in oblivios-docs (it cannot read the private repository and the three code repositories that the SBOM describes, and the snapshot is audited with gitleaks over the private tree), a timer that regenerates and pushes unattended (the same objection), reading the live site by eye only (it cannot see a file that differs by one line).

3Further text

[measured: sync-site.py] the live check was identical for 33 files of oblivios.org and 340 of oblivios.dev after the push of the portal snapshot, and for both after the push of ADR-272; a regeneration of an unchanged state makes no commit; the first check of oblivios.dev failed on the router's DNS cache while the site was live, which the fallback to a public resolver removed.

The analytics route of the portal answers like that of oblivios.org (script 200 and identical, 400 on an invalid body). Not measured: a real page view in a browser, what Search Console and Bing show (nothing is indexed yet), and whether the counter fires on every page. The footer change of (2) is built and committed and is live only after the next push. The agent found the false footer at the close of the session and not when ADR-272 was written.

4Further text

A command can fail halfway, after the commit and before the push, and leave oblivios-docs one commit ahead until the next run; the live check proves equality with the build and not that the content is right; the sites stay stale between a change in this repository and the owner's yes for a push.

5Last cell

The owner allows an automatic push; the live check fails after a push; Vercel changes how a project builds or serves; a site is added or moves to another host.

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