🍊😺 obot
Launched
Commit6ab6d6b

changelog v4.29.2 is current with this build

What changed · full log

← 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.

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:

Ships in: milestone 2027q1. The pilots run in December and January.

Requirements

To be filed under this objective, in this order:

  1. Charter: purpose, membership, ways of working, decisions, the role of the agents, the 2027 goals.
  2. 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.
  3. Contributors: a contributor guide, roles and starter issues so another developer can go from setup to a merged change. Piloted with one outside developer.
  4. Relaunch announcement.

Boundaries


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.