Skip to content

Show where each agent slash stands as a room on the slashes page - #315

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

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

Conversation

@RunTimeAdmin

Copy link
Copy Markdown
Owner

What

A new card at the top of the Slashes page draws the proceedings the page has already rebuilt, in three.js (the vendored r170):

  • a pad where every slash is filed, and three floors (open, executed, dropped) with a count each
  • one capsule per slash, standing where it is now, with an amber band if the operator disputed it and a white halo if the admin vetoed it
  • an executed slash drawn as its stake, split to scale into burned, paid to the victim and paid to the member who filed it
  • a replay that sends each slash off from the pad in the order filed, with the counts following what is over each floor

Pointing at a slash describes it. Clicking scrolls to its entry in the list and outlines it. A key under the room names each part and says the replay shows order and outcome, not duration.

slashes.js publishes what it rendered and gives each entry an id. Without WebGL the card stays hidden. With reduced motion there is no replay.

The description panel shared with the Operators room now draws over labels with an opaque background.

Checked

  • Exercised locally against the real six slashes (this page needs no stub).
  • Clicking a capsule scrolls to and outlines the matching entry.
  • Site tests (57) and the docs check pass. The full suite was not re-run locally.
  • Judged from stills at 1440, 820 and 390 wide by three fresh critics (no, no, yes). Three small changes made after the third were not re-judged.

Not checked

  • Real phones and touch, reduced motion, the no-WebGL fallback.
  • More than a handful of slashes per floor.

🤖 Generated with Claude Code

A new card at the top of the Slashes page draws the proceedings the page
has already rebuilt, in three.js: a pad where every slash is filed, and
three floors (open, executed, dropped) with a count each. A slash is a
capsule standing where it is now, with an amber band if the operator
disputed it and a white halo if the admin vetoed it. An executed slash is
its stake, split to scale into what was burned, paid to the victim and
paid to the member who filed it.

A replay sends each slash off from the pad in the order they were filed,
and the counts follow what is over each floor. Pointing at a slash
describes it; clicking scrolls to its entry in the list and outlines it.

slashes.js publishes what it rendered and gives each entry an id. With no
WebGL the card stays hidden, and with reduced motion there is no replay.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@RunTimeAdmin
RunTimeAdmin merged commit 75d6406 into main Nov 15, 2026
7 checks passed
@RunTimeAdmin
RunTimeAdmin deleted the slashes-scene-3d branch November 15, 2026 21:35
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