Trace one claim down to the Reddit text
Historical worked example, reproduced from the earlier manual. Its paths and commands describe that recorded run, not a new launch. Original manual page · Exact Markdown.
For a reading-only route, browse saved checkpoint outputs. Those checkpoints are separately dated records, not proof that they reproduce this earlier example.
Trace one PlaceNL quote to its archived code and source thread, using the shared R6 checkpoint.
Participant handles in these reading copies use the pixel stream's identifiers: base64(SHA1(username)), case preserved, without a salt. These are linkable pseudonyms. Profile links are removed; missing-author markers remain. Original research files are unchanged. Quote offsets refer to original text. Source and reading-copy hashes are listed separately.
Reading Markdown with participant IDs. The linked original manual retains its recorded text.
Kind of page: tutorial: about ten minutes, with a terminal and
zstd (brew install zstd on macOS,
apt install zstd on Linux). Run the commands from the
repository root.
A qualitative reader asks of any claim: which words, said by whom, and read how? This page follows one claim of the r/armenia case from the coder's account down to the Reddit comment it rests on. Every coded claim in the study can be traced the same way, and the aggregator's store carries the same code, so a claim of the model can be followed down through it too.
1. The claim, in the case account
case.md is the case lead's account of the room's week;
it sits at out/case.md inside the room's run, which step 2
opens. For r/armenia it says, in its chronology:
dfp16peannounces an alliance with r/greece in which "They will help us and we will help them."
The backticked id is a Reddit item: a post (six characters) or a comment (seven). An account may only cite items its coders read; the gate checks this before the room is verified.
2. Open the room's run
mkdir -p /tmp/armenia && zstd -dc coder/rooms/armenia/run.tar.zst | tar -x -C /tmp/armenia
cd /tmp/armenia/runOn Linux, GNU tar prints lines about an unknown keyword
LIBARCHIVE.xattr.com.apple.provenance: the archives were
made on a Mac, and the lines are harmless. out/ holds what
the coders wrote; coder_corpus.jsonl is the record they
read, one Reddit item per line.
3. The code behind the claim
grep '"item_id": "dfp16pe"' out/codes.jsonlreturns code c0006: first-order label "getting an
alliance with r/greece", theme t03, thread
62qqvs, characters 0 to 25 of the item, and the quoted
passage I got us in an [alliance].
4. The theme the code belongs to
grep '"theme_id": "t03"' out/themes.jsonlt03, "asking neighbours for pixel help and returning
it", groups 23 codes. This is the coder's second-order theme, bound to
this one case; the themes across cases are the aggregator's work (for
reviewers).
5. The words in the record
grep '"id": "dfp16pe"' coder_corpus.jsonlreturns the comment as the archive holds it: a reply in thread
62qqvs (parent_id t3_62qqvs),
written 2017-04-01 15:41 UTC, whose body begins
I got us in an [alliance](...) with /r/greece. They will help us and we will help them fight against invaders.
(the link, to an r/greece thread, shortened here) Characters 0 to 25 of
the body are exactly the code's quote. The gate's check C3 made this
comparison for every code in the room.
6. That the coder read it
out/_read.jsonl logs every call to the reading tool, in
order. Its entries 10 and 11 serve the post 62qqvs and then
the comment dfp16pe; the gate's C9 checks that every code
sits on an item the tool served.
7. On Reddit
permalink in the record is
/r/armenia/comments/t3_62qqvs/dfp16pe, in the archive's
form; on Reddit the same comment is at
https://www.reddit.com/r/armenia/comments/62qqvs/_/dfp16pe/.
It may have been deleted since; the archive keeps it as it was taken in
2017.
From the aggregator's side
The aggregator's store holds the same code:
aggregator/runs/claude-v43-1/00_GIVE-THE-AGENT/package/store/codes.jsonl,
sub armenia, code_id c0006, with its text. A
third-order theme the analyst builds lists the second-order themes it
groups, and each of those its codes, so any claim of the model leads to
codes like this one and down the steps above.
Historical text hashes
Original SHA-256: f500e724d612fb472c06835497c8e6c6d4854b72c329272cb740cc8ed1fb7047. Reading-copy SHA-256: f500e724d612fb472c06835497c8e6c6d4854b72c329272cb740cc8ed1fb7047.