Eternal Haven

Home · Star Chart

Room · the public sky

The Eternal Haven Star Chart

A live sky of anchored seals: names, roots, and a hash pulse you can watch. What it is for, and what a chart does not prove.

Justin Helmer
Room guide · updated 6 November 2026 · about an eight-minute read

The Star Chart is the workshop's public sky. Each star is an anchor: a named piece of work whose file has been hashed and recorded, with the date and the root it belongs to. There are over thirteen hundred of them now, which is a number that means less than it sounds — many are small artifacts, and a count is not a quality. What matters is that a stranger can look at a star and check it.

This page was a redirect for a long time. If you landed here from a bookmark and expected to be moved, you still can be: the live chart is the interactive sky. What you are reading now is the explanation that should have been here, so that the room has a door with something behind it.

What a star actually is

A star is a record with three parts: a name, a digest, and a position in a tree. The digest is a hash of a file or a small pack of files. The position in the tree comes from a Merkle structure, which means a single root number stands for the whole set: change any file in the set and the root changes.

That structure is the reason the chart can be public without being a privacy problem. It publishes numbers and names, not contents. You can verify that a file you hold is the file that was anchored, without the chart ever storing the file. If you want the vocabulary, the glossary defines hash, Merkle root, and seal in the same plain language.

The hash pulse

The chart shows a live pulse: the current root recomputed on a schedule. It is a heartbeat, not a proof of liveness. A pulse that stops means the publisher stopped publishing, which is useful to know and also entirely expected when the publisher is one person with a laptop. I would rather show a pulse that can go quiet than a green dot that lies.

Where the chart lives, and why

The chart itself is hosted on GitHub Pages because it is a static page with a large data file and no server to keep alive. This domain, eternalhaven.ca, is the library: the place where the work is described and the argument is made. Splitting the two is not modesty. It is the same reason a printing press is not in the reading room.

There is also a room on this domain called the Star Chart room, which explains the anchoring practice in more depth and links the live surface. If the two pages ever disagree, the live chart wins on numbers and this page wins on meaning. That is the canon-versus-reference distinction the house uses everywhere: a chart is a report, an essay is a claim.

How to read a star

Start with the name. If the name is a book, the digest is probably the manuscript or the ebook. If the name is a skill or a champion pack, it is a bundle of small files and the digest covers the pack, not each file. Then look at the date. A star is a snapshot: it says what the file was on that date, not what it is now. If an author keeps editing a file, the star stays true to the older version, which is the correct behaviour and surprises people.

Then check the root. If you are comparing two stars from the same pack, they should share a root. If they do not and the dates are the same, something in the set changed between the recordings. That is not necessarily a scandal; it might be a typo fix that re-ran the whole tree. But it is information, and information is the point.

What the chart does not prove

It does not prove the work is good. A hash is indifferent to quality; a terrible manuscript hashes as cleanly as a great one. It does not prove authorship beyond the publisher's own claim, and it does not prove that no other copy exists. It proves that a specific set of bytes was recorded at a specific time under a specific root — and in a world of quiet edits, that is most of what a reader needs.

It also does not survive a change of host gracefully. GitHub Pages URLs move; a page that anchors to one is only as durable as the account behind it. That is a known weakness of every public ledger run by an individual. The honest mitigation is redundancy: the numbers are published in more than one place, and the essays describe what they mean so that losing a host does not lose the meaning.

Why keep it public at all

Because a private receipt is a diary. The value of hashing a manuscript is not that I can prove it to myself; it is that you can check it without asking me. That is the difference between a claim and a record, and it is the only reason a small publisher can play the same game as a large one.

If you have a star you cannot read, write to me with the name and I will explain what it covers. If you want the practice rather than the sky, read How a book gets a hash.

Justin Helmer

Writes the Eternal Haven saga and the essays on this domain, publishes music as Excavationpro, and keeps the lantern on at /start.html.