Read the record.
Every decision ObliviOS has made, and the bill of materials of what it is built from, read from the same repository as the code, so a page cannot drift from the record.
This site writes nothing of its own. It reads the repository and shows what is there.
The decision log, the threat model, the engineering notes and the bill of materials are read from docs/ and sbom/ when the site is built, and each decision, each document and each page of the bill of materials names the file it was read from. A new decision in the repository becomes a new page here, and nobody has to edit the site for it.
Start where your question is
Each page is built from a file of the repository and says which one.
Decisions
Every product and security decision, with its status, what it mentions and when to look at it again.
Components
The libraries, upstream projects and tools the four repositories rest on, each with its licence and its advisories.
Advisories
What OSV lists against the locked versions, and the assessment of each one.
Files and patches
What the files of the repositories are, and which parts of the upstream baseline the patches change.
Data
The data files the code reads and the public sources they were made from, each with its licence.
Verify
The commands that rebuild the SBOM, and how each prebuilt binary was made.
Threat model
Who could attack ObliviOS and along which path, and what each service may and may not do.
Engineering notes
What was learned building each area: the exact command, the error, the cause and the way that works.
Quickstarts
What each reusable component is and is not, and the commands that build and test it.
From the log
The newest entries, with the trigger that would reopen each one.
- ADR-2712026-11-19Accepted
A disclosure of the portal (the advisories of a library, the filter panel of the lists) moves on opening as well as on closing.
Review when: The owner finds the time or the curve wrong; a browser that the owner uses lacks ::details-content (a script would then be weighed against the one-script rule); a new disclosure is added (it takes the same two rules).
- ADR-2702026-11-19Accepted
Split the long documents of the portal into parts and pages, and settle the header, the tabs, the contents column and the disclosures after the owner read the build…
Review when: Point (5) is replaced by ADR-271; a part or a page of cases becomes too long or too short for its size; a published document gets a section whose id is not in a part of its entry (the part is then missing from the site and the check of…
- ADR-2692026-11-19Accepted
Add the threat model, the capability boundaries, the engineering notes and the quickstarts of three components to oblivios.dev.
Review when: A command or a fact in a README of oblivios-services that a quickstart restates changes; the owner rejects a page or its layout; a published document uses a Markdown construct the reader does not know (the build fails and names the…
- ADR-2682026-11-19Accepted
Build the developer portal oblivios.dev as the Astro application site/dev, after the owner approved its mockups on 2026-11-19.
Review when: The owner rejects a page, a print, the proof blue or the search ranking; the index outgrows its budget or a phone cannot fetch it; a sentence of the portal is found unsupported in the claim review; the portal needs a second script; a…
All of it lives in four repositories.
The portal, the project site and the code are built from the same source, on the same account. Read it where it is written.