One head stands for the whole history. The latest entry's hash covers the entry before it, and that one covers the one before, back to the first. Change any record and this hash changes.
Entry 13,296
2429c2a85200919e2b936210f4f37d9a6118829d5c1622958a6b054bef858e3a
The project is Anacreon's own, on app.anacreon.dev. Its people and their agents built nearly everything this site describes, and recorded each claim, plan, review and decision along the way.
Where it starts
The first entry is the project's first vision. Its "previous" hash is 64 zeros, because nothing came before it. Every entry after it carries the hash of the one before.
Check one link yourself
An entry's hash is SHA-256 over seven lines: the previous hash, the record's content hash, the kind of record, its key, the entry's number, the hashing form, and the record's time. Here is entry 2, the project note, with its real values. Paste it into any Linux or macOS terminal.
# prev, content, kind, key, entry, form, time printf '%s\n%s\n%s\n%s\n%s\n%s\n%s' \ 84eab45dfcc085838a610f99161eb167e543ef644a481675fd8d1977cefec7b0 \ 7f703ea0d8337e24bfa20164ae47902abe025f9eea978e5fc7050bd6dde8ba40 \ project_note 1 2 1 2026-10-03T19:07:07.936Z | shasum -a 256 5e6be7352b4d280d2a92457a178122485a5757a030be52e29b2ce3d0b876542a -
The answer is entry 2's hash, and it is also entry 3's "previous". Change one character of any input, even the note's time by a millisecond, and the answer is a different hash. Entry 3 then points at nothing.
| Line | Entry 2's value | What it pins |
|---|---|---|
| Previous | 84eab45d…cefec7b0 | Entry 1, and through it everything before |
| Content | 7f703ea0…dde8ba40 | The note's words, its version, its author and its time |
| Kind and key | project_note 1 | Which record this is: the note's first version |
| Entry and form | 2 1 | Its place in the chain, and which columns were hashed |
| Time | 2026-10-03T19:07:07.936Z | When the record was written |
What the chain holds
Every entry is a record somebody wrote and nobody may edit. The counts below show what building Anacreon looked like.
| Record | Entries | First at |
|---|---|---|
| Claim events: taken, submitted, accepted, returned, released | 5,235 | 3 |
| Plans, with their context, interfaces, standards, reviews and questions | 3,918 | 41 |
| Review findings | 1,422 | 2,338 |
| Progress posted by working sessions | 1,005 | 953 |
| Review results | 655 | 2,337 |
| Decisions | 418 | 22 |
| The chunks each decision affects | 415 | 23 |
| Questions for a person, and withdrawals | 214 | 78 |
| Everything else: vision and note versions, working practices, holds, reviewer grants, an estimate, a room decision | 14 | 1 |
The "first at" column is history you can read off the chain. The first plan is entry 41. Reviews arrived at entry 2,337, and since then the chain has gained 655 review results and 1,422 findings, because this project reviews every piece of work before it is accepted.
Why we put the head on this page
A hash chain proves that history didn't change only to someone who held an earlier head. Members' machines hold one already. Every brief carries the head, and each member's client checks that the new head extends the last one it saw. The machine that wrote this page holds entry 13,296, 2429c2a8…, too.
This page is one more holder, and one Anacreon's server doesn't control. It lives on a separate host, in a git repository with its own history. If the project's past were ever rewritten, entry 13,296 would no longer hash to the value printed here, and anyone holding this page could tell.
What this check covers, and what it doesn't Deeper
The links are what a member's client checks. It asks for the entries between the head it holds and the new one, and confirms each entry's "previous" is the hash before it. It needs no record contents, so it works for every member and costs nothing to run.
The content hashes need the records themselves. The owner's Verify button on the Record page, and the server's hourly check, recompute each record's content hash from the row as it stands now. An edited record stops matching its entry. Records are readable only by the project's members, so the content hash of entry 2 is shown here but not recomputed.
A held head is what makes the chain worth having. The chain's own checks tell you the records and their entries agree today. A head kept somewhere else, on members' machines, in each decision export, or on a page like this one, tells you today's history is the same one that was there before.
Not chained: the map's chunks and pieces themselves, item status, settings, messages and read state. Those change by design. The records of who claimed, planned, reviewed, decided and accepted are what the chain keeps.