# Reboot log — cc-ci orchestrator Pi

One line per genuine reboot of the orchestrator Pi (`raspberrypi`), appended automatically by
`reboot-log.sh` (ExecStartPre of `cc-ci-loops.service`, boot_id-gated so manual service restarts are
NOT counted). The Pi hosts the Builder + Adversary loops + watchdog; a reboot drops the tmux sessions
(and this orchestrator session), and `cc-ci-loops.service` restarts the loops on boot. Count the
lines below to see how often it's happening.

## Reboots

- 2026-05-28 (~19:?? BST) — reboot (backfilled from memory; mid-Phase-2). Orchestrator + loops were
  down until manually relaunched. This pre-dates the systemd auto-restart service.
- 2026-05-28 (~20:02 BST) — reboot (backfilled from memory; uptime showed 5 min at 20:07). Loops
  manually relaunched at phase 2; this is what prompted adding `cc-ci-loops.service` +
  auto-logging. Auto-logging is live from the next reboot onward.