One community: r/PlaceNL
Follow one community from its public record and coding to its local model, its contribution to the population model, and its place among the final organizational forms.
What r/PlaceNL was
r/PlaceNL did not exist before the canvas opened. Its record starts at H27:40 with a post calling itself “the official coordination for placing pixels in Place”, and runs to the day after the freeze. In that time it published hourly plans, sent its planners to Discord, ran maintenance scripts, made pacts and broke them, handed orange ground back to communities it had displaced, and argued among its members over whether a Yeti should stay in its artwork. It wrote in Dutch and English. Its neighbours in the Dutch area were r/thenetherlands, the standing national subreddit, and r/cirkeltrek, its circlejerk.
The example, part by part
Each part has a page that opens with a short version, then the run's record in detail.
The Dutch area was built by many communities, and r/PlaceNL joined it on the second day. Its record starts with a post calling itself the official coordination. Most hands that built the area left no post in the community that claimed it.
In detail The Dutch area, hour by hour
Show this part in the instrument: 1 step
- The record: founded for the event, r/PlaceNL has 701 posts and comments from its first post at H27:40, none in the week before, and eight artworks in the atlas. The Dutch area, hour by hour
The record is silent until H27:40, so the account cannot say how the community began. Its first visible act is a declaration of official coordination. Codes, themes and the account below are the community coder's; the English in brackets is ours.
Short version When the codes fall · The plan and its venue · Building and erasing
In detail The coding · The case account · The chronology · The local model: R6
Show this part in the instrument: 6 steps
- 1. The briefing: r/PlaceNL was founded during the event, so the week before holds nothing and its brief is empty (the brief writer's contract).
- 2. Every thread: its 701 posts and comments sit in 101 threads; above 500 items, the gate split them between two fleet coders. r/PlaceNL: community coding
- 3. First-order codes: 246 codes on 228 items, in the members' words. The coding
- 4. Themes: 21 themes, from publishing and updating the current plan to fighting among the members over whether the Yeti stays. The coding
- 5. The case account: a case account of the community and a chronology of its event. The case account · The chronology
- After the coding: the local model (R6): the same coder built r/PlaceNL's own model; the aggregator did not use it. The local model
The aggregator never reads r/PlaceNL's posts. It reads the community coder's work, writes a note, and places each theme in the population's coding structure.
Short version The aggregator's note · From theme to dimension
In detail The aggregator's first reading · r/PlaceNL in the population coding
Show this part in the instrument: 3 steps
- Reading, A1: the aggregator wrote a note on r/PlaceNL before naming any common scheme. The aggregator's first reading
- Coding, B1 to B4: its 21 themes were placed among the population's third-order themes. r/PlaceNL in the population coding
- Model, C1 to C5: the model was built across all 705 communities. r/PlaceNL's codes lean to coordination without command and order without law (from theme to dimension); the model itself is on the population's page.
The population model went back to the coder who knew r/PlaceNL. Its answer about the canal houses came beside corrections from other communities that revised the model's account of repair; the aggregator then accepted it as a specification of the revised claim.
Short version The objection · The ruling
In detail The model goes back to r/PlaceNL
Show this part in the instrument: 1 step
Communities that asked for similar changes form a group. r/PlaceNL anchors the raids in form B and holds its scripts and chat too.
Short version Where it departs from its form
In detail r/PlaceNL in the final forms
Show this part in the instrument: 2 steps
- Forming, D4 to D6: r/PlaceNL falls in form B, Behind the thread, and departs from it in places. r/PlaceNL in the final forms · Where it departs
- Formalizing, E1 and E2: the audit and the aggregator's review cover the whole run; they are on the population's forms page.
English translations supplied with the artifact have not been reviewed by a Dutch speaker. Source hashes.