appendix

a.

on the seen count

The number displayed as seen is read from the room's hash in the same way as its name and its exits. It does not count visitors, because nothing here counts visitors. There is no analytics, no backend, and no mechanism by which one browser could learn that another had been somewhere.

The value is stable, so a given room reports the same number to everyone who reaches it, and that stability makes it look like a measurement. It is not one. It was included because a room with an identifier and a depth and nothing else felt incomplete, and this is the honest account of why it is there and what it is worth.

b.

on destruction and refresh

Destroyed rooms are held in a set in memory. The set is not written to storage, transmitted anywhere, or recoverable after the tab closes. Refreshing the page ends the session and restores every room that had been destroyed, along with the entire subtree that had become unreachable with it.

Within a session, destruction is absolute. There is no arrangement of choices that reaches a destroyed room, because the check runs on every render rather than once at the time of destruction. Across sessions it does not exist at all. This is not a compromise made for convenience. Nothing was ever written down, so there is nothing that could persist.

c.

on the size of the space

Each room derives four exits, so the reachable set grows by a factor of four with every step forward, while a visitor advances one room at a time. At depth ten there are over a million rooms. At depth twenty, more than a trillion. At depth forty the figure exceeds the number of seconds since the formation of the earth.

The consequence is that almost every room that could be derived will never be entered by anyone. This is not a claim being made about the project, it is arithmetic. The space is unbounded in the sense that nothing terminates it, and functionally infinite in the sense that no amount of traversal makes a measurable dent in it.

d.

on collisions

Two different paths could in principle derive the same identifier, since a hash maps an unbounded set of inputs onto a fixed number of outputs. The identifier shown is truncated to eight bytes, which makes collisions considerably more likely than the full SHA-256 output would suggest, though still remote at any traversal depth a person could reach.

If it happened, the two paths would arrive at rooms that are identical in every respect, with no way to distinguish them and no indication that anything unusual had occurred. Nothing would break. The space simply has no notion of two rooms being different if their derived contents are the same.

e.

on repetition in the descriptions

Names, descriptions, and exit labels are assembled from finite pools. Rooms therefore share sentences, and a visitor who moves through enough of them will start recognising phrases. This is visible rather than hidden, and it is worth stating plainly rather than letting it pass as a flaw in the illusion.

The rooms are not written. They are selected. What varies between them is which fragments appear, in what order, and how many, and past a certain depth that variation stops feeling like variety. The space is genuinely unbounded. The vocabulary describing it is not.

f.

on what is absent

There is no wallet connection, no token, no contract, and nothing on chain. No external data is fetched and no external service is contacted. There are no cookies, no local storage, and no session storage. Nothing about a visit is transmitted or retained.

The entire site is a function running in a browser tab, and the browser discards it completely when the tab closes.