← Knowledge base · seed/07-incident-reports.md

Incident report guidelines

Severity

• High: robot stopped or unsafe to operate, mission failures, risk of hardware damage (overheating, brake drag). Action required this shift.

• Medium: degraded operation (missed dispatches, recurring warnings), plan a fix this week.

• Low: expected behaviour or cosmetic, monitor only.

Content

Each incident should state the robot, time window, the causal chain from root cause to visible symptom, the error codes involved, the evidence (log lines, telemetry), and concrete recommended actions with an owner (maintenance, IT/network, operations). Distinguish clearly between a root cause and its consequences; an aborted navigation goal is rarely the root cause.