Case study · 2026 · Personal fork
Ringer /
Ringside
Built on Ringer and Ringside by the upstream project and contributors.
Verified delegation, made visible. Ringer coordinates AI coding agents and checks their output; Ringside makes the runs, attempts and failure evidence inspectable.
01From a status to an explanation
From a status to an explanation: what ran, what failed, and what to do next, on one timeline.
Ringer coordinates AI coding agents and checks their output. My fork tests those checks before any real work starts and puts every run, attempt and failure on one timeline.
Product design · Front-end development · Orchestration · Verification
- 01
Test the checks
An optional preflight runs each check against declared known-good and known-bad examples before any real work starts, so a check that passes everything is caught early.
- 02
Review, then release
An optional pilot runs one nominated task first and holds the rest until it is approved. A rejection or a timeout ends the held work.
02Details and directions
From many views to one timeline. The August explorations tried a compact table, a poster-scale overview and a left rail before the surfaces converged.
The September consolidation removed the rail, the separate destinations and the slide-over. Runs, artifacts and models now share one wall-clock timeline, and details expand in place.


Fork design & implementation: Josh Butner. Built on Ringer and Ringside by the upstream project and contributors.

