How the panels connect
The links between panels were placed one at a time, and the count only includes those.
Nexus market addresses in this board
copy, do not retypenexusb2l73qzjn4slhyfxa3jvpolw7fomiz5sgyyefnsdhikaqgborqd.onionnexusma2iekjhhyenua3u4zlyfsj2ubwxr2nt6gdte5rvwukzze63fyd.onionnexusabcdbnjw6or46y3hh6uicsl4xvu5cncfp27hkggznvtxhxlngad.onionPrinted as supplied, in no order, with nothing marked best or main. This board never opens an address, so nothing on this page says one of them is reachable for you now.
What is counted
Each panel declares a short list of related panels, which is what produces the three cards near the bottom of every page. The metric counts those declarations across the whole registry.
It does not count the navigation bar, the breadcrumb, the section lists, the prev and next controls, or the full index in the footer. Every one of those is generated from the structure, so counting them would be counting the same structural fact many times over.
Why the distinction matters
A generated link carries no information. It exists because a page exists, and it would exist whatever the page said. A hand placed link is a small statement that two specific panels are related, made by somebody who had read both.
Counting them together would inflate the figure by a large factor and would measure the template rather than the writing. Keeping them separate is the same instinct that keeps every other number on this board narrow.
Depth, and what it means
The last tile counts the slashes in this page address and adds one. That is an upper bound on how many clicks it takes to reach from the front, not a measured path.
It is an upper bound rather than a measurement because the actual shortest route depends on which links exist, and this board deliberately does not compute that. A shortest path calculation would be genuinely interesting and would take considerably more code than the honest simple version, and the honest simple version is labelled accurately.
Prev and next, and how the labels work
Panels inside a section are chained, and each chain entry stores only the address of the neighbouring panel. The label shown to you is read from that panel own heading when the page is built.
That is a small thing with a real consequence: a prev or next label cannot drift away from the page it points at, because there is no separate copy of the label to become wrong. Rename a panel and every reference to it updates on the next request.
What the link count does not say
- Whether the links are good ones. Relatedness is a judgement and no count reaches it.
- Whether any panel is well connected. A panel with three incoming links and one with none look identical in this figure.
- Whether anybody follows them. Nothing here observes a click.
- Whether more would be better. Past a certain density, related links stop being a recommendation and become wallpaper.
The one link on every page
There is one link this board places everywhere, which is the wordmark at the top pointing at the front page. It is on every page without exception, generated rather than declared, and therefore not in the count above.
It is worth mentioning because it is the only navigational promise the board makes: whatever page you are on, the thing in the top left goes home. Everything else is arranged by section, and the section bar is the second promise.
Why every cross reference is checked
There is a specific failure that sites like this ship constantly: a link to a page that does not exist, written when the target was planned and never updated when the plan changed.
It survives because nothing catches it. The link renders fine, the page looks correct, and the only way to find it is to click every link on every page, which nobody does after the first week.
On this board the related panel cards are rendered from the registry, so a reference to a page that does not exist simply does not draw, and the same registry is used to check every declared reference before anything is published. That is a small piece of plumbing and it is the reason a reader can follow any card here without landing on an error.
Reading this panel wrong
3 ways it happens- Reading the link count as connectedness.It counts declarations. It says nothing about whether the connections are sensible or whether anybody follows them.
- Reading depth as a measured click distance.It counts slashes in an address. The label says upper bound because that is what it is.
- Assuming more links would be better.Past a point they stop being recommendations and become decoration, which is a design judgement rather than a number.
What this panel is not: a graph analysis. It counts declarations and computes an upper bound, and says so on the tiles.