🍊😺 obot
Launched
Commit6ab6d6b

changelog v4.29.2 is current with this build

What changed · full log

← All goals

Objective: A demo app ready to show — the safety.viz demo app, clear to a first-time visitor and ready for the keynote

Goal issue #401 · slug demo-ready

7/7 member issues closed

✅ Done 7

closed members.

Direction

Intent

@jwildfire, 2026-10-09, after reading the design review of release 1.10: "Goal is to have this next version ready for demo at keynote and good enough for people to play with, so need extreme focus on UX and usability."

Release 1.10 put everything in the app: eighteen charts, the biomarker statistics and the RBQM tab, the last two run by R in the browser. This objective adds no chart and no metric. It makes what is there read clearly to someone who has never seen it, on a shared screen at the R/Pharma keynote on Wednesday 21 October 2026 and on a stranger's laptop afterwards. The design is one published page of six desktop mockups with every change numbered (design for release 1.11), which he approved in the session of 2026-10-09 after three rounds. It rests on his feedback:

Definition of done

End state: on the released demo app (https://jwildfire.github.io/safety.viz/demo/) at 1,280 pixels wide, the header carries one Exploratory label that opens the disclaimer and the four-rung ladder on a click; each of the five Experimental charts and the RBQM tab carries the same label with its own reason; no tab's hex is graphite; R is started from the same control on the Biomarkers tab and the RBQM tab, and that control is a chip once R is ready; the RBQM tab has a row of metrics under the header with a status icon on each, has no file box, draws the site overview with number columns no more than 100 pixels wide, and keeps its log folded until asked for; gsm raw files dropped on the Data tab are recognised there and the RBQM tab runs on them; and the four defects found in the review of release 1.10 are gone.

Proof: a browser test in safety.viz's CI walks the keynote's demo path on the deployed dev demo at 1,280 by 720 pixels with no console error, and its screenshots are in the evidence set; every metric's Results rows still match desktop R's on the RBQM demo study; the network tests still show the study's rows are sent nowhere; every requirement below is closed with its proof comment; safety.viz v1.11.0 is tagged and its demo page is on the hub.

Ships in: safety.viz v1.11.0, milestone 2026-10-talk.

Requirements

In session order:

  1. Every tab has a colour, and the first screen says where you are (#402).
  2. One status ladder, with one label for the app and one for anything below it (#403).
  3. One R control, slim, in the same place on both tabs that use R, and a chip once R is ready (#404).
  4. The RBQM tab reads at a glance: a row of metrics like every other tab, status icons, a table that fits its numbers, the log folded away (#405).
  5. All files come in on the Data tab: gsm raw files recognised there, and the file box gone from the RBQM tab (#406).
  6. Nothing looks broken: the defects found in the review, and the keynote's demo path walked by a test (#407).
  7. The standards this release set are written into the scaffold: the status ladder, the app's conventions and how a design is made (#408).

Boundaries


This issue was drafted by Claude Code using Opus 5.5 from @jwildfire's feedback of 2026-10-09. The tree is signed off only by his comment here.


Members are generated from the objective issue's sub-issue links at build time; priority is the selecting session's judgment, not list order (#53 v2). The --auto policy binding — active/paused, grant profile, repo-level backlog feeds — lives in obot.agent/goals/registry.json. Readiness labels: auto = ready for autonomous implementation, draft = needs @jwildfire steering.