A map of a system and a map of what happened in it

About thirty nodes, four rings deep, density increasing towards the middle. Every node linked to its neighbours in green phosphor glow. One path threads from the outer edge to the centre, drawn far heavier than the rest of the lines.

The rings were drawn first, by someone planning a defence. The heavy path was drawn after, by someone describing what actually happened to it.

What does a topology map like this actually record?

Two different things, laid on top of each other, and only one of them was true when it was drawn.

The rings and the node links are the design — the architecture as somebody specified it before anyone tried to get through. The single heavy path is a route, added afterwards, showing where one attempt actually went. A blueprint and an incident report have been printed on the same sheet, and the difference between them is the entire content of the image.

Why rings instead of a single wall?

Because a single wall is a bet that it holds, and rings are an admission that it might not.

One perimeter says: stop them here or the job has failed. Four concentric rings, each denser than the last, say something more honest — the designer assumed the outer ring would eventually be crossed, and built three more behind it on that assumption. Density increasing toward the centre isn't decoration. It's where the actual asset lives, guarded in proportion to how much it costs to lose it.

Why does the centre have more nodes than the edge?

Because the outer ring only has to slow somebody down, and the centre has to actually stop them.

A thin outer ring buys time and raises an alarm — it's tripwire, not defence. By the third and fourth ring in, every additional node is a genuine obstacle, chosen because whatever sits at the centre is worth defending properly. Reading density outward to inward is reading a budget: cheap coverage at the edge, real cost concentrated where it matters.

The one heavy path breaks that logic entirely

Every rule the rings establish — go through, get stopped, get slowed — applies to an attacker who doesn't already know the map. The heavy path was drawn by someone who did, or found out the hard way and lived to draw it. It doesn't respect ring density at all; it just goes where it went. That's what makes it read as a record rather than a plan.

What makes a good version of this design?

Restraint on everything except the one line that breaks the pattern.

Thirty nodes across four rings is close to the limit before the eye stops counting rings and starts seeing static — a map of a place works the same way, precise enough to be usable, not so dense it becomes texture. The heavy path only works if it's the single exception. A second bold route, or a dashed alternate, turns one clear story into an unreadable diagram.

Is a system like this owned by whoever built it?

The design of a defensive network belongs to whoever specified it, the same way a real building's security plan belongs to the client who paid for it. Nothing here depends on any real company's actual network diagram or a specific named protocol — it's an invented topology in an invented setting, which is the only version this design should ever be.

Does the same idea work outside a purely digital defence?

Anywhere a plan gets drawn before the event and a route gets drawn after it.

A patrol's assigned beat marked out on a floor plan, against the single line someone actually walked after finding a gap in it. A building's fire escape diagram against the path someone actually took the one night it mattered. The rings-versus- route structure isn't specific to a network at all — it's what any planned system looks like once somebody's actual experience of it gets overlaid on the plan.

Doesn't a defence with rings just mean it eventually fails?

No — it means whoever built it was honest about odds instead of promising a wall that never breaks.

A single perimeter that's never been tested reads as confident right up until it isn't. Four rings of increasing density is what a designer draws when they've already priced in that the outer layers will go down, and built the response into the structure rather than pretending it won't be needed. The heavy path proves the design worked exactly as intended — it cost someone four rings to get through, not one.

Does it print well?

Yes, on a dark ground with a single accent ink carrying every line.

One acid green on near-black is doing the CRT-phosphor read on its own — adding a second colour for the heavy path undercuts the exact thing that makes it heavy, which is that it's drawn thicker, not differently coloured. Keep the node dots small and the connecting lines fine; only the one path gets weight. Flat lines with hard edges hold up at chest scale in a way a soft glow effect never will on cotton.

How do I get one made?

Describe the network at JustOG — how many rings, how dense, and where the one route goes. Pick a direction, drag the crop frame, see it composited on the real garment, and it's made to order and shipped.

Designs other people have published are in the shop.

Four rings built to be broken in a particular order, and one line showing which order it was.