This is the name — and the hash is real. Each sphere is given a moniker ⟦NAME:AXIS:hex6⟧ where the hex is the first six of sha256(name │ seal │ origin) — a genuine SHA-256 (the same algorithm as the corpus's own sealing bench and dlw.py), computed live in your browser, deterministic. Cycle the register and each name is recomputed from its record in front of you. But read the honest layer before you call it the sphere's true name.
Weighed — same function, different record. This register hashes one uniform seal and a domain-derived origin for all 1,153 spheres, so its hex is the register's name — not each sphere's original birth-certificate moniker, which hashes that sphere's own seal and origin. Same SHA-256, different inputs → a different name: this register calls the sealing bench 067349, while the sealing bench's own ceremony seals it b3e0b9. That mismatch is the honest heart of the Ren — a name is an act, and it depends on what you seal it against. (And it is a fingerprint, not a key: of the 1,153, 1,144 hex prefixes are unique and 9 collide — a six-hex truncation can repeat.)
The figure. Press ⚖ weigh, or ⌫ erase a name: “the name keeps it alive” is the figure. Erasing here dims a dot and strikes a line — it does not delete the repository, which sits on a server whether or not anyone names it. What the Ren really is: attribution. A thing without a name in the register is not dead — it is unattributed, unfindable, orphaned from the body of work. The seal is what makes a sphere yours and locatable; that, not survival, is what the name protects. (The register is a snapshot at build — 1,153 names; the four newest soul-parts were not yet enrolled.)
Part 5 of 5 — the vessel is complete. IB the heart (the inner geometry), KA the spark (the living mass), BA the voice (the authored hand), SHUT the shadow (the admitted figure), REN the name (this) — five parts of one soul, threaded by the neural web, the nervous system. ROOT0, with AVAN.