Every six hours status.yml probes each live service, reads its repo's latest Actions run, appends what it saw to an append-only log (log/sweeps.jsonl), and redraws the rows above from that log. If a row says down, it is actually down.
The longer version
I came to software sideways. Physics concentration at Manhattan University, then a CS degree at WGU, with a few years of unglamorous operations work in between — a bank branch running a core banking platform, a residential facility where the life-safety system going down was a real problem and not a page in a runbook.
That background is why the work above looks the way it does. I am less interested in apps than in the thing that has to keep running on Tuesday at 3 a.m. with nobody watching: the scheduled job, the append-only store that survives a bad re-run, the deploy that either works or rolls back cleanly.
Currently: finishing my B.S. in Computer Science at WGU (November 2026), starting Georgia Tech's M.S. in Computer Science in January 2027, running the services above, and looking for a team where infrastructure is a first-class concern rather than something the backend engineers do on Fridays.
Reach me: swegeraldogrell@gmail.com
This README is rebuilt by a GitHub Action. If it looks stale, something in my own pipeline broke, and that is on me.
Last sweep: 2026-11-18 20:33 UTC