The faces show a level's SOWs (adr-014), their receipts, and a SOW's view whose aside names the ADRs it cites as text (sow-the-faces-know-who-reads-and-prepare-their-acts-2). The principal asked, 2026-10-08, that the viewer also show ADRs and biops — part of a project's specs — and dossiers, with a main menu per project: Dossiers, SOWs, ADRs, Biops, History; that every item open in a tab of its own; and that items be articulated and referenced in plain view: «that an ADR, a SOW, a biop can be articulated, referenced and in view changes everything, in the clearest spirit of transparency».
What exists, measured 2026-10-08: - ADRs are ontoref's: `ontoref adr list --fmt json` (id, title, status, date, scope) and `ontoref adr show <id> --fmt json` (context, decision, rationale, consequences, alternatives, constraints, tensions_engaged, related_adrs, amendments), answered from a member through the constellation (code/ asks and the spine's .ontoref/adrs/ answers). - Biops are ontoref's: `ontoref biop show <id> --fmt json`, in two rungs — the project's .ontoref/biop/ overlay and the protocol's reflection/biop/, inherited. - Dossiers are SpecDossier's own format, written where the project's `.governance/dossiers.ncl` declares (adr-002), a path relative to the project's root — outside the level. adr-003 holds that the service never reads the project for a round and keeps no address of it; adr-002 left open «how a deployed service learns which projects to read». - The level's history is in its files: `ledger/<id>.jsonl` (Landed, Reviewed…), `ledger/archive.jsonl`, `ledger/<id>.notices.jsonl`, `receipts/`. - The service already asks ontoref, from a level's root and without ONTOREF_PROJECT_ROOT, for what it publishes — the registry, status-sow, describe project, qa show — and holds those readings for a reader's registry_ttl (held.rs).
EACH PROJECT HAS ITS PLACES. For each level a service declares, the main menu leads to its Dossiers, SOWs, ADRs, Biops and History; each lists its items with filters as the SOWs' list does, and each item has its own page and a stable address — `/p/<project>/sows/<id>` (the SOW view kept at its present address too), `/p/<project>/adrs/<id>`, `/p/<project>/biops/<id>`, `/p/<project>/dossiers/<id>`, `/p/<project>/history`. A link to an item opens in a tab of its own.
ADRS AND BIOPS ARE SHOWN AS ONTOREF PUBLISHES THEM. The service asks `ontoref adr list|show --fmt json` and `ontoref biop show --fmt json` from the level's root, as it asks for the registry, and shows what is answered — nothing derived, nothing judged — with when it was read when the reading is held. It reads no file of `.ontoref/`. Where ontoref gives no answer the place says so; a project without ontoref has no ADRs or biops to show.
DOSSIERS ARE READ WHERE THE LEVEL DECLARES THEM, AND ONLY READ. Where a level holds `.governance/dossiers.ncl`, the service reads the dossiers in the directory it declares — read only, never written — and shows each with the stage SpecDossier derives from the files, as `specdossier dossier` does. It reads nothing else of the project.
ITEMS ARE REFERENCED IN PLAIN VIEW. Wherever an item names another — a SOW the ADRs it cites, an ADR its related ADRs and amendments, a dossier the SOWs it governs, a SOW its predecessor, successors and receipt — the name is a link to that item's page; an item names where it is referenced from when that is read from what is shown (an ADR the SOWs of the level that cite it). What ontoref later declares between items (an edge of dependency or of what it unblocks) is shown the same way, read and never derived (adr-008).
THE HISTORY IS THE LEVEL'S FILES, AS WRITTEN. `/p/<project>/history` lists, newest first, the events of the level's ledgers and its receipts, each linking to its item, filtered by kind and by item.
WHAT THIS AMENDS: adr-003's «the service keeps no address of the project» — a service may read, never write, the dossiers its level's declaration names; a round still reads nothing of the project. It settles adr-002's open question for reading: a deployed service learns a project's dossiers from the level it declares.
WHAT THIS DOES NOT DECIDE: the review of ADRs and biops (adr-019 applies once they are shown); a dashboard across projects; ontoref's declared edges between items, which are ontoref's.
ADRs and biops are shown only as `ontoref adr list|show --fmt json` and `ontoref biop show --fmt json` answer them; no source of specdossierd reads a file under .ontoref/
A service reads dossiers only in the directory its level's .governance/dossiers.ncl declares, and writes none
Every SOW, ADR, biop and dossier shown has a stable address under /p/<project>/, and every name of another item on its page links there
Read .ontoref/adrs/*.ncl and the biop files directly
Rejected: Binds SpecDossier to ontoref's file layout and evaluates its formats itself; ontoref publishes them, and SpecDossier reads what is published.
Keep the viewer to SOWs, ADRs named as text
Rejected: The principal asked for the specs to be read and referenced in view; text names leave the navigation to the reader.
The service keeps each project's dossier addresses
Rejected: Makes the service a register of projects (adr-002); the level already declares them.