Projects · 03
Orbital Watch
Satellite passes over a ground station next to live space weather, on a static site that reports how fresh its own data is.
Right now
Checking…
-
Orbital Watch checking
Open them directly: Orbital Watch
- My part
- My own project, built with Claude Code. Its design decisions, and the failures that forced them, are written up in the repository's DECISIONS.md.
- Result
- Each of the seven upstream sources is marked fresh, stale or failed on the page, with the reason. A build with every source unreachable still finishes and says so, and CI checks that on every push.
- Stack
-
- Python build
- Cloudflare Pages
- A Cloudflare Worker on a schedule
- GitHub Actions
- pytest
The idea
A monitoring system must report its own degradation as honestly as it reports its data. Every number on the page carries its source and age. Every upstream source is classified fresh, stale or failed against published thresholds, and no fallback is ever allowed to claim freshness it does not have.
The orbital mechanics are not the interesting part. What happens when things break is.
How it works
A Python build fetches element sets and space weather, computes satellite positions and passes, judges the health of every source, and writes JSON files into the build output. The page loads those files and renders. The browser never contacts an upstream API.
That buys three things. An upstream outage cannot take the site down: the build falls back to a cache or a committed snapshot, every panel still renders, and the health panel says the data is stale and why. Hosting is static files on a CDN. And “last updated” is measured, not asserted, because every fetch is recorded with its outcome and time.
Every network call goes through one function. It has a hard timeout, catches failure, records
the outcome, and never raises, so no caller can abort the build by forgetting a try.
Why it is on this site twice
The status panel on the home page follows the same rule. Its service reads this project’s own health file, and when a check fails the panel says “could not check” and gives the reason. It does not guess.
Architecture · scroll sideways for all of it →
Where these claims come from
-
Each of the seven upstream sources is marked fresh, stale or failed on the page, with the reason; a build with every source unreachable still finishes and says so; CI checks that on every push.
GitHub profile README; the repository README, "Reliability behaviour".
-
Python build, Cloudflare Pages, a Cloudflare Worker on a schedule, GitHub Actions, pytest. Built with Claude Code.
-
The page's health panel is written to data/health.json by each build.
The live file, read on 18 November 2026 (seven sources, all fresh).