When the computers became a constellation

There are at least two ways to lose track of a computer project. You can build too little to see what it is. Or you can build so much that looking at the whole thing requires opening six terminals and reconstructing the past from memory.

I had drifted firmly into the second camp.

A machine to coordinate. A machine to compile. A GPU box with an entirely different job. A quieter server that should keep things alive while the exciting experiments break. Laptops, agent sessions, model servers, bridges and bits of automation that were all useful on their own. They did not have a shared place to be seen.

The obvious answer was a dashboard. The problem was that I didn't want a row of twenty-four tiny graphs pretending the problem had been solved.

Make the machines legible

The first image that stuck was a constellation. Let each physical machine have a stable position, like a star whose location you learn. Let the things it hosts become smaller objects. Let links carry relationships rather than decorating empty space. A working system might glow differently from a missing observation. You could turn the sky and select something without forgetting where the other machines were.

It was a visual metaphor, but it was not meant to stop at metaphor. The chart is an entrance into the operational truth: health, services, machines, agents and eventually the ability to work on one of them.

That difference matters. A useful atlas doesn't just look connected. Its connections mean something.

The beautiful part had to tell the truth

As we built the first slice, a less glamorous problem kept appearing: what did we actually know?

A machine being registered on the private network is not proof an agent is awake. A port being open is not proof the program behind it works. A desktop-shaped icon is not a desktop. A record from fifteen minutes ago cannot quietly masquerade as a live event.

The first NEXUS version drew a cyanotype-like chart and offered a read-only catalogue. The more we pressed it, the more the design became about uncertainty: current, stale, missing and unverified are different states. We added tests around those boundaries rather than letting an attractive diagram make confident promises on behalf of the cluster.

An exhibit, not an open control panel

Try the public constellation. It's the real renderer with frozen, fictional data and no private backend. It preserves what is interesting about the interaction and keeps the actual cluster behind its own device authorization.

This chart is only the first way of seeing NEXUS. I still want a control room that can show agent sessions, model memory, services, and workbench screens. But I also want to keep the moment where a mess of machines first became a place you could navigate.