Reports › Contract docs

Contract docs

The specs the decisions cite, as they stood on 24 October 2026. A decision page says which doc backs it.

• Runs v1: a live terminal for every utility2026-10-24 · The seam for runs: a real action on a pseudo-terminal, where records go, the output ring and recordings, Stop and the plugin's own stop.
• On-connect probe2026-10-23 · The driver says what to check when a device is plugged in: the verb, when the host runs it, the three standard events, and the query-only rule.
• The expected setup (a rig manifest)2026-10-23 · A small file that says what this PC should see, so the page can say 6 of 7 boards and name the missing one.
• Stable and Preview channels2026-10-23 · Why each setting in stable-preview.json is what it is, and how the login service brings Stable up.
• One action vocabulary across drivers (record v0.1)2026-10-22 · The standard action names, their one label each, the four danger classes, the dry run and the model_id identity key.
• Diagnostics record v02026-10-22 · ROS DiagnosticStatus kept whole, plus Entity, Event, Fault and Action. Eight lessons from the field, the rules, and the evidence re-checked.
• IO diagnostics: converged design2026-10-22 · Scope, layout, the two planes, port ownership, the contract and the open question about reusing Lichtblick.
• IO diagnostics v1: build plan2026-10-22 · The decisions, the plugin boundary (a subprocess speaking JSON lines), the lanes, and the interfaces frozen between them.
• Server API v12026-10-22 · What the page may rely on: state, activity, plugins, actions and their single-use tokens, history, settings.
• Round 2 brief2026-10-22 · Zach's round-2 feedback as five structure proposals and eleven skins.
• Round 2 seams: tokens, skins and structures2026-10-22 · The contract for skins, structures, the row object and page state, with the decisions taken in rounds 3 and 3.5.
• Round 3 brief2026-10-23 · What was settled in round 3 (resizable panes, warning colours reserved, quieter utilities) and the three sets of proposals.
• Bring your own tokens: writing a skin2026-10-22 · A skin is one file of token declarations; the 39 base tokens, the gates a skin must pass, and a 20-line example.
• Name research: 20 alternatives to RobotDiagnostics2026-10-22 · The scored list behind the naming decisions.