Status page for deployed systems

[AlexAxthelm]

Counter-tracked in Monday: https://rmi.monday.com/boards/7707313975/pulses/11819513054

have a high-level overview of deployed systems (potentially subsystems)
Inspirations (fancy versions):
https://status.openai.com/
https://www.githubstatus.com/
https://azure.status.microsoft/en-us/status

Past work:

@jdhoffa was previously maintaining https://github.com/RMI-PACTA/pacta.sit.rep to monitor PACTA systems and CI flows (A remarkable number of which are still reporting green). Can serve as a good template for public GH workflows in a simple tracker.

Related work

Centralizing Build/deploy infrastructure allows for making good reporting/service discovery a standard part of the process, rather than something that needs to be built new for each project

[jdhoffa]

Two-cent:
Given how difficult it has proven to be to ever get time/ funding for platform engineering OR maintenance, I would opt for the simplest and lowest-burden version of this in terms of maintenance. Otherwise we are just building something that we won't have time to actually maintain.

So with that in mind, I tend to think we should get as much mileage as we can out of the "throw a bunch of badges into a .md" approach as possible