# mainskeeper CLI — PROPOSED product contract, not shipped software. Fictional demonstration data.
# screen: status-bw · host: bw-pi-01 · 120 columns · NO_COLOR · exit 0
# clock: Wed 30 Sep 2026 15:22 PDT · Fixture · incident state, now 15:22
# stderr lines (counting the prompt line as 1): none
bw-pi-01 $ mainskeeper status
MainsKeeper · bw-pi-01 · site Broadwater                                                       Wed 30 Sep 2026 15:22 PDT
■ BW Rack UPS on battery since 15:09:00 PDT · observed 13 min (live)

COLLECTOR       bw-pi-01 · Raspberry Pi 4 · Raspberry Pi OS 12 · site witness (always-on)
SERVICE         ● running · mainskeeperd 0.4.2 (systemd) · since Mon 14 Sep 03:12 PDT
CLOUD           ● connected · Heartbeat on time · last contact 4 s ago · every 15 s · heartbeat 15 s (local override)
ROLES           UPS monitoring on · connectivity monitoring on · applied (set in the dashboard)

UPS             2 UPSs on this collector
                UPS             Power          Charge  UPS estimate   Load   Reading
                BW Rack UPS     ■ on battery   71%     18 min est.    38%    On schedule · 4 s · every 30 s
                BW Office UPS   ● on utility   100%    ▨ Unsupported  12%    On schedule · 7 min · every 10 min
                freshness     every 30 s: On schedule ≤ 60 s · Overdue ≤ 90 s · Stale · last known beyond (allowance
                              30 s)
                              every 10 min: On schedule ≤ 15 min · Overdue ≤ 25 min · Stale · last known beyond
                              (allowance 5 min)

BW Rack UPS     APC Smart-UPS SMT1500 · USB · circuit A (rack)
                reading       On schedule · read 4 s ago · expected every 30 s · at 15:21:56
                on battery    observed 13 min since 15:09:00 PDT (measured, live)
                input · temp  0 V · 31 °C
                UPS estimate  18 min est. · initial estimate 34 min at 15:09
                powers        bw-router, bw-nas-01, bw-switch-24 (configured)
BW Office UPS   Eaton 5S 700 · SNMP v3 card 10.0.20.15 · circuit B (office, separate)
                reading       On schedule · read 7 min ago · expected every 10 min · at 15:15:00 · next report due by
                              15:25:00
                input · temp  121 V · ▨ Unsupported
                secret        Configured · last test 15:20:10 (stored locally)
                powers        bw-desk-ws — sleeping, no agent (relationship recorded)

CONNECTIVITY    ● 3 of 3 targets answering · gateway 192.168.10.1 · checked 20 s ago

INCIDENT        ■ INC-0412 BW Rack UPS on battery · Critical · Open · Not acknowledged
                First evidence        15:09:00 PDT · UPS reported on battery (received 15:09:01)
                Grace period started  15:09:00 PDT · 60 s on-battery delay
                Declared              15:10:00 PDT · still on battery after 60 s
                Acknowledged          Not acknowledged
                notified              email delivered 15:10:04 · push delivered 15:10:05
                low runtime           rule “UPS estimate < 10 min” not triggered

HISTORY SYNC    ● current · 0 pending · 12.4 MB of 2 GB disk cap

DASHBOARD       https://mainskeeper.example.net/incidents/INC-0412
                site          1 of 2 UPSs on battery · 1 on utility (separate circuit)
                fleet         2 open incidents (1 critical, 1 warning; 0 acknowledged)
                collectors    4 of 6 expected collectors reporting · 1 workstation asleep
                › Acknowledge in the dashboard. The CLI changes nothing on the UPS or equipment.

Battery AssuranceRead-only. Never starts self-tests or transfers.
                BW Rack UPS   Battery operation observed: 13m so far at ~38% load (live)
                BW Office UPS Evidence overdue under 60-day policy · self-test PASS (date unknown)
