← All goals
Objective: ISG relaunch — the Interactive Safety Graphics working group relaunched in Q1 2027 on the safety.viz platform
Goal issue #424 · slug isg-relaunch
0/4 member issues closed
Other open members 4
no readiness label yet.
- #425 the ISG charter — purpose, membership, ways of working and the role of the agents, accepted by the group (Backlog · documentation · status: backlog)
- #426 ISG intake — requests from clinical users turned into GitHub issues by a triage agent, piloted with the convener (Backlog · ai · status: backlog)
- #427 ISG contributors — a guide, roles and starter issues that take an outside developer from setup to a merged change (Backlog · infrastructure · status: backlog)
- #428 the ISG relaunch announcement — the charter, the tools and the way to send requests, to the wider ISG membership (Backlog · documentation · status: backlog)
Direction
Intent
Relaunch the Interactive Safety Graphics (ISG) working group in the first quarter of 2027,
with safety.viz and the obot agents as its foundation. Two things come first: a charter
agreed with the group's convener, and a technical framework that lets several developers
work on the charts and lets clinical users, most of whom will not use GitHub, send
comments and requests that end up as GitHub issues.
Definition of done
End state: by 31 March 2027 the working group has an accepted charter, a working
contributor process with at least one developer besides @jwildfire, a working intake
process from the channels clinical users already use, and a relaunch announcement to the
wider ISG membership.
Proof:
- The charter is published, with the meeting at which the group accepted it.
- A pull request by a developer other than @jwildfire or the bot is merged in safety.viz
or gsm.safety through the documented contributor process.
- At least one request from a clinical user who does not use GitHub came in by the web
form, a meeting or email, became an issue, and the requester heard back. The issue
links its intake record.
- The announcement links the charter, the tools and the way to send requests.
Ships in: milestone 2027q1. The pilots run in December and January.
Requirements
To be filed under this objective, in this order:
- Charter: purpose, membership, ways of working, decisions, the role of the agents, the
2027 goals.
- Intake: the web form, meeting notes and email turned into GitHub issues by a triage
agent, with human review where @jwildfire sets it. Piloted with the convener as the
clinical user.
- Contributors: a contributor guide, roles and starter issues so another developer can
go from setup to a merged change. Piloted with one outside developer.
- Relaunch announcement.
Boundaries
- Code stays under
jwildfire for Q1. Pilot developers are added as collaborators. Where
the code lives after the relaunch (a group organisation, Pharmaverse) is a charter
question.
- Nothing goes out in the group's name, and no outside person is quoted in a public issue,
without a human approving it.
- Clinical content (what a chart shows and why) is reviewed by a clinician, not just by
code review.
- If the calendar slips, the announcement waits for the charter. Intake and contributors
can open to the group in stages.
This Issue was drafted by Claude Code using Opus 5.5 and reviewed by @jwildfire
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.