## Chronology

When the canvas opened, cirkeltrek was already turning its own subreddit into an April joke. From `62mify` at d0 03-31 17:09 (“Heil🇩🇪zaam🙏”) through `62s99y` at d0 04-01 11:49 (an anti-Protestant answer to removing the Spain theme), people joined or resisted Spanish and German styling, demanded the old picture back, and played ordinary 1 April pranks. This was conduct in the room, not conduct on the canvas.

Canvas work appears inside that episode. `62mzbr` at d0 03-31 18:18 says “Er is te weinig oranje op /r/plaats,” and people then recruit placers, publish coordinates, lay out the Wilhelmus and subreddit names, and correct spelling and spacing. The episode from `62mzbr` through `62ul04` at d1 04-01 18:39 includes exact-pixel plans, a synchronized A-to-O repair in “Nassouwe,” windmill construction, and repeated disputes about whether to expand or finish the drawing. The “muur der schaamte” in `62s6zh` names people who keep changing O to A; the plan post `62sk70` supplies “exacte pixels”; and `dfp8e7z` reports “De eerste molen staat.” These are attempts to maintain shared work, not evidence that every Dutch placer followed them.

The next episode, `62umog` at d1 04-01 18:47 through `6300y1` at d1 04-02 14:52, intensifies the conflict between expansion and restraint. Its opening “kutgrieken” is followed by calls to annex Greece, Armenia, GreyBlob, Turkey, and nearby pictures, while other participants ask for peace, borders, alliances, and room for cats, dogs, and flags. Alongside that conflict, people continue proposing lions, portraits, text, and windmills and route current plans through Discord. The episode inherits unfinished Wilhelmus and border work across the batch 01|02 boundary, but lies within batch 02; the record does not show one speaker or decision causing the community-wide contrast.

From `6301n9` at d1 04-02 14:55 through `637ugl` at d3 04-03 16:26, the inherited project continues through new attack calls, borders, scripts, night defence, alliances, and designs. People ask for houses, a ship, provincial flags, mottos, a beer bottle, a “kaaskat,” and a final plan, while visitors ask them not to overwrite GreyBlob, Yeti, Pusheen, and other work. The recurring pattern is not a settled turn from conquest to care: different speakers continue to demand both.

Placement ends before `6383mq`, which at d3 04-03 17:05 says “/r/place is opgehouden.” From `6383mq` through `63esf5` at d3 04-04 15:27, participants mourn, celebrate, thank placers, argue with angry visitors, recount the result, and preserve it as a header, wallpaper, timelapse, and compilation. `6385tk` makes one response explicit: “PLAATS IS DOOD TIJD OM WILLEM TE PALEN.” Later, `63dplh` calls pxls.space “r/plaats … terug(soort van),” and `63eg3x` calls people to “blijven strijden” there. The first pxls.space invitation follows `6383mq` by 19 hours 4 minutes 41 seconds, and the second follows the first by 2 hours 21 minutes 32 seconds. That is an observed redirection within the window; the record does not show whether it lasted.

## Relations — what set off what

The clearest response chain turns repeated spelling correction into public accountability. `dfot8bg` proposes: “Als we iedereen taggen in een soort wall of shame zullen ze hopelik stoppen met verkeerd verbeteren.” Its direct answer, `dfotaa3`, says “Doen we! Ik maak er een topic voor aan!” The later topic therefore answers a named proposal; reply position alone is not the evidence.

Armenia’s request produces a revealing answer. `62vffi` asks the Dutch to “spare Armenia the fate that Greece has befallen.” `dfpe692` replies, “We have no control over our people so this can probably not be stopped. Get out while you still can.” The request set off an answer, but the participant’s own explanation supports inability to control expansion, not successful restraint.

Pusheen’s appeal produces both apology and a protective proposal. `62z31i` asks, “Please stop invading Pusheen.” `dfq3eb2` answers that some placers are trying “to make a tri-color ribbon to dam us in,” and `dfq3f11` says the plan is to shorten the flag and make a border: “We won't remove them.” This supports a negotiated response in that exchange. It does not establish that all placers complied or that the canvas outcome followed.

The shutdown explicitly sets off a return to ordinary posting in `6385tk`: “PLAATS IS DOOD TIJD OM WILLEM TE PALEN.” The later pxls.space invitations `63dplh` and `63eg3x` follow the shutdown and name a substitute place to continue. I report the measured sequence above; the corpus does not support a durable migration or a causal claim about later participation.

No causal relation is carried across a slice boundary. Cross-slice continuity is used only to describe sequences of still-active practices; every relation above rests on words that answer or name what came before.

## Posts against comments

The post layer repeatedly presents commands as settled collective action, while comments expose disagreement and limited reach. In batch 02, `62uvxr` says “ANEXEER ANEXEER ANEXEER” while Greece sleeps; in batch 01, the comment `dfp0v4a` says there is a peace treaty and “geen enkele reden om dat te schenden.” This is a descriptive contrast between speakers, not evidence that the community changed its mind.

Posts also make plans look definite. In batch 01, `62sk70` publishes “exacte pixels”; in batch 02, the comment `dfq262s` asks what the current plan is and says it cannot be found, while `dfq46nw` explains that “te veel mensen” do not follow it. The comment layer supplies the participant explanation for why published coordination remained partial. It also records repair work: `dfrtvj6` says most of the writer’s tiles repaired nyancat from random pixels.

Neighbor petitions live mainly in posts, while negotiation and limits often appear in replies. `62vffi` asks for Armenia to be spared; `dfpe692` answers that “our people” cannot be controlled. `62z31i` requests protection for Pusheen; `dfq3eb2` and `dfq3f11` answer with a proposed ribbon and shortened flag. Conversely, many claims about what an image showed live only in image-post titles. They are claims by posters, not direct observations of the external image.

After shutdown, the post layer converges on ending and preservation: `63893y` says “WIJ DEDEN HET,” `638n4t` thanks “kameraden” for their work, and `63911t` shares a timelapse. A contrary visitor post, `6387s7`, still condemns the Dutch placers. Celebration and condemnation coexist; neither proves a single collective assessment.

## Counter-reading

My one-sentence reading is: cirkeltrek used royal and local language to recruit, build, correct, defend, and remember a Dutch canvas project, while its public plans remained partial and were continually contested by attack calls and neighbors’ requests.

Before searching, I wrote that this reading would be wrong if the corpus instead showed mainly uncontrolled orange expansion dressed as jokes, with people explicitly ignoring plans or agreements and participants unable to control placers.

The strongest contrary item is `dfpe692`: “We have no control over our people so this can probably not be stopped.” The targeted search then found `dfq46nw`, which says “er zijn te veel mensen die het plan niet volgen,” and `dfq5646`, where a struck-through Discord agreement to leave the left side alone is replaced by “Het plan is veranderd! Oorlog met de Armenen!” `dfq262s` also cannot find the current plan. These items rule out an account of cirkeltrek directing a unified Dutch force.

The competing account does not erase visible maintenance and negotiation. `dfotaa3` acts on the shame-wall proposal; `dfq3eb2` proposes a ribbon to contain expansion; and `dfrtvj6` says most of the writer’s tiles repaired random damage. The revised reading therefore survives as attempted, hands-on coordination with limited control, not as successful collective governance.

Two narrow searches—one for nobody reading/listening to a plan and one for no or absent coordination/control—returned no hits. A further English/Dutch inability-to-control search returned `dfpe692`; plan/change/ignore and random-action searches returned the contrary items above plus irrelevant name or wording matches. Those null results apply only to the queried phrases in this 97-hour record; they cannot establish absence in deleted bodies, external venues, or synonymous wording.

## Saturation

Selection saturation: all 321 threads were disposed by the three coders, with event-touching threads read in full under the common triage rule; the pooled record contains 281 coded threads. No selected long thread was abandoned at its window. Because one coder read each arbitrary slice, there is no agreement measure and no single reader held the raw week.

Practice saturation: batch 01 founded the nine practices of making the subreddit’s April joke, recruiting/routing placers, laying out content, publishing plans, correcting work, defending pixels, attacking/annexing, negotiating/protecting neighbors, and commenting on outcomes. Batch 02 repeated and extended those practices without founding another. Batch 03 repeated them and first introduced two practices made possible by the event’s ending: marking and preserving the stopped canvas, and moving pixel work to pxls.space. The eight late counter-reading/relation codes extended the existing plan, correction, and negotiation themes rather than opening a new practice.

The Reddit record is not the whole activity. Discord carried plans, scripts, and tactical decisions that return here only as reports or images; external images and video are not directly visible; and pxls.space continues beyond the temporal edge. Deleted and removed bodies break exchanges. These limits qualify the claims they touch, especially control, visual outcomes, and off-platform decisions, rather than making the textual record generally unusable.

## Selection

The case lead read the complete openings overview before the gate, then branch B was selected because the manifest exceeded the 500-item threshold. The lead did not read raw threads while the fleet ran. Three coders read whole-thread slices in corpus order, retaining explicit placement, design, repair, defence, negotiation, celebration, aftermath, and the subreddit’s separate April conduct. Ordinary posts without recruited event practice were excluded. After consolidation, the lead read pooled codes and slice cases in slice order, then used `find` and `read item` only during the prescribed counter-reading.

## Other communities named

Other communities appear as targets, neighbors, petitioners, and planning venues rather than one stable set of allies. `62rgz4` reports a Greek alliance; `62vffi` speaks for `r/Armenia`; `62w4r4` comes from `r/greyblob`; `62yu2z` proposes a pact with Goodboye; and `62ztpx` proposes a Norway–Netherlands pact. `631ex0` says the Czechs are friends, while other posts call for annexing them. `636vkr` asks `r/F1` for collaboration, and `637krj` asks for room for `r/hardstyle`. `63052u` asks people to upvote a thread in `r/russia`. PlaceNL and a Netherlands Discord are named as places for plans; what happened inside them is not visible here.

## Absence

All three slice accounts report no moderator-distinguished or sticky item in their assigned records. Participants nevertheless invoke “mods,” so those references remain participant reports rather than moderator speech. Deleted and removed bodies are frequent and sometimes leave only a title or replies; the long missing chain in `6331r9` particularly limits the script dispute. External images, polls, Discord discussions, video, and pxls.space activity are absent except for the words that point to them. Absence claims are therefore bounded to the supplied Reddit text and its window, not to the wider canvas or off-platform activity.