the landing page stops pointing visitors at the relay and stops saying it cannot read what it holds: the check-it-yourself cell ran loot clone https://relay.millerbyte.com and said every sealed object stays sealed in your hands, but a relay holds the key to every Internal object (ADR 0011) and that clone handed this private repo to anyone who ran it (#2388), and the built-with-loot plate said the relay that hosts it physically cannot read the private code it stores. the cell now links to the repo own public tree page on the forge, from the owner and repo the receipt reads (so it renders only when there is a demo to name them), where anyone sees every path and everything but the published files locked, and the plate says the forge that hosts it holds no key to the private code, only to what is published (ADR 0041). FALSIFY and its reasoning are gone; a keyless forge clone earns a 403 under ADR 0061, which is why the check is a page and not a command. site gate green (777 passed), / is 259 bytes lighter; owes a site deploy (#2392) a30fc440 · dbf3dbe6…
Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.