Skip to content

Show the services as a row of beacons on the status page - #321

Merged
RunTimeAdmin merged 1 commit into
mainfrom
status-scene-3d
Nov 15, 2026
Merged

RunTimeAdmin merged 1 commit into
mainfrom
status-scene-3d

Conversation

@RunTimeAdmin

Copy link
Copy Markdown
Owner

What

A new card at the top of the Status page draws the judgement the page already makes, in three.js (the vendored r170), and draws it again each time the page reads.

  • Each service is a beacon whose light is its state: green running, amber look at this, red down, and a hollow violet ring for no answer.
  • The two operators and the event index stand on a glass column: the time since the last epoch finished, or the blocks behind the chain, against labelled rings at the limits status.js applies. A column with no measure read fades out, so it cannot be taken for a good one.
  • A red diamond is a disagreement that can still be rejected.
  • Floor lines run from each service that reads the chain, and from the checker to its disagreements.

Pointing at a beacon describes it. Clicking opens where it was read from. A key under the room names each part.

status.js publishes what it judged, with the limits and one fact per service in a few words. Its judgements are unchanged. Without WebGL the card stays hidden. With reduced motion nothing moves by itself.

Checked

  • Running, look-at-this, down and open-disagreement states, through a temporary local stub (since deleted), because the operators' endpoints answer sigvara.xyz only. No-answer was seen for real on localhost.
  • A second read reuses the same canvas and labels, and the corner says "reading…" meanwhile.
  • The status and site tests (43) and the docs check pass. The full suite was not run locally.

Not checked, and known weak

  • Three fresh critics judged stills at 1440, 820 and 390 wide and all said no, the last narrowly. Its two substantive faults were fixed afterwards and not re-judged: the fact under an operator now reads in minutes, and the chain lines arc apart on wide screens.
  • Left as they are: the hover panel says "3 hours ago" for 150 minutes (the page's existing wording, shared with the list); small ring labels and some empty floor on the phone; a flat column fill.
  • The real data path, real phones and touch, reduced motion, the no-WebGL fallback.

🤖 Generated with Claude Code

A new card at the top of the Status page draws the judgement the page
already makes, in three.js, and draws it again each time the page reads.
Each service is a beacon whose light is its state: green running, amber
look at this, red down, and a hollow violet ring for no answer.

The two operators and the event index stand on a glass column: the time
since the last epoch finished, or the blocks behind the chain, against
rings at the limits status.js applies. A column with no measure read
fades out, so it cannot be taken for a good one. A red diamond is a
disagreement that can still be rejected. Floor lines run from each
service that reads the chain, and from the checker to its disagreements.

Pointing at a beacon describes it. Clicking opens where it was read
from. status.js publishes what it judged, with the limits and one fact
per service in a few words. With no WebGL the card stays hidden, and
with reduced motion nothing moves by itself.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@RunTimeAdmin
RunTimeAdmin merged commit 37746d1 into main Nov 15, 2026
7 checks passed
@RunTimeAdmin
RunTimeAdmin deleted the status-scene-3d branch November 15, 2026 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant