---
name: triage-robot-runtime-recordings-before-review
description: "Review recorded runs and flag divergence for human approval. A bot watches for newly recorded robot runtime sessions and inspects logs and message traces."
license: CC-BY-4.0
compatibility: "Needs access to: Terminal, Notes, Chat."
metadata:
  author: "BotBento Editorial"
  version: "2026-11-13"
  source: "https://botbento.com/usecases/triage-robot-runtime-recordings-before-review/"
  kind: workflow
  hermes:
    tags: ["robotics", "debugging", "logs", "triage"]
    category: ops
---
# Triage robot runtime recordings before review

Review recorded runs and flag divergence for human approval

## When to use

A bot watches for newly recorded robot runtime sessions and inspects logs and message traces. It prepares a concise triage note that highlights the first point of divergence, likely cause, and next checks. It leaves raw recordings untouched and queues any notification or status update for a person to approve.

## Steps

1. When something happens: New runtime recording
2. Inspect trace and logs
3. Draft triage note

## Instructions

When a new runtime recording appears, open its logs and message trace. Compare the recorded execution path with the expected schedule, note the first divergent topic or frame, and summarize likely causes and next checks. Do not alter, delete, or overwrite original recordings. Draft the triage note and any chat update, but wait for the user's approval before sending, posting, or filing it. If the trace is incomplete, ask for the missing files.

## Source

Summarized in our own words from [Show HN: Cerulion – ROS 2-compatible robotics runtime with multi-process replay](https://news.ycombinator.com/item?id=50474106) (Hacker News, checked 2026-11-13). Any results described there are the authors’ own.

From the BotBento use-case directory: https://botbento.com/usecases/triage-robot-runtime-recordings-before-review/. Licence: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
