There is one rule the whole site is built under: no shape without a number, and no number where the source gave none. The two halves pull against each other, which is why most dashboards get it wrong in one direction or the other.
The clearest case is the database hop. The architecture trace on /arsip draws the path a request takes — browser to Next handler, handler to the Go backend, backend to Postgres — and the third segment has no length. The health endpoint answers without a duration field, so hopsDari() returns database.ms as null by construction, and the page prints the hop's name with an em-dash and draws no segment for it at all. A zero there would say: we measured it, and it was instant. Nobody measured it.
The same rule decides what happens when a poll fails. The telemetry store erases the reading instead of keeping the last good one. A stale number wearing a live colour is worse than an empty field, so the HUD marks the process silent and the pit wall prints dashes across every measurement cell. The verifier mocks a dead endpoint and fails the page if any of those cells manages to show a digit.
Where there is a number, the shape has to follow it and not the other way around. The frame-rhythm bars are six minute buckets drawn from one law: a bucket with no reports has no bar, an overshoot past the 33 ms budget is compressed rather than clipped, and the ceiling is a ratio of 2.2 so that one terrible minute stays visible without flattening the five neighbours. The same function computes the HUD bar and the page below it, which is why the two can be checked against each other.
The repository index obeys the same discipline in the negative. The GitHub payload this site reads carries id, name, description, homepage, url, stars, forks, language and a fork flag — no timestamp of any kind — so the index prints no dates at all, and an empty description cell means GitHub said nothing, not that this repo has nothing to say. Sorting by update time happens upstream; the page just refuses to invent the field.
None of this is modesty for its own sake. A dash is a cheaper interface than an apology: it tells the reader where the boundary of the measurement is, in the same place the number would have been.