Chemical Safety Assistant

Appearance

ADR-0070: Chrome overlaps Conversational Content rather than being part of it, and the design extract is cited by locator ​

Status: Accepted — amends ADR-0064 and ADR-0066 Date: 2026-09-20

Decisions ​

D-146 Chrome and Conversational Content overlap; neither contains the other ​

Where chrome is something the app says — a field label, a route name, the emergency bar's wording — it is also Conversational Content. Where it is a colour, or a term matched against but never shown, it is chrome and is not Conversational Content, because that term is defined as everything the app says.

Chrome may never be model-generated, whatever the rest of Conversational Content may be. That property is what D-139 needed and it stands on its own; it never required a containment relation.

D-139's supporting sentence — "Chrome is the fixed part of Conversational Content" — is withdrawn. D-139's ruling is untouched: the First Run Notice's Escalation control is app-authored chrome, it acknowledges First Run and routes to the Escalation surface, and it renders no Curated Escalation text.

D-147 The design extract is cited by a locator, so the claims made about it can be checked ​

ADR-0066 makes four claims about what the extract contains. Each is checkable only against the artifact, so the artifact is named here:

  • Project: "Chem Assistant Design Extract", a claude.ai design project, id 3c10dc05-a3d7-499f-900f-1f86b1b403e1, owner Nonthakorn Inthong.
  • File: Chem Assistant App Flow.dc.html, read 2026-09-20.
  • Provenance the project states about itself: its github.md records a sync from redcats002/chem-assistant-frontend, branch main, commit 2981bde2cba3, dated 2026-09-15.

A claim about the extract cites the file it is read from, the way a claim traced to the source PDF cites a page.

Context ​

Both decisions come from a cross-model grill on ADR-0064..0066, run 2026-09-20 on Claude Fable 5.1 and on Sonnet, each cold and neither a fork of the session that wrote those ADRs. Three earlier rounds had been forks and found neither defect.

On D-146. CONTEXT.md defines Conversational Content as "Everything the app says that is not Safety-Critical Content". The Chrome entry written in the same session lists, among its own examples, "a neutral surface colour" and "the terms Routing matches against without ever showing them". Both reviewers reached the same conclusion independently: a colour is not something the app says, and RoutingFloor.ts and EscalationTrigger.ts both document their term lists as never displayed. The containment claim was false against the glossary's own definitions, and it had been asserted in an Accepted ADR without any ADR deciding it.

The claim also has a history worth recording, because it is the shape that produced it. The word "chrome" was first removed from D-139 in a fork round on the belief that it was an invented synonym; it is house vocabulary in nine files. That was reverted, Chrome was glossed, and the gloss then reached for a tidy set relation to justify the revert. The error was not the vocabulary; it was wanting the two terms to sit in a hierarchy.

On D-147. ADR-0066's Context lists four things the extract does — it links Google Fonts, labels the Conversational surface "online-only", glosses chrome strings in English, and routes Home's First Aid and Spill tiles straight to a record. Those four are the evidence D-142 rests on, and a search of the repository found the extract's name in only four files, never with a locator. This repository cites a scanned PDF by page number precisely so a future agent can check a claim it cannot grep. A design artifact reachable only through one session's tool access is weaker than that.

Decision ​

Chrome and Conversational Content overlap and neither contains the other; chrome may never be model-generated regardless. D-139's containment sentence is withdrawn and its ruling stands. The design extract is cited by project id and file name wherever a claim is made about it.

Rejected options ​

On D-146:

  • Narrow Chrome to text alone, so the containment claim becomes true — rejected because it contradicts the repo's own usage in nine files: main.css writes "neutral chrome" of a colour, BlankLayout.vue writes "the layout with no chrome" of furniture, and two modules use it of terms documented as never displayed. This is the third time a definition has been bent to fit a sentence about chrome, and each time the code was right and the sentence was not.
  • Fix CONTEXT.md and leave ADR-0064 asserting containment — rejected because the glossary and an Accepted ADR would then state different relations for the same two terms, which is the defect the grill reported rather than a fix for it.
  • Edit the sentence inside ADR-0064 in place — rejected because an Accepted ADR is never edited; that rule is what stops a decision being quietly altered, and the cost of honouring it here is one amending ADR.

On D-147:

  • Leave the four claims uncited — rejected because they are the whole evidentiary basis of D-142, and a reader who cannot reach them has to take the ADR's word for what a design file says.
  • Vendor a copy of the extract into the repository — rejected because the file is a .dc.html document carrying a proprietary runtime (support.js, x-dc custom elements) that renders nowhere but claude.ai. A committed copy would be bytes nobody can open, which reads as checkability without providing it. The locator plus ADR-0066's four claims stated explicitly is what a reader can actually use.

This ruling may not be re-decided ​

If a change contradicts this ADR: stop and raise it. Do not implement over it.

Specifically: do not restate chrome as a subset or superset of Conversational Content, do not narrow Chrome to text in order to make such a relation hold, and do not make a claim about the design extract without citing the file it was read from.

Consequences ​

What becomes true. The glossary and the ADRs agree on what chrome is. D-139's ruling keeps the property it actually needed — the wording is authored and never generated — without resting on a relation nothing decided.

What this costs. An amending ADR for what began as one sentence, and a locator that will go stale if the design project is renamed or deleted. The github.md provenance is recorded above so that a dead link still leaves a commit to compare against.

What is closed off. Any future tidy hierarchy between chrome and Conversational Content, and citing the extract by name alone.

Coverage ​

No upstream finding lands here. Both decisions came from the cross-model grill of 2026-09-20 — adversarial review against the glossary's own definitions and against the code — rather than from any R-nn (D-104).