The first time you open the homepage in a session, an agent appears to build it in front of you. A cursor with a name on it, Kofi, Abena or Kwame, types my name out letter by letter, takes you down the page to lay out the live numbers, then comes back and draws a terminal window for you to use. On a wide screen a second agent prints the ascii card at the same time. Every step shows up in a build log in the corner. I want to be straight about what that is, because the honest version is more interesting than the illusion.
The build is a scripted replay. No model writes this page on every visit; that would be slow, expensive and pointless. The names are real, though. Kofi, Abena and Kwame are the three OpenClaw agents I actually run, each on its own machine, and the panel below the hero checks whether each of them is up right now.
##What is real
Everything in the system.signals panel is measured on smartqix-web, the Hetzner server that serves this site, at the moment you ask for it. Nothing is typed in by hand.
- -Products online: the server requests the homepage of each product I run, retries once, and counts anything that answers without a server error as up.
- -AI agents online: the same check against the gateways of Kofi, Abena and Kwame.
- -Last shipped: every Next.js build and every Laravel deploy leaves a timestamp on disk. The panel reads the newest one.
- -Stories GhanaFront read: GhanaFront's own statistics endpoint. The age shown is the age of the newest story, not the moment the panel asked.
- -Books in Sankofa: counted live from the Sankofa API, which runs on the same machine.
- -Server uptime and load: read straight from the kernel.
- -Local time: your own clock, converted to Columbus and Accra.
##Freshness is part of the number
These sources move at very different speeds. Load changes every second; a deploy happens a few times a week; GhanaFront publishes when the news does. A number without its age quietly claims to be current, so every tile says where it came from and how old it is. If a source cannot be reached, the tile shows a dash rather than the last value it saw. The server measures at most once a minute however many people are reading, so the panel costs my machines almost nothing.
##What is scripted, and the one part that is not
The build is choreographed. The typing has a human rhythm because it is written to: slower at word breaks, slower still after punctuation, never perfectly even. The window is dragged out with a crosshair the way you would draw a frame in a design tool. The sections further down are written in quickly while the log narrates them. One step is not theatre: the signals step waits for the server to answer before it places a single tile, and the log reports what actually came back, so if a source is down you will see it there first.
##The guard rails
- -If your system asks for reduced motion, the build never runs.
- -Search engines and other crawlers skip it and get the finished page.
- -It plays once per browser session. Reloading replays it, and so does the replay button in the corner.
- -The build scrolls the page for you, but the moment you scroll, click, tap or press a key it gets out of the way and shows you the finished page. A click on a link still goes where you meant.
- -The page is hidden before the first frame so you never see it flash, which is risky: if the code that runs the build failed to load, you would be left looking at nothing. So a tiny script in the page head reveals everything after four and a half seconds unless the build has taken over. The illusion can only ever add to the page.
The idea comes from Sai Kambampati's site, where an agent called Muse draws the page with a pencil. His panel of live signals is what convinced me: the animation is fun once, but numbers that are actually true keep a page worth coming back to. Mine just measure a different kind of life, the machines and products I spend my days keeping alive.