MainsKeeper Product & System Guide Edition 0.2.3

Reference

Diagram gallery

Fourteen figures. Chapters embed the same SVG files. fig-enroll-sequence.svg matches Figure 6, and fig-replay-sequence.svg matches Figure 8. Enrollment sequence · Replay sequence.

Multi-site product overview

Figure 1. Multi-site product overview

System context and external boundaries

Figure 2. System context and external boundaries

Deployment-pattern comparison

Figure 3. Deployment-pattern comparison

Domain relationships

Figure 4. Domain relationships — reads vs powers

Logical components and responsibility boundaries

Figure 5. Logical components and responsibility boundaries

Enrollment sequence

Figure 6. Enrollment sequence

Normal telemetry flow

Figure 7. Normal telemetry flow

Offline buffering and replay

Figure 8. Offline buffering and replay

Broadwater outage timeline

Figure 9. Outage timeline — known vs unknown

Configuration states

Figure 10. Configuration states

Operational incident lifecycle

Figure 11. Operational incident lifecycle

Battery Assurance lifecycles

Figure 12. Battery Assurance lifecycles

Storage layers

Figure 13. Storage layers

Standalone monitoring versus centralized platform. Prometheus scrapes the collector. Grafana queries Prometheus. Telemetry goes collector, buffer, ingestion, history. Enrollment only establishes identity.

Figure 14. Standalone vs centralized platform

Enrollment sequence for a synthetic Broadwater collector, from the enroll command through credential check-in.

Enrollment sequence

Takeaway: Approval, first contact, and the first UPS reading stay separate.

Replay sequence: local buffer, late upload, acknowledgement, and history written at observation time.

Replay and acknowledgement sequence

Takeaway: Replay writes history at observation time and does not invent the span a full buffer dropped.