🍊😺 obot
Launched
Commit6ab6d6b

changelog v4.29.2 is current with this build

What changed · full log

← All goals

Objective: RBQM in the browser — a study's raw files through the standard gsm workflows to the site-level charts, with R computing every number

Goal issue #375 · slug rbqm

3/12 member issues closed

Other open members 9

no readiness label yet.

✅ Done 3

closed members.

Direction

Intent

@jwildfire, 2026-10-07: "Build a barebones RBQM tab in the safety.viz demo app: a user loads their study's raw files, the standard gsm workflows run in R in the browser, and the standard site-level charts draw from the result. Top priority for the R/Pharma talk on 21 October 2026."

Nothing is precomputed. The reader's files stay in the browser; pressing Start R runs the mapping, metric and reporting workflows there through workr, and gsm.viz draws the Results, Bounds, Groups and Metrics tables that come out. The tab is the report.

Definition of done

End state: on the deployed dev demo (https://jwildfire.github.io/safety.viz/dev/demo/), choosing the RBQM demo study and pressing Start R runs the standard gsm workflows in the browser and draws the group overview table, the scatter plot and the bar chart for every site-level metric the loaded files support; loading a reader's own raw files with gsm's standard column names does the same; a metric whose files are not loaded says so; no number on the tab is computed by the app.

Proof: a browser test in safety.viz's CI holds every in-scope metric's Results rows to desktop R's on the same input; the app's network test shows the study's rows are sent nowhere; both requirements below are closed with their proof comments, and the second one's comment quotes the measured download size and run time.

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

Requirements

In session order:

  1. The gate: the standard gsm workflows run in browser R, adverse event rate by site from raw files to Results rows, matching desktop R (#373).
  2. The RBQM tab: the demo study, a reader's own files, and the three site-level charts for the metrics in scope (#374). Starts only when the gate has closed with its proof.

Boundaries


This issue was drafted by Claude Code using Opus 5.5 from @jwildfire's brief of 2026-10-07. 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.