← 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.
- #402 every tab has a colour, and the first screen says where you are — tab colours, counts, a welcome line and the way back to the docs (Released · safety · status: released)
- #403 one status ladder — Qualified, Exploratory, Experimental, Prototype — with one label for the app and one for anything below it (Released · safety · status: released)
- #404 one R control — slim, in the same place on both tabs that use R, and a chip once R is ready (Released · safety · status: released)
- #405 the RBQM tab reads at a glance — a row of metrics like every other tab, status icons, a table that fits its numbers, and the log folded away (Released · safety · status: released)
- #406 all files come in on the Data tab — gsm raw files recognised there, and the file box gone from the RBQM tab (Released · safety · status: released)
- #407 nothing looks broken — the defects found in the review of release 1.10, and the keynote's demo path walked by a test (Released · safety · status: released)
- #408 the standards this release set are written into the scaffold — the status ladder, the app's conventions and how a design is made, where the next session will read them (Released · infrastructure · status: released)
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:
- The R control is one slim control, the same wherever R runs, and shrinks to a chip once R is ready.
- "All of this is 'exploratory' - nothing is qualified. All results should be confirmed." The status ladder is Qualified, Exploratory, Experimental, Prototype. Nothing is Qualified. The app carries one Exploratory label.
- The RBQM tab has a row of names under the header like every other tab, with the metrics as its items and R started from the same control as the biomarker charts. It uses icons for metric status, a table whose columns fit their numbers, and a log that stays folded until asked for. Files are loaded on the Data tab and nowhere else.
- Every tab has a colour. A module names its own; one that names none is given an open one, never grey.
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:
- Every tab has a colour, and the first screen says where you are (#402).
- One status ladder, with one label for the app and one for anything below it (#403).
- One R control, slim, in the same place on both tabs that use R, and a chip once R is ready (#404).
- 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).
- All files come in on the Data tab: gsm raw files recognised there, and the file box gone from the RBQM tab (#406).
- Nothing looks broken: the defects found in the review, and the keynote's demo path walked by a test (#407).
- 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
- The design page is the reference. A session builds what its mockup shows; where the mockup cannot be built as drawn, the session says so on its requirement and asks, and does not redesign.
- No chart and no metric is added, and nothing the app computes changes. R computes every number, as now. Files never leave the browser, and the footer's sentence stays true.
- Nothing is labelled Qualified. The build refuses the word until there is a qualification record to point at.
- Requirements 1 to 5 all change the app's page and style files (
src/app/page.js, src/app/styles.js), so their sessions run one at a time, in order. Requirement 6 changes chart files and the docs site's styles and can run alongside any of them. Requirement 7 changes documents and a skill only: its hub and obot.agent tasks can be done at any time, and its safety.viz task is written last, once the code it describes has merged.
- The file box leaves the RBQM tab in the same pull request that makes the Data tab take raw files, never before, so that a reader's own raw files work at every commit.
- The release candidate is opened by the session of the last requirement to close, with release notes through the release-notes skill and a demo page on the hub. The target is a release candidate in front of @jwildfire by Thursday 15 October, the hub milestone's date.
- The cut line if the calendar slips, first to go first: raw files on the Data tab (requirement 5, leaving the file box where it is); the welcome line and the phone-width navigation items of requirement 1; the details behind the R chip in requirement 3. The status label, the RBQM tab and the defects are not cut.
- Left out, each filed as a follow-up on the
backlog milestone when its requirement closes: one R shared by the Biomarkers and RBQM tabs (unproven, and it needs a release of the biomarker library); one set of treatment-arm colours across the QT, time-to-event and biomarker charts; one casing for chart names; the status label in gsm.safety's R widgets, which arrives when that package next copies the chart library.
- Reading gsm raw files in the app is an interim path (@jwildfire, 2026-10-09: "I'm hoping to move to RAW -> SDTM -> ADaM for everything. Not in this releases though"). This objective moves that loading to the Data tab and invests no further in it.
- The RBQM follow-ups already on the backlog (more metrics, country level, the time series chart, the report, mapping non-standard column names) are not part of this objective.
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.