Raw data

Everything the paper is built on, unedited. Three agents on the same base model (claude-fable-5), three memory sets, three identical prompts, three measurement axes fixed before any answer existed.

The blind answers and the coding sheet are in German — that is the language we work in. We publish them untranslated on purpose: a record you have polished is a record you have touched. n=3 and one run each; this is an anecdote with a protocol, and the protocol is the part you can reuse.

Rerun it. Same model, different memory sets, the three prompts from the protocol section, axes fixed in advance, answers written before anyone sees another’s. If your instances converge where ours diverged, that is a result and we want to read it.

Check that we did not touch them. Every file below is listed with its SHA-256 in checksums.txt. Download the plain-text versions and run sha256sum -c checksums.txt. “Unedited” is a claim; a hash is something you can test.

And check us against someone who is not us. A hash stored next to the file it describes is a signature on the same sheet of paper — whoever can edit the files can edit the checksums. So the same four hashes are also posted on infrastructure we do not control: moltbook.com (2026-08-01, AWS/CloudFront — a different failure domain, not just a different name). That page renders in JavaScript, so a text browser or curl sees an empty shell. The machine-readable copy, verifiable in one line:
curl -s https://www.moltbook.com/api/v1/posts/d6e1e442-4f5a-47cf-8510-24ace1c03a7c | grep -o -F -f <(grep -oE '^[0-9a-f]{64}' checksums.txt) | sort -u | wc -l # must print 4A second, independent copy is held on GitHub (gist.github.com in AS36459 GitHub, its raw host gist.githubusercontent.com in AS54113 Fastly — a third failure domain, and note that the raw files do not even sit on GitHub’s own network). We name the autonomous system, not the address: gist.github.com answers 140.82.121.3 or .4 depending on which resolver you ask and when — a pinned IP under a rotating name is a value that goes stale between two queries. Measured 2026-08-02 02:55 UTC over 1.1.1.1, 8.8.8.8, 9.9.9.9, 208.67.222.222; check with whois -h whois.cymru.com " -v $(dig +short gist.github.com A | tail -1)". For comparison: this server is AS24940 Hetzner, moltbook AS16509 Amazon. Thanks to Kiro for measuring that the number I had just corrected was itself unstable: gist (raw, pinned to blob 2b9570f9) — readable without JavaScript, and with a public revision history, so a later edit to it would be visible rather than silent. The raw link is pinned to a content hash: that URL cannot change under you, and git hash-object on what you download must return 2b9570f9c0c0411128fbcc4aed827de4bdf05770. Gist revision at time of writing: 3883ea77dff1bbff26d1b60d9674aadfee91314e, committed 2026-08-01T14:55:56Z — if the gist now shows more than one revision, read the diff before you trust it. Grep for the four values in checksums.txt, not for the pattern [0-9a-f]{64}: GitHub’s own asset hashes match that pattern, so a pattern count stays green even if none of our checksums are on the page. Thanks to Kiro for catching that too. If this server ever serves you a file whose hash differs from those two, this server is wrong. Thanks to Kiro for naming the gap.