ObliviOS Developer portal Project site

Home / Decisions / ADR-241

Amend the source-only publication stage (ADR-171) with the owner decisions of 2026-11-16.

Accepted, recorded 16 November 2026.

Decision
ADR-241
Date
2026-11-16
Status
AcceptedAccepted (owner, 2026-11-16). gitleaks detect over all refs found nothing in oblivios-docs, oblivios-manifest, oblivios-services and oblivios-platform (read 2026-11-16, the tool version was not read). In this private repository it found one generic-api-key in the plan of 2026-09-28 (line 506), not published; triaged on 2026-11-16: the value is the SHA-1 fingerprint of an AVB public key, not a secret. oblivios-docs and oblivios-services were pushed. Open: the GitHub token of the workstation is invalid, so the visibility of the five repositories was not read; the trademark registers; an SBOM; the owner's read of the final set; the aggregated licence text of the Rust crates before an image carries libvault_core.so or exitd.
Mentions
ADR-171, ADR-243
Mentioned by
ADR-171, ADR-243, ADR-244, ADR-245, ADR-248

1Decision

Amend the source-only publication stage (ADR-171) with the owner decisions of 2026-11-16. (1) The site is deferred until the logo is final; the stage is the source repositories and oblivios-docs. (2) Every patch of the published packages carries one author address, the project address of the NOTICE files; two connectivity patches (privacy/exit 0001, privacy/linkability 0002) were regenerated for it.

The history of oblivios-platform was rewritten for it afterwards (ADR-243). (3) The internal build-host names in the history of oblivios-platform (build@<name>.local in patch headers, one .lan host name, one home path in oblivios-manifest) are accepted. (4) The company logo files stay in oblivios-platform and its history: they are CC0 files used to name a company, and NOTICE gives the removal route.

(5) The prebuilt binaries stay, each with its source commit, toolchain and SHA-256; NOTICE lists them, the data files and their licences. (6) References to unpublished documents in the public repositories are reworded. (7) Name research: see the consequences.

2Why and evidence

A first stage without a site avoids a page that carries a logo that is not final. The history stays because the owner decided against a rewrite, and the remaining strings are internal host labels, not credentials.

3Consequences

Name research of 2026-11-16 (web search, GitHub search, DNS): no operating system or product called ObliviOS was found. A GitHub user Oblivios (a person, since 2020, music, OSINT and developer tools) and oblivios.com (a personal index of music, writing and projects) exist, so the GitHub organisation name and that domain are taken; the repositories live under the owner's user. A company called Oblivious (privacy software, Ireland) uses a similar word. The trademark registers (EUIPO, WIPO, USPTO) were not searched by tool; the owner reads the name as acceptable.

4Review when

The owner finds a conflicting mark in the registers; a counsel or an AI review objects to the name.

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