# mainskeeper CLI — PROPOSED product contract, not shipped software. Fictional demonstration data.
# screen: doctor-cloud · host: duplex-pi-probe · 80 columns · NO_COLOR · exit 7
# clock: Wed 30 Sep 2026 14:58 PDT · Fixture · earlier moment — duplex-pi-probe at 14:58, during the fixture’s Duplex outage (probe restarted 14:52:10, connectivity restored 15:02:06).
# stderr lines (counting the prompt line as 1): 15, 16, 17, 18, 23
duplex-pi-probe $ mainskeeper doctor
MainsKeeper · duplex-pi-probe · doctor                 Wed 30 Sep 2026 14:58 PDT
Checks read state only. Nothing on the UPS or attached equipment is changed.

✓ config
  /etc/mainskeeper/collector.toml valid (schema 1)
✓ enrollment
  enrolled · valid (not checked online)
✓ service
  mainskeeperd.service active (running) since 14:52:10 PDT (±90 s)
✓ clock
  synchronized at 14:54:00 PDT; records 14:52:10–14:54:00 flagged ±90 s
✓ UPS source
  Duplex Utility UPS answering (USB) · utility present
✗ cloud
  cannot reach ingest.mainskeeper.example (HTTPS) — connect timeout
  Connectivity failure confirmed by local probe: gateway 192.168.77.1, DNS
    resolver and ingest all failing
⇡ queue
  recording locally · oldest pending 13:41 · gap 14:30–14:52 (probe offline, no
    records exist)

Result  1 problem · exit 7 (cloud unreachable)

Nothing is lost while disconnected: records upload in order when the connection
returns, at their observation times. Progress: mainskeeper queue
