# r/sweden ## Selection The gate assigned branch B because the room exceeded the fixed threshold. Eighteen whole-thread slices were read in corpus order; I consolidated their 835 first-order codes, reviewed each slice account and the pooled code record, and grouped practices incrementally. This is consequently a case-level synthesis of bounded readers, not one person's continuous reading of the week. ## Chronology The window opens mostly on ordinary Sweddit business, with a lone call to regroup at `(600, 80)` in `62c5rf`. In batch 02, `62mukf` becomes a workroom: participants invite a common effort, start a flag, correct its cross, request a sticky, negotiate surrounding art, and move planning to Discord and r/SwedenOnPlace. The early canvas episode runs from `62mukf` to `62nkjh`. Across batches 03–07, building becomes shift work. People clean wrong pixels, repair the cross and text, debate expansion versus a defensible “lagom” flag, and hand maintenance from night to morning. At the same time they negotiate with South Africa, r/airforce, the Dutch, Maryland, Norway and many smaller drawings. The timed Operation Lilla Bält episode, from `62s3ii` through `62v4u2`, includes planning, a 16:00 attack, reported success, Danish recovery, correction and renewed defence. These are successive and competing practices, not a single community decision. Batches 08–15 show the room acting as contested territory and as shelter. Visitors ask for protection or space; participants alternately refuse, bargain, accommodate and repair. Moderators repeatedly refer standalone r/place posts to the sticky and r/SwedenOnPlace. Operation Dalahäst in `636a8n` is especially revealing: users initially erase an unrecognised design, then apologise and help after its plan is explained; a renewed horse call in `6373ni` remains unresolved in that slice. The final transition runs from live truce, attack and build calls in `637fgl` to retrospective threads in `63enmi`. After placement ends, participants preserve albums and videos, thank allies, continue the r/forsen argument, propose using the flag as a banner, and turn the Maryland relationship into reciprocal flair and jokes about annexation or personal union. Ordinary questions, news and moderation again dominate the late slice. ## Themes ### Building, repairing, and decorating the shared canvas These codes share hands-on care for a finite picture: placing pixels, correcting proportions, cleaning damage, adding Knugen, fika, hearts and horses, and deciding what may occupy the flag. What varies is whether speakers prioritise expansion, a spotless defensible flag, or coexistence with smaller art. ### Rallying attacks and mounting defence Participants turn threats and openings into musters, timed attacks, counterattacks and watch shifts. The targets and outcomes vary, and martial joking sits beside genuine repair labour; a peace call followed by an attack call is contrast, not proof that the community changed its mind. ### Making peace, bargains, and room for neighbours People negotiate borders, hearts, refuge, reciprocal protection and restraint. Some offers invoke ordinary kindness—“the big must be kind” in `635mr2`—while others are conditional bargains, such as help in exchange for protection. Refusals and unresolved requests belong to the practice because negotiation does not guarantee settlement. ### Moving plans and coordinating the work Times, templates, scripts, polls, Discord and r/SwedenOnPlace are used to make dispersed pixel work legible. Plans sometimes return to Sweddit, but recognition and compliance vary: `dfq6cj9` says “Discord gruppen har röstat fram” a latest plan, while `dfq2akw` says too many people still preserve the Dutch hearts. ### Redirecting and policing the room Moderators route r/place talk to a sticky or dedicated subreddit while also enforcing ordinary rules on duplicates, surveys, spam and titles. The repeated template establishes a policy and destination, not compliance or effects inside the unseen venue. ### Turning the event into jokes and memory Participants name battles, celebrate and mock, thank allies, save albums and videos, and convert relationships into flair and union jokes. The memory is not uniform: finished artifacts coexist with reopened blame about r/forsen. ### Keeping ordinary Sweddit life going Questions, news, politics, advice and subreddit housekeeping continue around the event surge. These varied small practices are grouped only as the ordinary room activity against which the canvas mobilisation appeared; no stronger common practice is claimed. ## Relations The clearest supported relations are local. In `635gt3`, a participant reports a Danish invasion; the reply `dfrhduz` answers “Vi måste gå till motoffensiv,” explicitly turning the report into a counterattack call. In the Dalahäst exchange, `dfrmv3s` asks how information should spread, `dfrmw67` answers via r/SwedenOnPlace, and `dfro8ll` says the approved plan was brought to Sweddit “för att försöka få alla att samarbeta.” That supports an attempted coordination link, not successful coordination. [crosses 14|15] Other sequences remain sequences. Repeated referrals follow proposals, and later posts sometimes move elsewhere, but the record usually does not say the referral caused the move. Similarly, victory claims, flag correction, alliance proposals and renewed defence follow one another after Operation Lilla Bält without establishing that each caused the next. ## Posts against comments The posts often issue terse proposals, alarms and commands; comments supply practical negotiation, correction and refusal (batches 13–15). The posts say occupants are “trash” or demand that people stop or defend; the comment layer says polite requesters deserve room and “the big must be kind” (`635mr2`, batch 14). Posts present peace and “NO PEACE” as competing imperatives, while comments debate terms and feasibility (batch 16). Post-event posts present polished final images and thanks; comments reopen r/forsen blame and turn alliances into travel talk (batch 17). These contrasts show simultaneous positions, not a community-wide reversal. ## Counter-reading My reading is that coordination remained distributed and repeatedly had to be translated between Sweddit, Discord and r/SwedenOnPlace rather than becoming one stable command accepted across the room. If that reading were wrong, the corpus would contain participants naming one settled plan, treating it as authoritative, and reporting broad compliance rather than continued overwriting, rival designs and requests to stop. The strongest contrary item is `dfq6cj9`: “Discord gruppen har röstat fram att detta ska vara vår senaste plan,” followed by a request not to remove the crown. Searching the case vocabulary for approved plans, Discord decisions and cooperation also returned `dfq2akw`, where the speaker says the design was marked as the Discord plan but too many people were still preserving Dutch hearts, and `dfro8ll`, where an approved plan was brought to Sweddit only “för att försöka” get everyone cooperating. The contrary item therefore changes the account by establishing real moments of collective decision; it does not overturn it, because the same record shows contested recognition and incomplete compliance. The search also returned many irrelevant ordinary uses of “plan” and “bestämt”; their null value is scoped to those hits, not to the whole room. ## Saturation All seven themes first appear by batch 02 except post-event memory, which becomes distinct later; subsequent slices mostly extend settled practices with new targets and artifacts. Later slices nevertheless add genuine developments: moderator-backed venue separation, explicit Maryland bargains, Dalahäst's information failure, and post-event flair and commemoration. The record is not socially whole. Removed bodies and unavailable images obscure proposals, long threads continue outside slice windows, and Discord, private messages, polls and r/SwedenOnPlace are visible mainly through what participants bring back. No reader held the whole week, slice boundaries can split exchanges, and the forest establishes reply sequence rather than causation. These limits weaken claims about agreement and off-platform deliberation but not the visible practices of moving coordination, repairing, bargaining and remembering. ## Other communities named Other communities function as neighbours, targets, allies, claimants and organising venues. Maryland is negotiated with, trusted for overnight protection and later thanked; Arch Linux is repaired and defended; Danish, Dutch, Norwegian, South African, r/airforce, r/forsen and many small-art communities become changing objects of attack, accommodation or dispute. r/SwedenOnPlace and Discord are different: participants use them as coordination infrastructure, while this corpus sees only what is referred outward or reported back. ## Absence Many short mobilisation posts retain only a title because bodies or images were removed. Surviving replies still show whether people resisted, redirected, negotiated or helped, but cannot reconstruct the missing design. The late return to ordinary traffic does not establish that off-platform canvas discussion ended; it establishes only that retained r/sweden discussion became retrospective and sparse.