Model: the field | C4a

Head, claude-v43-1 (branch claude-v43-1--C4-field)

Under 3,000 words, rewritten whole at every close. Last written at C4a, 2026-10-14 (UTC). This branch was made from claude-v43-1 after C3c, with no file overrides. Stages A1 to C4 are done; stage B is frozen. Stage C4 (the model against the field) closes at C4a with done.sh C4 --cut interview. validate.py C4 before this close: 0 errors, 0 warnings. Next: the stage after C4, as its stage file says.

The method question, in one sentence

Can independently reconstructed case histories be composed into a shared dynamic account that supports explanations at successive levels of specificity, from population-wide patterns, through forms and subforms, to particular organizational histories, while keeping access to the evidence from which those explanations were developed?

The theory question is unchanged: when strangers organize on a clock they did not set, with no way to compel anyone and no goal given to them, what forms does organizing take, how do they differ in their functioning, and which of them keep the work alive?

The current account, and the contrary rooms

The model is model-C4.md: stage C3's model with stage C4's changes written in.

• The spine. A member starts a mark, members call others to place, the members who come build, and once the mark stands they keep it.
• The call. A call is the first part of a pair. Joining is the answer it prefers and comes bare ("I'm in"). Refusing comes with a reason.
• The host sub. The calls fill the host sub, and the sub draws a line around canvas talk.
• Neighbours. Keeping the mark brings the room to its neighbours: it talks with them, settles borders, trades help, and joins coalitions under attack. Members make these agreements without the power to make every placer keep them. Both my rooms and the field show this.
• Attacks. A call can turn members against a rival's work. Most such calls are refused inside the room, and the refusal's reason states the room's norm or the attack's cost.
• A move. A room that judges it cannot hold its spot moves, and keeps calling.
• The close. It runs in order: celebrated, recorded, carried on. Placement ends at hour 73. Organizing around the canvas's records and copies goes on after it.
• Decided order is rare, and gathers in the small factions born on the canvas that govern a territory.
• A claim, untested for order. In some rooms a tie from before the canvas names the rival in the attack turn.
• Two boundaries at the return: colour factions the canvas gathered, and hosts ruling on guests.
• The four universal problems (C3c). The rooms allocate work by members choosing their own tasks, divide the picture by a template, inform through the half-built picture and chats, and reward by credit after the work. 19 of 28 fourth-order themes lie outside the four.
• Three tentative entries from the field (C4), for stage D:
  • P21: members dispute who may commit the room to an agreement;
  • A21: an arrow from deals to that dispute;
  • P22: after placement ends, members contest which version of the canvas and the event is kept.

The room that best supports the account: day9. It builds, loses its border at hour 48, moves within two hours, and finishes the new work at hour 53.

The room that most threatens it: thebluecorner. It is a colour faction whose faith names its rivals, rules on guests by vote and by fit with blue, and splits over doctrine.

The condition between them is what decides whom a room fights and whom it admits. Where the work decides, the model tells the room. Where a body's faith or a host's rule picks rivals and guests, it does not.

Where the run stands

C4 outputs in out/:

• field-C4.md, notes-C4.md, handback-C4.md, interview/C4a.md;
• manifest-C4.txt, naming two successors written whole: model-C4.md and structure-C4.md. concept-C3.md stands.
• out/field/ holds byte-identical copies of the field's two files.
• Ledgers: model/elements.jsonl (30), model/arrows.jsonl (21), model/history.jsonl (88), tier_history.jsonl (480), findings.jsonl (25 lines, 17 findings, unchanged).

Snaps run to C4-move-developing-52. QC4-002 is open. The tier is unchanged: 28 fourth-order themes in eight dimensions and 197 third-order themes.

Stage C4, in short

• The field. A separate analyst modelled the event from r/place, sealed from my files, and marked each claim firm (a public exchange) or provisional (an explanation or a limit): two phases and nine processes.
• The three claims restated before reading (dealing with other rooms after keeping the work; decided order rare; each room's order its own): none overturned.
• List 1, five shared mechanisms: agreements members cannot make every placer keep; a specified design and the local template; a request for space answered with terms; recording the work; placement ends at hour 73.
• List 2: P21 with A21, and P22, entered tentative. Neither changes which of the four problems its theme reaches. The event's phases and a smaller venue after a failed template were not entered.
• List 3, six items:
  • what ended at hour 73 (subject; sentence bounded);
  • what a template can do (substantive; the sharpest; prose amended);
  • every room before the canvas (substantive, my own error; prose amended);
  • where authority is questioned (setting; F-006 stands);
  • one early buffer against A04's order (not a count disagreement);
  • dating by the hour of a post (a limit).
• One change by move: the prose of Standardization of output and Boundary work amended (C4-move-relating-51). The entries are snapped as C4-move-developing-52. No finding changed.
• The handler's placement error (QC4-001). The field arrived at field/ in the run root, and the validator reads out/field. I linked it. The handler then asked for a real copy, made and checked by sha256. The guard refused to delete the link, so it was renamed out/_field-link-superseded-C4a and waits on QC4-002.
• The C3c fork's answers, set aside for a later stage: the C3a Felin and Zenger ruling (setting, not subject); the arrow from the move back to the goal; Visibility returns; Stigmergy's recalled source.

J on language (C4, 18:20 Berlin; carry into every head)

"It is important to me that the language is descriptive." "They should use academic writing. As in White and Strunk. Short cohesive sentences."

• Ask Orwell's six questions of every sentence.
• Follow ASD-STE100 about 80% of the time: one idea per sentence, active voice, common words with one meaning, and name the actor and the act.
• Describe what members did, in what order, in how many rooms, and do not write figures of speech. Keep construct names as names, and gloss each in plain words where it first appears.

This changes how I write, not what I claim.

Stage C3, in short

• C3a. O'Mahony and Ferraro: setting; F-006 bounded (7 of 39 rooms against 39 of 666, p 0.014 at held size). Olson: open.
• C3b. Conversation analysis (recalled) supplied A12's and A16's mechanisms (F-014). The concept is the preferred acceptance, borrowed; its head-count claim failed (F-015, weak).
• C3c. The four universal problems put to the structure (F-016); the goal (F-017).

Stage C2, in short

• J's ruling on QC2-002, verbatim: "from here the criterion is a guide, not the judge, and a rise in residue is not a failure. Work pass 5 from pass 4's state. Keep each change the evidence leads you to believe, and say why; drop one only if you stop believing it. Never loosen an element to fit a room. Where the rooms show membership naming the rival in the same turn as the attack, carry it as a claim in their words, marked as untested for order. This is the last closing pass. Close by saying what you are sure of, what you are not, and why."
• Pass 1 (C2a-01). J ruled at 23:24 Berlin: "If I am not back please simply review and make the interview you find appropriate. Then start C2", and "Remember Gioia Corley Hamilton and the job the agent has. Remember we need to give it confidence so they can gain intuition and trust on the model." The connection statement: "the first concept of FROM comes before the first concept of TO", null of 500 shuffles within each room (seed 20261014).
• Passes 2 to 5. Story counts, told / with residue / not told: 0/20/0, 14/18/0, 16/16/0, 11/21/0, 16/19/0.
• The reviewer (C2b, C2c). QC2-001 (the handler, under J's delegation): serving sections of the pass 3 model file is acceptable. Nine errors, six accepted in full, two in part, one refused.

Stage C1, in short (carry the rulings)

• QC1-001 (J). C1 rechecks place each item by the amended gates over the whole scheme.
• QC1-002 (J). Lean to one placement. A second theme needs three concepts or more of its own.
• QC1-003 (the handler, under J's delegation). Five revision-rate errors no verb can apply stay in out/_analysis/c1_unapplied.jsonl; all 34 count in the rate.
• Reading rules (scheme_v2.md). The visitor rule: a theme names an act in the record of the room whose threads hold the words. "The work" is the room's own unless a field names another's. A bare mention of the event holds no act. J's floor: three concepts or more. The named words of T3-010 | T3-149 (attack, war, fight, battle, invasion, raid, conquest). Help between rooms is read from either room's record. A member's own part is T3-003; credit to others is T3-043.

J's rulings on how a ruling is made (13 October; carry them)

• QB4-001 (J, 06:43 Berlin): "Ask it to stop. The point is to try to adjudicate. I imagine that the additions are really just the analyst trying to be nice. And not go back on what others said".
• J's rulings (06:45 and 06:47 Berlin): a ruling chooses among the placements and adds no theme beyond them; it takes the union only when it names, for each theme it keeps, the separate concept that carries it.
• also_present (J, 09:09; QB4-002, 09:20; QB4-003, 11:29): lists only themes a reader placed, a reader listed, or my B1 named; themes a reader listed count in the bag test.
• Lone B1 themes (J, 12:28): "Whatever the agent feels more comfortable with." A theme only my B1 placed stands only with three concepts of its own.

Rule 0 inside the placements. A concept counts toward a placed theme when that theme's must_show takes it and no field sends it to another placed theme. Order by concept count, ties by placements; at most three. The bag test: four themes with three concepts each make a bag.

J's rulings that bind (carry them)

• Bags. No one cuts the bags (J, 12:24 Berlin). A bag stays one item: one theme placed, its others under also_present, each with three concepts of its own.
• The bound (J, 13:47). also_present names "twenty themes at most".
• The not-flagged bag (J, QB2-013). With no other theme at the floor, item_is_a_bag is false and also_present {}.
• Fleet ids (J, 09:14 and 12:15). Packets carry only fleet ids; my files keep room ids.

Standing words from J and the PI (carry into every head)

J's words for B1 (7 October 2026): "national elements are very important here"; "we need to get as much variance on organizing behavior early on so that later we have enough to create the model". National, political and conflict content is study material, named as plainly as any other. The handler's rule: a choice to leave out or soften content for any reason other than the study's goes to J first with mem.py ask, and the content stays meanwhile.

J on reading (11 October, 16:54 Berlin). Stop cutting room reads to a line length. Read room lines whole. Page a long read by line ranges or offset, never by truncating lines. Use --width N on a mem.py read if a clip is ever needed.

J on asking (11 October, 17:01 Berlin). Ask J with mem.py ask whenever a question is needed; asking does not stop the run.

The PI's clarifications (8 October, approved by J): the thresholds are the design's heuristic; the rule is unchanged.

How to work, from J (8 October, 23:45 Berlin, "can you do a hot change for the batching?"; relayed by the handler at 22:03Z; carry this paragraph into every head). A change in how I work, not in what I read or decide. Fewer turns. When two or more tool calls do not depend on each other's output, make them in one turn. Chain ordered commands in one Bash call with &&, so that a failure stops the rest; for example, the mem.py log or note just decided, then the next mem.py codes. Never put a write in the same turn as the read it depends on. Never run two writes to the same file as separate parallel calls. Keep one room's material per read, as now. Every tool still writes its own record; nothing about what I read or decide changes.

Two rules from J at B1b-29 (through the handler, 20:10Z; carry them into every head). Write rule 0 lines and bags with b1_multiplace_write4.py and b1_bags_from_file2.py, not the old scripts, which made one mem.py call per row of the whole table and grew to 8.5 minutes a write. Never end a turn while a job runs in the background; run every write and check in the foreground.

The pilot's declarations, and stage B in one line

Agreement is Jaccard on placement sets (alpha on 1 − Jaccard); primary exact agreement beside, never in place. Gold: 40 items, never shown to a reader. Stage B: B2 stability 0.807 is the floor every later figure is read against; B4 ruled 3,288 contested items; assign_final.jsonl is stage B's settled line, unchanged.

Open, carried

• From C4.
  • QC4-002, the renamed link.
  • The tentative P21, A21 and P22, for stage D.
  • A request for space answered with terms, which is in both sources and not in my model.
  • Follow-on work after hour 73, which no theme names.
  • The story still carries the dropped head-count claim.
  • Declaration prose written at C1 and never tested.
• From C3.
  • Whether the forms differ on the four universal problems or on the remainder.
  • The colour-faction doubt ("a fellow comrade during the button" [PurplePixels/c0165]).
  • Olson, open.
  • The four declined reads.
  • One coder for every C3 code and the mapping.
  • The constructs' C1 sources still recalled.
• From C2. What a mark brings back into its room. The two boundaries for the return. The claim untested for order.
• From C1. Thin constructs (Decided order, Neo-tribes, Symbolic boundaries); c1_unapplied.jsonl (5); the form-pass findings, never counted.
• From B1. J counts 841 B1 bags; an older head said 846. Not reconciled.
• My doubts. Where words carry no speaker's sub I read them as the room's own. The verdicts, the vetting coding and the mapping are mine alone.

Rules kept

• Checking.

  • Never type an id, an order or a name from memory; check with a script.
  • Never log a write before the tool answers. Count a ledger's lines after appending.
  • Check a claim about a ledger against the ledger, and a claim about a paper against the shelf, before writing it.
  • Keep the field's firm or provisional mark wherever a field claim is used.

• Logging.

  • There is no --kind close and no --kind episode; log those as notes.
  • Log an abductive read with --kind abductive before it runs, with its rules written first.
  • Log a move with --kind move and snap it.

• Questions. A question to J is mem.py ask "<question>" --assume "<meanwhile>". Read an answer with mem.py asks <id>.

• Writing and checks.

  • Never put a placeholder or a no-op in a command or a log line.
  • Never put an Edit or Write and the check that verifies it in one turn.
  • Count the head's words before the closing line. Never write an id-like token the run does not define in the head.

• Reading the store.

  • Draw from the store with mem.py codes --fourth/--third ... --json (label field first_order); mem.py codes --grep <re> --json searches words.
  • mem.py rooms --with <id> prints plain text, paged at 80 lines; pass --limit.
  • cite.py serves by --room and --code.
  • The theme a reply sits under does not track its stance.

• The permission check refuses:

  • deleting a file (rm), even a link;
  • shell variables set and expanded; shell loops and words beginning "for_"; shell functions, brace groups and heredocs;
  • find -exec with braces; awk with system() or $ fields; env-var prefixes;
  • cat or jq on out/diary/; cut -c after a read; head -n -N.

  Write a script in out/_analysis/ instead.

• Output limits. A Bash output above about 30 KB is cut; measure first. A Read above about 25,000 tokens is refused.

• After a compaction, before any other step: read the head and the stage file in full, run diary --last 5, and log exactly "compacted; head reconciled" with --kind note in a call of its own.

• Files. Never delete a file; supersede it with a new name. A generated document that must keep its name is corrected in place with Edit, and its script is fixed too. The field is read from out/field.

The next comparison

The stage after C4, as its stage file says. Carry into it:

• the model as model-C4.md, the structure as structure-C4.md, and the concept as concept-C3.md, borrowed and not leaned on;
• the tentative field entries, which stage D sends to every room;
• J's ruling on language for every sentence written.

The concept, stage C2 (Part B), pass 1 (C2a-01)

The task is to name the one concept, two at the outside, that the literature has no adequate word for: not the largest theme, the one unaccounted for. The literature is held only from recollection until stage C3, and every nearest concept below is named from memory and says so.

The candidate chosen, provisionally: the one-line enrolment

What it is, in a sentence a stranger could use. A one-line enrolment is a public reply of one to three words ("I'm in.", "On it.", "Did my part.") by which a member answering a stranger's call joins the work. It commits the member and asks for nothing back, and it lets the room see its numbers when it has no list of members.

The nearest existing concepts, from recollection, and how this differs.

• Slacktivism, or token support (a term from writing on online activism, recalled). It names low-cost support that substitutes for action. The one-line enrolment precedes action: it answers a call to place, and the answers that follow it in the forest are placements and repairs.
• The pledge, or an assurance contract (Schelling's commitment; collective-action writing on conditional pledges, recalled). A pledge there is conditional ("I will if enough others do") and binds by its terms. The enrolment here is unconditional, binds nothing, and is useful because it is visible: other members read the room's mass off it.
• Gioia and Chittipeddi's sensegiving does not fit: nothing is explained.

The difference that matters: the enrolment is how a room with no membership and no way to compel knows whether a call has drawn hands. It is the room's own head count, made of replies.

How many communities carry it, and how I counted. The gate was written before the count, at C1's form pass (out/_analysis/c1_form_patterns.json): a reply whose quoted words are only a one-line commitment, done report, assent or refusal, thanks, or bare salute. Under it the form pass found 590 concept lines in 337 of 705 communities (finding FP-01 in form_pass-C1.md). That figure describes the search. The finding is never counted in the model's arithmetic and travels on exemplars (rule 5). It is also a floor: the coders dropped most items that carried no code, and many one-line replies are among them.

Three quotes, through cite.py.

• "I'm in." [sips/c0027, h44.92], answering "Let's draw sips from 'Spacemen' in r/place" four minutes earlier.
• "On it." [fivenightsatfreddys/c0483, h56.65], answering a call to clean the room's spot 22 minutes earlier.
• "Did my part." [TeamDignitas/c0017, h10.58].

What having it lets me explain.

• Why calls work at all where no one can be compelled: the cost of joining is one line.
• How a room reads its own critical mass (dimension D01): from the enrolments under a call, and from their absence, which is when doubt is voiced ("not enough people").
• Why the record undercounts participation: the enrolment is the act most often left uncoded.

In the model it is element P15 and arrow A12 (a call answered by an enrolment, shown on transitions and never counted).

The candidates rejected, kept here

1. Organizing without decided order (element C01; T4-011 with FP-08). Rooms aligned their placers with almost no decided element of order. Rejected as the concept: Ahrne and Brunsson's distinction between decided and emergent order (recalled) already names it. Here it is a finding about how much of each the rooms used, not a new concept.
2. The return to spot choice (finding F-002). A room that loses its spot goes back to choosing a spot, not to recruiting. Rejected: it is a dynamic, the model's material (Part C), not a concept.
3. Host framing (dimension D06, coined). What a standing community does with a passing event inside its own space. Rejected: it is coined for the structure, but its nearest concepts (frame analysis, boundary-work) handle most of it. What is new is the conjunction with April Fools, which belongs to this corpus.
4. The relay across time zones (T3-141 and FP-03): members keep the work by who is awake. Rejected: "follow-the-sun" work in distributed software teams (recalled) already names the practice, if not the volunteer version.

The candidate I came closest to choosing instead: organizing without decided order. It carries the theory question more directly, but its words already exist.

Part B's return, pass 1

• The concept in one sentence: a one-line enrolment is a public reply of one to three words by which a member joins a stranger's call, committing and asking nothing back, and by which a room without members can see its numbers.
• The nearest existing concept and the difference: slacktivism, which substitutes for action; the enrolment precedes action and is the room's head count.
• How many communities: 337 of 705 (590 lines) under the form pass's declared gate; never counted in the model, and a floor.
• The candidate I came closest to choosing instead: organizing without decided order.
• The literature a reader would say already covers it: writing on low-cost online participation and on conditional pledges in collective action (both recalled); the enrolment differs from both in being unconditional, followed by labour, and read by others as a count. This is provisional: stage C3 may show the literature has the word.

Part B's return, pass 5 (C2d-02), the last pass

Passes 2 to 4 left the concept unchanged. At the last pass the answer is the one-line enrolment, chosen. It stays marked as recalled against the literature until stage C3.

• The concept in one sentence: as at pass 1.
• How many communities: as at pass 1, 337 of 705 under the form pass's gate, never counted in the model. At pass 4 the call's boundary with it was read: at most 228 of the 1,980 concepts cited under the call's themes are joining lines, and stripping them out changes no arrow from the call.
• One more candidate, rejected: a tie the members had before the canvas naming the rival in the attack call (the claim C02, pass 5). It is rivalry with a known competitor and frame bridging, both named in the recalled literature (Kilduff, Elfenbein and Staw; Snow and colleagues). It is a claim in the model, not a concept the literature lacks.
• The candidate I came closest to choosing instead: still organizing without decided order.

The onset contrast (contract section 5), written at A1a, 2026-10-06, before any room is read

Target length: under 900 words, the member lists apart.

The rule

The clock is onset_first_code_hour in rooms.jsonl: the hour, since the canvas opened, of the room's first coded turn. It is populated for all 705 rooms.

• Early side: the first coded turn falls after hour 0 and before hour 3. These rooms wrote about the canvas within its first three hours, while it was still mostly empty.
• Late side: the first coded turn falls after hour 48. These rooms first wrote about the canvas in its third day or later, when most of it was already drawn and held.
• Rooms with a first coded turn before hour 0 (r/italy at -1.14, r/yogscast at -18.58) stand on neither side. Their first coded turn comes before the canvas existed, so it does not date when they came to it. In r/yogscast that turn (yogscast/c0024, at -18.58) is an offer of spare streaming keys. Its first canvas turn is yogscast/c0001 at hour 5.03.
• The middle, hours 3 to 48, is left out. With the two rooms above, 513 rooms stand on neither side.

The bounds come from the canvas's own clock, not from these figures. Hour 3 ends the first stretch of the empty canvas. Hour 48 starts the third day. Placement stopped at hour 73. I chose the bounds after seeing the quartiles (q1 3.76, median 9.51, q3 24.82). That knowledge shaped the bounds, and I say so here.

Size of each side

• Early: 131 rooms (of 705).
• Late: 61 rooms (of 705).

The confound, before anything else

Onset on this clock is in large part a measure of how much a room wrote. A room that writes more has more chances to write early. The two sides differ a hundredfold in size. The early side's median items_in_window is 5067 (q1 1468, q3 10885). The late side's median is 33 (q1 18, q3 131). The canvas areas differ the same way: medians of 1564 px and 152 px. Contract section 5 says code mass measures corpus size, not conduct. So any difference between the two sides must first be shown not to be a size difference.

I carry a held-size comparison with the main one. It uses the rooms on each side whose items_in_window lies in the census's middle half (156 to 2770). That leaves 41 early rooms and 12 late rooms. Twelve is thin, and any claim from it is labelled thin (rule 8).

What I expect to differ

These are expectations, written before reading, for stage C2 to test against the model's arrows.

1. Late rooms will organize around finding room on a full canvas. I expect asking neighbours for space, moving the drawing, fitting into gaps and treaties made to be let in. Early rooms will organize around claiming and enlarging a space and then holding it against others.
2. Late rooms will have shorter organizing lives, with fewer hours between the first and last coordinating turn. Their record will hold more single calls with no visible reply. Some late rooms will show no coordination at all: one notice that something of theirs appeared on the canvas (r/watchmen, r/yerbamate are of this kind on the screen).
3. Early rooms will more often name rivals and keep fights going over many hours. Late rooms will more often name a host or a neighbour who let them in.
4. The held-size comparison will keep difference 1 and lose most of difference 3. If difference 1 also vanishes at held size, then onset on this clock is size and the contrast shows nothing about timing.

Members, early side (131)

bitcoin, halo, overwatch, pcmasterrace, schoolidolfestival, dota2, leagueoflegends, thesilphroad, smite, totallynotrobots, worldoftanks, streetfighter, clashroyale, counting, india, mls, wow, hearthstone, ElderScrolls, globaloffensive, oneplus, australia, tagpro, thenetherlands, 2007scape, dankmemes, splatoon, pokemon, texans, kingdomhearts, teslamotors, philippines, undertale, babymetal, smashbros, eve, spacexmasterrace, mylittlepony, twitchplayspokemon, homestuck, cloud9, tf2, formula1, puzzleanddragons, rit, thailand, zootopia, titanfall, de, ice_poseidon, baylor, cirkeltrek, giivasunner, eagles, TheGreatGreenBox, AprilKnights, brasil, uofm, startrek, asktransgender, eder, fivenightsatfreddys, Rainbow6, mechanicalkeyboards, drugs, argentina, europe, ockytop, harrypotter, fullcommunism, frankocean, anarchism, rotmg, bindingofisaac, catholicism, feedthebeast, wholesomememes, monsterhunter, patriots, GreenEmpire, kanye, ireland, luciomains, radiohead, prequelmemes, nintendo, sweden, donaldglover, haskell, danganronpa, redhotchilipeppers, traaaaaaannnnnnnnnns, newzealand, unitedkingdom, paladins, france, habs, romania, leafs, h3h3productions, rwby, warthunder, rickandmorty, EraseThePlace, starlightstage, megaman, stlouisblues, transgender, chicubs, touhou, wallstreetbets, foxes, DestinyTheGame, ainbowroad, nascar, evex, runescape, lakers, nlsscirclejerk, rocketleague, PurplePixels, asexuality, kirby, denmark, floridagators, chile, portugal, suomi, trees, crusaderkings, dwarffortress

Members, late side (61)

littlewitchacademia, vermont, fxKorea, guatemala, vietnam, latin, COSI, sooners, wsu, k_on, CelticFc, UMiami, watchmen, corridor, MiamiHurricanes, UPenn, mysterydungeon, nVade, parabola, ukplace, OrderOfTheKoi, DevonUK, natsume, seventeen, udub, mcgillrobotics, sheffield, bees, DiamondClub, Villanova, CSUFoCo, quq, Clannad, ibo, VelvetUnderground, heyyea, ManningPlace, Redox, Dorset, OKState, ElSalvador, DCFU, TheID, crystalclear, mamamoo, bigbang, signal, rainbowgrid, Cornwall, TheAdventuresofTintin, sakartvelo, azores, aeskwadraat, carletonu, Produce101, aeon, tetris, cgpgrey, UNLincoln, pgang, azerbaijan

Held size (items_in_window 156 to 2770)

Early, 41: totallynotrobots, ElderScrolls, oneplus, tagpro, splatoon, texans, undertale, spacexmasterrace, twitchplayspokemon, homestuck, cloud9, rit, thailand, zootopia, cirkeltrek, giivasunner, eagles, TheGreatGreenBox, AprilKnights, uofm, ockytop, frankocean, luciomains, donaldglover, haskell, danganronpa, redhotchilipeppers, traaaaaaannnnnnnnnns, EraseThePlace, starlightstage, megaman, transgender, touhou, foxes, nlsscirclejerk, PurplePixels, asexuality, kirby, floridagators, chile, dwarffortress.

Late, 12: littlewitchacademia, vermont, vietnam, latin, k_on, mysterydungeon, nVade, ukplace, udub, ibo, ManningPlace, cgpgrey.

The lists come from mem.py facts --field onset_first_code_hour --where ... calls made in leg A1a and logged in _mem_reads-A1.jsonl.

Recomputed on J's ruling 3, leg A1b-20, 2026-10-07

J ruled on 7 October 2026 that the onset is the room's first coded turn at hour 0 or later. Turns before hour 0 are reported apart. The sides keep their bounds: early from hour 0 to before hour 3, late after hour 48. The text above stays as written at A1a.

I recomputed the onset from every concept's hour in the store. The concepts were read through mem.py codes by out/_analysis/a1_codes_dump.py. Two rooms have a coded turn before hour 0, one turn each:

• r/italy: one turn at h-1.14. Its onset is now h0.15, so it moves from neither side to the early side.
• r/yogscast: one turn at h-18.58, the offer of streaming keys (yogscast/c0024). Its onset is now h5.03. It stays on neither side.

No other room moves. The quartiles of the onset are unchanged: q1 3.76, median 9.51, q3 24.82.

Sizes on the new rule:

• Early: 132 rooms (131 above, with italy). The median items_in_window is 5149.
• Late: 61 rooms, unchanged. The median items_in_window is 33.
• Neither: 512 rooms.
• Held size (items_in_window 156 to 2770): 41 early and 12 late, unchanged, because r/italy lies outside the band.

The model read against the field, stage C4

This file compares my model of the 705 rooms (model-C3.md) with the field analyst's model of the event, built from r/place itself (field/model.md). It also answers the field analyst's check of my model (field/check.md). The notes and the record of each step are in notes-C4.md and the diary.

What the field is. r/place was the subreddit where the rooms met. Factions recruited there, made alliances, argued over borders and reported what was happening. The census kept it out of my 705 rooms for that reason. A separate analyst coded it under its own contract and built a model of the event from it. That analyst did not see my files, and I did not see theirs before this stage. I hold the field analyst's model and its evidence, not r/place's threads.

How the field marks its claims. The field analyst marks each claim firm or provisional. A firm claim is a supported public statement or exchange. A provisional claim is the analyst's proposed explanation, or a limit of the evidence. I keep that mark wherever I use a field claim.

Three claims a view of the whole event could most easily overturn

Written at C4a, 2026-10-14 (UTC), after I read model-C3.md again and before I opened field/.

1. Rooms began to deal with other rooms after they began to keep their own work. In my rooms, the first upkeep (watching and repairing the mark) comes before the first border talk in 235 of 401 rooms (A04). It comes before the first help traded with another room in 171 of 240 (A13), and before the first coalition in 87 of 121 (A19; F-008). My model reads this as one process. Keeping a mark brings a room up against its neighbours, so the room talks with them, trades help and joins coalitions. A view of the whole event could overturn this reading. Alliances, borders and permits may have been made in r/place's own threads and shared chats before most rooms placed anything. Then the order in my rooms would show when a room's own thread first mentioned a deal, not when the deal was made. My rooms already bound the claim on the late side: only 6 of 15 late rooms keep the order.

2. Rooms aligned their placers mostly without deciding how they were organized. A decided element of order is coded in 46 of 705 rooms (C01; F-006). A decided element is a leader, a vote, an oath, a sanction or a division of the work. Stage C3 bounded the claim: decided order gathers in the small factions born on the canvas that govern a territory. A view of the whole event could overturn it. The large factions, the shared chats and the event's best-known bodies may have had leaders, councils and plans, made where my rooms cannot see them. My rooms record only the decisions that came back to their threads, in 33 rooms. If the field shows decided order wherever the work was large, my claim describes what a room's thread shows, not how the work was organized.

3. Each room's order of steps is the room's own, not the event's clock. My order counts compare the first concept of one element with the first concept of another inside each room. The null keeps each room's hours fixed and shuffles which element each turn belongs to. It does not hold the event's phases constant. If every room moved from building to defending at about the same hour, because the canvas filled up for everyone at once, then the spine's order follows the event's clock. The spine is the sequence from the call through building to keeping (A01, A03, A04). The early and late sides of the onset contrast are my only control for this. A field account of the event's phases could show it is not enough.

What the field holds

The field model has two phases and nine processes.

• Phase 1, hours 0 to 73. Members propose designs, ask for help, negotiate space, report repairs and contest encroachment (firm). The field analyst cannot divide this period into one progression from creation to defence, because groups changed practices at different times (provisional).
• Phase 2, hours 73 to 97. Members separate the end of placement from work on histories, archives and copies (firm). Hour 73 is the study's boundary, not evidence that everyone changed activity together (provisional).
• The nine processes: making a shared design actionable; negotiating reciprocal limits without collective authority; turning a space conflict into a changed plan; the representation problem in coalition building; correcting a public account; closure information stopping a renewed invitation; preservation for future audiences; dividing follow-on work by sector; negotiating what preservation should keep.

The field analyst read model-C3.md and model/story-p5.md whole, structure-C3.md in part, and the handbacks by a qualified route. Its check lists four agreements, four disagreements, three things the room record cannot see, and three of my claims it trusts least.

What happened to the three claims

None of the three was overturned.

• Claim 1 (dealing with other rooms after keeping the work). The field does not count order. It holds one early negotiation in r/place: a Helix contributor asks a rainbow group for a three-pixel buffer at hours 5.00 to 7.08 (62mg1j, firm). That is border talk early in the event. It does not show whether either group was already repairing. The claim stands, with this episode printed beside A04 (list 3, item 5).
• Claim 2 (decided order is rare). The field supports it. In its records, members make agreements while they disclaim the authority to bind their group, and a treaty announced between large factions is met with "You don't speak for me, man." (62qib1, c720105, firm). The field shows members seeking leaders, not leaders deciding. F-006 stands (list 1, item 1; list 3, item 4).
• Claim 3 (each room's order is its own). The field analyst could not find one progression from creation to defence across groups (provisional). This is an absence in the field's own reading, so it supports the claim weakly. It does not test it.

List 1: where the two agree

Five mechanisms appear in both models. Two analysts who could not see each other's work found each one. For each, the next items give my model's words, the field's words, one room, one field thread, and the findings it touches.

1. Members make agreements between rooms that they cannot make every placer keep.
   • My model: "Rooms settle borders, truces and deals with neighbours by talk, through envoys, hold each other to them and dispute them" (P08). "Rooms aligned their placers mostly without deciding how they were organized" (C01). The fourth-order theme Negotiated order asks how order is made "between rooms that cannot bind their own placers".
   • The field: "Negotiating reciprocal limits without collective authority". The acceptance "may create a local expectation of restraint. It does not establish collective ratification or compliance" (provisional).
   • Room: "Unfortunately, just because one user/users made an agreement doesn't mean every lurker/person active on the sub agrees." [flyers/c0166, h53.41]
   • Field thread: "I don't speak for all rainbownians, but I agree to these terms" (62mg1j, c60256, firm).
   • Touches: F-006 and the claim C01. Both stand, now with a second source.
2. A specified design makes the work possible to act on, and inside a thread a posted template settles a design under argument.
   • My model: "Design talk in a thread is settled by someone posting a template that fixes the agreed design pixel by pixel" (A11, theorised: it holds inside threads, and its order across rooms is at chance).
   • The field: "Making a shared design actionable". The field's check says that stage C3 "correctly separates this local transition from a general order in which design always precedes templates".
   • Room: "Maybe make it 20x20? Or just a purple W?" [udub/c0008, h55.02], answered "20x20 is possibly a better idea... Will update template image and upload here." [udub/c0009, h55.09]
   • Field thread: a contributor offers a small Helix design "that we should be able to accomplish pretty easily." (62mg1j, c60185, firm).
   • Touches: no finding. A11 stays theorised. The field disagrees with what my structure said a template can do (list 3, item 2).
3. A request for space, answered with terms, changes one room's plan.
   • My structure: yielding space when asked (17 rooms) and granting a neighbour room (13 rooms), inside Territoriality. My model does not use these two themes. Its only route to a changed plan is the move after a loss (A10), and the field's check says its episode does not show that route.
   • The field: "Turning a space conflict into a changed plan".
   • Room: "we would like to ask for some room under your art, of course not touching anything and travelling around and behind your badge. Suggestions?" [FederationPlace/c0040, h53.49]
   • Field thread: "How much space do you need?" and then "thanks for being understanding!" (632pnj, c2550036, c2550041, firm).
   • Touches: no finding. The two models agree on the mechanism. My model leaves it out, and I record that as a gap for stage C5.
4. Members record the work so that it outlasts the canvas.
   • My model: "The room records what happened to its work: screenshots and timelapses, reports of its fate, mourning, imagined art, atlas entries, the end marked" (P12). What is celebrated is recorded (A08), and the record is carried on (A09).
   • The field: "Mobilizing preservation through future audiences".
   • Room: "Petition to add that image to the subreddit theme." [uiuc/c0155, h76.39]
   • Field thread: "do it for your great great great great (*) grand-children.", answered "r/placeAtlas" and "Awesome, thanks!" (63di76, c3910036 to c3910038, firm).
   • Touches: F-004 (the close runs in order). It stands.
5. Placement ends at hour 73, and members tell those who propose to place after it that the canvas is closed.
   • My model: "What is irreversible across hour 73: placement stops."
   • The field: "Supplying an operating constraint to a renewed invitation", and the second phase.
   • Room: "Place is over. RIP restoring process" [osugame/c0685, h73.05]
   • Field thread: "r/place has ended. . Like yesterday" (63ef7u, c3920007, firm).
   • Touches: no finding. The field disagrees with what my model said ended at hour 73 (list 3, item 1).

One further agreement, on the clock. Neither model finds one progression shared by every group. Both treat hour 73 as the end of placement and not as the end of everything. This is an agreement about what the record cannot show, not a mechanism.

The field's trust in stage C3's correction. The field analyst trusts least the earlier story's claim that joining replies show a room its numbers. Stage C3 dropped that claim (F-015). model/story-p5.md still carries it, and stage C5 rewrites the story.

List 2: what only the field sees

The field sees what happens between rooms in the square. No single room's record shows the whole of these. Each entry below sits under a fourth-order theme that stage C3 mapped. None changes which of the four universal problems that theme reaches.

1. Who may commit a group to an agreement. Entered: P21 (element) and A21 (arrow), tentative.
   • The field: in 62mg1j, two members disclaim speaking for their groups before one reports "We have an agreement!" (c60256, c60257, c60265). In 62qib1, a treaty between major factions meets "You don't speak for me, man.", a Tiny Hearts member refuses to speak for the group, and the organiser answers "Well I want to talk to your group leader haha." (c720095, c720105, c720108, c720109). The exchanges are firm. The field's explanation, that a coalition claim prompts members to examine who can commit a group, is provisional.
   • Why only the field sees it: both sides of the exchange stand in one thread in the square. A room holds only its own members' side.
   • What a room can answer: whether its members dispute who may commit the room, and whether that dispute follows an agreement made in its name. My rooms hold the theme disputing who speaks for rooms in 15 rooms. flyers shows its side twice, five minutes apart [flyers/c0166, h53.41; flyers/c0169, h53.46].
   • Level and evidence: the mechanism is between rooms. The field items show the announcement and the other side's request for a leader. The room items show members of one room refusing the agreement's reach. They come from different episodes, so they show the two sides of the mechanism, not one exchange.
   • The entries: P21 states the room's side. A21 runs from deals and truces (P08) to P21. It is not counted, it stays out of the model's standing count, and stage D asks every room. The field's instance is a protective treaty, which my model would place under deals (P08) or coalitions (P17).
   • The four problems: P21 sits under Negotiated order, mapped to none. The authority to commit a group is not one of the four.
2. Which version of the canvas and of the event is kept. Entered: P22 (element), tentative.
   • The field: after hour 96 a cleanup project for a copy of the whole canvas tells contributors to "reserve a sector to cleanup by commenting on the quadrant thread" and to upload the file to a folder (63f0qb, c3920184, c3920185). A member asks "who gets to decide what gets cleaned/removed?" (c3920186). The project keeps "the small white triangle above the American flag as a direct request from erasetheplace." (c3920193). Another member says that cleanup would "sterilise history" (63e1pb, c3910162). A list of groups is corrected after "You've got the void all wrong." (63b6md, c3850139, c3850142). The exchanges are firm. That keeping a shared object requires negotiating its version is provisional. The cleanup's execution is not observed.
   • Why only the field sees it: the copy and the histories belong to the whole event. No room holds the project.
   • What a room can answer: whether its members asked the project to fix their work, took part, or argued over what to keep. My rooms show all three after hour 73, found by a keyword search and not yet by any theme: "The logo can still be cleaned up if somebody posts this to r/thefinalclean" [AMD/c0435, h86.14]; "I think imperfections are our battle wounds, I'm ok with the scars that remain." [SquareSpiral/c0217, h94.18]; a link to a shared folder of the final cleanup, celebrated with "Woo" [strangerthings/c0145, h94.53].
   • The four problems: P22 sits under Collective memory, mapped to none. The division of the cleanup by sector is task division and allocation, but it belongs to the event's project and not to any room's theme. The mapping line for Collective memory stays as it is.
3. The event's phases. Not entered. No room can answer a phase of the whole event from its own record. My model already holds the one boundary both models share, hour 73.
4. A smaller venue and a revised design after a template fails. Not entered. The field's provisional account of the Helix design says that members organised through a subreddit and Discord and revised the sprite after they failed to follow the first design. This happens inside one group, and my rooms already show its parts: moving planning into a chat is in 263 rooms. It is in my structure and not in my model. Its order is for a later stage to test, from my rooms, without the field.

List 3: where they disagree

J asked that a substantive disagreement be kept apart from a difference of setting or of subject. Each item says which kind it is, which source I trust and why, and what changed.

1. What ended at hour 73. A difference of subject.
   • My model: "Its organizing for this canvas is over."
   • The field: placement on the original canvas ended, but organizing around its products went on. At hours 96.06 to 96.98 a project divided the cleanup of a copy by sector (63f0qb).
   • My rooms agree with the field. Members asked for their work to be cleaned in a shared copy and argued over its scars, up to hour 94 (list 2, item 2).
   • Which source I trust: the field, because it holds the project, and my rooms confirm their side of it. The sentence was mine and it claimed more than placement.
   • What changed: model-C4.md bounds the sentence. Organizing of placement on this canvas ends at hour 73. Organizing around its records and copies goes on (P12, P13, and the tentative P22).
2. What a template can do. Substantive (the world).
   • My structure (Standardization of output): the standard "replaces argument with reference" and is "the room's strongest coordination at scale".
   • The field: a design offered at hour 2.04 as easy to follow was, by its contributor's later account, not followed: "we failed to coordinate enough to actually follow the picture." (6384jy). Members then organised a venue and revised the design.
   • My rooms agree with the field:
     • "Stop adding periods, the template is wrong." [2007scape/c0230, h17.72];
     • "sorry for the vandalizing on the original one, just a lack of coordination!" [AvoArmy/c0228, h56.19];
     • "I've probably been undoing it thinking it was vandalism to the trans flag" [criticalrole/c0049, h55.86].
   • Which source I trust: the field and my rooms together, against my own declaration. No test of mine ever ranked the template against other ways of coordinating. "Strongest at scale" had no evidence behind it.
   • What changed: the declaration's prose is amended. A template gives an argument something to point to. It does not make placers follow it, and it can be wrong. The move is relating or contrasting, snapped as C4-move-relating-51. A11 is unchanged: it is a local transition, and the field's check agrees that it is.
3. Whether every room existed before the canvas. Substantive, and my own error.
   • My structure (Boundary work): "Every room was a standing community before the canvas opened".
   • The field: "I started /r/placesnek" (62p7xw, c570391).
   • My own model already counted 78 of 705 rooms with no posts in the week before the canvas, and side subs opened for it. The declaration's prose contradicted my own model.
   • Which source I trust: the field and my model, against the prose.
   • What changed: the prose is narrowed to most rooms, in the same move (C4-move-relating-51).
4. Where questions of authority arise. A difference of setting, and partly of subject.
   • My finding: decided order, an element of order that is decided and placed, is coded in 46 of 705 rooms and gathers in the small factions born on the canvas that govern a territory (F-006, bounded at C3a).
   • The field: members ask who may commit a group in a treaty between large factions (62qib1) and in a cleanup after the close: "who gets to decide what gets cleaned/removed?" (63f0qb, c3920186).
   • Why it is not a contradiction: the field shows authority sought and questioned. My finding counts authority established. The field's check says itself that "seeking authority is also different from establishing it".
   • Which source I trust: both, on different things. The rooms count where decided order was placed. The field sees where it was asked for, between groups.
   • What changed: F-006 stands. The field's side enters as the tentative P21. This item is printed beside F-006 in model-C4.md.
5. Early border terms and the order of A04. Not a disagreement about the count.
   • My model: in 235 of 401 rooms the first upkeep comes before the first border talk (A04).
   • The field: one buffer was negotiated at hours 5.00 to 7.08 in r/place (62mg1j), and the field does not say whether either group was already repairing.
   • Which source I trust: the rooms, on the order across rooms, because one episode cannot test a count over 401 rooms. The field, on the fact that terms could be offered early in the square. A04 already has a bound for neighbours present from a room's first post.
   • What changed: nothing. The episode is printed beside A04 in model-C4.md.
6. Dating an act by the hour of its post. A limit of my evidence, which the field names.
   • The field: a retrospective post at hour 83.76 says "Eventually we got better organized". It reports a change made earlier, and its hour does not date that change (6384jy).
   • My order counts date each concept by the hour of its post. They compare first concepts, so a late retrospective report moves an element's first hour only when it is the room's only concept of that element.
   • Which source I trust: the field, on the limit. Any first concept that comes only from a retrospective report dates the report, not the act.
   • What changed: nothing. The limit is written into model-C4.md under the dynamics.

The field's three limits of the room record

The field's check names three things the room record cannot see or establish alone. I accept all three.

• The full reach of an agreement. No room count shows who kept an agreement. P21 asks the rooms only for their side: whether members dispute it.
• One clock for every group. See list 3, item 6, and claim 3.
• One uncontested version of the event. My structure puts memory, transition and authority in separate themes. The field shows them meeting around one shared object, the copy of the canvas. P22 asks the rooms for their side of that.

Findings bounded or changed by the field

None. F-006 stands, with list 3, item 4 printed beside it. F-004 stands, and list 1, item 4 adds a second source. F-016's mapping line for Standardization of output already said that no one can make a placer follow the template, and the amended prose now says the same. No finding was withdrawn.

Fourth-order themes, stage C1 (cut at C1a-10)

These are the fourth-order themes of stage C1, section 8: named groups of third-order themes, each a construct from the moment it was cut. They partition the third-order tier of scheme_v2.jsonl: each third-order theme sits in one fourth-order theme, and a second-order theme reaches two only through its own placements (rule 0). The lines are in fourth/fourth.jsonl; each cut is a line in tier_history.jsonl (tier fourth, event created, move merging or relating), a move line in the diary and a snap. The specs, and the reasons for each bundle, are in out/_analysis/c1_t4_specs.json.

The stories are provisional. They are the structure stage C2 starts from, and C2 may change any of them. No number was set: the material carries 28 constructs over 195 of the 197 third-order themes, and the diary says why. Every borrowed or adapted source is recalled, since only the method shelf is held at C1; stage C3 checks each against a text and verifies or withdraws it. The form-pass findings in form_pass-C1.md are a tier of their own; they are not members of any fourth-order theme.

The next table lists each fourth-order theme with its declaration, its move, the number of third-order themes it holds, and the placement lines and rooms whose second-order themes reach it through any of their placed themes. The reach is description, not a share: a line placed on two fourth-order themes is counted under each.

T4-001. Keying

• Gloss. "Is this an April fool?" [kerbalspaceprogram/c0083]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Goffman, E. (1974) Frame Analysis; Bateson, G. (1972) A theory of play and fantasy.
• What changed, and why. Goffman's keying turns a primary frame into play for participants who know it. Here a play frame is laid over a whole community space for one calendar day, by its moderators or its members. Changed: the unit keyed is a venue, not a strip of activity, and the keying is contested as well as performed.
• Would be disconfirmed by. Fails where a shared play frame lies over a community's space during a collective task and members never test, break or extend it, or where its presence changes nothing in how the task's own calls are read.
• Move. Relating (Grodal, Anteby and Holm).

The canvas opened on April Fools' Day, and many subs laid a play frame over their own space. What holds this bundle together is that frame and the work of keeping it: someone sets it, others play inside it, others ask of any claim whether it is in the frame or out, some object that the play is in the way and switch it off, some want what was made in play to outlast the day, and some answer a company's play in earnest. The frame gives a room a shared joke to perform. It also makes every announcement, a call to the canvas included, open to the question whether it is meant. Much canvas work went on inside, beside or against this frame.

Members (placement lines, rooms):

• T3-001 staging April Fools fake news (349, 274)
• T3-023 running an April Fools takeover (254, 173)
• T3-032 objecting to April Fools posts (80, 72)
• T3-048 reacting to official April Fools (99, 63)
• T3-064 spreading the room's joke elsewhere (16, 16)
• T3-093 playing with granted moderator powers, rare (3, 2)
• T3-095 testing others' April Fools claims (101, 88)
• T3-097 switching off the prank styling (49, 42)
• T3-100 keeping April Fools changes afterwards (35, 30)
• T3-106 calling a network boycott, rare (1, 1)

T4-002. Boundary work

• Gloss. "Please take all /r/place content to the stickied Megathread." [madokamagica/c0073]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Gieryn, T. F. (1983) Boundary-work and the demarcation of science from non-science, American Sociological Review.
• What changed, and why. Gieryn's boundary-work is the demarcation of science from non-science, drawn for authority and resources. Here a standing community demarcates its own agenda from an event that floods it, with rules and venues as well as words.
• Would be disconfirmed by. Fails where a passing event floods a standing community and the community neither contains nor contests it, or where containment does not change where the project's work is talked about or in whose name.
• Move. Merging (Grodal, Anteby and Holm).

Every room was a standing community before the canvas opened, with its own subject and rules, and the canvas arrived as a flood of posts about something else. This bundle is the community deciding what belongs in its space and what the event is worth to it. The means are moderators' rules, removals, a single thread, a separate sub, members' objections and arguments that the canvas is worth nothing. Boundary work shaped the canvas effort from outside: it settled where the work could be talked about and whether the work was the community's or a side project of some of its members.

Members (placement lines, rooms):

• T3-015 routing canvas posts into megathreads (131, 123)
• T3-037 arguing the canvas's worth (84, 76)
• T3-063 removing canvas posts by rule (90, 83)
• T3-075 objecting to the canvas flood (73, 72)
• T3-090 opening a canvas sub (49, 49)
• T3-140 moderators disowning the canvas work, rare (0, 0)
• T3-184 pausing the sub's usual events (2, 2)
• T3-185 changing the sub's posting rules (18, 17)

T4-003. Sensemaking

• Gloss. "How does r/place work?" [clashroyale/c0195]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Weick, K. E. (1995) Sensemaking in Organizations.
• Would be disconfirmed by. Fails where members faced with a novel, shared and changing object never ask what it is or what its parts show, or where their accounts never feed their next action.
• Move. Merging (Grodal, Anteby and Holm).

The canvas was new, changed by the minute and showed up in every sub at once. This bundle is the room building a working account of an equivocal object from cues and mostly after the fact: what the event is and how one takes part, what a picture or detail shows, what the neighbours made. The account is what lets a newcomer place a first pixel and lets a member read what has happened to the room's corner. Because the explanation often goes to someone who asked, the same account recruits.

Members (placement lines, rooms):

• T3-016 explaining what the canvas is (249, 232)
• T3-018 decoding the finished picture's details (56, 53)
• T3-052 remarking on neighbouring pictures (64, 63)

T4-004. Frame bridging

• Gloss. "r/place is over... the hornet isnt finished, just like the game" [starcitizen/c0375]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Snow, D. A., Rochford, E. B., Worden, S. K. and Benford, R. D. (1986) Frame alignment processes, micromobilization, and movement participation, American Sociological Review.
• What changed, and why. In Snow and colleagues, frame bridging links congruent but unconnected frames to recruit participants. Here a room links the canvas episode to frames it already holds, so the episode is told in the room's language. Changed: the bridge runs from a community's existing culture to a new collective episode, and its effect is on meaning and commitment inside the room more than on recruiting outsiders.
• Would be disconfirmed by. Fails where canvas talk in rooms with a strong prior culture draws on that culture no more than talk in rooms without one, or where the episode is told in the event's generic idiom rather than in each room's.
• Move. Merging (Grodal, Anteby and Holm).

Rooms did not meet the canvas with a blank vocabulary. What holds this bundle together is the direction of borrowing: an interpretive frame the room already held, its running jokes, its fandom's lore, its own quarrels or its politics, is bridged to the new episode, so that the episode becomes another chapter of the room's story. The bridge is how a room makes a strangers' event its own, and it is why the same act on the canvas is told so differently from room to room.

Members (placement lines, rooms):

• T3-031 playing the room's in-jokes (258, 218)
• T3-086 carrying in the sub's quarrel (23, 21)
• T3-135 telling clashes as fandom lore (16, 16)
• T3-179 arguing ideology from the canvas (15, 12)

T4-005. Mobilization

• Gloss. "we need more people." [MMA/c0432]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: McCarthy, J. D. and Zald, M. N. (1977) Resource mobilization and social movements: a partial theory, American Journal of Sociology.
• What changed, and why. McCarthy and Zald treat mobilization as movement organizations gathering money and labour. Here what is gathered is minutes of placing time from members who owe nothing, and the mobilizer is any member who posts a call. Changed: the resource is time on a clock, the organization is often only the call, and the inducements are encouragement and timing.
• Would be disconfirmed by. Fails where a work needing many hands on a clock gets them as often by chance as by being called, or where calls draw no hands.
• Move. Merging (Grodal, Anteby and Holm).

A picture of any size needs many pixels from many people within hours, and nobody can be ordered to place. This bundle gathers hands, from the room's own members first and from kindred subs after, by calls, encouragement, a time set for placing together, and sometimes by keeping the call quiet so it draws no attackers. The call is cheap to make, and the form pass found the answer to it cheaper still. Mobilization is how a room turns a crowd's attention into placed pixels, and its absence is the first reason a proposed work never appears.

Members (placement lines, rooms):

• T3-002 calling members in to place (364, 345)
• T3-062 recruiting kindred subs to help (44, 44)
• T3-104 cheering the builders on (24, 23)
• T3-144 recruiting quietly to avoid attackers, rare (0, 0)
• T3-167 timing a mass placement together (2, 2)

T4-006. Collective representation

• Gloss. "Let's represent ourselves at r/place" [stevenuniverse/c0013]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Durkheim, E. (1912) Les formes elementaires de la vie religieuse.
• What changed, and why. Durkheim's collective representations are the emblems through which a group represents itself to itself, the totem above all. Here the emblem is a pixel mark the room chooses, designs and claims on a shared canvas. Changed: the group makes its emblem within days and in public competition for space, so choosing it is a collective decision that can fail.
• Would be disconfirmed by. Fails where groups choose their marks for reasons unrelated to what the mark says of them (space, ease, chance), or where a mark of the group made by others is never claimed as its own.
• Move. Merging (Grodal, Anteby and Holm).

Before a room can build, it must decide what it will show of itself. What holds this bundle together is that the mark is the room's emblem: proposing it, designing it, signing it or leaving it unsigned, honouring a creator or the dead through it, and claiming a mark that others made or began are all choices about what the room is, and members argue them as such. The emblem is also what the room later defends, mourns and takes into its banner.

Members (placement lines, rooms):

• T3-004 settling the mark's design (306, 281)
• T3-033 proposing the room's mark (178, 166)
• T3-077 animating the mark in timelapse, rare (1, 1)
• T3-082 finding the room's mark placed (44, 43)
• T3-092 making a tribute alone (5, 5)
• T3-160 building memorials to the dead (4, 4)
• T3-169 signing the sub's name (35, 35)
• T3-175 adopting a sign others began (8, 6)
• T3-191 leaving the work unsigned, rare (2, 2)
• T3-197 heeding the creator's wishes, rare (1, 1)

T4-007. Stigmergy

• Gloss. "I saw a half done logo and knew my life had purpose for a few hours." [starbound/c0082]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Grasse, P.-P. (1959) La reconstruction du nid et les coordinations inter-individuelles, Insectes Sociaux; Heylighen, F. (2016) Stigmergy as a universal coordination mechanism, Cognitive Systems Research.
• Would be disconfirmed by. Fails where placers work only from explicit instructions (templates, chat orders, calls) and the state of the surface never prompts the next placement.
• Move. Merging (Grodal, Anteby and Holm).

Once a mark is begun, the mark coordinates. The trace on the canvas tells the next placer what is missing and where; a half-done logo is a call no one had to post. What holds this bundle together is work organized through the work: building and reporting progress, growing the mark beyond its first form, and adding a personal piece to a mark many share all read the state of the canvas and change it for the next placer. This is the coordination the template formalizes and the backstage plans, and it runs without either.

Members (placement lines, rooms):

• T3-038 building and reporting the mark (260, 237)
• T3-041 extending the room's work (188, 168)
• T3-060 adding a personal piece (7, 7)

T4-008. Standardization of output

• Gloss. "I'd rather just follow the template and not have these debates over that pixel." [xenoblade_chronicles/c0030]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Mintzberg, H. (1979) The Structuring of Organizations.
• Would be disconfirmed by. Fails where works with a shared template show no more agreement among placers than works without one, or where templates circulate and hold no one to them.
• Move. Merging (Grodal, Anteby and Holm).

A template specifies the output pixel by pixel, so strangers who never speak can place toward one picture. What holds this bundle together is the standard: an object that settles in advance what each pixel should be, and so replaces argument with reference. Members circulate it, ask for it, hold strays to it, demand one plan when calls scatter, and write to individual placers who depart from it. The standard is the room's strongest coordination at scale, and also the point where scripts can take over the placing.

Members (placement lines, rooms):

• T3-008 messaging individual placers to stop (4, 4)
• T3-034 asking for coordinates and instructions (13, 12)
• T3-049 complaining the calls are scattered (12, 11)
• T3-070 sharing coordinates, templates and how-to (221, 207)
• T3-091 keeping everyone on one template (30, 30)

T4-009. Workarounds

• Gloss. "Remember, you can use your old alt accounts to draw more pixels." [truestl/c0022]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Gasser, L. (1986) The integration of computing and routine work, ACM Transactions on Office Information Systems.
• What changed, and why. Gasser's workarounds are users' ways of getting work done around a system that does not fit it. Here the misfit is deliberate: the event limits each account to one pixel per interval, and rooms work around it. Changed: the constraint is the event's central rule, the workaround becomes a collective capacity, and its fairness is argued in the open.
• Would be disconfirmed by. Fails where groups under a per-person rate limit that could multiply their hands do not, or where the workaround never comes under the group's governance.
• Move. Merging (Grodal, Anteby and Holm).

The clock the rooms did not set is the cooldown: one pixel per account per interval. What holds this bundle together is that rule and the collective wish to place faster than the members can. Rooms built machine hands and extra accounts and shared their targets; once they had them, they had to govern them, arguing whether they were fair, switching off old versions that fought the plan, and teaching a script to spare a neighbour. The workaround turns a fixed clock into a capacity that some rooms had and others did not.

Members (placement lines, rooms):

• T3-027 arguing whether scripts are fair (82, 80)
• T3-028 running scripts for the work (163, 158)
• T3-074 working around the timer (37, 37)
• T3-088 placing beyond the pixel limit (39, 37)
• T3-089 switching off stale scripts (24, 24)
• T3-108 sharing one bot target (7, 7)
• T3-120 lending accounts to a bot (4, 4)
• T3-168 editing scripts to spare neighbours (5, 5)

T4-010. Backstage decision-making

• Gloss. "We decided on the discord (which you should join cough cough)" [drumcorps/c0082]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Goffman, E. (1959) The Presentation of Self in Everyday Life (the back region).
• What changed, and why. Goffman's back region is where performers prepare out of the audience's sight. Here the room's deliberation moves out of the public thread into a chat where those present decide, and the thread becomes the stage where decisions are announced. Changed: the backstage is a place of decision, and who is in it is contested.
• Would be disconfirmed by. Fails where moving planning into a closed venue does not change who decides, or where decisions taken there are never brought to the thread and never contested.
• Move. Relating (Grodal, Anteby and Holm).

Many rooms moved their planning out of the thread into a chat, most often a Discord. The acts in this bundle relate to that move: making it or refusing it, choosing the venue, bringing its decisions back, keeping plans from rivals who read the thread and watching theirs. The move creates a backstage where fewer people decide faster and in private, and a front stage where the rest learn the result. It brings speed and secrecy, and it raises the question no thread had asked: who may speak in the chat, and whether its plan binds those who were not there.

Members (placement lines, rooms):

• T3-014 moving planning into a chat (268, 263)
• T3-107 keeping planning in the thread (3, 3)
• T3-109 arguing which chat to use (3, 3)
• T3-114 disputing the chat's authority (9, 9)
• T3-116 hiding the plan from rivals (3, 3)
• T3-132 spying in a rival's chat (6, 6)
• T3-152 announcing what the chat decided (33, 33)

T4-011. Decided order

• Gloss. "Can we elect you as our leader and have whatever we're doing edited into your post?" [fireemblem/c0309]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Ahrne, G. and Brunsson, N. (2011) Organization outside organizations: the significance of partial organization, Organization.
• Would be disconfirmed by. Fails where groups formed on a clock with no prior structure decide elements of formal order (leader, vote, division of tasks, oath, sanction) as often as they do without them, or where deciding them makes no difference to how the group decides.
• Move. Merging (Grodal, Anteby and Holm).

Most rooms organized without anyone deciding how they were organized. This bundle holds the exceptions, where a room decides an element of formal organization: a hierarchy, a vote or election, a division of the work, membership and oaths, a sanction on its own vandals, a succession; and at the other pole the room that says outright it has no plan. Ahrne and Brunsson's point is that organization can be partial, a decided element or two without a formal organization. Here decided order is rare, which the form pass also found in the absence of the question who leads.

Members (placement lines, rooms):

• T3-066 putting decisions to a vote (18, 18)
• T3-101 putting one member in charge (6, 6)
• T3-103 dividing the picture among teams (5, 5)
• T3-121 excluding the room's own vandals (13, 13)
• T3-125 saying the room wings it (2, 2)
• T3-172 renewing the order's oaths (2, 2)
• T3-173 holding elections for office (2, 2)
• T3-187 handing the work over (4, 4)

T4-012. Collective efficacy

• Gloss. "We don't have enough people working on it to make it larger." [roosterteeth/c0032]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Bandura, A. (1997) Self-Efficacy: The Exercise of Control; Bandura, A. (2000) Exercise of human agency through collective efficacy, Current Directions in Psychological Science.
• Would be disconfirmed by. Fails where a group's stated belief in its strength has no bearing on what it attempts or keeps.
• Move. Merging (Grodal, Anteby and Holm).

Before and during the work, members judged aloud what the room could do. What holds this bundle together is that shared belief about the room's capability, voiced as doubt: too few people, a canvas too full, a room absent or outclassed, defenders told to give up, members quitting under strain. It is the other face of mobilization: a call says the room can, these say it cannot, and the belief shapes whether hands come and stay.

Members (placement lines, rooms):

• T3-036 judging the canvas too full (4, 4)
• T3-059 urging others to give up (8, 8)
• T3-098 questioning the room's canvas presence (19, 19)
• T3-136 doubting the room's strength (44, 43)
• T3-181 quitting the effort under strain (20, 20)

T4-013. Repair work

• Gloss. "I will keep an eye on it when I can today and help to protect it." [wildhockey/c0143]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Jackson, S. J. (2014) Rethinking repair, in Gillespie, Boczkowski and Foot (eds) Media Technologies.
• What changed, and why. Jackson treats repair as the ongoing work that keeps technological orders going against breakdown and decay. Here the decay is other people's pixels, continuous and sometimes hostile. Changed: the erosion is social, so repair shades into defence, and it competes for the same hands as growth.
• Would be disconfirmed by. Fails where works on an open surface survive without continuous attention, or where defence against attack and routine repair never draw on the same hands.
• Move. Merging (Grodal, Anteby and Holm).

A finished work on the canvas does not stay finished: stray pixels, neighbours' growth and attacks wear it away within hours. What holds this bundle together is maintenance against erosion: watching, fixing, defending under attack, covering the night, reshaping the mark to resist tampering, and choosing to keep what is held before growing. The theory question's last clause turns on it. Whether the work is kept alive depends on whether a room sustains repair after the excitement of building has passed.

Members (placement lines, rooms):

• T3-005 defending the work against attackers (425, 392)
• T3-021 watching and repairing the work (305, 293)
• T3-042 choosing upkeep over expansion (46, 43)
• T3-055 reshaping the mark against tampering (20, 20)
• T3-069 concentrating effort on fewer pieces (32, 29)
• T3-141 covering the night shift (24, 24)

T4-014. Territoriality

• Gloss. "we were here first. Want proof? I got lots of it." [Okami/c0036]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Brown, G., Lawrence, T. B. and Robinson, S. L. (2005) Territoriality in organizations, Academy of Management Review.
• Would be disconfirmed by. Fails where groups on a shared surface treat space as no one's, never invoking arrival or work as a right, or where claims to a spot carry no weight with neighbours.
• Move. Merging (Grodal, Anteby and Holm).

The canvas is finite, and a mark needs a place. What holds this bundle together is the feeling and expression of ownership over a place no one owns: a room's claim rests on having been there first and having made something there, and others mostly treat the claim as real. Choosing a spot, holding it, yielding it, granting part of it, weighing a fight for a lost spot against a move, and moving all work on that claim. Territoriality is what turns a free canvas into a map of holdings.

Members (placement lines, rooms):

• T3-012 granting a neighbour room (13, 13)
• T3-020 choosing a canvas spot (135, 132)
• T3-022 relocating after losing the spot (119, 116)
• T3-039 yielding space when asked (17, 17)
• T3-045 arguing who was there first (18, 18)
• T3-123 refusing to give up space (18, 17)
• T3-124 weighing fighting against moving (17, 17)

T4-015. Live and let live

• Gloss. "Everyone over here, please respect the American Flag and build around it." [greenlattice/c0076]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Axelrod, R. (1984) The Evolution of Cooperation; Ashworth, T. (1980) Trench Warfare 1914-1918: The Live and Let Live System.
• Would be disconfirmed by. Fails where restraint between neighbours appears only under an explicit agreement, or where it does not track the neighbour's restraint.
• Move. Relating (Grodal, Anteby and Holm).

Most neighbours never agreed anything, and most spared each other anyway. The acts in this bundle relate as a cycle: restraint offered, a defection, an appeal or an apology, restraint restored, and the argument over whether covering is fair at all. The system needs no agreement because each room meets its neighbour again and again within hours. It explains why the open canvas was not a war of all against all, and why a single member's defection could set off a quarrel the room then had to repair.

Members (placement lines, rooms):

• T3-007 urging repair over retaliation, rare (1, 1)
• T3-024 refusing to cover others' work (88, 85)
• T3-025 placing rival marks together, rare (1, 1)
• T3-040 apologizing to neighbours for damage (34, 34)
• T3-046 arguing whether covering is fair (44, 42)
• T3-047 making up with another sub (10, 10)
• T3-076 reining in the room's attackers (60, 60)
• T3-102 defying the call for restraint (2, 2)
• T3-119 turning attackers into helpers (12, 12)
• T3-139 pleading with attackers to stop (19, 19)
• T3-183 mourning art the room covered (2, 2)

T4-016. Negotiated order

• Gloss. "we did some diplomacy and managed to agree on a border" [theexpanse/c0056]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Strauss, A. (1978) Negotiations: Varieties, Contexts, Processes and Social Order; Strauss, A. et al. (1963) The hospital and its negotiated order.
• Would be disconfirmed by. Fails where order between neighbours on a shared surface comes about without talk, or where agreements once reached are never invoked, broken or renegotiated.
• Move. Merging (Grodal, Anteby and Holm).

Where tacit restraint was not enough, rooms talked. What holds this bundle together is order as the outcome of continuing negotiation: borders, truces and deals made by envoys across threads and languages, held to by reminders and accusations of breach, disputed afterwards, and always facing one difficulty, who can speak for a room whose placers no one commands. It explains why the canvas's borders were dense with talk, and why an agreement was only as good as a room's hold over its own placers.

Members (placement lines, rooms):

• T3-010 settling borders with neighbours (445, 418)
• T3-030 disputing how an alliance went (8, 8)
• T3-067 trading away another room's work, rare (1, 1)
• T3-083 negotiating across a language gap (3, 3)
• T3-126 disputing who speaks for rooms (15, 15)
• T3-138 staying neutral between two rooms (6, 6)
• T3-149 agreeing truces with rival rooms (112, 107)
• T3-161 mediating between other rooms, rare (0, 0)
• T3-193 arguing whether cooperation is surrender (3, 3)
• T3-194 acting as envoys between rooms (13, 13)
• T3-195 holding rooms to their agreements (22, 20)

T4-017. Reciprocity

• Gloss. "We will help you guys if you help us from Michigan." [purdue/c0056]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Gouldner, A. W. (1960) The norm of reciprocity: a preliminary statement, American Sociological Review.
• Would be disconfirmed by. Fails where help between groups carries no expectation of return, or where groups that helped are helped no more than groups that did not.
• Move. Relating (Grodal, Anteby and Holm).

Help crossed between rooms constantly, and it was rarely free of accounts. The acts in this bundle relate through the norm Gouldner named: help creates an obligation to return it, acknowledged in thanks and greetings, honoured in counter-help, traded outright, or broken by a refusal. Reciprocity explains how rooms that could compel no one could still count on hands beyond their own members.

Members (placement lines, rooms):

• T3-011 helping another room's work (119, 114)
• T3-071 letting neighbours adopt the work (2, 2)
• T3-072 thanking the room's allies (66, 62)
• T3-084 asking other rooms for help (76, 73)
• T3-115 turning away another room's request (13, 13)
• T3-122 sending greetings to another room (20, 20)
• T3-151 bartering help with neighbours (121, 118)

T4-018. Meta-organization

• Gloss. "Did /r/GreenLattice approve it?" [warframe/c0248]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Ahrne, G. and Brunsson, N. (2008) Meta-Organizations; Ahrne, G. and Brunsson, N. (2005) Organizations and meta-organizations, Scandinavian Journal of Management.
• Would be disconfirmed by. Fails where groups on a shared surface act only one by one, or where bodies of groups are named but never admit, refuse or rule on a member's work.
• Move. Merging (Grodal, Anteby and Holm).

Some organizing on the canvas had rooms, not people, as its members. What holds this bundle together is a room's membership in a body of rooms, with the body deciding something for its members: kindred hubs, hosts that admit and rule on others' building, shelter under a bigger neighbour, named alliances, shared councils, joint marks. It explains how many small rooms held space they could not have held alone, and why a room's standing could depend on another room's approval.

Members (placement lines, rooms):

• T3-013 gathering kindred rooms together (13, 13)
• T3-019 tallying kindred rooms' works (6, 6)
• T3-035 asking a host for space (55, 52)
• T3-056 making joint marks with others (28, 27)
• T3-094 disputing who approves a spot (6, 6)
• T3-099 relying on a bigger neighbour (5, 5)
• T3-150 forming alliances between rooms (97, 91)
• T3-153 meeting other rooms in chat (31, 31)
• T3-162 vetting others' requests to build (8, 7)

T4-019. Attribution

• Gloss. "Who keeps adding the unnecessary black squares on his right arm?" [terraria/c0081]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Heider, F. (1958) The Psychology of Interpersonal Relations; Kelley, H. H. (1967) Attribution theory in social psychology, Nebraska Symposium on Motivation.
• What changed, and why. Attribution theory concerns how people infer the causes of behaviour. Here every changed pixel on an anonymous surface poses the question who did it and why. Changed: the inference is collective, public and practical, and it includes disowning one's own placers.
• Would be disconfirmed by. Fails where groups respond to damage the same way whatever they infer about its author.
• Move. Relating (Grodal, Anteby and Holm).

No pixel carries a name, so every change to a work is a puzzle. The acts in this bundle relate through inference about the author and intent of a change: tracing who did it, finding that it was a friend or a mistake, blaming the site's or the sub's officers, and telling others that placers acting in the room's name are not the room's. The attribution decides whether a room repairs quietly, forgives, appeals or strikes back. It is the hinge between restraint and contention.

Members (placement lines, rooms):

• T3-087 tracing who changed the work (125, 119)
• T3-118 blaming moderators for a loss (5, 5)
• T3-170 mistaking friendly work for vandalism (46, 46)
• T3-188 disowning placers outside the plan (16, 16)

T4-020. Repertoire of contention

• Gloss. "quick lads, lets destroy the union jack" [ireland/c0484]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Tilly, C. (1978) From Mobilization to Revolution; Tilly, C. (1995) Popular Contention in Great Britain, 1758-1834.
• What changed, and why. Tilly's repertoire is the limited, learned set of performances by which people make claims on others, states above all. Here the claims are made on other rooms' works with the moves the canvas affords. Changed: the target is a rival's work, not an authority, and some performances make no claim at all.
• Would be disconfirmed by. Fails where attacks take no recurring forms learned and reused across groups, each episode inventing its own.
• Move. Merging (Grodal, Anteby and Holm).

Attack on the canvas took a small number of recurring forms, learned and copied from room to room. What holds this bundle together is that these were the moves a room had to hand when it chose to contest others' work, and every rival knew them too: erasing, encroaching, converting another's sign, raiding on a streamer's call, planting a hostile script, harassing a person off the site, griefing for fun. The repertoire is what repair and restraint had to answer.

Members (placement lines, rooms):

• T3-006 calling to deface rivals' work (176, 163)
• T3-061 pushing into a neighbour's space (66, 62)
• T3-068 converting a neighbour's art (61, 59)
• T3-128 relaying a streamer's attack call, rare (1, 1)
• T3-176 planting disguised scripts on rivals (3, 3)
• T3-178 brigading one person off Reddit (2, 2)
• T3-192 griefing the work for fun (13, 13)

T4-021. Rivalry

• Gloss. "We outlasted the overwatch logo on r/place" [paladins/c0246]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Kilduff, G. J., Elfenbein, H. A. and Staw, B. M. (2010) The psychology of rivalry: a relationally dependent analysis of competition, Academy of Management Journal.
• Would be disconfirmed by. Fails where contests between groups leave no relationship behind, or where repeated opponents are treated like any other.
• Move. Merging (Grodal, Anteby and Holm).

Some contests became relationships. What holds this bundle together is rivalry: a competitive relationship with a history, in which one other room matters more than any other and outdoing it is a stake of its own. Taunts and chants before, victory claims and salutes after, grievances kept past the close all address that one rival. Rivalry raises effort and lengthens memory, and it is one reason some fights went far beyond what the space was worth.

Members (placement lines, rooms):

• T3-050 trading taunts with rivals (85, 78)
• T3-058 blaming attackers after the close (25, 25)
• T3-134 flooding rivals' threads with chants (6, 6)
• T3-154 claiming victory over rival rooms (23, 23)
• T3-155 saluting rivals after the fight (5, 5)

T4-022. Flagging the nation

• Gloss. "constructing, expanding and defending their flag, our nation's flag" [india/c0191]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Billig, M. (1995) Banal Nationalism.
• What changed, and why. Billig's flagging is the daily, unnoticed reminding of nationhood by flags hung everywhere. Here the flag is made by hand, pixel by pixel, and fought over, so banal flagging turns into enacted nationalism at small stakes. Changed: the flag is a collective product rather than a fixture, and making it draws national history and politics into a game.
• Would be disconfirmed by. Fails where rooms named for a land make its flag no more often than other marks, or where building a national flag on a shared surface stirs no talk of belonging, history, kin nations or national others.
• Move. Merging (Grodal, Anteby and Holm).

Rooms named for a nation, state or region mostly made its flag, and making it was never only a picture. What holds this bundle together is the nation reproduced through a shared, ordinary artefact: members felt national through it, filled it with emblems, helped kin nations and joined flags in friendship, cast canvas fights as historic wars, read politics into it, argued who belongs, and mocked rival peoples. It explains why national rooms organized fast and fought hard: the flag carries a membership that was in place before the canvas opened.

Members (placement lines, rooms):

• T3-065 building the homeland's flag (109, 96)
• T3-078 helping kin nations' flags (9, 8)
• T3-079 joining flags with a heart (14, 13)
• T3-081 casting fights as national history (27, 24)
• T3-085 weighing the room against nations (5, 5)
• T3-113 drawing national emblems (41, 39)
• T3-130 reading national politics in pixels (23, 22)
• T3-142 making ethnic jokes about rivals (10, 10)
• T3-145 feeling national through the canvas (11, 10)
• T3-165 debating friendship with historic enemies (3, 3)
• T3-166 arguing the nation's historical record, rare (2, 2)
• T3-180 disputing national belonging (4, 4)

T4-023. Neo-tribes

• Gloss. "LONG LIVE THE BLUE CORNER! DEATH TO THE GREENCORNER" [GreenCorner/c0023]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Maffesoli, M. (1996) The Time of the Tribes: The Decline of Individualism in Mass Society.
• Would be disconfirmed by. Fails where groupings born on the surface hold members by interest alone, with no hails, loyalty or creed, or where membership in them is as fixed as membership in a standing community.
• Move. Merging (Grodal, Anteby and Holm).

The canvas grew its own collectives, with no sub behind them at first: colour factions and the void. What holds this bundle together is a grouping formed around a shared aesthetic and held by affect and ritual, fluid in membership and quick to divide: people join by placing a colour, hail it, spread it, defect from its rivals, give their pixels to an outside group's build, and split over what it stands for. These are the canvas's own organizations, and the other rooms met them as forces, as the form pass found.

Members (placement lines, rooms):

• T3-096 hailing the colour corners (5, 4)
• T3-137 joining an outside group's build (11, 10)
• T3-163 defecting from a rival faction (2, 2)
• T3-171 spreading a faction's colour (17, 15)
• T3-174 professing loyalty to a colour (16, 15)
• T3-190 splitting a faction over doctrine (8, 7)

T4-024. Symbolic boundaries

• Gloss. "Help remove the swastika appearing near/on our banner in /r/place" [poland/c0093]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Lamont, M. and Molnar, V. (2002) The study of boundaries in the social sciences, Annual Review of Sociology.
• What changed, and why. Lamont and Molnar's symbolic boundaries are distinctions by which people sort objects, practices and people. Here rooms draw the line of what may stand on a canvas anyone can mark. Changed: the line is enforced with the same pixels that drew the transgression, with no authority above the rooms.
• Would be disconfirmed by. Fails where offensive symbols on a surface anyone can mark stand unremarked, or where arguments over what may stand never lead anyone to cover or remove anything.
• Move. Merging (Grodal, Anteby and Holm).

Anyone could place anything, and some placed swastikas and slurs. What holds this bundle together is the moral line of the open canvas, drawn and enforced by the rooms themselves: hate symbols covered, bigoted talk shut down, symbols and jokes judged, and the transgressions that provoked them. It explains how a surface with no written rules on content still kept, mostly, to rules no one had written.

Members (placement lines, rooms):

• T3-080 arguing over political symbols (25, 24)
• T3-143 judging whether a joke offends (12, 11)
• T3-146 covering swastikas and hate symbols (6, 6)
• T3-177 calling to draw swastikas (3, 3)
• T3-182 shutting down bigotry in chat (8, 8)

T4-025. Visibility returns

• Gloss. "Thanks to our pixel art in /r/place, we gained 80+ new subscribers in 2 days!" [zootopia/c0195]
• Declared. Coined, this corpus's. A reader may mistake it for: Publicity, or signalling (Spence 1973). A signal is sent to inform a receiver's choice; these are returns a room courts, counts and fears from an audience it does not choose.
• Would be disconfirmed by. Fails where a community's mark on a widely watched surface brings nothing back (no newcomers, no notice from creators or press, no returning members), or where communities never court or fear what it brings.
• Move. Relating (Grodal, Anteby and Holm).

The canvas was watched by the whole site and then by the press, and a mark on it was seen by people who had never visited the room. The acts in this bundle relate through what being seen brings back: rooms courted the audience through the site's rankings and listings, put demands and slogans before it and hoped their creators would notice, then counted and feared the return, newcomers, returning fans, coverage, a sub swamped by visitors. It explains why some rooms built for an audience beyond themselves, and how the canvas changed the communities that took part.

Members (placement lines, rooms):

• T3-044 recruiting canvas visitors (85, 76)
• T3-051 pushing posts up the rankings (22, 22)
• T3-053 spelling slogans with post titles (3, 3)
• T3-110 placing a tile as payment (2, 2)
• T3-127 seeking the creators' notice (4, 4)
• T3-129 making passers-by notice a demand (5, 5)
• T3-147 sharing the work's press coverage (4, 4)
• T3-189 fearing newcomers the mark draws (3, 3)
• T3-196 drawing lapsed fans back (8, 7)

T4-026. Completion ritual

• Gloss. "We did it reddit!" [liquicity/c0001]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Collins, R. (2004) Interaction Ritual Chains; Durkheim, E. (1912) Les formes elementaires de la vie religieuse (collective effervescence).
• What changed, and why. Collins's interaction ritual is a gathering with shared focus and mood that yields emotional energy, solidarity and group symbols. Here the ritual is the room's marking of its finished work, in posts, with credit and rewards handed out in it. Changed: the participants are strangers co-present only in a thread, and the ritual follows a joint product rather than a gathering.
• Would be disconfirmed by. Fails where completing a joint work draws no shared marking, or where groups that mark it show no more later solidarity (emblems adopted, ties kept, return to the next round) than groups that do not.
• Move. Merging (Grodal, Anteby and Holm).

When a work was up, the room marked it. What holds this bundle together is the ritual of completion: shared attention on a finished thing that turns many strangers' pixels into 'we did it', with credit to makers and defenders, members' own parts told, prizes handed out, the meaning of working with strangers said aloud, and comfort drawn from being seen. The ritual pays the members whom no one could pay, and it produces the emblems and stories the room keeps.

Members (placement lines, rooms):

• T3-003 reporting one's own placing labour (61, 60)
• T3-009 celebrating the finished work (478, 442)
• T3-026 announcing the mark is up (54, 54)
• T3-043 crediting who made the work (167, 156)
• T3-157 reflecting on working together (40, 38)
• T3-159 rewarding helpers with prizes (7, 7)
• T3-164 feeling supported through the canvas (7, 7)
• T3-186 celebrating the feat in person, rare (1, 1)

T4-027. Collective memory

• Gloss. "Figured I might as well take screenshots of it before it's inevitably destroyed." [rhythmheaven/c0044]
• Declared. Borrowed, recalled (stage C3 verifies or withdraws). Source: Halbwachs, M. (1950) La memoire collective; Halbwachs, M. (1925) Les cadres sociaux de la memoire.
• Would be disconfirmed by. Fails where groups whose shared surface is wiped keep no record of their work.
• Move. Merging (Grodal, Anteby and Holm).

The canvas was going to end, and works were lost before it did. What holds this bundle together is the making of a record the room can hold once the canvas is gone, shaped by what the room needs to remember: images saved as the work stood, accounts of what happened to it, mourning, the art imagined but never placed, entries in the shared atlas, the end marked. It explains how a three-day effort outlived the surface it was made on.

Members (placement lines, rooms):

• T3-029 mourning the lost work (103, 101)
• T3-073 reporting how the work fared (221, 209)
• T3-105 saving screenshots and timelapses (107, 103)
• T3-112 entering the work in atlases (4, 4)
• T3-117 marking the canvas's end (113, 108)
• T3-148 imagining art the canvas missed (10, 10)

T4-028. Transition

• Gloss. "LONG LIVE THE LATTICE!! In the form of the official Steam group" [greenlattice/c1156]
• Declared. Adapted, recalled (stage C3 verifies or withdraws). Source: Lundin, R. A. and Soderholm, A. (1995) A theory of the temporary organization, Scandinavian Journal of Management.
• What changed, and why. Lundin and Soderholm name transition as one of the four concepts of temporary organization (time, task, team, transition): the change the temporary effort brings about at its end. Here the temporary effort is a room's canvas work, and transition is what passes from it into the permanent community or beyond. Changed: the temporary organization was never planned as one; it discovers at the end what of itself to keep.
• Would be disconfirmed by. Fails where the end of a temporary collective effort leaves nothing that passes into lasting bodies: no work rebuilt, no venue kept, no tie carried on, no product claimed.
• Move. Merging (Grodal, Anteby and Holm).

When the canvas closed, each room had to decide what of its temporary effort to keep. What holds this bundle together is passage: the temporary organization ends, and something of it moves into the permanent community or out into the world, the work carried to later canvases or remade in other media, the canvas sub given a new purpose, the mark taken into the sub's banner, a tie with another room kept, the shared work sold or argued over. It explains which forms outlived the clock.

Members (placement lines, rooms):

• T3-054 carrying work to new canvases (146, 145)
• T3-057 remaking canvas art elsewhere (46, 42)
• T3-111 repurposing the canvas sub (19, 19)
• T3-131 arguing over selling canvas art (5, 4)
• T3-156 adopting the mark as emblem (36, 36)
• T3-158 proposing ties beyond the canvas (11, 10)

Third-order themes no fourth-order theme picks up

They are listed, not gathered into a catch-all (section 8).

• T3-017 carrying on ordinary sub talk (334, 212). The sub's ordinary business going on during the canvas week, apart from the canvas and April Fools. It is the ground the host community's boundary work protects, not an act of organizing the work, and no story about the canvas holds it.
• T3-133 recovering a hacked sub, rare (1, 1). A sub recovered after a moderator's account was hacked: one room, one event, unrelated to the canvas work.

Handback, stage C4: the model against the field

Written at C4a, 2026-10-14 (UTC), at the close of stage C4.

• The comparison: field-C4.md, in three lists.
• The successor files stage C5 reads first, through manifest-C4.txt: model-C4.md and structure-C4.md, each written whole. concept-C3.md has no successor.
• The record of each step: notes-C4.md and the diary.
• The field's own files: out/field/model.md and out/field/check.md. They are byte-identical copies of the handler's files.

What the counts here license. The field analyst worked from r/place, the subreddit where the rooms met, and marked each claim firm or provisional. A firm claim is a public statement or exchange. A provisional claim is that analyst's explanation or a limit of the evidence. The field's selected episodes do not retest my room counts. My counts are of coded turns in 705 rooms. Neither source sees what members did off the record.

The claim

The field confirmed the model's account of authority and changed none of its counts.

• Members make agreements between rooms that they cannot make every placer keep. Both sources show this. In the square, a member accepts a buffer with "I don't speak for all rainbownians, but I agree to these terms" (62mg1j). In flyers, a member says that one user's agreement "doesn't mean every lurker/person active on the sub agrees" [flyers/c0166, h53.41].
• Decided order is rare (F-006). The field shows members seeking leaders, not leaders deciding.
• The field adds two mechanisms that live between rooms. Members dispute who may commit their room to an agreement. After placement ends, members contest which version of the canvas and of the event is kept. Both entered the model as tentative entries for stage D to put to every room.
• The field corrected three of my sentences:
  • a sentence in my model, that organizing for the canvas ended at hour 73;
  • two sentences in my declarations, that a template is the strongest coordination and that every room existed before the canvas.

The room that best supports the model: day9. It builds, loses its border at hour 48, moves within two hours and finishes the new work at hour 53. The field has no episode from day9 and does not test it.

The room that most threatens it: thebluecorner, a colour faction whose faith names its rivals and picks its guests. The field's records show members of large groups asking who may speak for them. They do not show the faith of a colour faction. The threat stands where stage C3 left it.

The counts of the comparison

The next table gives the size of each list in field-C4.md.

The five shared mechanisms:

1. Members make agreements between rooms that they cannot make every placer keep.
2. A specified design makes the work possible to act on, and inside a thread a posted template settles a design under argument.
3. A request for space, answered with terms, changes one room's plan. My structure holds this; my model does not use it.
4. Members record the work so that it outlasts the canvas.
5. Placement ends at hour 73, and members tell those who propose to place after it that the canvas is closed.

The sharpest disagreement, and the source I trust

What a template can do. My declaration of Standardization of output said that a template "replaces argument with reference" and is "the room's strongest coordination at scale". The field holds a design offered at hour 2.04 as easy to follow. By its contributor's later account, "we failed to coordinate enough to actually follow the picture." (6384jy). My rooms show the same:

• "Stop adding periods, the template is wrong." [2007scape/c0230, h17.72];
• "sorry for the vandalizing on the original one, just a lack of coordination!" [AvoArmy/c0228, h56.19].

I trust the field and my rooms together, against my own declaration. No test of mine ever ranked the template against other ways of coordinating. The prose is amended: a template gives an argument something to point to, it does not make placers follow it, and it can be wrong. A11, the local transition from an argued design to a posted template, is unchanged. The field's check agrees that it holds inside threads.

The other disagreements.

• What ended at hour 73: a difference of subject. I trust the field, and my rooms confirm it.
• Whether every room existed before the canvas: substantive, and my own error. I trust the field and my own count of 78 rooms.
• Where authority is questioned: a difference of setting. I trust both on different things: the field sees authority sought, and my rooms count authority placed.
• One early buffer in the square against the order of A04. I trust the rooms' count across 401 rooms on the order.
• Dating by the hour of a post: a limit. I trust the field.

Findings bounded or changed by the field

None. No finding was withdrawn, bounded or rewritten.

• F-006 and C01 stand, with the field's authority questions printed beside them.
• F-004 stands, with a second source.
• F-016's line for Standardization of output already said that no one can make a placer follow the template.

Files with a stage C4 successor

• model-C3.md, and the earlier model files it superseded: superseded by model-C4.md.
• structure-C3.md, and the earlier structure files it superseded: superseded by structure-C4.md.
• concept-C3.md: no successor.

What I am sure of, what I am not, and why

Sure.

• The five agreements. Each is shown by one of my rooms and one field thread, and two analysts who could not see each other's work found it.
• The two amended sentences were wrong as written. The field and my own rooms or counts contradict each one.
• None of the three claims I named before opening the field was overturned.

Not sure.

• The entries' basis. The tentative entries rest on explanations the field marks provisional.
• P22's room side was found by a keyword search after hour 73, not by any theme.
• A21's direction, from an agreement to a dispute over who may commit the room, comes from one field episode.
• The field's silence on the rest of my structure is not agreement. It read structure-C3.md only in part and by reconstruction.
• The validator's reading rests on the handler's correction of the field's place (QC4-001). A renamed link waits for the handler (QC4-002).

For the stages after

• Stage C5 reads model-C4.md and structure-C4.md through the manifest, and writes in descriptive, academic English, as J ruled. Three points for it:
  • the story still carries the head-count claim stage C3 dropped, and the field trusts the drop;
  • the closure sentence is bounded, and the story should say what went on after hour 73;
  • a request for space answered with terms (yielding and granting) is in both sources and not in my model.
• Stage D sends P21, P22 and A21 to every room, marked tentative and with no word of their source.
• Set aside here, carried from the C3c interview fork:
  • the correction to the C3a ruling on Felin and Zenger, where the setting differs, not the subject;
  • the arrow from the move back to the goal, which would close the first loop;
  • Visibility returns;
  • the recalled source for Stigmergy.

The model, stage C4: read against the field

The model is typed: elements in model/elements.jsonl, arrows in model/arrows.jsonl, every change in model/history.jsonl, loops in model/loops.jsonl (empty at pass 5). Pass 1's version is model.md; passes 2 to 4 are model-p2.md to model-p4.md. All are kept unchanged; model-p3.md is the text the reviewer read (sha256 aa75ee6c…).

What stage C4 changed

This file supersedes model-C3.md whole (rule 18). Stage C4 read the model against the field. The field is the model of the event that a separate analyst built from r/place (field/model.md), with that analyst's check of my model (field/check.md). What each comparison found is in field-C4.md. Stage C4 changed:

• Three tentative entries from the field. P21: members dispute who may commit the room to an agreement with other rooms. A21: an arrow from deals and truces to that dispute. P22: after placement ends, members contest which version of the canvas and of the event is kept. Each is origin: from-field and status: tentative, with the field's threads and items. None is counted. None is in the standing count. Stage D asks every room about each. They are listed in their own section, before the theorised arrows.
• One sentence bounded. The model said that a room's organizing for this canvas is over at hour 73. Placement on the canvas ends at hour 73. Organizing around its records and copies goes on (field-C4.md, list 3, item 1).
• Two disagreements printed beside the model. Beside F-006 and C01, the field shows authority sought between groups, which is not decided order placed. Beside A04, the field shows one early buffer negotiated in r/place.
• One limit written in. An order count dates each concept by the hour of its post, and a retrospective report does not date the act it reports.
• Two construct declarations amended (structure-C4.md). Standardization of output no longer says that a template replaces argument or is the strongest coordination at scale. Boundary work no longer says that every room existed before the canvas.

No standing element or arrow was added, bounded, demoted or withdrawn. No strength or count changed. No tier was recut. No finding changed. The story is not rewritten here; that is stage C5's.

The text below is stage C3's, with these changes written into it.

What stage C3 changed

This file supersedes model-p5.md whole (rule 18). Stage C3 read the pass 5 model against the explanation literature; what each work did is in literature-C3.md. Stage C3 changed:

• A bound on decided order (C3a). F-006 is superseded by a bounded line, prompted by O'Mahony and Ferraro (2007, verified). Decided order gathers in the small canvas-born factions that govern a territory or rule on guests: 7 of 39 such rooms carry it, against 39 of 666 others, held to room size (p 0.014), and only in the smaller rooms. C01's statement is unchanged.
• Two mechanisms from a distant field (C3b). The mechanisms of A12 (the one-line answer to a call) and A16 (an attack call refused inside the room) are taken from conversation analysis (recalled: Schegloff and Sacks 1973; Pomerantz 1984; Levinson 1983). A call is the first part of a pair. Joining is the preferred answer and comes bare; refusing is dispreferred and comes with a reason, which in a refusal of an attack call states the room's norm or the attack's cost. Tested on attack calls (F-014): refusals gave a reason in 23 of 38 read pairs, acceptances in 2 of 14. The stage C2 sentences are kept beside the new ones, in model/arrows.jsonl and below.
• The concept renamed (C3b). The one-line enrolment is a relabelling of conversation analysis's preferred acceptance (concept-C3.md). Its claimed function as the room's head count failed its test (F-015, weak).
• Two construct declarations amended (C3b). Stigmergy and Decided order each name a construct from the shelf they may be mistaken for (structure-C3.md).

No element was added or withdrawn; no arrow was added, bounded, demoted or withdrawn; no strength or count changed; no tier was recut. The story is not rewritten here; that is stage C5's.

The text below is pass 5's, with these changes written into it.

Pass 5 is the last closing pass. It worked from pass 4's state under J's ruling on QC2-002: the criterion is a guide, not the judge; each change is kept while the evidence leads me to believe it; no element is loosened to fit a room; and membership naming the rival in the same turn as the attack is carried as a claim in the rooms' words, untested for order. Pass 5 changed:

• one claim added, C02, untested for order, on finding F-013;
• two forms stated as boundaries at the return: colour factions the canvas gathered, and hosts ruling on guests;
• the story's contest and closing sections (model/story-p5.md).

Pass 5 kept every pass 4 change, each for the reason given in notes-C2.md (pass 5, declaration 2). No arrow was added, bounded, demoted or withdrawn, and no tier was recut.

The pass 5 story was read against 35 rooms drawn by seed 20261019 before any was opened. It told 16, told 19 with a residue and left none untold (pass 3: 16, 16, 0; pass 4: 11, 21, 0). Of the 21 rooms carried from pass 4's residue, the claim C02 told 7. Fresh rooms carried a residue at pass 4's rate: 5 of 11 against 5 of 13. The model rests on pass 5 (notes-C2.md, pass 5).

Pass 4 answered the reviewer's return (C2c) and the interview's points. It changed:

• two fourth-order recuts, each by a rule written first: hosting's four third-order themes left Meta-organization for Territoriality, and the land's flag and emblems left Flagging the nation for Collective representation;
• three elements restated: the coalition element (P17) narrowed to coalitions, the call to settle the mark (P02) widened to the land's flag and emblems, and the candidate membership carried in (K04) narrowed to the nation beyond the mark;
• an audit of every instance: 48 support transitions checked six ways, 14 failing a check, each reported as failing and none swapped;
• recounts: A19 on coalitions alone, A11 on the widened P02, A20 by actor while the canvas runs, and the four arrows that start from the call with joining lines stripped out;
• the failure clause counted for every order arrow;
• the reviewer's accepted errors carried into the text: new instances for A02, A04 and A05, transformers as a failure of A20's mechanism, "no posts in the week before the canvas" in place of "founded by the canvas", bounds told as bounds, and "order fails in" in place of "Present".

At pass 4 no arrow was added, demoted or withdrawn, and no element was added.

Earlier passes: pass 3 added the host's line (P20, A20), two candidates (K04, P19) and A10's bound. Pass 2 added P16 to P18, the candidate K03, A13 to A19, bounds on A04, A06 and A07, and the dimension Contention (D08).

The counts come from out/_analysis/c2_arrow_evidence.py. Pass 4's outputs are c2_arrow_evidence-p4a.txt (retests after the recuts), -p4b.txt (the host's line by actor before hour 73), -p4c.txt (the call without joining lines) and -p4d.txt (the failure clauses). The audit is c2d_instance_audit-p4.txt; the joining lines dropped are listed in c2d_enrol_drop.txt. The apparatus tables are printed by c2_model_tables.py (c2_model_tables-p4.md), the dimension masses by c2_dim_mass.py (c2_dim_mass-p4.txt), the unused themes by c2_unused_t3.py (c2_unused_t3-p4.md), and each arrow's pass 4 facts by c2d_model_facts_p4.py (c2d_model_facts-p4.txt).

The model relates presences and their order in time, never amounts. No coder wrote down a covariation between degrees, so no arrow is drawn between degrees.

What the model says, in prose

The contract asks the model for four things: how a scattered readership becomes able to act and how it settles what to act on; what sends a group back to that beginning; what brought organizing about when it came, and what followed; and what is left behind. Pass 5's model is a spine, a fork between rooms, a contest, and a close, with the host sub's answer to the calls beside the spine.

How a scattered readership becomes able to act. A member proposes a mark or begins it (R01). Calls gather around the start [A02], and calls bring the hands that build [A01]. The cheapest answer to a call is one bare line, "On it.", which commits a member and asks for nothing back [A12]. Joining is the answer a call prefers, so it needs no reason; refusing is dispreferred and comes with one (conversation analysis, recalled; F-014). The coders placed some of these joining lines among the calls. A pattern that over-reads finds at most 228 of the 1,980 concepts cited under the call's themes. With all 228 stripped out, each of the four counted arrows that start from the call still beats the null. Where a member placed first, the call follows the first build (A01's bound). The calls fill the host sub, and the sub draws a line around canvas talk: a megathread, removals under its rules, a canvas sub, members objecting to the flood [A20]. While the canvas runs, the calls come before the host sub's rulings in 102 of 118 rooms and before members' objections in 57 of 64 (finding F-010). One room in nine has no posts in the week before the canvas (78 of 705). An empty week does not show that the canvas founded a room. Side subs opened for the canvas, quiet subs and bodies the canvas gathered all have one.

How it settles what to act on. The room settles what its mark will show (P02). A national room's mark is mostly the land's flag or its emblems, and settling that is the same act as settling any room's picture. Inside a reply thread, a template settles a design under argument [A11]. Across rooms the first template is as likely to come before design talk as after it, and it can arrive with the first call (A11's bound). The half-built mark tells the next placer what is missing (P03). Decided order, such as a leader, a vote or an oath, is rare (C01; finding F-006). It gathers in the small canvas-born factions that govern a territory or rule on guests (F-006, bounded at C3a, prompted by O'Mahony and Ferraro 2007). The field shows members asking who may commit a group, between large factions and after the close. That is authority sought, not decided order placed, and F-006 stands (field-C4.md, list 3, item 4; the tentative P21).

What brought organizing about when it came, and what followed. Organizing came when someone started and others answered [A02] [A01]. The April Fools frame (K01) does not, across rooms, delay that start (finding F-009). Then the road forks.

• Keeping the work. Once a mark stands, keeping it becomes the work [A03]. Upkeep under attack outruns one pixel per interval, and members turn to scripts and spare accounts [A06].
• Keeping the work brings in other rooms. Upkeep brings a room up against the neighbours whose pixels erode it, and the room talks with them [A04]. A settled border gives members a line they keep [A05]. Short of hands, a room also turns to other rooms for help and receives it [A13]. Talk over a border can open a channel through which the two rooms trade help [A14]. A room keeping its work joins other rooms whose works face the same threat in a coalition [A19] (finding F-008).
• The contest. A call to the canvas can also turn its hands against a rival's work [A15]. A room's own call to attack is mostly answered inside the room: members refuse it, rein the attackers in or apologise [A16], or invoke a truce or propose a deal [A17] (finding F-007). Where the attack goes on, it is carried on in talk: taunts, chants, claims of victory, a salute after the fight [A18].

What sends a group back to the beginning. A loss. A room that judges it has too few hands stops fighting for its spot and moves [A10]. A room inside a coalition can also move by the coalition's plan, and a late room may write its reason after the move (A10's bound). After the move, calls fall from the crisis before it: a call comes in the six hours after the first move in 0.392 of moving rooms, against 0.500 in the six hours before. The room keeps calling more than rooms that did not move, which stand at 0.290 at the same hours (finding F-002, bounded). It goes back to choosing a spot, and often to a fresh call.

What is left behind. A finished mark is celebrated together [A07]; where hour 73 cut the work unfinished, the room marks the attempt (A07's bound). What is celebrated is recorded [A08]. What is recorded is carried on into banners, later canvases and lasting groups [A09] (finding F-004). Placement stops at hour 73. After it, a room can celebrate, record, carry on, keep up its rivalries in talk, and work on copies of the canvas (the tentative P22).

Conditions. The April Fools frame (K01) and doubt about numbers (K02) are conditions. Membership carried in from outside the canvas is in the structure as Collective identity and not in the model. Two candidates stand for it:

• a quarrel carried in (K03): its one test had 9 rooms and failed;
• membership carried in (K04), narrowed at pass 4 to the nation claimed beyond the mark, colour faiths and frames: its first concept comes before the first attack in 52 of 126 rooms (0.413), below the null mean of 0.532 (F-011). The reverse, attack first and membership told after, shows in that count. It was not declared and is not tested.

A claim, untested for order (C02, pass 5). In some rooms a tie the members had before the canvas names the rival in the same turn that calls for or carries out the attack: a league or school rivalry, a nation's history, an ideology, lore. "You mean WPI? I'm down for a lil interpolytechnic griefing." [rpi/c0022]. Read in the story rooms of passes 1 to 4, 10 turns in 7 rooms show it (finding F-013): unitedkingdom, anarcho_capitalism, completeanarchy, CKCrusaders, lakers, cardinals and rpi. The tie and the attack are one turn, so no order statement can count it, and no share of rooms is claimed. It is carried in the rooms' words by J's ruling on QC2-002. The membership candidate (K04) stays a candidate, and F-011 stands beside the claim: membership does not come before the attack more than chance, and in these turns it names the rival in the attack itself.

Hosting. One room's work living on another's mark under the host's rule is a candidate (P19). From pass 4 its four themes sit in Territoriality: hosting is a claim on space, not a partnership. It follows neither exchange, coalition, upkeep nor border talk. Hosts that give a ground for a ruling most often give space or design (F-012). The six hosts whose own rulings are cited all have no posts in the week before the canvas. Hosts with readers before the canvas (sweden, catalunya, smashbros) rule on guests too.

The reviewer's errors, as carried here

The reviewer's nine errors (C2c, review-C2.md) were answered under rule 13 in notes-C2.md. The next list gives where each accepted error lands in this file:

• error 2, A02's instances were joining lines: new instances under A02;
• error 3, A04's instances: new instances under A04, with switzerland's own order beside them;
• error 4, A05's one-turn instance: a transition under A05;
• error 5, transformers: a failure of A20's mechanism, under A20 and in its bound;
• error 6 in part and error 8, bounds tagged as uses: in this file and in story-p4.md a bound is named as the arrow's bound;
• error 7, "founded by the canvas": "no posts in the week before the canvas", in the prose above and under where the model should break;
• error 9, "Present": every order arrow now says "the order fails in N of M rooms" and gives the failure clause's count apart.

Error 1 (A01's instance as a coordinate) was refused. The reviewer's reading is printed beside the claim under A01.

The elements

The next table lists the 28 elements with their kind, statement, tier, dimension and range. K03, K04 and P19 are candidates, not in the model. The other 25 stand. P02, P17 and K04 were restated at pass 4. C02 was added at pass 5, untested for order.

Every element has a range. 21 of the 25 standing elements are named for what they do. Four (K01, K02, C01, C02) are named for a state or a pattern. Fewer than a third are named for what they are about, so the model is not a lattice. K04, a candidate, is named for what it is about.

Why 25. Pass 1's 20 elements stand. Pass 2 added three because the pass 1 story could not tell what 9, 6 and 4 of its twenty rooms did: exchange between rooms (9 rooms), the contest carried on in talk (6), and coalitions (the rooms that entered the canvas through other rooms). Pass 3 added the host's line around canvas talk, which the pass 2 story could not tell in 4 of its 32 rooms. Pass 4 added none. Pass 5 adds the claim C02 by J's ruling on QC2-002: in 7 of the story rooms read at passes 1 to 4, a tie the members had before the canvas names the rival in the same turn as the attack, and no order statement can count that.

What pass 4 restated.

• P17 is now coalitions alone: kindred hubs, alliances, shared chats, tallies of kindred works, joint marks. Hosting left it with its themes, so P17 no longer holds a room ruling on guests.
• P02 now holds making the land's flag or its emblems the mark. The rule written first: a theme whose acts draw or settle what the room's own mark shows goes with the mark's content. Read against their gates, two members of Flagging the nation do that, building the homeland's flag (T3-065) and drawing national emblems (T3-113). The other ten claim, argue or narrate the nation beyond the mark.
• K04 loses those two themes and keeps the nation beyond the mark, colour faiths and frames.

Each process and condition enters only with a grounded arrow. The two claims stand on findings and carry no arrow: C01 on F-006, and C02 on F-013, untested for order. The quarrel carried in, membership carried in and hosting had no grounded arrow and stay candidates. P19's four themes are in Territoriality and are not used while P19 is a candidate.

The arrows

The next table lists the 20 arrows in the model. For each it gives the kind, the strength, the rooms where the connection statement holds out of those carrying both elements, the permutation null (500 shuffles of labels within each room, seed 20261014), the holds on the early and late sides of the onset contrast, and whether the base rate is beaten. A11 and A19 were recounted at pass 4.

The connection statement, written before every count: "in a room carrying both, the first concept of FROM comes before the first concept of TO". It is a statement of order. The null holds each room's coded turns and their hours fixed, and shuffles which element each turn belongs to. A relation that holds nearly everywhere is not deleted by its base rate. A03, A16 and A20 are in part constitutive: a work must stand before it can be kept, an attack must be called before it can be reined in, and a canvas post must exist before it can be removed or objected to.

The failure clause, counted at pass 4. Each order arrow's failure clause says that TO comes only before any FROM. The second statement, "in a room carrying both, some concept of TO comes after the first concept of FROM", fails in exactly those rooms. Below, each arrow gives two numbers: the rooms where the order statement fails, and the smaller number where the failure clause holds. Pass 3's "Present" counted the first and labelled it as the second (the reviewer's error 9).

Tests, by pass. Pass 2 ran twelve order tests and seven beat the null; A14 and A19 beat the 95th percentile by 0.009 and 0.044, so they are thin. Pass 3 ran seven and three beat it; one entered the model (A20). Pass 4 ran eight declared tests; at 0.05 each, eight give about 0.4 false passes by chance. Three beat the null: upkeep then coalition on coalitions alone (A19's recount, 0.719 against a 95th percentile of 0.678), and the calls before the host sub's rulings and before members' objections while the canvas runs. Five did not: border talk then coalition (0.679, at the 95th percentile and not above it), exchange then coalition, border talk then hosting, A11 on the widened P02, and membership then attack on the narrowed K04. Pass 4 also recounted standing arrows without adding tests: A20 whole before hour 73, the four arrows from the call without joining lines, and the failure clause of 18 order arrows.

The instance audit (pass 4). Every support transition of every arrow was checked six ways:

• (i) the room holds the arrow's order;
• (ii) both turns are in one thread, the second replies at some depth to the first, by another author, later;
• (iii) both lines are cited under the two elements' themes;
• (iv) the first line's words, read whole, do the FROM act;
• (v) the second line does the TO act as a new act answering the first;
• (vi) the printed quote is the store's text, with its hour and the interval.

Checks (i), (ii), (iii) and (vi) ran by script and (iv) and (v) were read. Of 48 transitions, 34 pass and 14 fail. 9 fail check (i), because the room does not hold the order. 3 fail check (iii). 3 fail on reading, and latin fails both (i) and (iv). Every failing transition stays in arrows.jsonl with its failure in its audit field. None was swapped out. Every arrow but A10 keeps at least one passing transition. A10 rests on quotes.

Every arrow is grounded codes-read: the concepts were read across rooms, and each arrow rests on quotes and, except A10, a transition in one thread that passes the audit.

Each arrow, with its mechanism, the observation that would show it failed, the two failure counts, its bound, the sampled rooms that failed, and its instances with their audit:

• A01, the call brings the hands that build (P01 to P03). Mechanism: a call brings members to the canvas who then start or extend the mark and say how far it has come. Fails if: build reports come only before any call. The order fails in 53 of 190 rooms; the failure clause holds in 8. Without joining lines: 132 of 189 (0.698) against a 95th percentile of 0.492. Bound: where a member has begun the mark before any call, the call follows the first build. Sampled and failing: xenoblade_chronicles. Transitions: 164 in 70 rooms. Instance: "Help us draw Metroid over at /r/place!" [metroid/c0001], answered one minute later by the location and a report of the placed piece: "Zoom in without moving around to see the top of Samus's head." [metroid/c0002]. It passes the audit. Read another way (the reviewer's error 1, refused): c0002 gives coordinates, so it could be read as a template act (P04) and not a build report. It is cited under building and reporting the mark, and its words report a piece already placed; I keep the build reading. latin c0010 to c0011 fails: in latin the first call and the first build report fall in the same hour (h49.48), and its first line, "Consider me conscripted!", joins rather than calls.
• A02, a start gives the call something to gather around (R01 to P01). Mechanism: a member who proposes or begins a mark gives the room something to answer, and calls gather around it. Fails if: calls come only before any proposal or start. The order fails in 25 of 89 rooms; the failure clause holds in 9. Without joining lines: 63 of 88 (0.716) against 0.568. Bound: where the room calls before anyone proposes, the proposal answers the call (worldoftanks, day9). Sampled and failing: worldoftanks. Transitions: 59 in 27 rooms. Instances, both passing: "I say we make an OG logo and change it to GREENWALL. Anyone down?" [opticgaming/c0191], answered one minute later: "We're all gonna have to come together to get it done." [opticgaming/c0192]; kerbalspaceprogram c0026 to c0028, 37 minutes. Pass 3's instances (sips, habs) answered the start with a joining line, not a call (the reviewer's error 2, accepted).
• A03, a built mark becomes a mark to keep (P03 to P05). Mechanism: once a mark stands on a surface anyone can change, keeping it becomes the work. Fails if: upkeep comes only before any build report. The order fails in 109 of 291 rooms; the failure clause holds in 8. Bound: where the mark was found already placed, or a rival attacked first, upkeep comes first. All four sampled rooms hold. Transitions: 214 in 85 rooms. Instance, passing: "It's done!" [monsterhunter/c0082], answered one minute later by "time for upkeep now" [monsterhunter/c0083]; reddevils c0124 to c0125 also passes.
• A04, keeping the mark brings the room to its neighbours (P05 to P08). Mechanism: keeping a mark against erosion brings the room up against the neighbours whose pixels erode it, and it talks with them. Fails if: border talk comes only before any upkeep. The order fails in 166 of 401 rooms; the failure clause holds in 18. Bound (pass 1): on the late side rooms talk with neighbours first (6 of 15 hold). Bound (pass 2): border talk also comes first where the work was found already placed (unitedkingdom), where a room entered the canvas through another room's offer (yuyuyu), and where neighbours were present from the room's first post (sweden, worldoftanks). Transitions: 293 in 129 rooms. Instances, both passing: "We have to stop this takeover!" [unturned/c0059], answered 53 minutes later: "Maybe we can arrange something with r/rarepuppers to get them to build somewhere else?" [unturned/c0060]; "bmo has been run over by the weird grey bar obsession group!" [adventuretime/c0064], answered: "They are too strong to be beaten through force. Diplomacy is our only option now" [adventuretime/c0065]. Pass 3's switzerland pair invoked a treaty made earlier, and DestinyTheGame fails the order (the reviewer's error 3, accepted in part). switzerland's own order holds: first upkeep h5.38, first treaty talk h18.62. The field (C4): one buffer was negotiated in r/place at hours 5.00 to 7.08 (62mg1j). One episode does not test this count, and the bound for neighbours present from a room's first post already covers it (field-C4.md, list 3, item 5).
• A05, a settled border is a line members keep (P08 to P07). Mechanism: a settled border gives members a line to keep, and they spare the neighbour's work by it. Fails if: sparing comes only before any border talk. The order fails in 52 of 158 rooms; the failure clause holds in 13. Bound: sparing is often tacit and first. Sampled and failing: edmontonoilers, totallynotrobots. Thin. Instance, passing: "Cool, but can you keep the [tiny rick]" [asktransgender/c0003], answered two minutes later: "We have a policy to not harm any artwork" [asktransgender/c0004]. Pass 3 printed one uncited turn, ubc c0084 (the reviewer's error 4, accepted).
• A06, scripts arrive under strain (P05 to P14). Mechanism: upkeep under attack outruns one pixel per interval, and members turn to scripts and spare accounts. Fails if: machine hands come only before any upkeep. The order fails in 43 of 203 rooms; the failure clause holds in 12. Bound: where a room scripted the building from the start; spare accounts can also serve an attack before any upkeep (canucks). Sampled and failing: canucks. Transitions: 117 in 53 rooms. Instance, passing: "We're fighting on several fronts, but this is a war we shall win" [ubc/c0089], answered two minutes later: "I got three accounts going right now, and an overdue essay I'm prioritizing over. We. Cannot. Give. In." [ubc/c0090]; TheFarLeftSide c0384 to c0385 also passes. Pass 3's foxes instance fails check (i): foxes' first machine hands (h69.26) come before its first upkeep (h70.63).
• A07, a finished mark is celebrated together (P03 to P11). Mechanism: a mark reported done gives the room a finished thing to point at, and the room celebrates it. Fails if: celebration comes only before any build report. The order fails in 100 of 282 rooms; the failure clause holds in 4. Bound: where the first mark was found made by others, the room celebrates the find; where hour 73 cut the work unfinished, the room marks the attempt ("We almost did it!" [ultrahardcore/c0212]; a watermark mourned in totallynotrobots). Transitions: 96 in 47 rooms. Instance, passing: suomi c0097 to c0098, "Me teimme sen!", 17 minutes. touhou c0090 to c0129 fails on reading: its second line, "The bomb is already done tho. lol", corrects the first and does not celebrate.
• A08, what is celebrated is recorded (P11 to P12). Mechanism: celebrating the work turns members toward keeping a record of it. Fails if: records come only before any celebration. The order fails in 64 of 289 rooms; the failure clause holds in 11. Bound: on the late side the record often comes first (8 of 15 hold). Transitions: 259 in 108 rooms. Instance, passing: "Place 2017, we did it guys. Good work." [lakers/c0226], answered in one minute by an account of the border [lakers/c0227]. titanfall c0211 to c0212 fails on reading: its first line posts the final image, a record and not a celebration.
• A09, the record is what passes on (P12 to P13). Mechanism: a record of the work gives the room something to carry. Fails if: carrying on comes only before any record. The order fails in 32 of 145 rooms; the failure clause holds in 8. Bound: where a room adopted its mark as an emblem while still building (texans). Sampled and failing: texans. Instance, passing: "Petition to add that image to the subreddit theme." [uiuc/c0155], 46 minutes after the final image [uiuc/c0154]; mexico c0369 to c0370 also passes.
• A10, too few hands, so the room moves (K02 to P10). Mechanism: a room that judges it has too few hands to hold its spot stops fighting for it and moves. Fails if: a move comes with no doubt before it. The order fails in 10 of 21 rooms; the failure clause holds in 3. Bound: where a room moves early by choice; where a late room writes its judgment of too few hands after the move (guatemala, h79.1); where a room inside a coalition moves by the coalition's plan with no doubt of its own (MiamiHurricanes). Sampled and failing: anarcho_capitalism. Thin. Its one transition, paranatural c0020 to c0021, fails check (i): paranatural moved at h38.15, before its doubt at h54.27. The instance is now a holding room's words: "Everyone has given up... Osu is taking over." [fivenightsatfreddys/c0623, h33.55] and, 14 minutes later in the same thread but not as a reply, a proposal "to abandon the effort of keeping the one we have now alive and instead focus on moving it" [fivenightsatfreddys/c0341]. No transition in a holding room passes all six checks.
• A11, a template settles a design argued in a thread (P02 to P04). Mechanism: design talk in a thread is settled by someone posting a template. Recounted on the widened P02: 100 of 166 rooms (0.602) against a 95th percentile of 0.639. Its order between rooms is still at chance, so it is kept as a transition. Sampled and failing: texas, empiredidnothingwrong. Instance, passing: "Maybe make it 20x20? Or just a purple W?" [udub/c0008], answered: "Will update template image and upload here." [udub/c0009]; wallstreetbets c0161 to c0162 also passes.
• A12, the cheapest answer to a call (P01 to P15). Mechanism (from conversation analysis, C3b): A call is the first part of a pair: posted to a thread, it makes an answer from each reader the next thing due. Joining is the answer the call prefers, so it comes bare, one line that commits and gives no reason ('I'm in'); declining is the dispreferred answer and comes with a reason. A bare one-line join is the ordinary way a call is accepted. Stage C2's sentence: A call is answered at the lowest possible cost: one line that commits the member and asks for nothing back. Fails if: The one-line pledges in a room answer no call, or every answer to a call is long and conditional. Or joins answer a call with reasons as often as refusals do, or refusals come as bare as joins. Tested on attack calls only (C3b); on calls to place this clause is not addressed. Never counted as an order. Instance, passing the checks that apply: "LETS CREATE THE DESTINY LOGO IN THE CENTER OF r/Place" [DestinyTheGame/c0002], answered "I'm in" [DestinyTheGame/c0008]. Pass 3's instance, lebanon c0026 to c0027, fails check (iii): its call is cited under building the homeland's flag, which is the mark's content and not a call. pcmasterrace c0904 to c0905 also fails check (iii).
• A13, short of hands, a room turns to other rooms (P05 to P16). Mechanism: a room keeping its work under strain runs short of hands and turns to other rooms for help, and other rooms send it. Fails if: help is traded only before any upkeep. The order fails in 69 of 240 rooms; the failure clause holds in 14. Bound: where a room helps before it has a work of its own, or comes to the canvas as another room's helper. All four sampled rooms hold. Transitions: 106 in 44 rooms. Instance, passing: "I wish people wouldn't keep placing different colored blocks on our letters just to mess with us." [aceattorney/c0049], answered one minute later: "Maybe we should ask the Danganropa subreddit for support." [aceattorney/c0050]; dragonquest c0036 to c0037 also passes. Pass 3's naruto instance fails check (i): naruto's first help (h27.81) comes before its first upkeep (h39.06).
• A14, a settled border opens a channel for help (P08 to P16). Mechanism: talk over a border opens a channel through which the two rooms trade help. Fails if: help is traded only before any border talk. The order fails in 76 of 214 rooms; the failure clause holds in 15. Bound: thin, 0.009 above the null's 95th percentile. All four sampled rooms hold. Transitions: 108 in 44 rooms. Instance, passing: "Hi, I'll be the ambassador for WIT on /r/place, we arent trying to write over you guys." [littlewitchacademia/c0049], answered: "Thank you very much! I'll stick around as often as I can to help maintain your logo :P" [littlewitchacademia/c0051]; sooners c0033 to c0034 also passes. ElSalvador c0006 to c0007 fails check (i).
• A15, a call's hands can turn on a rival (P01 to P09). Mechanism: a call brings members to the canvas, and some turn its hands against a rival's work instead of, or before, building the room's own. Fails if: attack calls come only before any call to place. The order fails in 36 of 129 rooms; the failure clause holds in 7. Without joining lines: 91 of 129 (0.705) against 0.535. Bound: where a room's first canvas act is an attack (edmontonoilers, canucks, anarcho_capitalism), the attack call is the first call. All four sampled rooms hold. Transitions: 34 in 19 rooms. Instance, passing: "me and my roommate are trying to make one in that spot rn if you wanted to join in" [Temple/c0005], answered four minutes later: "Conversely we could aim for right over the Penn State logo" [Temple/c0007]; completeanarchy and stlouis also pass.
• A16, an attack call is refused inside the room (P09 to P07). Mechanism (from conversation analysis, C3b): A call to attack makes an answer from the room due in its thread. Members who do not want the attack refuse it, rein in the attackers or apologise to the target; refusing is the dispreferred answer, so it comes with a reason, and the reason states the room's norm or the attack's cost ('Nah, keep /r/place neutral.'; 'Why? That'll just cause them to want to attack us'). Stage C2's sentence: A call to attack another room's work is answered inside the room: members refuse it, rein in their attackers or apologise to the target. Fails if: In a room, sparing and restraint come only before any attack call, or attack calls draw no refusal. Or refusals of attack calls come as bare as acceptances. Tested (F-014): refusals of attack calls gave a reason in 23 of 38 read pairs, acceptances in 2 of 14; refusals were not longer. The order fails in 22 of 104 rooms; the failure clause holds in 5. Bound: partly constitutive; where sparing is tacit and first (touhou, calgaryflames), restraint comes before any attack call. Sampled and failing: touhou, calgaryflames. Transitions: 127 in 52 rooms. Instances, all three passing: "Wipe out the Dolphins. They're building." [nyjets/c0086], answered in one minute: "Nah, keep /r/place neutral." [nyjets/c0087]; "How about we just work on our own and not be assholes" [leafs/c0240]; "No, stop messing with other schools" [Temple/c0054].
• A17, an attack call is met with a truce (P09 to P08). Mechanism: a call to attack is met by the room's relations with its neighbours: members invoke a truce or propose a deal. Fails if: border talk comes only before any attack call. The order fails in 77 of 172 rooms; the failure clause holds in 17. Bound: early side only; on the late side border talk comes first (0 of 4). Sampled and failing: strangerthings. Transitions: 73 in 35 rooms. Instance, passing: "Let is be us for once who invades! Texas shall fall" [czech/c0151], answered four minutes later: "We [already agreed to a truce here]" [czech/c0153]. PlaceNL c0042 to c0043 and thailand c0162 to c0165 fail check (i): in both rooms border talk comes first.
• A18, an attack is carried on in talk (P09 to P18). Mechanism: an attack makes the rival a named party, and the contest is carried on in taunts, chants, claims of victory and a salute. Fails if: rivalry talk comes only before any attack. The order fails in 12 of 68 rooms; the failure clause holds in 2. Bound: early side only; no late room carries both. All four sampled rooms hold. Transitions: 50 in 14 rooms. Instances, passing: "Help us hijack the WPI r/place!" [rpi/c0024], answered: "Come at us bro" [rpi/c0026]; anarcho_capitalism c0088 to c0089. clg c0040 to c0041 fails check (i): clg's rivalry talk (h12.62) comes before its first attack (h37.54).
• A19, under attack, works join in coalitions (P05 to P17). Mechanism: a room keeping its work against attack joins other rooms whose works face the same threat. Fails if: coalitions come only before any upkeep. Recounted on coalitions alone: 87 of 121 rooms (0.719) against a null mean of 0.614 and a 95th percentile of 0.678. The order fails in 34 of 121 rooms; the failure clause holds in 7. Bound: on the late side no room of 4 holds, since late rooms enter the canvas through other rooms (bretagne, MiamiHurricanes, yuyuyu); thin. Sampled and failing: lakers (pass 4), bretagne. Transitions: 52 in 28 rooms (pass 2's count, on the element with hosting). Instance, passing: "Now we get to defend it" [criticalrole/c0057], answered four minutes later: "hopefully those friendly folks at RWBY and the Bold and Brash people help on occasion" [criticalrole/c0058]. Pass 3's naruto instance fails check (i): naruto joined a coalition (h32.15) before any upkeep (h39.06). yugioh c0107 to c0110 fails check (iii): its second line is a host's ruling, which left the coalition element with the recut.
• A20, the calls fill the host sub, and the sub draws a line (P01 to P20). Mechanism: calls to the canvas flood the host sub, and its moderators or members answer by drawing a line around canvas talk: one thread, removals, a canvas sub. Fails if: the line comes before any call, or the line's words name no canvas flood. The order fails in 23 of 155 rooms, of three kinds: the sub's automatic rules remove the first call as it is posted (9 rooms, three in the same hour); a canvas sub or megathread is set up before the host carries any call (7); members dismiss the canvas or object to other rooms' canvas posts before the room calls (7). The failure clause's first half holds in 5. By actor, while the canvas runs (before hour 73): the calls come before the host sub's rulings (megathreads, removals, a canvas sub, disowning the work, pausing events, new posting rules) in 102 of 118 rooms (0.864, 95th percentile 0.644), and before members' objections (to the flood, or to the canvas's worth) in 57 of 64 (0.891, 95th percentile 0.688). Both beat the null, so by the rule written first A20 stands on the whole line: 122 of 144 rooms before hour 73 (0.847, 95th percentile 0.618). Without joining lines: 129 of 154 (0.838) against 0.584. The mechanism fails in transformers: the order holds there, but its first line, at h80.40 after the close, is a member's judgment of the canvas's worth and names no flood (the reviewer's error 5, accepted). Bound: partly constitutive; the three paths above; and a judgment of the canvas's worth after the close, which answers no flood. Transitions: 29 in 22 rooms. Instances, all three passing: "Help build a Mario in /r/place!" [nintendo/c0120], answered 17 minutes later: "Maybe want to go to the /r/place Megathread where we're trying to build a Mario... slowly..." [nintendo/c0121]; "Can we just stop posting about r/place please? It's becoming just spam at this point" [rocketleague/c0722]; "N'y a t il pas de super poteau pour cette requête?" [france/c0444].

Tentative entries from the field (stage C4)

These entries came from the field, not from my rooms. Each is a hypothesis. Stage D sends it to every room, marked tentative and with no word of where it came from, and each room says from its own record whether it shows its side, contradicts it, or says nothing. None is counted, and none enters the counts above.

• P21, process (tentative, from the field). Members dispute who may commit the room to an agreement with other rooms: they say that one member's agreement does not bind every placer, deny that a treaty speaks for them, or ask another group for a leader to deal with. Range: from one member saying that a deal cannot stop everyone to a treaty announced in r/place answered 'You don't speak for me, man.'. Sits under T3-126. Level: between rooms; a room shows its side in its own members' talk. The field's mark: firm: the disclaimers, the denial and the request for a group leader are public exchanges; provisional: that an agreement or coalition prompts the dispute. Field support: r/place 62mg1j c60256; r/place 62mg1j c60257; r/place 62mg1j c60265; r/place 62qib1 c720095; r/place 62qib1 c720105; r/place 62qib1 c720108; r/place 62qib1 c720109. Room side found so far: flyers:c0166, flyers:c0169.
• P22, process (tentative, from the field). After placement ends, members contest which version of the canvas and of the event is kept: they ask a cleanup of a shared copy to fix their work, take part in it, argue that the cleanup should keep the damage as history, and correct accounts of the event that describe their group wrongly. Range: from one member asking that a logo be cleaned in a shared copy to a room arguing that its scars are its history. Sits under T4-027. Level: the event (a shared copy and public histories of the whole canvas); a room shows its side in its own members' talk after hour 73. The field's mark: firm: the sector instructions, the question of who decides, the retention decision, the objection to sterilising history and the correction promised are public exchanges; provisional: that preserving a shared object requires negotiating its legitimate version; the execution of the cleanup is not observed. Field support: r/place 63f0qb c3920184; r/place 63f0qb c3920185; r/place 63f0qb c3920186; r/place 63f0qb c3920193; r/place 63e1pb c3910162; r/place 63e1pb c3910163; r/place 63b6md c3850139; r/place 63b6md c3850142. Room side found so far: AMD:c0435, SquareSpiral:c0217, strangerthings:c0145.
• A21, P08 to P21 (tentative, from the field). Connection: in a room carrying both, the first agreement with another room (a border, a truce or a deal) comes before the first dispute over who may commit the room. Mechanism: An agreement made with another room in the room's name puts its members' compliance in question. Members who did not make it say that it does not bind them, or that no one can bind every placer, and the other side asks who can speak for the group. Fails if: In a room carrying both, the dispute over who may commit the room comes only before any agreement with another room, or the dispute answers no agreement. Level: between rooms; the order is counted inside each room's record. The field's mark: provisional: 'a protective coalition claim prompts participants to examine who can commit a group' (field/model.md, process 4); the field's instance is a protective treaty, which my model would place under deals (P08) or coalitions (P17). Field support: r/place 62mg1j c60256; r/place 62mg1j c60257; r/place 62mg1j c60265; r/place 62qib1 c720095; r/place 62qib1 c720105; r/place 62qib1 c720108; r/place 62qib1 c720109; r/place 62qib1 (a treaty announced between major factions). Room side found so far: flyers:c0166, flyers:c0169.

Theorised arrows, and the model with and without them

No arrow rests on my reading alone. Two arrows do not rest on an order count that beats a shuffle, and they are listed apart as theorised:

• A11: its order across rooms is at chance, at pass 4 as at pass 3, and it stands on transitions inside threads only.
• A12: never counted, on exemplars only. Since C3b its mechanism is conversation analysis's, tested on attack calls and not on calls to place.

Four more are counted and beat the null, but thinly: A05, A10, A14 and A19. A10 now rests on quotes alone, since its one transition fails the audit.

Without the two theorised arrows, the model can no longer say how a room settles a design under argument, or why calls are cheap to answer.

Without all six weak arrows, the model keeps the spine (A02, A01, A03, A04, A06), the host's line (A20), exchange under strain (A13), the contest (A15, A16, A17, A18) and the close (A07, A08, A09). It loses why rooms with neighbours mostly do not fight (A05), what sends a room back (A10), help traded along a border (A14), and coalitions (A19). The second of the four things then has no counted answer.

The model on the dimensions

The next table gives, per dimension, the mass of coded turns answering coded turns across the dimension's boundary (c2_dim_mass-p4.txt). Rooms are beside each count. The last three columns drop every transition touching a double. Of 56,071 transitions with both ends placed, 31,636 touch no double. The masses changed at pass 4 for Coordination without command and Collective identity only, because the land's flag and emblems moved from the second to the first. The hosting recut stayed inside Order without law.

The next table states the arrows at the dimension level. Each row names the arrows beneath it, a mechanism written at that level, the observation that would show it failed, the strongest instance beneath that passes the audit, and the transition mass from the first dimension to the second.

Pass 3's table printed sips c0026 to c0027 for the second row and naruto c0144 to c0145 for the fourth. The first is a joining line (the reviewer's error 2). The second fails the audit's check (i).

One cross-dimension arrow is reported as mass, not as a dimension-level arrow. A10 runs from Critical mass to Order without law, but it rests on 21 rooms, against a mass of 1,257 transitions of other traffic. A12 runs from Critical mass to a form-pass element outside the dimensions. A05 and A14 lie inside Order without law, A08 and A09 inside Imprinting, A11 inside Coordination without command, and A18 inside Contention.

What the arrows and masses show:

• Contention is not residue. One arrow runs in (from Critical mass) and two run out (to Order without law). Its masses are close to balanced (407 in, 309 out, without doubles). The contest is fed by mobilized hands and answered by the order between rooms.
• Order without law draws in about twice what it sends (1,776 against 892 without doubles). Six arrows run into it from other dimensions (A04, A13 and A19 from Maintenance, A10 from Critical mass, A16 and A17 from Contention) and none out, so it is residue: the model ends there.
• Imprinting is residue too: A07 runs in and nothing runs out. Its masses say otherwise: 1,121 transitions go into Maintenance and 1,298 into Order without law, since "we did it" posts are answered by repair and border talk (see the ungrounded relationships).
• Host framing is almost all internal (6,839 against 226 out, without doubles). One arrow runs in (A20, from Critical mass) and none out, so it is residue: the host's line answers the calls, and no arrow says what the line does to the room's work. Finding F-009 says the play frame does not delay the canvas work across rooms.
• Collective identity carries no arrow. Its candidates failed: the quarrel carried in on 9 rooms, and membership carried in on 145 rooms at pass 3 and on 126 after the flag and emblems left it (F-011). With those two themes gone, its in-mass without doubles fell from 565 to 461 and its out-mass from 643 to 245.

Dynamics

• Loops. None is grounded. A within-room loop needs one room's dated chain to run the whole cycle. Passes 4 and 5 add no arrow, so no loop can close. The contest runs from calls to attack to restraint or truce, and nothing grounded runs from restraint or truce back to a call. The move-and-rebuild candidate (loss, move, build, keep) still lacks an arrow from the move to building that beats its base rate. model/loops.jsonl is empty.
• What returns a room to a state it had left: a loss. The room goes back to choosing a spot and cutting its design to what can survive. Its calls fall from the crisis before the move, but it keeps calling more than rooms that did not move (F-002, bounded).
• What is irreversible across hour 73: placement stops. Calls to place, building, upkeep, machine hands, attacks, help traded in pixels and deals over pixels end with it. After hour 73 a room can celebrate, record and carry on (A07, A08, A09), call for a later canvas, judge the canvas's worth, and keep a rivalry going in talk (victory claims, salutes, blame after the close). Its organizing of placement on this canvas is over. Organizing around the canvas's records and copies goes on after it (P12, P13; the tentative P22; field-C4.md, list 3, item 1).
• Dating by the hour of the post (C4). Each order count dates a concept by the hour of its post. A retrospective report posted late does not date the act it reports. Because the counts compare first concepts, such a report moves an element's first hour only when it is the room's only concept of that element (field-C4.md, list 3, item 6).

Ungrounded relationships

These relations have a count and no mechanism I have stated and tested. They are correlations, in_model false by definition, listed so that stage C5 can mark anything that rests on them. Counts are from mem.py pairs and c2_dim_mass-p4.txt.

• Completion ritual answered by repair work: 1,167 transitions in 274 rooms (fourth-order ledger).
• Completion ritual answered by border talk: 805 transitions in 221 rooms.
• Coordination without command into Order without law: 3,196 transitions, the largest cross-dimension mass, and 1,975 back.
• Imprinting into Order without law: 1,298 transitions.
• Collective identity into Order without law: 441 transitions (848 at pass 3, before the flag and emblems left Collective identity).
• Order without law into Contention: 598 transitions. Deals broken may turn into attacks; no arrow from talk to attack was tested.
• Membership carried in, then hosting (K04 to P19, pass 3): 21 of 28 rooms (0.750 against a 95th percentile of 0.714). Its declared mechanism (guests come to the body's mark) shows in 5 of the 21 rooms. 16 show the reverse role: a room asks a host for space after laying its own mark (c2_first_concepts-K04-P19-p3.txt). Not in the model, and not recounted on the narrowed K04.
• Hosting, then coalition: 12 of 17 rooms carrying both put hosting first (pass 3). The reverse of a declared test, not declared and not tested.
• Attack, then membership carried in (pass 4): on the narrowed K04 the first attack comes first, or in the same hour, in 74 of 126 rooms. The reverse of a declared test, not declared and not tested.

Looked for and not found

Each of these was tested and not grounded. They are results (rule 8).

Pass 1:

• Attribution as the hinge between restraint and contention. P06 to P07 holds in 0.452 of rooms against a null mean of 0.456. P06 to P09 holds in 0.194 against 0.408, reversed.
• A room under attack, then repair or a move. P09 to P05 holds in 0.444 against a 95th percentile of 0.449. P09 to P10 holds in 0.561 against 0.610.
• Doubt, then calls. K02 to P01 holds in 0.175 against 0.352, reversed.
• Machine hands, then upkeep. P14 to P05 holds in 0.202 against 0.375, reversed.
• Emblem before template, as an order between rooms: at chance.

Pass 2:

• Exchange, then sparing. P16 to P07 holds in 0.427 against 0.494.
• Border talk, then coalition. P08 to P17 holds in 0.632 against a 95th percentile of 0.654.
• Exchange, then coalition. P16 to P17 holds in 0.384 against 0.450.
• A quarrel carried in, then attack. K03 to P09 holds in 2 of 9 rooms.
• Attack, then the room's own building. P09 to P03 holds in 0.385 against 0.469, reversed: rooms build first.
• The play frame delaying the canvas work. 59 frame-filled rooms start at a median h21.80, against h20.25 for 275 others (p 0.43; F-009).
• A move stopping the room's calls. A move lowers calling from the crisis before it, but not below other rooms (F-002, bounded; c2_relocation_window-p2.txt).

Pass 3:

• Membership carried in, then attack. K04 to P09 holds in 0.593 of 145 rooms against a 95th percentile of 0.634 (F-011).
• Exchange, then hosting. P16 to P19 holds in 0.379 of 29 rooms against 0.552.
• Coalition, then hosting. Coalitions without hosting, then P19, holds in 0.294 of 17 rooms, below the null mean of 0.451.
• Upkeep, then hosting. P05 to P19 holds in 0.635 of 52 rooms against 0.654.
• A host admitting guests by fit with the body it carried in. Of 23 cited rulings that give a ground, 6 give fit with the nation, colour or theme, 12 give space or design, and 5 give ties (c2_vetting_tally-p3.txt; F-012).

Pass 4 (c2_arrow_evidence-p4a.txt):

• Border talk, then coalition, on coalitions alone. P08 to P17 holds in 74 of 109 rooms (0.679), at the 95th percentile of 0.679 and not above it.
• Exchange, then coalition, on coalitions alone. P16 to P17 holds in 31 of 79 rooms (0.392) against 0.570.
• Border talk, then hosting. P08 to P19 holds in 22 of 39 rooms (0.564), below the null mean of 0.604.
• Membership carried in, narrowed, then attack. K04 to P09 holds in 52 of 126 rooms (0.413), below the null mean of 0.532 (F-011).
• The design before the template, on the widened P02. P02 to P04 holds in 100 of 166 rooms (0.602) against 0.639: still at chance (A11).
• The call's boundary with one-line joining, as a change to any arrow. With the joining lines stripped out, no arrow from the call changes its beaten status (c2_arrow_evidence-p4c.txt). P01 holds some joining lines the coders placed with calls, and the boundary is reported as read, not recut.

Pass 5: no test was run. By J's ruling on QC2-002, membership naming the rival in the same turn as the attack is carried as a claim (C02), untested for order.

The tiers the arrows run between, and what the model does not use

Most arrows join two elements tied to fourth-order themes. A02 runs from a pair of third-order themes (R01) to a fourth-order theme. A10 runs from a fourth-order theme to a pair of third-order themes (P10). A12 runs to a form-pass finding (P15). Five standing elements carry no arrow: P06, K01, C01, C02 and R02.

At pass 5 the script's rule counts 41 of 197 unused (c2_unused_t3-p5.md). The rule lets a standing element use every member of its fourth-order themes, so C02 takes up Frame bridging and Flagging the nation. C02 uses them only as the words of a tie in an attack turn, untested for order, and nothing else in the model uses them. I report both counts: 41 with C02 and 55 without it. The next list is the 55, as pass 4 left it.

The next list gives the 55 of 197 third-order themes the model does not use without C02 (c2_unused_t3-p4.md; 53 at pass 3), grouped by fourth-order theme. The two pass 4 recuts changed the list. The four hosting themes, now in Territoriality, are unused while P19 is a candidate. The land's flag and emblems are now used, through P02. K04's members are listed as unused, since K04 is a candidate.

• T4-003 Sensemaking (3): T3-016 explaining what the canvas is; T3-018 decoding the finished picture's details; T3-052 remarking on neighbouring pictures.
• T4-004 Frame bridging (4; in the candidate K04): T3-086 carrying in the sub's quarrel (the candidate K03); T3-179 arguing ideology from the canvas; T3-135 telling clashes as fandom lore; T3-031 playing the room's in-jokes.
• T4-010 Backstage decision-making (7): T3-014 moving planning into a chat; T3-107 keeping planning in the thread; T3-109 arguing which chat to use; T3-114 disputing the chat's authority; T3-116 hiding the plan from rivals; T3-132 spying in a rival's chat; T3-152 announcing what the chat decided.
• T4-014 Territoriality (9; its other two members are P10): T3-020 choosing a canvas spot; T3-039 yielding space when asked; T3-123 refusing to give up space; T3-012 granting a neighbour room; T3-045 arguing who was there first; and the candidate P19's four, T3-035 asking a host for space, T3-094 disputing who approves a spot, T3-099 relying on a bigger neighbour, T3-162 vetting others' requests to build.
• T4-022 Flagging the nation (10; in the candidate K04): T3-078 helping kin nations' flags; T3-079 joining flags with a heart; T3-085 weighing the room against nations; T3-145 feeling national through the canvas; T3-165 debating friendship with historic enemies; T3-180 disputing national belonging; T3-081 casting fights as national history; T3-130 reading national politics in pixels; T3-142 making ethnic jokes about rivals; T3-166 arguing the nation's historical record.
• T4-023 Neo-tribes (6; in the candidate K04): T3-137 joining an outside group's build; T3-096 hailing the colour corners; T3-163 defecting from a rival faction; T3-171 spreading a faction's colour; T3-174 professing loyalty to a colour; T3-190 splitting a faction over doctrine.
• T4-024 Symbolic boundaries (5): T3-080 arguing over political symbols; T3-146 covering swastikas and hate symbols; T3-177 calling to draw swastikas; T3-182 shutting down bigotry in chat; T3-143 judging whether a joke offends.
• T4-025 Visibility returns (9): T3-051 pushing posts up the rankings; T3-053 spelling slogans with post titles; T3-110 placing a tile as payment; T3-044 recruiting canvas visitors; T3-129 making passers-by notice a demand; T3-189 fearing newcomers the mark draws; T3-196 drawing lapsed fans back; T3-127 seeking the creators' notice; T3-147 sharing the work's press coverage.
• Unpicked by any fourth-order theme (2): T3-017 carrying on ordinary sub talk; T3-133 recovering a hacked sub.

What was dropped, and which of the five it failed. The five are the concept and the contract's four things. Each item below was considered as an element and left out, because at pass 4 the model says nothing different about any of the five without it.

• Sensemaking would bear on becoming able to act. No arrow was formed.
• Frame bridging, Flagging the nation and Neo-tribes would bear on becoming able to act and on what followed, as membership carried in. Tested as one condition (K04) at pass 3 and again, narrowed, at pass 4: it does not come before the attack more than chance, and at pass 4 it falls below the null mean. Its count before hosting rests on the reverse of its declared mechanism. The quarrel carried in alone failed at pass 2.
• Symbolic boundaries would bear on settling what to act on (which symbols may be drawn). Left out of K04 by declaration; no arrow was formed.
• Hosting (four members of Territoriality from pass 4) would bear on what followed between rooms. Tested as P19: it follows neither exchange, coalition, upkeep (pass 3) nor border talk (pass 4).
• Backstage decision-making would bear on settling what to act on. Chat decisions reach the record only as announcements.
• Visibility returns would bear on what is left behind. No arrow was formed. The reviewer set recruiting canvas visitors and drawing lapsed fans back beside the call. It was to be considered only if P01 were recut at its boundary with joining, and P01 was not recut. At pass 5 it is the residue of six story rooms: scp, carried from pass 4, and five of the 11 fresh rooms (parahumans, TheAdventuresofTintin, shishamo, hunterxhunter, luciomains). In them the mark brings readers to the sub or back to the topic, and the room talks about the newcomers. The story says it is one room's residue; at pass 5 it is six rooms'. No element was added, because the pattern showed only during the reading and no test was declared for it. It is material for the next stage.

Where the model should break, in its own terms

• Rooms whose canvas work is one thread (ultrahardcore): the spine collapses into one exchange, and the model can still tell it (below).
• Rooms where a starter places alone and no one answers: R01 with no P01.
• Bag rooms (greenlattice t03), where many acts between rooms each carry a few concepts: P07, P08, P09, P16 and P17 cannot be told apart there.
• Late rooms that enter the canvas through other rooms (bounds on A04, A17, A19): there the order between rooms comes before the room's own work.
• Rooms that host other rooms' works on their own mark (sweden, catalunya, smashbros, placeDE, greenlattice, orderofthebluecorner, purplecorner, among the pass 3 story rooms). From pass 4 hosting is a claim on space inside Territoriality, and P17 no longer holds it as a coalition. P19 is a candidate with no grounded arrow, so the model can tell a host's claim on its spot, not its rulings on guests. From pass 5 this is stated as a boundary at the return, for hosts with readers before the canvas and without. The vote or form that decided each guest is decided order, which the model counts as rare.
• Colour factions the canvas gathered (greenlattice, purplecorner, orderofthebluecorner, thebluecorner; a boundary at the return from pass 5). Their faith names their rivals: 5 turns in 3 of these rooms pass C02's three checks with a colour as the tie, for example "We need to attack back. Blue the Purple Corner!" [thebluecorner/c0230]. Their faith also rules on guests, by vote and by fit with the colour, and splits the faction over doctrine: art on a coloured backdrop against a pure corner. The model tells their steps from their first post, not their faith, and C02 does not reach them, since a colour faith is not a tie from before the canvas.
• Rooms with no posts in the week before the canvas (78 of 705). An empty week does not show that the canvas founded a room: side subs, quiet subs and bodies the canvas gathered all have one. The six hosts whose rulings are coded as vetting are all among them, but hosts with readers before the canvas (sweden, catalunya, smashbros) rule on guests too. The pass 3 rooms of this kind (rainbowgrid, pgang, placecanada, CKCrusaders, purplecorner, greenlattice, orderofthebluecorner) run the story's steps from their first post. What three of them do after it, as hosts ruling on guests and as colour faiths naming a rival, the model does not reach.
• Rooms whose answers the coders dropped: the enrolment and many replies are not in the record.

The three strongest arrows, read as artefacts

The three are chosen by the gap between share and null mean: A20 (0.314), A16 (0.259) and A01 (0.254). For each, the argument is that the order comes from which turns the coders chose to code and how they labelled them.

• A20. A removal, a pointer to the megathread or an objection to the flood is coded as such only when there is a canvas post to remove, point or object to, so the line would follow the first call by definition. What separates it from a pure artefact: P20 also holds acts that need no call in the host sub (opening a canvas sub, arguing the canvas's worth), and 23 rooms draw the line first. In 22 rooms a line by another member or a moderator replies to a specific call in the same thread within minutes (29 transitions). Counted by actor while the canvas runs, both the host sub's rulings and members' objections follow the calls. transformers shows the artefact's edge: a judgment of the canvas's worth after the close follows the calls in order and answers none of them.
• A16. A refusal is coded as reining in an attacker only when there is an attack call to refuse, so restraint would follow attack by definition. What separates it from a pure artefact: P07 also holds tacit sparing and apologies, which need no prior call, and 22 rooms spare first. In 52 rooms a refusal by another member replies to a specific attack call in the same thread, within minutes (127 transitions). All three printed instances pass the audit.
• A01. A call is usually a submission title, the first turn of its thread, and build reports are comments under it. What separates: the null keeps each room's coded turns and hours fixed, so the choice of turns is held constant. In 53 rooms the order fails, and in 8 no build report comes after the first call. 70 rooms have a build report replying to a call (164 transitions). With the joining lines stripped out of the call, the order still holds in 132 of 189 rooms.

Two tests

Every element has a range. See the elements table.

The odd room: ultrahardcore, read again whole at pass 4 against the pass 4 model. The April Fools frame (K01) filled the room from h7.65 to h40: 193 of its 212 coded items fall before h40, and only a question about the canvas at h40 touches it. The offensive posts coded under ethnic jokes belong to the frame's licence and claim no nation, so the narrowed K04 does not reach them. The moderators' play with their own powers belongs to the frame; the host sub drew no line around canvas talk, so A20 does not fire. Across rooms the frame does not delay the canvas work (F-009), so ultrahardcore's late start is the room's own, inside the frame. At h57.58 a starter asked for a design (R01). Within half an hour the thread had a proposal (P02), a template, a spot and an order: "Make it completely red first." [ultrahardcore/c0209] (A11). Building followed (P03). There was no second call, no neighbour, no help from another room, no coalition, no host and no contest, so A03, A04, A13, A15 and A19 never fired. At the close the room marked an attempt cut short ("We almost did it!" [ultrahardcore/c0212]; A07's bound) and recounted it (P12). The model tells it as a late, compressed spine that the clock cut before upkeep. What it cannot say is why this room, inside a frame that does not delay most rooms, came so late.

ultrahardcore at pass 5, read again whole against the pass 5 model and story: told. The pass 4 reading above missed one short exchange. The thread first proposed taking over other works' hearts: "Let's take over some of the hearts" [ultrahardcore/c0203] at h57.91 (A15). Five minutes later a member spared one: "Maybe not that heart, since it was the first heart made on /r/place and people want to keep it blank." [ultrahardcore/c0206] (A16). The thread then turned to an outer heart (c0207). So the contest did fire, inside one thread and within minutes of the start, and was answered inside the room. No tie from before the canvas names the target, so C02 does not reach it, and the frame's offensive posts claim no nation, so K04 does not either.

The model, stage C2, pass 1 (C2a-01)

The model is typed: elements in model/elements.jsonl, arrows in model/arrows.jsonl, every change in model/history.jsonl, loops in model/loops.jsonl (empty at pass 1). Counts come from assignments_final.jsonl through out/_analysis/c2_arrow_evidence.py, whose outputs are out/_analysis/c2_arrow_evidence-p1a.txt, -p1b.txt and -p1c.txt. The apparatus tables are printed by out/_analysis/c2_model_tables.py, the dimension masses by c2_dim_mass.py, and the unused themes by c2_unused_t3.py.

The model relates presences and their order in time, never amounts. No coder wrote down a covariation between degrees, so no arrow is drawn between degrees.

What the model says, in prose

The contract asks the model for four things: how a scattered readership becomes able to act and how it settles what to act on; what sends a group back to that beginning; what brought organizing about when it came, and what followed; and what is left behind. Pass 1's model answers them with a spine, a fork between rooms, and a close.

How a scattered readership becomes able to act. A member proposes a mark or begins it (R01). Calls gather around the start [A02], and calls bring the hands that build [A01]. The cheapest answer to a call is a one-line enrolment, "On it.", which commits a member and asks for nothing back [A12]. Where a member placed first, the call follows the first build and recruits to a mark already begun (A01's bound).

How it settles what to act on. The room settles what its mark will show (P02). Inside a reply thread, a template settles a design under argument [A11]. Across rooms the first template is as likely to come before design talk as after it. The half-built mark itself tells the next placer what is missing (P03). Decided order, such as a leader, a vote or an oath, is rare (C01; finding F-006).

What brought organizing about when it came, and what followed. Organizing came when someone started and others answered [A02] [A01]. Upkeep followed: once a mark stands, keeping it becomes the work [A03]. Upkeep brings the room up against the neighbours whose pixels erode it, and the room talks with them [A04]. A settled border gives members a line they keep [A05], though most sparing is tacit and comes before any talk (A05's bound). Upkeep under attack outruns one pixel per interval, and members turn to scripts and spare accounts [A06] (finding F-005). Why organizing came when it did is the part the model holds least. The April Fools frame (K01) filled some rooms for a day or more before any canvas talk, and no arrow from it has been tested.

What sends a group back to the beginning. A loss. A room that judges it has too few hands stops fighting for its spot and moves [A10]. The move returns it to choosing a spot more than to recruiting. After a relocation, calls and build reports come less often than a shuffle of the room's own concepts would make them (finding F-002). Four of the twenty pass 1 story rooms, day9 among them, still called members in again after a loss, so this is a corpus rate and an open question (_questions/relocation-renewed-calls.md). day9 is the case of the move. Its border agreement broke at h48. Members chose to move at h49.7, made it official at h50.7, and finished the new work at h53.1 (finding F-003).

What is left behind. A finished mark is celebrated together [A07]. What is celebrated is recorded [A08]. What is recorded is carried on into banners, later canvases and lasting groups [A09] (finding F-004). Placement stops at hour 73. After it, a room can only celebrate, record and carry on.

Conditions. The April Fools frame (K01) and doubt about numbers (K02) are conditions. Membership carried in from outside the canvas (the nation, the fandom, the colour tribe) is in the structure as Collective identity and not in the model. Only K02 carries a grounded arrow at pass 1.

The elements

The next table lists the 20 elements with their kind, statement, tier, dimension and range.

Every element has a range. 17 of the 20 are named for what they do. Three (K01, K02, C01) are named for a state or a pattern. Fewer than a third are named for what they are about, so the model is not a lattice.

Why 20. The four things and the concept need 17 elements:

• becoming able to act: R01, P01 and P15;
• settling what to act on: P02, P03, P04 and C01;
• what brought organizing about and what followed: P05, P07, P08, P14 and K01;
• what sends a room back: K02 and P10;
• what is left behind: P11, P12 and P13.

The other three (P06 attribution, P09 attack, R02 the envoy) carry the hinge from Attribution to Live and let live or Repertoire of contention, which the interview asked the model to test. That hinge was tested and not grounded (below). The three elements stay without arrows because the within-case rooms need them: ubc refused to retaliate against a neighbour, and day9 named a diplomat.

The arrows

The next table lists the 12 arrows in the model. For each it gives the kind, the strength, the rooms where the connection statement holds out of those carrying both elements, the permutation null (500 shuffles of labels within each room, seed 20261014), the holds on the early and late sides of the onset contrast, and whether the base rate is beaten.

The connection statement, written before every count: "in a room carrying both, the first concept of FROM comes before the first concept of TO". It is a statement of order. The null holds each room's coded turns and their hours fixed and shuffles which element each turn belongs to. A relation that holds nearly everywhere is not deleted by its base rate. A03 is in part constitutive, since a work must stand before it can be kept, and its 109 counterexamples show it is not only that. Every arrow is grounded codes-read: the concepts were read across rooms, and each arrow rests on quotes and on at least one transition in one thread.

Each arrow, with its mechanism, the observation that would show it failed, its bound, the sampled rooms that failed, and its instances:

• A01, the call brings the hands that build (P01 to P03). Mechanism: a call brings members to the canvas who then start or extend the mark and say how far it has come. Fails if: in a room, build reports come only before any call, or calls are followed by no build report. Present: in 53 of 190 rooms. Bound: where a member has begun the mark before any call, the call follows the first build and recruits to a mark already started. Sampled and failing: xenoblade_chronicles (first build h25.04, first call h33.60). Transitions: 164 in 70 rooms. Instances: "Help us draw Metroid over at /r/place!" [metroid/c0001], answered one minute later by the location [metroid/c0002]; latin c0010 to c0011, two minutes.
• A02, a start gives the call something to gather around (R01 to P01). Mechanism: a member who proposes or begins a mark gives the room something to answer, and calls for hands gather around it. Fails if: calls come only before any proposal or start, or a proposal draws no call. Present: in 25 of 89 rooms. Bound: where the room calls before anyone proposes, the proposal answers the call. Sampled and failing: worldoftanks (first call h34.81, first start h72.33). Transitions: 59 in 27 rooms. Instances: "Let's draw sips from 'Spacemen' in r/place" [sips/c0026], answered four minutes later by "I'm in." [sips/c0027]; habs c0047 to c0048, 20 minutes.
• A03, a built mark becomes a mark to keep (P03 to P05). Mechanism: once a mark stands on a surface anyone can change, keeping it becomes the work. Fails if: upkeep comes only before any build report, or a reported build is never watched. Present: in 109 of 291 rooms. Bound: where the mark was found already placed by others, or a rival attacked before the room reported building, upkeep comes first. All four sampled rooms hold. Transitions: 214 in 85 rooms. Instances: "It's done!" [monsterhunter/c0082], answered one minute later by "time for upkeep now" [monsterhunter/c0083]; reddevils c0124 to c0125, two minutes.
• A04, keeping the mark brings the room to its neighbours (P05 to P08). Mechanism: keeping a mark against erosion brings the room up against the neighbours whose pixels erode it, and it turns to talk with them. Fails if: border talk comes only before any upkeep. Present: in 166 of 401 rooms. Bound: on the late side, rooms that came to a full canvas talk with neighbours first, asking for space before they have a mark to keep (6 of 15 hold). All four sampled rooms hold. Transitions: 293 in 129 rooms. Instance: "We're currently under attack. Seems like its coming from the mona lisa guys, I need help fellow swiss people!" [switzerland/c0044], answered in two minutes: "We have a peace treaty with the mona lisa guys and the rainbow." [switzerland/c0045].
• A05, a settled border is a line members keep (P08 to P07). Mechanism: a settled border gives members a line to keep, and they spare the neighbour's work by it. Fails if: sparing comes only before any talk. Present: in 52 of 158 rooms. Bound: sparing is often tacit and first; the arrow holds where restraint rests on a settled border. Sampled and failing: edmontonoilers (sparing at h13.33, border talk at h73.81) and totallynotrobots (h71.04 against h71.71). Thin: 0.671 against a null 95th percentile of 0.658. Transitions: 59 in 31 rooms. Instances: roosterteeth c0097 ("We already established with a guy from /r/halo that the border that collides with them will go under") answered by "That's some quality /r/place etiquette right there" [roosterteeth/c0098]; "We have an agreement with them, we won't mess with each other." [ubc/c0084].
• A06, scripts arrive under strain (P05 to P14). Mechanism: upkeep under attack outruns what one pixel per interval can hold, and members turn to scripts and spare accounts. Fails if: machine hands come only before any upkeep. Present: in 43 of 203 rooms. Bound: where a room scripted the building itself from the start. Sampled and failing: canucks (machine hands h29.32, upkeep h39.37). The reverse order (P14 to P05) was tested first and holds in 0.202 against a null mean of 0.375. Transitions: 117 in 53 rooms. Instances: "DEFEND THE FOX WITH EVERYTHING YOU HAVE." [foxes/c0061], answered in one minute by a console script; TheFarLeftSide c0384 to c0385; "I got three accounts going right now..." [ubc/c0090], two minutes after c0089.
• A07, a finished mark is celebrated together (P03 to P11). Mechanism: a mark reported done gives the room a finished thing to point at, and the room celebrates it together. Fails if: celebration comes only before any build report. Present: in 100 of 282 rooms. Bound: where the first mark was found already made by others, the room celebrates the find. All four sampled rooms hold. Transitions: 96 in 47 rooms. Instances: touhou c0090 to c0129; suomi c0097 to c0098, "Me teimme sen!".
• A08, what is celebrated is recorded (P11 to P12). Mechanism: celebrating the work together turns members toward keeping a record of it: the final image, the timelapse, the list of what changed. Fails if: records come only before any celebration. Present: in 64 of 289 rooms. Bound: on the late side the record often comes first, a screenshot of a work found rather than built (8 of 15 hold). All four sampled rooms hold. Transitions: 259 in 108 rooms. Instances: "Place 2017, we did it guys. Good work." [lakers/c0226], answered in one minute by an account of the border at the end [lakers/c0227]; titanfall c0211 to c0212.
• A09, the record is what passes on (P12 to P13). Mechanism: a record of the work gives the room something to carry. Fails if: carrying on comes only before any record. Present: in 32 of 145 rooms. Bound: where a room planned its next canvas or its banner while still building. Sampled and failing: texans (carrying on at h34.50, record at h73.21). Transitions: 26 in 13 rooms. Instances: "I cleaned up the final UIUC /r/place section. Thanks to everyone who helped out!" [uiuc/c0154], answered 46 minutes later by "Petition to add that image to the subreddit theme." [uiuc/c0155].
• A10, too few hands, so the room moves (K02 to P10). Mechanism: a room that judges it has too few hands to hold its spot stops fighting for it and moves. Fails if: a move comes with no doubt before it. Present: in 10 of 21 rooms. Bound: where a room moves early by choice rather than after a loss. Sampled and failing: anarcho_capitalism (move at h9.03, doubt at h32.91). Thin: 21 rooms, one transition. Instances: "Guess we're a little too small to make this work" [paranatural/c0020], answered in one minute by "We're in a new spot now." [paranatural/c0021]; "it looks like this is a losing battle. I'll help move it" [day9/c0023].
• A11, a template settles a design argued in a thread (P02 to P04). Mechanism: design talk in a thread is settled by someone posting a template that fixes it. Its order between rooms was tested and is at chance (0.556 against 0.557). The arrow is kept as a transition inside threads, with base_rate_beaten false. Sampled and failing: texas (template h5.87, design talk h23.45) and empiredidnothingwrong (h9.55 against h55.92). Transitions: 82 in 36 rooms. Instances: "Maybe make it 20x20? Or just a purple W?" [udub/c0008], answered in four minutes: "Will update template image and upload here." [udub/c0009]; wallstreetbets c0161 to c0162.
• A12, the cheapest answer to a call (P01 to P15). Mechanism: a call is answered at the lowest possible cost, one line that commits the member and asks for nothing back. Never counted: a form-pass finding travels on exemplars. Sampled: fivenightsatfreddys holds; teamcube not testable. Instances: "Help us build the lebanese flag! In the middle of the orange patch (10, 840)" [lebanon/c0026], answered 37 minutes later by "On it" [lebanon/c0027]; DestinyTheGame c0002 to c0008, "I'm in"; pcmasterrace c0904 to c0905, "On it".

Theorised arrows, and the model with and without them

No arrow rests on my reading alone. Two arrows do not rest on an order count that beats a shuffle, and they are listed apart as theorised:

• A11: its order across rooms is at chance, and it stands on transitions inside threads only.
• A12: never counted, on exemplars only.

Two more are counted and beat the null, but thinly: A05 (just above the null's 95th percentile) and A10 (21 rooms).

Without the two theorised arrows, the model loses two things. It can no longer say how a room settles a design under argument (A11), or why calls are cheap to answer (A12). Everything else stands.

Without the four thin arrows, the model is the spine A02, A01, A03, A04 and A06, and the close A07, A08 and A09. It still says how a room becomes able to act, what followed, and what it leaves behind. It loses two more things: why rooms with neighbours mostly do not fight (A05), and what sends a room back (A10). The second of the four things then has no answer in the model.

The model on the dimensions

The next table gives, per dimension, the mass of coded turns answering coded turns across the dimension's boundary. It comes from _views/transitions.tsv lifted through the placements by out/_analysis/c2_dim_mass.py. Rooms are beside each count. The last three columns drop every transition touching a double (a second-order theme placed on two third-order themes). Of 56,071 transitions with both ends placed, 31,636 touch no double.

The next table states six arrows at the dimension level. Each has one arrow beneath it, which supplies the strongest instance. The last column is the transition mass from the first dimension to the second, from the same script.

One cross-dimension arrow is reported as mass, not as a dimension-level arrow. A10 runs from Critical mass to Order without law, but it rests on 21 rooms, while the mass between the two dimensions is 1,417 transitions of other traffic. A12 runs from Critical mass to a form-pass element outside the dimensions. A05 lies inside Order without law, A08 and A09 inside Imprinting, and A11 inside Coordination without command.

What the arrows and masses show:

• Order without law draws in about twice what it sends (2,028 against 1,046 without doubles). Two arrows run into it (A04 and A10) and none out, so in the stage file's terms it is residue: the model ends there. That is drift toward the order between rooms.
• Imprinting is residue too: A07 runs into it and nothing runs out. Its masses say otherwise. It sends 5,577 transitions out and draws 3,631 in, with 1,121 into Maintenance and 1,630 into Order without law. "We did it" posts are answered by repair and border talk, because a celebrated work is still being kept. No mechanism is written for that yet (see the ungrounded relationships).
• Host framing is almost all internal (6,839 against 226 out, without doubles). The April Fools frame talks to itself. It carries no arrow, so at pass 1 it is a condition with nothing tested from it.
• Critical mass sends more than it draws (1,076 against 696 without doubles). Calls lead into the rest.
• Collective identity carries no arrow. Its masses are smaller and close to balanced (643 out, 565 in, without doubles).

Dynamics

• Loops. None is grounded. A within-room loop needs one room's dated chain to run the whole cycle. The candidate is the room that loses its spot, moves and rebuilds (K02 to P10 to P03 to P05, and back to loss). day9 runs it once, from h48 to h53.1. The model has no arrow from P10 to P03 that beats its base rate (finding F-002), so the loop cannot close. model/loops.jsonl is empty.
• What returns a room to a state it had left: a loss. The room goes back to choosing a spot and cutting its design to what can survive. Across rooms it goes back to recruiting less often than chance (F-002), though day9, texas, scp and worldoftanks called members in again after a loss.
• What is irreversible across hour 73: placement stops. Calls to place, building, upkeep, machine hands and deals over pixels end with it. After hour 73 a room can celebrate, record and carry on (A07, A08 and A09 cross it in most rooms), or call for a later canvas. Its organizing for this canvas is over.

Ungrounded relationships

These relations have a count and no mechanism I have stated and tested. They are correlations, in_model false by definition, listed so that stage C5 can mark anything that rests on them. Counts are from mem.py pairs and c2_dim_mass.py.

• Completion ritual answered by repair work: 1,167 transitions in 274 rooms (fourth-order ledger).
• Completion ritual answered by border talk (Negotiated order): 805 transitions in 221 rooms.
• Coordination without command into Order without law: 3,128 transitions, the largest cross-dimension mass, and 2,154 back. Design and building may change borders, and deals may change designs. Neither is tested.
• Imprinting into Order without law: 1,630 transitions. Recounting after the close often names neighbours.
• Collective identity into Order without law: 1,169 transitions. National rooms may talk borders more because their membership is set before the canvas. No mechanism is written or tested.

Looked for and not found

Each of these was tested at pass 1 and not grounded. They are results (rule 8).

• Attribution as the hinge between restraint and contention. P06 to P07 holds in 0.452 of rooms against a null mean of 0.456. P06 to P09 holds in 0.194 against 0.408, reversed. Working out who changed the work does not, across rooms, come before sparing or before attack.
• A room under attack, then repair or a move. P09 to P05 holds in 0.444 against a null 95th percentile of 0.449. P09 to P10 holds in 0.561 against 0.610. The attack a room suffers is usually another room's act, so this link runs between rooms. It needs joint dated evidence from two rooms, which pass 1 did not assemble.
• Renewed calls or building after a move. Under "some TO after the first FROM", P10 to P01 holds in 0.722 against a null mean of 0.962, and P10 to P03 in 0.754 against 0.939. Both are below chance (F-002).
• Doubt, then calls. K02 to P01 holds in 0.175 against a null mean of 0.352, reversed. Calls come first and doubt follows them.
• Machine hands, then upkeep. P14 to P05 holds in 0.202 against 0.375, reversed. A06 replaced it.
• Emblem before template, as an order between rooms: at chance. A11 keeps only the transition.
• The play frame delaying the canvas work. ultrahardcore suggests it. It was not tested across rooms at pass 1.

The tiers the arrows run between, and what the model does not use

Nine of the 12 arrows join two elements tied to fourth-order themes (A01, A03, A04, A05, A06, A07, A08, A09 and A11). A02 runs from a pair of third-order themes (R01) to a fourth-order theme. A10 runs from a fourth-order theme to a pair of third-order themes (P10). A12 runs from a fourth-order theme to a form-pass finding (P15). Five elements carry no arrow at pass 1: P06, P09, K01, C01 and R02.

The next list gives the 82 of 197 third-order themes the model does not use, directly or through their fourth-order theme, grouped by fourth-order theme (out/_analysis/c2_unused_t3.py).

• T4-002 Boundary work (8): T3-015 routing canvas posts into megathreads; T3-063 removing canvas posts by rule; T3-075 objecting to the canvas flood; T3-140 moderators disowning the canvas work; T3-184 pausing the sub's usual events; T3-185 changing the sub's posting rules; T3-090 opening a canvas sub; T3-037 arguing the canvas's worth.
• T4-003 Sensemaking (3): T3-016 explaining what the canvas is; T3-018 decoding the finished picture's details; T3-052 remarking on neighbouring pictures.
• T4-004 Frame bridging (4): T3-086 carrying in the sub's quarrel; T3-179 arguing ideology from the canvas; T3-135 telling clashes as fandom lore; T3-031 playing the room's in-jokes.
• T4-010 Backstage decision-making (7): T3-014 moving planning into a chat; T3-107 keeping planning in the thread; T3-109 arguing which chat to use; T3-114 disputing the chat's authority; T3-116 hiding the plan from rivals; T3-132 spying in a rival's chat; T3-152 announcing what the chat decided.
• T4-014 Territoriality (5; its other two members are P10): T3-020 choosing a canvas spot; T3-039 yielding space when asked; T3-123 refusing to give up space; T3-012 granting a neighbour room; T3-045 arguing who was there first.
• T4-017 Reciprocity (7): T3-011 helping another room's work; T3-071 letting neighbours adopt the work; T3-084 asking other rooms for help; T3-115 turning away another room's request; T3-122 sending greetings to another room; T3-151 bartering help with neighbours; T3-072 thanking the room's allies.
• T4-018 Meta-organization (9): T3-153 meeting other rooms in chat; T3-035 asking a host for space; T3-094 disputing who approves a spot; T3-099 relying on a bigger neighbour; T3-162 vetting others' requests to build; T3-150 forming alliances between rooms; T3-013 gathering kindred rooms together; T3-019 tallying kindred rooms' works; T3-056 making joint marks with others.
• T4-021 Rivalry (5): T3-058 blaming attackers after the close; T3-050 trading taunts with rivals; T3-134 flooding rivals' threads with chants; T3-154 claiming victory over rival rooms; T3-155 saluting rivals after the fight.
• T4-022 Flagging the nation (12): T3-065 building the homeland's flag; T3-078 helping kin nations' flags; T3-079 joining flags with a heart; T3-085 weighing the room against nations; T3-113 drawing national emblems; T3-145 feeling national through the canvas; T3-165 debating friendship with historic enemies; T3-180 disputing national belonging; T3-081 casting fights as national history; T3-130 reading national politics in pixels; T3-142 making ethnic jokes about rivals; T3-166 arguing the nation's historical record.
• T4-023 Neo-tribes (6): T3-137 joining an outside group's build; T3-096 hailing the colour corners; T3-163 defecting from a rival faction; T3-171 spreading a faction's colour; T3-174 professing loyalty to a colour; T3-190 splitting a faction over doctrine.
• T4-024 Symbolic boundaries (5): T3-080 arguing over political symbols; T3-146 covering swastikas and hate symbols; T3-177 calling to draw swastikas; T3-182 shutting down bigotry in chat; T3-143 judging whether a joke offends.
• T4-025 Visibility returns (9): T3-051 pushing posts up the rankings; T3-053 spelling slogans with post titles; T3-110 placing a tile as payment; T3-044 recruiting canvas visitors; T3-129 making passers-by notice a demand; T3-189 fearing newcomers the mark draws; T3-196 drawing lapsed fans back; T3-127 seeking the creators' notice; T3-147 sharing the work's press coverage.
• Unpicked by any fourth-order theme (2): T3-017 carrying on ordinary sub talk; T3-133 recovering a hacked sub.

What was dropped, and which of the five it failed. The five are the concept and the contract's four things. Each fourth-order theme below was considered as an element and left out, because at pass 1 the model says nothing different about any of the five without it. The list says where each would bear if pass 2 brings it in.

• Boundary work: would bear on what brought organizing about when it came. A host that routes or removes canvas posts may delay the work. Untested; pass 2 tests it with the play frame.
• Sensemaking: would bear on becoming able to act. No arrow was formed.
• Frame bridging and Rivalry: would bear on what followed, through attack. No arrow was formed.
• Backstage decision-making: would bear on settling what to act on. A decision made in a chat reaches the record only as an announcement, so its order cannot be read from the threads.
• Reciprocity and Meta-organization: would bear on what followed. In bag rooms they cannot be told apart from border talk (P08). Pass 2 tests one element of exchange for them.
• Flagging the nation, Neo-tribes and Symbolic boundaries: would bear on becoming able to act, as membership carried in. Identity is not tested as a condition yet.
• Visibility returns: would bear on what is left behind, as attention gained. No arrow was formed.

Where the model should break, in its own terms

• Rooms whose canvas work is one thread (ultrahardcore): the spine collapses into one exchange. The model can still tell it (below).
• Rooms where a starter places alone and no one answers: R01 with no P01. The model expects no hands and has no element for a work one person keeps.
• Bag rooms (greenlattice t03), where many acts between rooms each carry a few concepts: P07, P08 and P09 cannot be told apart there.
• Late rooms that talk with neighbours before they have a work (A04's bound).
• Rooms whose answers the coders dropped: the enrolment and many replies are not in the record.

The three strongest arrows, read as artefacts

The three are chosen by the gap between the share and the null mean: A01 (0.254), A03 (0.233) and A08 (0.214). A07 (0.212) is next. For each, the argument is that the order comes from which turns the coders chose to code and how they labelled them.

• A01. A call is usually a submission title ("Help us draw X"), the first turn of its thread, and build reports are comments under it. If coders coded titles more often than comments, the call would come first because of what was coded. What separates the two: the null keeps each room's coded turns and their hours fixed and shuffles only the labels, so the choice of turns is held constant. In 53 rooms the coded build report comes before any coded call, so coders did code builds that had no call before them. In 70 rooms a build report replies to a call in the same thread (164 transitions), which is an act answering an act.
• A03. A coder labels a turn "upkeep" only once something stands, so repair would follow building by definition. It is partly constitutive and is kept as such. What separates it from a pure artefact: in 109 rooms upkeep or defence comes before any build report, on marks found already placed or attacked first. In 85 rooms an upkeep turn replies to a build report in the same thread (214 transitions).
• A08. Coders may have coded the closing post first and the screenshot replies after it. Screenshots are also posted after placement ends. What separates the two: in 108 rooms a record replies to a celebration in the same thread (259 transitions). In 64 rooms the record comes first, which coding order alone would not produce.

Two tests

Every element has a range. See the elements table.

The odd room: ultrahardcore. The model tells it as one way of running the same structure. The play frame (K01) filled the room from h7.7 to h40: 193 of its 212 coded items fall before h40, and only one of them, a question at h40 about what the room had done on the canvas, touches it. At h57.6 a starter asked for a design (R01). Within half an hour the thread had a proposal (P02), a template, a spot and an order: "Make it completely red first." [ultrahardcore/c0209] (A11). Building followed (P03), but there was no second call, no defence and no neighbour, so A03 and A04 never fired. At the close the room wrote "We almost did it!" [ultrahardcore/c0212] and recounted the unexpected end (P11, P12). The model tells it as a late, compressed spine under the play frame, cut by the clock before upkeep. What the model cannot say is why the frame held the room so long. That is the untested arrow from K01.

Notes, stage C4 (the model against the field)

Order kept

• The branch. This leg runs in the branch claude-v43-1--C4-field, made from claude-v43-1 after C3c. The handler recorded no file overrides. Earlier validation belongs to the original inputs. This leg's checks are its own.
• The startup packet. I read AGENT.md, the head, the stage file, the last five diary lines and validate.py --open C4 (0 errors, 0 warnings).
• The field's arrival. field/ held model.md (1,206 words) and check.md (1,298 words). I logged its arrival before I opened it.
• My own model first. I read model-C3.md whole. I then wrote the three claims a view of the whole event could most easily overturn into field-C4.md and logged them. Only then did I open field/model.md and field/check.md, each whole.
• The PI's message. It carried my answers from the C3c interview fork, which I did not see, and J's ruling on language. The next section says which answers I used.

The field's folder and the validator (QC4-001)

The handler's placement error, corrected.

• The problem. The stage C4 validator looks for the field at out/field, but the handler placed it at field/ in the run root. As placed, validate.py C4 reported that the field had not arrived, so the close would have failed.
• The interim step. I asked J (QC4-001). Under the assumption stated there, I made out/field a symbolic link to ../field.
• The answer. The handler had put field/ in the wrong place, and the validator was right. The handler asked me not to keep a link, because the close's capture compares real files, and to copy the two files into a real out/field folder.
• What I did. The guard refused to delete the link ("never delete a file"), so I renamed it to out/_field-link-superseded-C4a. I created out/field as a real folder and copied field/model.md and field/check.md into it unchanged. The sha256 sums match the originals: 5708dd9d… and b630db95…. field/ at the run root is untouched. From this point I read the field from out/field.
• What rested on the assumption. Only the validator's reading of the field. The text I read and quoted is byte-identical in both places. Snaps C4-move-relating-51 and C4-move-developing-52 were taken while out/field was the link.
• Still open: QC4-002. It asks whether the handler will remove the renamed link. Meanwhile it stays in place, and nothing reads it.

The answers from the C3c fork: used, and set aside

• Used: "What I trust more passed tests that could have failed." I applied it to the field. Where the field and my rooms both showed a point, I trusted it. Where the field showed one episode against a count over hundreds of rooms, I trusted the count on the order (field-C4.md, list 3, item 5).

• Used: order between rooms as a problem for any organization whose work sits next to others' work on a surface no authority allocates. The two field entries both live between rooms, as that answer expects.

• Set aside for a later stage:

  • the correction to the C3a ruling on Felin and Zenger (the setting differs, not the subject);
  • the arrow from the move back to the goal, which would close the first loop;
  • Visibility returns;
  • the recalled source for Stigmergy.

  Each needs the literature or a test the stage C4 file does not allow. The head carries them.

J's ruling on language

From this leg on I write descriptively. I use short sentences in the active voice and name the actor and the act. The new text in field-C4.md, in model-C4.md's stage C4 section, and in the two amended declarations follows the ruling. The older text in the successor files is stage C3's, carried whole. Stage C5 rewrites the story under the ruling.

What the leg did

• The confrontation, in field-C4.md.
  • Five mechanisms appear in both models (list 1).
  • Two mechanisms only the field shows were entered as tentative entries, and two others were not entered, each with its reason (list 2).
  • Six disagreements are listed, each marked substantive, a difference of setting, or a difference of subject (list 3).
• One change the field forced, by move. The prose of two declarations was amended: Standardization of output (a template does not make placers follow it) and Boundary work (most rooms, not every room, existed before the canvas). Each has a tier_history.jsonl line (now 480 lines). The move is relating or contrasting, snapped as C4-move-relating-51.
• Three tentative entries from the field. P21 and P22 are elements and A21 is an arrow. Each has origin: from-field, status: tentative, field_support, the field's firm or provisional mark and a model/history.jsonl line (now 88 lines). The move is developing or dropping working hypotheses, snapped as C4-move-developing-52.
• Successor files written whole by script.
  • model-C4.md (c4_model_md.py) bounds the closure sentence and prints two disagreements beside the model. It also writes in the dating limit and lists the tentative entries.
  • structure-C4.md (c4_structure_md.py) carries the two amended declarations.
  • manifest-C4.txt names both successors. concept-C3.md has no successor.
• Findings. None changed. Rule 14 was applied in the same act as each change. F-016's mapping line for Standardization of output already says that no one can make a placer follow the template. F-010 does not rest on the Boundary work sentence. F-006 and F-004 stand, with the field printed beside them.
• Quotes. I served 14 quotes from my rooms through cite.py. The field's quotes are given as field/ gives them, with their thread and item ids.

What the leg showed that I did not expect

• The field's analyst and my rooms found the same limit of authority. A member in the square says "I don't speak for all rainbownians, but I agree to these terms". A member in flyers says that one user's agreement "doesn't mean every lurker/person active on the sub agrees". The two analysts could not see each other's work.
• Two of my declarations claimed more than my own evidence. The field caught one sentence that my own model had already contradicted (every room existed before the canvas), and one that no test of mine had supported (the template as the strongest coordination). Both were in prose I wrote at stage C1 and never tested.
• My rooms hold the follow-on work after hour 73. They show a cleanup of a shared copy and an argument over keeping its scars. No theme of mine names this, and I had written that organizing for the canvas was over at hour 73.

What I am sure of, and what I am not

• Sure:
  • The five agreements, each shown by a room and a field thread.
  • That the two amended sentences were wrong as written.
  • That none of the three claims I named was overturned.
• Not sure:
  • The field marks its explanations provisional, and the entries rest on them.
  • The room side of P22 was found by a keyword search, not by a theme.
  • A21's direction comes from one field episode.
  • The field read structure-C3.md only in part, so its silence on the rest of my tier is not agreement.
  • QC4-001 is unanswered.

Slips, C4a

• A date in local time. The first version of field-C4.md dated the three claims 2026-10-15. The run's ledgers record UTC, and in UTC it was still 2026-10-14. The line was corrected.
• The stage file's safe stops. I checked for .pause after the first forced change and after the lists, but not after each list separately.
• An edit and its check in one turn. While I cut the head under 3,000 words, the last edit and its word count ran in one turn. The count and the link check ran again in a turn of their own.
• A link where a copy was wanted. I first linked out/field to the handler's folder. J asked for a real copy. The guard would not delete the link, so it is renamed and waits on QC4-002.

The close-check, C4a

python3 tools/validate.py C4, run after the notes body, the handback and the interview brief, and before the head was rewritten:

stage C4:
  entries from the field: 3; successors: model-C4.md, structure-C4.md


0 errors (0 distinct shapes), 0 warnings

done.sh C4 --cut interview runs the same check at the close. Its report is in the leg's closing diary line.

The third-order scheme, B1e

Written at stage B1, leg B1e, 2026-10-11. 197 themes in 21 families; 14 are on the rare tier (seen in one room, or in rooms that tell one episode). Not frozen: stage B2 tightens it against fresh readers.

How to read a theme. Place each second-order theme on one theme. Add a second or a third only where a concept of its own supports it, and say why one does not carry it. The gate is must show, must not show and decide when both. A discriminator is the question that separates a theme from a near neighbour. A family is an index of themes a reader would confuse, and nothing else. Exemplars are participants' words, with the room and the concept id; rivals are other concepts of the same room that also pass the gate.

Index

G01 April Fools in the sub

• T3-001 staging April Fools fake news: Members post their own April Fools fakes in the sub as if true (news, leaks, patches, releases, claims) and play along with them, fall for them or reveal them.
• T3-023 running an April Fools takeover: The sub is turned into something else for April Fools, by its moderators or by the sub as a body (renamed, restyled, given new rules or a new subject, or one sub's joke raid on another), and members play inside it.
• T3-032 objecting to April Fools posts: Members object to the April Fools jokes in their sub as unfunny, stale, hurtful or in the way, and ask for them to stop or come down.
• T3-048 reacting to official April Fools: Members react to the April Fools jokes of the company, creator, channel or organisation the sub follows: waiting for them, judging them, comparing years, missing them.
• T3-064 spreading the room's joke elsewhere: Members carry their sub's joke or in-joke into other subs or sites, or show another sub what the room is doing.
• T3-093 playing with granted moderator powers (rare): Every member is made a moderator for April Fools, and members play with the powers and with losing them.
• T3-095 testing others' April Fools claims: Members work out whether a claim they did not make is an April Fools joke: a moderators' or company's announcement, a public figure's post, a news story, another room's claim, or real news taken for a joke.
• T3-097 switching off the prank styling: Members get past the sub's April Fools look or rules: turning the style off, working around it, reporting what it breaks, asking for it gone, or the moderators switching it back.
• T3-100 keeping April Fools changes afterwards: Members ask that something made for April Fools outlive the day: the sub's flairs, styling or name, or a company's joke feature made real.

G02 the sub's rules and usual posts

• T3-015 routing canvas posts into megathreads: Moderators or members gather the sub's canvas talk into one stickied thread, a megathread, and send other canvas posts there.
• T3-017 carrying on ordinary sub talk: The sub's ordinary business goes on during the canvas week: its usual subject, news, help, jokes and quarrels, apart from the canvas and April Fools.
• T3-051 pushing posts up the rankings: Members ask for upvotes so a post, an image or a joke climbs: up r/place or the front page so placers see it, or to the top of a search result.
• T3-053 spelling slogans with post titles: Members post a run of posts whose titles, read down the front page or the sub's listing, spell a slogan or a chant.
• T3-063 removing canvas posts by rule: Moderators, or their bots, remove, filter or flair canvas posts under the sub's standing rules, and members ask about or contest the removals.
• T3-075 objecting to the canvas flood: Members object that canvas posts crowd out the sub's usual talk, and ask for them to stop, be condensed or move.
• T3-106 calling a network boycott (rare): Members answer a TV network's April Fools prank by calling for a boycott: piracy, cancelled subscriptions, complaints.
• T3-110 placing a tile as payment: A member offers to place a canvas tile in return for an upvote or a favour.
• T3-133 recovering a hacked sub (rare): The moderators recover the sub after a moderator's account is hacked and used to change it.
• T3-140 moderators disowning the canvas work: The sub's moderators say the canvas work is not the sub's: members may go on, but not in the sub's name.
• T3-184 pausing the sub's usual events: The sub puts one of its recurring events on hold for the canvas and resumes it after.
• T3-185 changing the sub's posting rules: Moderators change the sub's posting rules around the canvas or April Fools, and members argue the change.

G03 where the planning happens

• T3-014 moving planning into a chat: The room moves its canvas planning into a chat outside the thread (a Discord most often; IRC, Skype, Telegram, Slack), setting it up, sharing invites and sending members there.
• T3-049 complaining the calls are scattered: Members complain that the room's calls and plans are scattered, duplicated or uncoordinated, and ask for one clear plan.
• T3-090 opening a canvas sub: Members open a separate subreddit for the room's canvas work, or ask for one, and send canvas talk there.
• T3-107 keeping planning in the thread: Members keep the canvas planning in the Reddit thread instead of a chat.
• T3-109 arguing which chat to use: Members argue over which chat to organise in, or whether to use one at all: Discord, IRC, Slack, an official or an unofficial server.
• T3-114 disputing the chat's authority: Members dispute whether the chat may decide for the room: who speaks there, who is left out, whether its plans bind the thread.
• T3-116 hiding the plan from rivals: Members hide the room's plan from rivals who read the thread: private messages, their own language, codes.
• T3-132 spying in a rival's chat: Members watch a rival room's chat from inside, or an outsider watches theirs, and report what they see.
• T3-152 announcing what the chat decided: Members bring the chat's decisions back to the thread: the plan agreed, a change authorised, where to place next.
• T3-153 meeting other rooms in chat: Members meet other rooms in chats (their own, the other's or a shared council) to talk terms, borders or joint work.

G04 calling people in to place

• T3-002 calling members in to place: Members call the room's own members to come and place for its work: to start, build, finish or hold a picture, calls to placers who are not yet a group included.
• T3-044 recruiting canvas visitors: The room's mark on the canvas brings outsiders to the sub; members welcome them, advertise the sub on the canvas for it, or count the newcomers.
• T3-062 recruiting kindred subs to help: Members take the room's call into other subs, mostly kindred ones (sister, regional, related fandoms), to bring more hands to the room's work.
• T3-104 cheering the builders on: Members and passers-by cheer those placing: praise, encouragement and good wishes while the work goes on.
• T3-129 making passers-by notice a demand: Members use the canvas to put a demand before passers-by: a wanted comeback, a new season, a sauce.
• T3-144 recruiting quietly to avoid attackers (rare): Members recruit only inside friendly communities and keep the work small, so that it draws no attackers.
• T3-159 rewarding helpers with prizes: Members reward those who helped the work with prizes: gold, medals, game codes, giveaways.
• T3-189 fearing newcomers the mark draws: Members fear what the canvas mark will bring into the sub: an influx of newcomers who do not read the rules or swamp the community.
• T3-196 drawing lapsed fans back: The room's mark on the canvas brings former fans back to the community; members welcome them or hope it will.

G05 telling placers what to place

• T3-034 asking for coordinates and instructions: Members ask where and how to place: coordinates, instructions, what to do with their pixel.
• T3-066 putting decisions to a vote: A choice about the work is put to the room: a vote, a strawpoll, a call to decide together.
• T3-070 sharing coordinates, templates and how-to: Members circulate what placers need to reproduce the work: coordinates, templates, grids, guides, colour, border and timing plans, and how-to.
• T3-091 keeping everyone on one template: Members hold the room to one official design or plan, against versions and placers that stray.
• T3-101 putting one member in charge: The room puts one member, or a few, in charge of the work, or members ask for someone in charge.
• T3-103 dividing the picture among teams: The work is divided: teams, colours, rows or areas of the picture assigned to members.
• T3-125 saying the room wings it: Members say the room has no plan or group: it goes with the flow, individuals placing on their own.
• T3-141 covering the night shift: Members keep the work through the night and across time zones: night watches, the work handed to another continent while they sleep.
• T3-167 timing a mass placement together: Members set a time to place together so that many pixels land at once.

G06 strain, doubt and giving up

• T3-036 judging the canvas too full: Members judge that the canvas is too full, or too far gone, for the room to join.
• T3-059 urging others to give up: Members tell the room, or its defenders, to give the work up: it is lost, over, not worth the fight.
• T3-074 working around the timer: Members work around the one-pixel cooldown, too few hands and placing troubles while they build.
• T3-098 questioning the room's canvas presence: Members ask whether and how the room shows on the canvas: why it is absent, whether a work counts as the room's, how it compares with other rooms.
• T3-124 weighing fighting against moving: Members weigh, after a loss or under pressure, whether to fight for the spot, rebuild it there, or move elsewhere.
• T3-136 doubting the room's strength: Members doubt that the room has the people or strength for a work: too few, too small, outnumbered, the work impossible.
• T3-181 quitting the effort under strain: Members quit the canvas work themselves: tired, stressed, beaten by scripts or rivals, or at odds with the room.

G07 choosing what to make and where

• T3-004 settling the mark's design: Members work out what the mark should look like (picture, colours, size, lettering, details) and correct it against the plan.
• T3-020 choosing a canvas spot: Members look for and choose where on the canvas the mark goes: open space, a corner, beside kindred marks, a new location.
• T3-033 proposing the room's mark: A member offers the room an idea of what to make on the canvas, and calls the room to make it.
• T3-055 reshaping the mark against tampering: Members change the mark's shape to make it harder to tamper with: borders, boxes, outlines, enlarging or compacting it, dropping parts easily griefed.
• T3-077 animating the mark in timelapse (rare): Members plan a mark that moves or flashes when the canvas is watched as a timelapse.
• T3-092 making a tribute alone: One member makes a small mark for the room, or for someone they admire, on their own and reports it, often asking others to keep it.
• T3-160 building memorials to the dead: Members make or protect memorials on the canvas to people who died: musicians, drivers, relatives, the victims of a disaster.
• T3-169 signing the sub's name: Members put the sub's name on or beside the work: r/name, a sign, a label.
• T3-191 leaving the work unsigned (rare): Members leave the sub's name off the work, so that it draws no attackers or because the builders are not the sub's.
• T3-197 heeding the creator's wishes (rare): The room shapes its canvas work around what the creator of its subject wants: the creator's name kept off, canvas talk moved out of the creator's way.

G08 building and growing the mark

• T3-003 reporting one's own placing labour: Members report their own part in the placing: what they placed, fixed or defended, and when.
• T3-026 announcing the mark is up: Members announce that the room's mark is on the canvas: 'we got on r/place', with a picture or its place.
• T3-038 building and reporting the mark: Members build the mark and report its progress: started, half done, almost there, the next part.
• T3-041 extending the room's work: The room adds pieces to its work or enlarges it: a second picture, another album, a bigger logo, details around the first.
• T3-042 choosing upkeep over expansion: The room puts keeping what it holds before growing: maintain, clean, defend first, no new fronts.
• T3-060 adding a personal piece: Members add their own piece to a mark many share: a word, a heart, a drug's name, a character.
• T3-069 concentrating effort on fewer pieces: The room drops or pauses some of its pieces to put its pixels on one: one priority, one attack point, the rest abandoned.
• T3-082 finding the room's mark placed: Members find a mark of their room already on the canvas, made by others or without them, and point to it.
• T3-175 adopting a sign others began: The room adopts as its own a sign others began: a neighbour's character made a mascot, a stray symbol claimed.
• T3-187 handing the work over: A member who led the work hands it to the community: maintainership passed on, the project kept community-run, a leader stepping down.

G09 defending and repairing the work

• T3-005 defending the work against attackers: Members rally to defend the room's work against an attack under way: alarms, calls to fight back and hold, reports of attacks staved off.
• T3-007 urging repair over retaliation (rare): After an attack, members urge the room to repair its work rather than strike back.
• T3-008 messaging individual placers to stop: Members contact individual placers who damage the work, by private message or by name, and ask them to stop or tell them the plan.
• T3-021 watching and repairing the work: Members keep watch over the room's work and repair it: fixing changed and stray pixels, cleaning, keeping it intact over hours.
• T3-022 relocating after losing the spot: After the work is erased or overrun, the room moves it: a new spot, a smaller version elsewhere, starting again.
• T3-139 pleading with attackers to stop: Members ask the room or group damaging their work to stop or spare it: 'please don't destroy our logo'.

G10 finding who changed the work

• T3-058 blaming attackers after the close: After the canvas closes, members blame the room that destroyed or attacked their work, and keep the grievance alive.
• T3-087 tracing who changed the work: Members work out who changed their work or who sent a call: checking placers, naming rooms, reading signs of bots or scripts.
• T3-118 blaming moderators for a loss: Members blame the sub's moderators, or the site's admins, for a loss: their prank, their removals, help they denied, a rigged game.
• T3-121 excluding the room's own vandals: The room sanctions its own members who damage the work or the room by exclusion: bans from the chat or sub, kicking, shunning, calling them traitors.
• T3-126 disputing who speaks for rooms: Members dispute who may speak or decide for a room toward others: false claims to be its moderator or representative, denials of being one, outsiders told not to decide for its work, no one yet able to speak for the placers.
• T3-170 mistaking friendly work for vandalism: Members find that what looked like vandalism was friendly work or their own mistake, and own or forgive it.
• T3-188 disowning placers outside the plan: An organised room tells others that placers acting in its name or against its plan are not under its control: rogues, the hivemind, individuals outside its chat.
• T3-192 griefing the work for fun: Members grief a work for fun, the room's own or another's, and own it or joke about it.

G11 scripts, bots and extra accounts

• T3-027 arguing whether scripts are fair: Members argue whether scripts and bots are fair: cheating or common practice, against the spirit of the canvas or the only way to hold ground.
• T3-028 running scripts for the work: Members write, share and run scripts or bots that place or keep the room's work.
• T3-088 placing beyond the pixel limit: Members place more than the one-pixel limit allows: extra accounts, alts, throwaway accounts, glitches used to place more.
• T3-089 switching off stale scripts: Members find the room's own scripts fighting its plan (old versions, wrong templates) and switch them off or update them.
• T3-108 sharing one bot target: Rooms pool one bot map or target so that a shared script keeps several rooms' works.
• T3-120 lending accounts to a bot: Members lend their accounts or machines to a bot, another room's or their own room's.
• T3-168 editing scripts to spare neighbours: Members change the room's script so it spares a neighbour: a border left untouched, overlapping pixels removed, a shared image.
• T3-176 planting disguised scripts on rivals: Members plant a script on a rival that secretly works against it: the rival's own script modified to cover its logo, a psyop to sow distrust.

G12 attacking others' work

• T3-006 calling to deface rivals' work: Members call for, plan or carry out attacks that destroy, black out or erase another room's work.
• T3-061 pushing into a neighbour's space: The room grows its own work into space a neighbour holds: expanding over another flag or picture, taking a neighbour's ground.
• T3-067 trading away another room's work (rare): In a deal with a neighbour, a room offers to remove a third room's work.
• T3-068 converting a neighbour's art: Members turn another room's art into the room's own sign: a logo changed into theirs, a flag recoloured into the room's flag, a symbol rewritten.
• T3-128 relaying a streamer's attack call (rare): Members relay a streamer's call for the audience to attack another work, and join it.
• T3-178 brigading one person off Reddit: Members propose or join harassing one person on another site: spamming an Instagram account, screwing with an actor on Twitter.

G13 holding back from others' work

• T3-024 refusing to cover others' work: Members keep the room's work off others' art: going around it, sparing it, sizing the work so it does not cover a neighbour.
• T3-039 yielding space when asked: The room gives ground when a neighbour asks: moving, shifting or shrinking its work, giving a spot back.
• T3-040 apologizing to neighbours for damage: Members apologise to a neighbouring room for damage the room or its members did to its work, often offering to help repair it.
• T3-046 arguing whether covering is fair: Members argue whether covering others' work is fair: an open canvas where anything goes, or a wrong done to others' effort.
• T3-076 reining in the room's attackers: Members tell their own room's attackers to stop: no more attacks, leave the neighbours alone, stop vandalising.
• T3-102 defying the call for restraint: A member goes on attacking or breaks a treaty after the room told them to hold back.
• T3-123 refusing to give up space: Members refuse to give up the room's space when a neighbour asks or presses: 'this is our space', 'we were here first', 'it stays'.
• T3-183 mourning art the room covered: Members mourn or regret art that their own room's work covered.

G14 space and help between rooms

• T3-010 settling borders with neighbours: Neighbouring rooms settle lines, overlaps, moves and spots between their works: borders drawn, a shift of a pixel or two, space shared.
• T3-011 helping another room's work: Members send their pixels to another room's work: helping build, finish or defend it, with nothing asked in return.
• T3-012 granting a neighbour room: The room grants a neighbour space on or beside its work: permission to build in its area, room made in its design.
• T3-035 asking a host for space: Members ask a room that holds space (a host, a faction, a neighbour) for room to build.
• T3-045 arguing who was there first: Members argue which room was at a spot first, with claims, timestamps and accusations of stealing.
• T3-071 letting neighbours adopt the work: A room lets a neighbour take its work into theirs, and thanks them for keeping it.
• T3-084 asking other rooms for help: A room asks another canvas room, as a group, to help with its work: to build, defend or repair it.
• T3-094 disputing who approves a spot: Members dispute whether a room needs another's approval to build, and who may give it.
• T3-099 relying on a bigger neighbour: A small room relies on a bigger neighbour to protect its work, or seeks such protection.
• T3-115 turning away another room's request: Members refuse another room's request for help, space or a cause.
• T3-137 joining an outside group's build: Members put their pixels into another group's build as their own effort: joining the Void, following another sub's plan, all pixels to another room's territory.
• T3-162 vetting others' requests to build: A host room rules on others' requests to build in its space: approvals, denials, conditions, published rules.

G15 pacts and envoys between rooms

• T3-030 disputing how an alliance went: Members dispute an alliance's conduct or worth, often after the close: who kept their word, betrayal, never again.
• T3-047 making up with another sub: Two subs settle a quarrel: apologies, thanks and good wishes exchanged.
• T3-083 negotiating across a language gap: Members deal with another room across a language gap: translating, machine translation, too little of the language to negotiate.
• T3-119 turning attackers into helpers: A room that attacked a work, or members of it, turn to help repair it.
• T3-122 sending greetings to another room: Members send greetings, compliments and thanks to another room with no deal attached.
• T3-138 staying neutral between two rooms: A room keeps out of a fight between others or declares neutrality, or a member is torn between two rooms.
• T3-149 agreeing truces with rival rooms: Rooms already in contact end or forestall a fight with a truce: peace asked for, offered, agreed, honoured.
• T3-150 forming alliances between rooms: Rooms join in an alliance for joint defence or a joint fight: alliances named, proposed, joined.
• T3-151 bartering help with neighbours: Rooms trade help: repairs, defence, maintenance or room given in return for the same.
• T3-161 mediating between other rooms (rare): A member acts as go-between for two other rooms.
• T3-193 arguing whether cooperation is surrender: Members argue whether cooperating with another room, or accepting a treaty, is surrender.
• T3-194 acting as envoys between rooms: A member acts for a room toward another room: envoy, diplomat, ambassador, representative, a proposal carried between threads.
• T3-195 holding rooms to their agreements: Members invoke an agreement already made: its terms spread to placers, the room reminded to honour it, a neighbour accused of breach, a lapsed deal restored.

G16 kindred rooms and colour factions

• T3-013 gathering kindred rooms together: Kindred rooms (a league's teams, a region's subs, sister fandoms) gather their canvas work in one hub sub or chat.
• T3-019 tallying kindred rooms' works: Members count which kindred rooms (teams, schools, bands) made it onto the canvas and which were lost.
• T3-056 making joint marks with others: Two or more rooms make one mark together: a shared design, a combined flag, lettering finished for each other.
• T3-096 hailing the colour corners: Members of other subs cheer the colour corners and factions, or call people to their side.
• T3-163 defecting from a rival faction: Members announce that they have left a rival faction and joined this one.
• T3-171 spreading a faction's colour: A colour faction spreads its colour across the canvas: expanding the corner, covering others with its colour, tendrils and cores.
• T3-172 renewing the order's oaths: A canvas-born order lays down or renews its rules, oaths and membership.
• T3-173 holding elections for office: A canvas-born faction holds elections for its leaders and offices.
• T3-174 professing loyalty to a colour: A colour faction's members profess loyalty to it: hails, slogans, propaganda, the colour as faith or empire.
• T3-190 splitting a faction over doctrine: A canvas faction splits over what it stands for: pure colour or art, erasing or cleaning, the void or coexistence.

G17 nations and their flags

• T3-065 building the homeland's flag: The room makes the flag of its nation, state or region its mark: calling hands to it, building, sizing and fixing it. A flag built in a room named for a land is that land's flag unless its concepts name another.
• T3-078 helping kin nations' flags: Members help the flags of kindred nations or regions: Baltic brothers, neighbours, a diaspora's homeland.
• T3-079 joining flags with a heart: Rooms join their national flags with a heart or another sign of friendship.
• T3-085 weighing the room against nations: Members weigh the room's art against the nations' flags on the canvas: flags called bland or too big, a nation's size claimed as a right to space.
• T3-113 drawing national emblems: Members draw their nation's emblems, figures and symbols beside or inside the flag: monuments, animals, the king's name, a coat of arms.
• T3-145 feeling national through the canvas: Members feel and voice national belonging through the canvas work: pride in the flag, a nation standing together, fighting for it from abroad.
• T3-165 debating friendship with historic enemies: Members argue whether canvas friendship with a historic national enemy means anything, or should exist at all.
• T3-180 disputing national belonging: Members dispute who belongs to the nation or region and who may speak or act for it on the canvas.

G18 politics, history and hate symbols

• T3-080 arguing over political symbols: Members argue over a political or religious symbol on the canvas: what it means, whether it belongs, whether to take it down.
• T3-081 casting fights as national history: Members cast canvas fights as their nations' historic wars: invasions repeated, old battles and songs replayed, occupation recalled.
• T3-086 carrying in the sub's quarrel: A community's own quarrel or rivalry is carried onto the canvas: one faction's slogan pushed over the other's, the rivalry fought in pixels.
• T3-130 reading national politics in pixels: Members read their nation's politics into the canvas: referendums, elections, governments, migration, old regimes.
• T3-142 making ethnic jokes about rivals: Members mock rival nations or peoples with ethnic jokes and slurs during the canvas fights.
• T3-146 covering swastikas and hate symbols: Members cover swastikas, Nazi flags and other hate symbols or slurs placed on or near their work, or call others to.
• T3-166 arguing the nation's historical record (rare): Members argue whether their nation has always been on the right side of history.
• T3-177 calling to draw swastikas: Members call for, or take part in, drawing swastikas and Nazi imagery on the canvas, the room's own logo included.
• T3-179 arguing ideology from the canvas: Members argue political ideology from the canvas: socialism, capitalism, anarchism, consensus, read into how the canvas was made.
• T3-182 shutting down bigotry in chat: Members or moderators shut down bigoted speech in the room's thread or chat: slurs removed, a speaker shut down, racist claims answered.

G19 taunts and victories over rivals

• T3-025 placing rival marks together (rare): A room puts its mark beside a rival's and keeps both standing without a war.
• T3-050 trading taunts with rivals: Members trade taunts, threats and mockery with a rival community over the canvas.
• T3-134 flooding rivals' threads with chants: Members flood a rival's thread with a chant or refrain: the Void's creed, a streamer's victory chorus, 'get gooned'.
• T3-135 telling clashes as fandom lore: Members retell the canvas clashes in their fandom's own terms: as the game's battles, the show's factions, the band's season.
• T3-143 judging whether a joke offends: Members argue whether a taunt or joke about the canvas goes too far: racist, cruel or just a joke.
• T3-154 claiming victory over rival rooms: Members claim victory over rival rooms: outlasting them, defending against bigger subs, defeating them.
• T3-155 saluting rivals after the fight: Members salute their rivals once the fight is over: well played, good game, thanks for playing.

G20 looking at the canvas and its worth

• T3-016 explaining what the canvas is: Members ask or explain what the canvas event is, why it is everywhere and how anyone places a pixel.
• T3-018 decoding the finished picture's details: Members work out or explain what a particular picture or detail on the canvas shows, means or refers to.
• T3-031 playing the room's in-jokes: Members play the room's own memes, catchphrases and running jokes in the canvas talk.
• T3-037 arguing the canvas's worth: Members argue whether the canvas, its fights or the time spent on it are worth anything.
• T3-052 remarking on neighbouring pictures: Members remark among themselves on the pictures beside or around their own mark.
• T3-057 remaking canvas art elsewhere: Members remake the canvas work or its fights in other media: Minecraft, LEGO, fan art, wallpapers, memes.
• T3-112 entering the work in atlases: Members get the room's work entered in a shared atlas, wiki or list of canvas works.
• T3-127 seeking the creators' notice: Members hope or ask that the fandom's creators, streamer, team or staff notice the canvas work, and celebrate when they do.
• T3-131 arguing over selling canvas art: Members argue over someone selling prints, posters or templates of the shared canvas work.
• T3-147 sharing the work's press coverage: Members share or remark on press, news or viral coverage that showed the room's work.

G21 after the canvas closed

• T3-009 celebrating the finished work: Members mark the room's own finished or nearly finished work as achieved: we did it, pride, congratulations, the final image.
• T3-029 mourning the lost work: Members grieve for the room's work, or a work they cared for, once it is covered, erased or left unfinished.
• T3-043 crediting who made the work: Members thank or credit the people who made, defended or perfected the work, or claim their own part in it.
• T3-054 carrying work to new canvases: Members take up or turn down a later canvas: rebuilding there, planning for next time, or declining to start again.
• T3-072 thanking the room's allies: Members thank other rooms that helped and tell the story of who stood with the room.
• T3-073 reporting how the work fared: Members report what happened to the work, live or after the close: what was covered, moved, repaired or survived.
• T3-105 saving screenshots and timelapses: Members save or share the work as it stood: screenshots, timelapses, final images, requests to save it before it changes.
• T3-111 repurposing the canvas sub: Members decide what the sub or chat made for the canvas becomes once the canvas closes.
• T3-117 marking the canvas's end: Members register that the canvas has ended: it's over, regret, signing off, hoping it returns.
• T3-148 imagining art the canvas missed: Members imagine art the canvas never held: what the work was meant to look like, what they would have drawn.
• T3-156 adopting the mark as emblem: Members take the canvas mark into the sub's identity: banner, sidebar, flair, avatar or a room joke.
• T3-157 reflecting on working together: Members say what the shared effort meant: strangers cooperating, the community as the point.
• T3-158 proposing ties beyond the canvas: Members carry a tie with another room past the canvas: trading recommendations, crossovers, sister cities, exchanges.
• T3-164 feeling supported through the canvas: Members find support, visibility or comfort through the canvas: a flag that says 'we are here', not being alone.
• T3-186 celebrating the feat in person (rare): A member invites others to meet in person to celebrate the canvas work.

G01 April Fools in the sub

T3-001 staging April Fools fake news

Members post their own April Fools fakes in the sub as if true (news, leaks, patches, releases, claims) and play along with them, fall for them or reveal them. Floor: trees and metalcore, unlike in size (trees holds 20,798 items in the window and metalcore 2,087, over twice as many).

• Must show: Members of the room themselves post something false as true for April Fools (a fake news story, leak, patch, release, announcement, trade or personal claim), or reply inside such a fake: playing along, being caught, revealing it.
• Must not show: A change to the sub itself staged by the moderators or the sub (T3-023); a joke made by the company, creator or organisation the sub follows (T3-048); members testing a claim the theme did not stage (T3-095).
• Decide when both: When a theme both stages fakes and tests claims from elsewhere, T3-001 if most concepts make or play inside the room's own fakes, T3-095 if most weigh an outside claim; objecting to the jokes in three or more concepts adds T3-032.
• Against T3-095: Did members of this room stage the claim? Yes: T3-001, the replies inside it included. It came from the moderators, the company, a public figure, the news or another room: T3-095.
• Against T3-023: Is the joke the sub's own changed state (its name, look, rules, subject or a staged takeover)? T3-023. Is it a member's post claiming something false inside the sub? T3-001.
• Against T3-048: Whose joke is it: the room's members (T3-001), or the game's company, the show's creator, an official channel or organisation (T3-048)?
• Against T3-031: Is the joke a fake posted as true for April Fools (T3-001), or the room's ordinary in-jokes and memes on any day (T3-031)?
• Against T3-017: Is anything posted as a fake for April Fools (T3-001), or are the posts ordinary (T3-017)?
• Varies: From one fake headline to a run of fake patch notes and leaks; from members who stay in character to members who reveal at once; from fooling the room to readers admitting they were caught.
• Is not: Members proposing pranks to play on friends away from the site: nothing is staged in the room, so it is the sub's usual talk (T3-017).
• Exemplars: "... nah not really, happy April 1st every one XD" (metalcore c0106); "April Fool's joke. OP is actually eating edibles. One for every upvote!" (trees c0217, rivals c0083); "Following the great reveal on Discord that I was faking, naw I actually do enjoy April Fool's quite a bit." (touhou c0037)

T3-023 running an April Fools takeover

The sub is turned into something else for April Fools, by its moderators or by the sub as a body (renamed, restyled, given new rules or a new subject, or one sub's joke raid on another), and members play inside it. Floor: zelda and patriots, unlike in size (zelda holds 9,309 items in the window and patriots 3,987, over twice as many).

• Must show: A change made to a whole sub for April Fools, announced or staged by its moderators or by a sub acting together: a new name, look, subject, rules or flairs, a fake sale or takeover by a character, company or rival sub, or one sub taking over another for the day; and members playing along inside it.
• Must not show: Members' own fake posts in an unchanged sub (T3-001); working out whether the change is a joke (T3-095); only complaining about the jokes (T3-032) or turning the styling off (T3-097).
• Decide when both: Playing along inside the takeover stays T3-023. Working out what the change was in three or more concepts adds T3-095; objecting in three or more adds T3-032; turning off or working around the look adds T3-097; asking to keep it after the day adds T3-100.
• Against T3-001: Is the joke the sub's changed state (T3-023), or a member's fake post inside the sub (T3-001)?
• Against T3-095: Are members playing inside the change (T3-023), or trying to tell whether the change is real and what it is (T3-095)?
• Against T3-097: Is the look being staged or played with (T3-023), or turned off, worked around or asked away (T3-097)?
• Against T3-093: Are moderator powers handed to every member and played with (T3-093), or is it any other takeover (T3-023)?
• Against T3-064: Is the target sub changed as a whole, as the joke's stage (T3-023), or do members carry the room's joke into other places one post at a time (T3-064)?
• Against T3-048: Is the joke the maker's (T3-048), or the sub's own moderators' change to the sub, even when they play the maker (T3-023)?
• Against T3-133: Is the change a joke the moderators staged (T3-023), or a real compromise they repair (T3-133)?
• Against T3-185: Is the rule change a joke for the day (T3-023), or meant to hold (T3-185)?
• Against T3-032: Is the sub turned into something else for the day and played inside (T3-023), or are the sub's April Fools jokes objected to and asked to stop (T3-032)?
• Against T3-100: Is the sub turned into something else for the day (T3-023), or is it asked that an April Fools change outlive the day (T3-100)?
• Varies: From a one-day styling swap to a full change of subject with removals enforced; from the moderators alone to a whole sub raiding another sub as a joke.
• Is not: A moderator removing canvas posts under the sub's ordinary rules on 1 April (T3-063): nothing about the sub was changed for the joke.
• Exemplars: "After many years of hard work on this sub, we've decided it's time to cash in! So we've sold the subreddit to Funko!" (gameofthrones c0007); "Annoucement: We received an intellectual property related cease and desist letter from the NFL's legal team today. Starting noon today, all football gifs are banned from r/Patriots." (patriots c0042); "What's the point in doing a joke like this without fully committing? It's not like we're getting rid of a place for people to talk about what they want to talk about, /r/horizon is currently a zelda subreddit." (zelda c0130)

T3-032 objecting to April Fools posts

Members object to the April Fools jokes in their sub as unfunny, stale, hurtful or in the way, and ask for them to stop or come down. Floor: europe and fivenightsatfreddys, unlike in size (europe holds 29,726 items in the window and fivenightsatfreddys 9,633, over twice as many).

• Must show: Objection to the sub's April Fools content carried by three or more concepts: calling the jokes unfunny, stale, hurtful or disruptive; asking members or moderators to stop them or take them down; warning others not to post them.
• Must not show: One or two passing complaints inside a theme about the jokes (named in the room note, not placed); complaints that the prank styling is hard to read (T3-097); objections to canvas posts (T3-075).
• Decide when both: A theme that stages or plays the jokes and objects to them keeps the staging kind as primary and adds T3-032 when the objecting has three or more concepts.
• Against T3-075: Are the posts objected to April Fools jokes (T3-032) or canvas posts flooding the sub (T3-075)?
• Against T3-097: Are the jokes themselves bad or unwelcome (T3-032), or is the joke look in the way of reading and voting (T3-097)?
• Against T3-063: Are members objecting (T3-032), or moderators removing posts under the sub's rules (T3-063)?
• Against T3-048: Is the objection to posts in the sub (T3-032), or a verdict on the company's or creator's own joke (T3-048)?
• Against T3-118: Is the moderators' joke objected to as a joke (T3-032), or blamed for a loss (T3-118)?
• Against T3-143: Are April Fools posts objected to (T3-032), or a canvas joke's limits argued (T3-143)?
• Against T3-023: Is the sub turned into something else for the day and played inside (T3-023), or are the sub's April Fools jokes objected to and asked to stop (T3-032)?
• Varies: From a sigh at a stale joke to calls for the moderators to undo a takeover; hurt at a joke about a nation, a language or a death.
• Is not: A member disliking the game company's April Fools feature (T3-048): the objection is to the maker's joke, not to posts in the sub.
• Exemplars: "This April fools' joke is in really poor taste. Hate towards a particular country and language is not a joke." (europe c0453); "Stop with these Kimi posts, they are getting boring fast" (formula1 c0203); "I forsee many of these 'jokes' coming, so as a PSA and if your reading, please do not make these posts." (fivenightsatfreddys c0166)

T3-048 reacting to official April Fools

Members react to the April Fools jokes of the company, creator, channel or organisation the sub follows: waiting for them, judging them, comparing years, missing them. Floor: overwatch and paydaytheheist, unlike in size (overwatch holds 45,381 items in the window and paydaytheheist 2,417, over twice as many).

• Must show: Talk about an April Fools joke made by the maker the sub is about (a game company's patch, trailer, store item or mode; a creator's or channel's video; a club's, school's or organisation's post): anticipating it, judging it, comparing it with other years, wishing for one, missing one.
• Must not show: An open question whether an announcement is a joke at all (T3-095); members' own fakes (T3-001); asking for the joke feature to stay after the day (T3-100).
• Decide when both: Judging the official joke stays T3-048. When most concepts ask whether an announcement is real, T3-095; asking to keep the joke feature in three or more concepts adds T3-100.
• Against T3-095: Is it still open whether the announcement is a joke (T3-095), or is the joke known and members judge it (T3-048)?
• Against T3-001: Is the joke the official maker's (T3-048) or the room's members' (T3-001)?
• Against T3-100: Reacting to the joke on the day (T3-048), or asking for it to stay or be made real after the day (T3-100)?
• Against T3-023: Is the joke the maker's (T3-048), or the sub's own moderators' change to the sub, even when they play the maker (T3-023)?
• Against T3-032: Is the objection to posts in the sub (T3-032), or a verdict on the company's or creator's own joke (T3-048)?
• Against T3-106: Do members only judge the maker's joke (T3-048), or call for action against the maker (T3-106)?
• Varies: From disappointment that a company made no joke this year to praise for a well-made fake update; companies, streamers, channels, clubs and universities.
• Is not: The sub's moderators staging a fake takeover by the company (T3-023): the moderators are not the company.
• Exemplars: "Blizzard usually goes all out for all their games, but this year it doesn't seem that way." (overwatch c0472, rivals c0766); "Gaijin is memeing on a whole new level" (warthunder c0006); "This year's April Fools update however, it was pretty amazing." (paydaytheheist c0103)

T3-064 spreading the room's joke elsewhere

Members carry their sub's joke or in-joke into other subs or sites, or show another sub what the room is doing. Floor: prequelmemes and totallynotrobots, unlike in size (prequelmemes holds 11,884 items in the window and totallynotrobots 1,288, over twice as many).

• Must show: The room's own joke (an April Fools takeover, an in-joke, a meme, a birthday flood) taken by members into another sub or site: posting it there, linking it into other subs, showing another sub what the room is doing, comparing the room's joke with other subs'.
• Must not show: A takeover of the room's own sub (T3-023); calls to other subs for canvas help (T3-062).
• Decide when both: One sub changing another sub as a whole for the day is T3-023; members carrying the joke into other places post by post is T3-064.
• Against T3-023: Is another sub taken over as the joke's stage (T3-023), or do members carry the joke into other places (T3-064)?
• Against T3-031: Is the in-joke played inside the room (T3-031), or taken out to other subs (T3-064)?
• Against T3-062: Does the message to another sub carry the room's joke (T3-064), or ask that sub for help on the canvas (T3-062)?
• Varies: From one link to another sub to a coordinated flood of birthday wishes across subs; from pride in the joke's reach to worry that another sub's joke is everywhere.
• Is not: Recruiting kindred subs to help with the canvas (T3-062): no joke is carried.
• Exemplars: "IT WOULD BE VERY INTERESTING TO USE THIS IDEA IN OTHER SUBS. WE ARE REAL HUMANS, BUT THEY WILL THINK WE ARE ROBOTS." (totallynotrobots c0005, rivals c0013); "Posted what we were doing here to the Love Live Reddit" (stardustcrusaders c0088); "When r/movies becomes r/prequelmemes for the day" (prequelmemes c0239, rivals c0209 c0327)

T3-093 playing with granted moderator powers

Rare tier. Every member is made a moderator for April Fools, and members play with the powers and with losing them.

• Must show: Moderator status handed to every member (or to many) for the day, and members playing with it: threats to ban or sticky, jokes about ruling, talk when the powers are withdrawn.
• Must not show: Any other takeover in which the moderators keep their powers (T3-023).
• Decide when both: The moderators' staging of the handout sits with T3-023; members' play with the powers goes to T3-093.
• Against T3-023: Do members hold moderator powers and play with them (T3-093), or do they play inside a change the moderators made (T3-023)?
• Against T3-133: Members playing with powers handed out for the day (T3-093), or a stolen account undone (T3-133)?
• Varies: From jokes about banning the real moderators to a mock mutiny once the powers end.
• Is not: A real election or appointment of moderators for the canvas work (T3-173, T3-101).
• Exemplars: "Unfortunately you can't ban other moderators, so really no one has any power!" (seahawks c0015, rivals c0031 c0023); "How do I ban all the other mods so I can be the only mod?" (seahawks c0031, rivals c0015 c0023); "At least I look good in moderator green." (seahawks c0023, rivals c0015 c0031)

T3-095 testing others' April Fools claims

Members work out whether a claim they did not make is an April Fools joke: a moderators' or company's announcement, a public figure's post, a news story, another room's claim, or real news taken for a joke. Floor: DestinyTheGame and loltyler1, unlike in size (DestinyTheGame holds 45,483 items in the window and loltyler1 1,815, over twice as many).

• Must show: Members asking or settling whether something the theme did not stage is real or a joke: checking the date and the source, pointing to evidence, warning others, confirming or exposing.
• Must not show: The room's own fakes and the replies inside them, readers caught by them included (T3-001); judging an official joke already known to be one (T3-048).
• Decide when both: If the room's members staged the claim, T3-001 even when readers test it; otherwise T3-095. Where a theme holds both, the kind with more concepts is primary and the other is added under rule 0.
• Against T3-001: Did members of this room stage the claim being tested (T3-001), or did it come from elsewhere, the moderators, a company, a public figure, the news, another room (T3-095)?
• Against T3-048: Is it still open whether it is a joke (T3-095), or do members judge an official joke they know is one (T3-048)?
• Against T3-023: Are members working out what the sub's change is and whether it is real (T3-095), or playing inside it (T3-023)?
• Against T3-016: Is the claim tested whether r/place itself is Reddit's April Fools joke, answered by explaining what r/place is (T3-016), or a claim about anything else (T3-095)?
• Varies: From a single 'April Fools?' to a thread tracing a leak to its source; claims by companies, moderators, players, news sites, public figures and other rooms; real news first taken for a joke.
• Is not: Readers falling for a fake that members of the same room posted (T3-001).
• Exemplars: "Is this a joke for april fools ?? #cracktheclue" (2007scape c0357); "Confirmed fake, puzzle by Math Class, not affiliated with Bungie" (DestinyTheGame c0200); "unban was a april fools joke?" (loltyler1 c0021)

T3-097 switching off the prank styling

Members get past the sub's April Fools look or rules: turning the style off, working around it, reporting what it breaks, asking for it gone, or the moderators switching it back. Floor: clashroyale and GuildWars2, unlike in size (clashroyale holds 19,914 items in the window and GuildWars2 7,667, over twice as many).

• Must show: The sub's April Fools styling or rule change treated as something to get past: turning off the subreddit style, browser and CSS workarounds, reports that it breaks reading, voting or links, requests to switch back, the moderators ending it.
• Must not show: Playing inside the changed look (T3-023); objecting to the joke posts as unfunny (T3-032); asking to keep the change (T3-100).
• Decide when both: A theme that stages the takeover and switches it off keeps T3-023 as primary and adds T3-097 when switching off or working around has a concept of its own.
• Against T3-100: Do members want the change gone or worked around (T3-097), or kept after the day (T3-100)?
• Against T3-032: Is the look in the way (T3-097), or are the jokes themselves unwelcome (T3-032)?
• Against T3-023: Is the change being staged or played (T3-023), or got rid of (T3-097)?
• Varies: From a reader's browser trick to the moderators restoring the old theme; contrast, fonts, flairs, hidden links and buttons that stop working.
• Is not: Moderators changing the sub's posting rules for good after the day (T3-185).
• Exemplars: "It's very hard to read these lol. Turn of subreddit style to get rid of it." (h3h3productions c0044); "It's harder to read and I can't find the "disable subreddit theme"" (clashroyale c0420, rivals c0361); "I found the April Fools background so annoying I turned off themes for this subreddit in Reddit's preferences and that is how it is going to stay." (GuildWars2 c0197, rivals c0176)

T3-100 keeping April Fools changes afterwards

Members ask that something made for April Fools outlive the day: the sub's flairs, styling or name, or a company's joke feature made real. Floor: rocketleague and rust, unlike in size (rocketleague holds 21,124 items in the window and rust 1,129, over twice as many).

• Must show: A request or decision that an April Fools change stay after the day: flairs, a theme, a name, a game mode, a rank set or a joke item; petitions, polls and settings asked for so that it can stay.
• Must not show: Reacting to the joke on the day (T3-048, T3-023); getting rid of the change (T3-097).
• Decide when both: Asking to keep a company's joke feature is T3-100 when the asking has a concept of its own, beside T3-048 for judging the joke.
• Against T3-097: Is the change wanted gone (T3-097) or kept (T3-100)?
• Against T3-048: Judging the official joke (T3-048), or asking that it stay or be made real (T3-100)?
• Against T3-105: Is the canvas work saved in screenshots and timelapses (T3-105), or an April Fools change kept in use (T3-100)?
• Against T3-023: Is the sub turned into something else for the day (T3-023), or is it asked that an April Fools change outlive the day (T3-100)?
• Varies: From a flair kept a few more days to petitions with thousands of votes asking a company to make a joke rank permanent.
• Is not: Asking to carry the canvas work to a successor canvas (T3-054): the canvas is no April Fools change.
• Exemplars: "Let's keep the April Fools flairs around a little longer anyway." (smashbros c0259); "THE PETITION TO KEEP THE VEGGIE RANKS" (rocketleague c0170, rivals c0560 c0614); "Mods, please keep this theme up." (rust c0026)

G02 the sub's rules and usual posts

T3-015 routing canvas posts into megathreads

Moderators or members gather the sub's canvas talk into one stickied thread, a megathread, and send other canvas posts there. Floor: heroesofthestorm and cubers, unlike in size (heroesofthestorm holds 22,813 items in the window and cubers 3,531, over twice as many).

• Must show: Canvas talk gathered into one thread inside the sub: a moderator stickying a megathread, members asking for one, posts redirected or removed with a pointer to it, the plan kept in one visible place.
• Must not show: Moving the planning out of the sub, to a chat or a new sub (T3-014, T3-090); removals under the sub's rules with no pointer to a gathering thread (T3-063); complaining about the flood without asking for a place to gather it (T3-075).
• Decide when both: Removing canvas posts and pointing them to the megathread is T3-015; removals resting on other rules (karma, titles, relevance) are T3-063. A theme with both in concepts of their own takes the larger as primary and the other under rule 0.
• Against T3-063: Is the post sent to one gathering thread (T3-015), or removed or filtered under a standing rule with no such pointer (T3-063)?
• Against T3-014: Is the gathering place a thread inside the sub (T3-015), or a chat outside it (T3-014)?
• Against T3-090: One thread in the sub (T3-015), or a new sub made for the canvas work (T3-090)?
• Against T3-075: Is one thread asked for so the work can go on in order (T3-015), or are members objecting that canvas posts crowd the sub (T3-075)?
• Against T3-049: Is the scattering complained of with no gathering act (T3-049), or is the talk gathered into one thread (T3-015)?
• Against T3-140: Is the thread only gathering canvas talk (T3-015), or do the moderators also say the work is not the sub's (T3-140)?
• Against T3-197: Is the canvas talk moved or shaped because the creator of the room's subject asked (T3-197), or gathered into one thread with no creator's wish behind it (T3-015)?
• Varies: From one moderator's sticky to dozens of posts redirected by hand; members asking for a thread that does not exist yet.
• Is not: A moderator removing a canvas post because the canvas has ended (T3-063): nothing is gathered.
• Exemplars: "Everybody, please stop creating /r/place threads on our sub. Keep your posts and ideas within this thread." (dbz c0052); "Why can't they pin 1 thread for all this /rplace stuff???" (heroesofthestorm c0318); "Please use the megathread" (cubers c0281)

T3-017 carrying on ordinary sub talk

The sub's ordinary business goes on during the canvas week: its usual subject, news, help, jokes and quarrels, apart from the canvas and April Fools. Floor: rocketleague and paydaytheheist, unlike in size (rocketleague holds 21,124 items in the window and paydaytheheist 2,417, over twice as many).

• Must show: Talk on the sub's usual subject during the window (the game, team, show, place or hobby; its news, help and arguments), or ordinary side talk inside a canvas thread, with no canvas work and no April Fools joke as its point.
• Must not show: Talk about the canvas work (other families); April Fools jokes (G01); the room's running in-jokes played in the canvas talk (T3-031).
• Decide when both: Usual talk inside a canvas or April Fools theme is named in the room note unless it holds three or more concepts of its own; then T3-017 is added under rule 0.
• Against T3-031: Is it the room's running in-joke carried into the canvas talk or the day (T3-031), or the sub's ordinary subject going on (T3-017)?
• Against T3-001: Is anything posted as a fake for April Fools (T3-001), or are the posts ordinary (T3-017)?
• Against T3-185: Are members arguing the sub's posting rules (T3-185), or talking about the sub's subject (T3-017)?
• Against T3-050: Does the sub's ordinary talk go on with no rival in it (T3-017), or is a rival community taunted (T3-050)?
• Against T3-184: Does the usual business go on (T3-017), or is a recurring event stopped or restarted around the canvas (T3-184)?
• Varies: From patch questions and match threads to a sub's politics, help requests and feuds; from whole themes of usual talk to usual talk drifting into a canvas thread.
• Is not: Members trading outside creators' April Fools releases as examples of the day done well: that is reacting to official April Fools (T3-048).
• Exemplars: "I'm glad RLCS is attractive enough to companies to have sponsors like that." (rocketleague c0648); "Uncheck all dlcs and start game, then close and re check all dlcs. Mine is now fully operational :))" (paydaytheheist c0159); "Don't know what to say but here's a virtual hug if you need it." (philippines c0031)

T3-051 pushing posts up the rankings

Members ask for upvotes so a post, an image or a joke climbs: up r/place or the front page so placers see it, or to the top of a search result. Floor: leagueoflegends and CKCrusaders, unlike in size (leagueoflegends holds 75,751 items in the window and CKCrusaders 487, over twice as many).

• Must show: A drive for votes: members asked to upvote a post so that it rises (to be seen by placers on r/place, to reach the front page, to make an image the first search result), or bargains of the form 'if this gets N upvotes'.
• Must not show: Calling members to place with no votes asked (T3-002); asking another sub for help (T3-062).
• Decide when both: A call to place that also asks for upvotes so the call is seen: T3-002 primary, T3-051 added when the vote drive has a concept of its own.
• Against T3-002: Are members asked to vote a post up (T3-051), or to come and place (T3-002)?
• Against T3-110: Is a tile offered in return for the vote (T3-110), or are votes gathered with nothing given (T3-051)?
• Against T3-053: Is one post pushed up (T3-051), or a run of posts lined up to spell a phrase (T3-053)?
• Against T3-062: Are upvotes asked so a post climbs (T3-051), or the room's call for hands carried into other subs (T3-062)?
• Varies: From one request to upvote a coordination post on r/place to joke campaigns to own a search result; pledges promised for a vote count.
• Is not: Offering to place a tile for an upvote (T3-110): the vote buys a tile.
• Exemplars: "In particular, upvote this thread so randoms will see and understand." (CKCrusaders c0040); "IceFrog. If this gets enough upvotes, this image will show up when you Google search "IceFrog"" (leagueoflegends c0289); "show up on google images when you search ya boi" (pokemon c0100)

T3-053 spelling slogans with post titles

Members post a run of posts whose titles, read down the front page or the sub's listing, spell a slogan or a chant. Floor: hearthstone and popheads, unlike in size (hearthstone holds 53,563 items in the window and popheads 4,512, over twice as many).

• Must show: Coordinated posts of single letters, words or lines timed so that the listing spells a phrase; plans to make the front page say something; praise for the result.
• Must not show: A vote drive for one post (T3-051); a chant repeated in replies without spelling anything across posts (T3-031).
• Decide when both: Posts timed to spell and upvoted so that they reach the front page: T3-053 for the spelling, T3-051 added when the vote drive has concepts of its own.
• Against T3-051: Is one post pushed up (T3-051), or a run of posts lined up to spell a phrase (T3-053)?
• Against T3-031: Is the room's chant played in replies (T3-031), or spelled across the titles of many posts (T3-053)?
• Varies: From letters spelling a name down the front page to song lyrics chained one word per post.
• Is not: Pushing one post up the rankings (T3-051).
• Exemplars: "get the front page to say" (hearthstone c0229, rivals c0075); "On my front page it took me a while to see the whole thing. Well done." (hearthstone c0075, rivals c0229)

T3-063 removing canvas posts by rule

Moderators, or their bots, remove, filter or flair canvas posts under the sub's standing rules, and members ask about or contest the removals. Floor: pcmasterrace and smashbros, unlike in size (pcmasterrace holds 40,459 items in the window and smashbros 8,519, over twice as many).

• Must show: Canvas posts handled under the sub's standing rules: removals for titles, links, karma, relevance, duplicates or politics; automatic filters; required flairs; members asking what the rules allow or contesting a removal.
• Must not show: Gathering canvas talk into one thread (T3-015); changing the rules themselves (T3-185); members objecting to the flood with no moderator act (T3-075).
• Decide when both: Removing with a pointer to a gathering thread is T3-015; removing under any other rule is T3-063; both with concepts of their own, the larger primary and the other under rule 0.
• Against T3-015: Is the post removed under a standing rule (T3-063), or sent to one gathering thread (T3-015)?
• Against T3-185: Are the rules applied as they stand (T3-063), or made, dropped or argued as a change (T3-185)?
• Against T3-075: A removal or filter applied (T3-063), or members complaining about canvas posts (T3-075)?
• Against T3-182: Posts removed for breaking the sub's rules (T3-063), or members shutting down bigotry in a chat (T3-182)?
• Against T3-121: Is a post removed under the sub's rules (T3-063), or a member excluded as a sanction (T3-121)?
• Against T3-032: Are members objecting (T3-032), or moderators removing posts under the sub's rules (T3-063)?
• Against T3-118: Is a removal contested (T3-063), or a loss laid at the moderators' door (T3-118)?
• Against T3-197: Are canvas posts handled under the sub's rules (T3-063), or shaped by the creator's wish (T3-197)?
• Against T3-140: Do moderators say the canvas work is not the sub's (T3-140), or remove or filter canvas posts under the sub's rules without saying so (T3-063)?
• Varies: From an automatic removal for an all-caps title to a moderator removing a post that ties the sub to fascism; members apologising in advance for breaking a rule.
• Is not: A moderator stickying a megathread and asking for posts there (T3-015).
• Exemplars: "Just letting you know I removed this because /r/place has ended." (smashbros c0345); "Reddiquette forbids titles written in ALL CAPS. Please fix this and resubmit your post." (pcmasterrace c0584); "Your link has been removed because it is not whitelisted." (2007scape c1423)

T3-075 objecting to the canvas flood

Members object that canvas posts crowd out the sub's usual talk, and ask for them to stop, be condensed or move. Floor: AMD and chibears, unlike in size (AMD holds 15,188 items in the window and chibears 1,957, over twice as many).

• Must show: Members complaining that r/place posts flood the sub, are spam or off-topic, or crowd out its news and subject; asking that they stop, be condensed into one post or be removed.
• Must not show: Moderators applying a rule (T3-063) or gathering posts (T3-015) with no members objecting; judging the canvas itself worthless (T3-037); objecting to April Fools posts (T3-032).
• Decide when both: Members objecting and moderators answering with a megathread: the larger part primary, the other under rule 0. A complaint that the canvas is pointless, not that it floods the sub, is T3-037.
• Against T3-037: Is the complaint that canvas posts crowd the sub (T3-075), or that the canvas is not worth doing (T3-037)?
• Against T3-032: Are the unwanted posts canvas posts (T3-075) or April Fools jokes (T3-032)?
• Against T3-015: Are members objecting to the flood (T3-075), or is the talk being gathered into one thread so the work can go on (T3-015)?
• Against T3-063: A removal or filter applied (T3-063), or members complaining about canvas posts (T3-075)?
• Against T3-189: Is the complaint about canvas posts crowding the sub (T3-075), or about the people the mark brings in (T3-189)?
• Varies: From one weary 'please stop' to threads arguing whether the canvas enlivened or wrecked the sub; refusals to join because of the spam.
• Is not: A member calling the canvas a waste of time with no word on the sub's space (T3-037).
• Exemplars: "Some fans come here to read bears news you guys are spamming this whole subreddit with this shit." (chibears c0114); "Enough with this r/place bullsh*t already. None of these things posted these last few days are even remotely related to Minecraft." (minecraft c0227); "Half the subs I'm subscribed to are flooded with this r/place garbage." (AMD c0341, rivals c0140)

T3-106 calling a network boycott

Rare tier. Members answer a TV network's April Fools prank by calling for a boycott: piracy, cancelled subscriptions, complaints.

• Must show: Calls to boycott or punish an outside company over its April Fools joke: withholding views, piracy, cancelling subscriptions, organising complaints.
• Must not show: Judging the official joke with no action against the maker (T3-048).
• Decide when both: A theme that judges the joke and calls a boycott in concepts of their own takes T3-048 as primary and T3-106 under rule 0.
• Against T3-048: Do members only judge the maker's joke (T3-048), or call for action against the maker (T3-106)?
• Varies: From one member's private piracy to a call for someone to organise a boycott.
• Is not: Objecting to joke posts inside the sub (T3-032).
• Exemplars: "I want to boycott adult swim. Who wants to organize that?" (samuraijack c0098, rivals c0099 c0154); "Adult Swim skips Jack, I cancel the subscription. Joke for a joke." (samuraijack c0169, rivals c0099 c0154); "BOYCOTT RICK AND MORTY" (samuraijack c0157, rivals c0099 c0154)

T3-110 placing a tile as payment

A member offers to place a canvas tile in return for an upvote or a favour. Floor: france and pgang, unlike in size (france holds 16,236 items in the window and pgang 8, over twice as many).

• Must show: A tile offered in exchange: 'one upvote and I place a tile', a pixel promised as thanks for help with something else, tiles counted as something a member can give.
• Must not show: Vote drives with no tile given (T3-051); extra accounts used to place more (T3-088); prizes for the room's helpers (T3-159).
• Decide when both: Counting alts as placing power is T3-088; offering the tiles in trade is T3-110.
• Against T3-051: Is a tile given for the vote (T3-110), or are votes gathered with nothing given (T3-051)?
• Against T3-088: Are extra accounts used to place more (T3-088), or tiles offered as payment (T3-110)?
• Against T3-159: Prizes or gifts for the room's helpers (T3-159), or a tile itself as the payment (T3-110)?
• Varies: From a joke offer for one upvote to a pixel promised as thanks for advice.
• Is not: Rewarding the room's helpers with prizes (T3-159).
• Exemplars: "1 UPVOTE AND I WILL PLACE A NEW TILE" (pgang c0002); "J'irais mettre un pixel sur r/place pour vous remercier." (france c0394)

T3-133 recovering a hacked sub

Rare tier. The moderators recover the sub after a moderator's account is hacked and used to change it.

• Must show: A moderator account compromised and used on the sub, and its repair: announcing the compromise, restoring the sub, removing what the intruder posted, explaining it to members.
• Must not show: A takeover staged as a joke (T3-023).
• Decide when both: A hack staged for April Fools is T3-023; a real compromise is T3-133.
• Against T3-023: Is the change a joke the moderators staged (T3-023), or a real compromise they repair (T3-133)?
• Against T3-093: Members playing with powers handed out for the day (T3-093), or a stolen account undone (T3-133)?
• Varies: From a one-line notice that a new moderator was hacked to removing the link the intruder posted.
• Is not: Members playing with moderator powers handed out for April Fools (T3-093).
• Exemplars: "A mods account got compromised - all is fixed now! Sorry" (PUBATTLEGROUNDS c0025, rivals c0024 c0045); "A brand new mod got hacked, it's sorted now :)" (PUBATTLEGROUNDS c0024, rivals c0025 c0045); "my account was hacked & someone decided that they wanted to have a bit of fun with the subreddit." (PUBATTLEGROUNDS c0045, rivals c0024 c0025)

T3-140 moderators disowning the canvas work

The sub's moderators say the canvas work is not the sub's: members may go on, but not in the sub's name. Floor: MMA and japan, unlike in size (MMA holds 22,396 items in the window and japan 1,332, over twice as many).

• Must show: Moderators stating that the sub as such takes no part in the canvas work: no official project, no brigading in the sub's name, members free to organise on their own.
• Must not show: Moderators gathering or removing canvas posts without saying the work is not the sub's (T3-015, T3-063); a room separating its own plan from rogue placers (T3-188).
• Decide when both: A sticky that gathers the canvas talk and disowns the work is T3-015 primary with T3-140 under rule 0.
• Against T3-188: Do the moderators say the sub has no canvas project at all (T3-140), or that placers acting against the room's own plan are not the room (T3-188)?
• Against T3-015: Is the thread only gathering canvas talk (T3-015), or do the moderators also say the work is not the sub's (T3-140)?
• Against T3-197: Do the moderators disown the work (T3-140), or does the room heed its creator (T3-197)?
• Against T3-063: Do moderators say the canvas work is not the sub's (T3-140), or remove or filter canvas posts under the sub's rules without saying so (T3-063)?
• Varies: From a moderator too tired to lead who leaves members to it to a statement that the moderators have nothing to do with any canvas activity.
• Is not: A room disowning rogue offshoots of its own work (T3-188).
• Exemplars: "we (the mods) have nothing to do with any /r/place-related activities." (japan c0091, rivals c0092); "If you guys want to organize something, go for it. I can't speak for the other mods but I'm a bit tuckered out." (MMA c0398); "don't brigade anyone on "the sub's" behalf. Have fun!" (japan c0092, rivals c0091)

T3-184 pausing the sub's usual events

The sub puts one of its recurring events on hold for the canvas and resumes it after. Floor: kanye and coldplay, unlike in size (kanye holds 4,101 items in the window and coldplay 385, over twice as many).

• Must show: A recurring event of the sub (a game among members, a contest, a daily thread) held off because of the canvas, or resumed once the canvas posts end.
• Must not show: Usual talk going on unchanged (T3-017); a change to the posting rules (T3-185).
• Decide when both: A theme that pauses an event and changes rules: the change to rules is T3-185, the paused event T3-184.
• Against T3-017: Does the usual business go on (T3-017), or is a recurring event stopped or restarted around the canvas (T3-184)?
• Against T3-185: Is a rule about what may be posted changed (T3-185), or an event of the sub paused (T3-184)?
• Varies: From holding a game round for the canvas to announcing that the regular programme is back.
• Is not: Removing canvas posts so that usual threads stay visible (T3-063).
• Exemplars: "Now that the flood of /r/place posts is over with, let's resume our regularly scheduled programming!" (coldplay c0075)

T3-185 changing the sub's posting rules

Moderators change the sub's posting rules around the canvas or April Fools, and members argue the change. Floor: Rainbow6 and warthunder, unlike in size (Rainbow6 holds 20,801 items in the window and warthunder 6,648, over twice as many).

• Must show: A change to the sub's rules or their enforcement meant to hold: allowing or banning a kind of post for a time, new flairs or filters, a rule dropped or added, members debating what the rules should be.
• Must not show: Applying the rules as they stand (T3-063); a rule change staged as a joke for the day (T3-023).
• Decide when both: Applying and changing in one theme: the larger part primary and the other under rule 0.
• Against T3-063: Is a standing rule applied (T3-063), or is a rule made, dropped or argued (T3-185)?
• Against T3-023: Is the rule change a joke for the day (T3-023), or meant to hold (T3-185)?
• Against T3-017: Are members arguing the sub's posting rules (T3-185), or talking about the sub's subject (T3-017)?
• Against T3-184: Is a rule about what may be posted changed (T3-185), or an event of the sub paused (T3-184)?
• Against T3-118: Are moderators or admins blamed for a loss (T3-118), or a change to the sub's posting rules made and argued with no loss in view (T3-185)?
• Varies: From a day's allowance for canvas posts to dropping a rule against memes for good.
• Is not: An automatic removal under an existing rule (T3-063).
• Exemplars: "Not a late April Fools': We're dropping the old Rule 2, memes are now allowed." (warthunder c0107, rivals c0121); "We've added a /r/Place link flair, please flair your posts as such if it is in regards to /r/Place at all." (Rainbow6 c0566, rivals c0567 c0568); "We're going to allow them for the next day or so. :)" (thesilphroad c0660)

G03 where the planning happens

T3-014 moving planning into a chat

The room moves its canvas planning into a chat outside the thread (a Discord most often; IRC, Skype, Telegram, Slack), setting it up, sharing invites and sending members there. Floor: bostonbruins and re_zero, unlike in size (bostonbruins holds 4,431 items in the window and re_zero 1,355, over twice as many).

• Must show: A chat set up or named for the room's canvas work; invites posted or asked for; members sent there for plans, live direction or voice.
• Must not show: Reporting in the thread what the chat decided, as the theme's own doing (T3-152); talking with other rooms in their chats or a shared one (T3-153); a new sub for the work (T3-090); arguing which chat to use (T3-109).
• Decide when both: Moving into a chat and relaying its decisions: T3-014 primary, T3-152 added when the relay has concepts of its own; meeting other rooms there adds T3-153.
• Against T3-152: Are members sent into the chat (T3-014), or told in the thread what the chat decided (T3-152)?
• Against T3-153: Is the chat the room's own planning place (T3-014), or where it meets other rooms (T3-153)?
• Against T3-090: Is the new venue a chat (T3-014) or a subreddit (T3-090)?
• Against T3-109: Is a chat simply set up and used (T3-014), or is the choice of chat argued (T3-109)?
• Against T3-015: Does the talk move out of Reddit into a chat (T3-014), or into one thread of the sub (T3-015)?
• Against T3-107: Does the planning stay in the thread (T3-107) or move into a chat (T3-014)?
• Against T3-116: Is the plan moved because rivals are reading (T3-116), or for speed and order (T3-014)?
• Varies: From one member's new server to a sub's official Discord with a channel per project; voice chat; invite links that break and are renewed.
• Is not: A room's members joining another room's chat to talk terms (T3-153).
• Exemplars: "Also, someone suggested a Discord to coordinate on so I set one up because why not." (bostonbruins c0044); "join the discord if you want to discuss where to place stuff" (re_zero c0020); "I never really made a discord before so any help modding would be appreciated." (patriots c0071)

T3-049 complaining the calls are scattered

Members complain that the room's calls and plans are scattered, duplicated or uncoordinated, and ask for one clear plan. Floor: touhou and predators, unlike in size (touhou holds 2,246 items in the window and predators 856, over twice as many).

• Must show: Complaints that the room lacks coordination: too many threads, coordinates or designs at once; no one keeping one plan up to date; members unsure where the work is.
• Must not show: Gathering the talk into one thread (T3-015) or onto one template (T3-091) as an act; doubting the room can manage the work at all (T3-136).
• Decide when both: A complaint answered in the same theme by a megathread or a template: the act (T3-015, T3-091) is primary when it has more concepts, T3-049 otherwise.
• Against T3-015: Is the scattering complained of with no gathering act (T3-049), or is the talk gathered into one thread (T3-015)?
• Against T3-091: Are many plans complained of (T3-049), or is one template set for all (T3-091)?
• Against T3-136: Is the room said to be uncoordinated (T3-049), or too weak or too few (T3-136)?
• Against T3-188: Is the plan itself scattered (T3-049), or are placers acting against a plan set apart from the room (T3-188)?
• Against T3-125: Is the lack of a plan complained of (T3-049), or stated as the room's way (T3-125)?
• Varies: From a request for one post that states the goal to a member admitting there is zero coordination; during the work and after it.
• Is not: A member saying the room has too few hands for its design (T3-136).
• Exemplars: "can we get a clear post on what the goal is? Going through this thread I'm seeing a whole bunch of different coordinates" (predators c0027); "we have pretty good consensus on discord but the posts on the sub are all over the place because there is no single one that is kept up to date" (touhou c0024); "there is zero coordination at this stage." (russia c0051)

T3-090 opening a canvas sub

Members open a separate subreddit for the room's canvas work, or ask for one, and send canvas talk there. Floor: europe and sweden, unlike in size (europe holds 29,726 items in the window and sweden 8,092, over twice as many).

• Must show: A new subreddit made for the canvas work (a place sub for the room or nation), asked for, or used: canvas posts redirected to it, members told to go there.
• Must not show: One thread inside the sub (T3-015); a chat (T3-014); a hub sub for many kindred rooms (T3-013); what the canvas sub becomes after the canvas (T3-111).
• Decide when both: A sub made for the canvas that later takes a lasting purpose: making it is T3-090, its future T3-111.
• Against T3-015: Is the canvas talk sent to a new sub (T3-090), or to one thread in the old one (T3-015)?
• Against T3-014: Is the new venue a subreddit (T3-090) or a chat (T3-014)?
• Against T3-013: Is the new sub for this room's work (T3-090), or a hub for many kindred rooms (T3-013)?
• Against T3-111: Is the sub being opened or used for the canvas (T3-090), or given a purpose after it (T3-111)?
• Against T3-197: Is a canvas sub opened for order (T3-090), or to keep the work out of the creator's way (T3-197)?
• Varies: From a request for a separate sub or filter to moderators sending every canvas post to a national place sub.
• Is not: A sub that gathers many kindred rooms for a joint mark (T3-013).
• Exemplars: "I've made the subreddit r/nzplace to talk about place-related stuff." (newzealand c0369, rivals c0346); "We refer everything related to r/place toithe dedicated subreddit: /r/SwedenOnPlace/." (sweden c0604); "Please use /r/europeplace for further /r/Place posts" (europe c0648, rivals c0750)

T3-107 keeping planning in the thread

Members keep the canvas planning in the Reddit thread instead of a chat. Floor: samuraijack and cloud9, unlike in size (samuraijack holds 5,172 items in the window and cloud9 232, over twice as many).

• Must show: A choice or agreement to coordinate in the thread rather than in a chat, or a chat tried and failed so that the thread carried the work.
• Must not show: Moving into a chat (T3-014); arguing which chat to use (T3-109).
• Decide when both: A theme that tries a chat and returns to the thread: T3-107 when the return carries the work, T3-014 when the chat does.
• Against T3-014: Does the planning stay in the thread (T3-107) or move into a chat (T3-014)?
• Against T3-109: Is the thread chosen over any chat (T3-107), or one chat argued against another (T3-109)?
• Varies: From a small room agreeing to stay in touch through the thread to a member recalling that a chat never coordinated anything.
• Is not: Gathering canvas talk into a megathread (T3-015).
• Exemplars: "Alright, let's just stay in touch through this thread then." (samuraijack c0284, rivals c0282); "Our community isn't the largest, so as far as i know, we done things through here" (samuraijack c0282, rivals c0284); "I tried getting the sneaky discord to do it but we could never coordinate." (cloud9 c0063)

T3-109 arguing which chat to use

Members argue over which chat to organise in, or whether to use one at all: Discord, IRC, Slack, an official or an unofficial server. Floor: theblackvoid and wales, unlike in size (theblackvoid holds 9,430 items in the window and wales 530, over twice as many).

• Must show: A dispute or choice among chats: Discord against IRC or Slack, the official server against a new one, whether a chat suits the room at all.
• Must not show: Simply moving into a chat (T3-014); disputing whether the chat may decide for the room (T3-114).
• Decide when both: When the question is which venue, T3-109; when it is whether the venue's decisions bind the room, T3-114.
• Against T3-014: Is a chat set up and used (T3-014), or is the choice of chat argued (T3-109)?
• Against T3-114: Is the argument about which chat (T3-109), or about the chat's right to decide (T3-114)?
• Against T3-107: Is one chat weighed against another (T3-109), or the thread kept over any chat (T3-107)?
• Varies: From an argument over proprietary software to a choice between two servers; a Void member rejecting any chat for an uncoordinated Void.
• Is not: Members disputing that a Discord may decide for the room (T3-114).
• Exemplars: "Why discord? and not a sane thing like IRC?" (archlinux c0141, rivals c0145 c0149); "Go ahead and use this one for now :) will set up an official one for /r/Wales as a whole tomorrow if I get a chance" (wales c0051); "having a discord goes against my thoughts on what The Void should be" (theblackvoid c1879)

T3-114 disputing the chat's authority

Members dispute whether the chat may decide for the room: who speaks there, who is left out, whether its plans bind the thread. Floor: furry and wales, unlike in size (furry holds 3,156 items in the window and wales 530, over twice as many).

• Must show: Contest over the chat's standing: a Discord said to have no right to decide; the work said to belong on Reddit; members outside the chat said to be left out; the chat's decisions defended as binding; a chat seized or closed.
• Must not show: Choosing which chat to use (T3-109); relaying the chat's decisions with no dispute (T3-152); disputing who may speak for a room toward other rooms (T3-126).
• Decide when both: A dispute over who speaks for the room to outsiders is T3-126; over whether the room's own chat governs the room, T3-114.
• Against T3-152: Are the chat's decisions only reported (T3-152), or contested or defended as binding (T3-114)?
• Against T3-109: Is the question which chat (T3-109), or whether the chat may decide (T3-114)?
• Against T3-126: Is the dispute about who speaks for the room to other rooms (T3-126), or about the chat's power inside the room (T3-114)?
• Varies: From a member asking why the Discord is an authority to outsiders seizing the room's server.
• Is not: Members telling outsiders that no one can speak for the placers (T3-126).
• Exemplars: "and why are they an authority?" (furry c0310); "Discord hat nichts zu entscheiden" (placeDE c0035, rivals c0363); "dies ist eine reddit aktion und sollte auf reddit bleiben." (germany c0101)

T3-116 hiding the plan from rivals

Members hide the room's plan from rivals who read the thread: private messages, their own language, codes. Floor: lakers and russia, unlike in size (lakers holds 3,479 items in the window and russia 1,401, over twice as many).

• Must show: A plan kept from rivals who read the thread: moved to private messages or a closed chat because of infiltrators; written in the room's own language or in a code.
• Must not show: Moving to a chat for speed or order with no rival in view (T3-014); spying in a rival's chat (T3-132); recruiting quietly so attackers do not notice (T3-144).
• Decide when both: A move into a chat made because rivals read the thread is T3-116; the same move for speed is T3-014.
• Against T3-014: Is the plan moved because rivals are reading (T3-116), or for speed and order (T3-014)?
• Against T3-132: Are rivals kept out of one's own plan (T3-116), or is the rival's plan read from inside (T3-132)?
• Against T3-144: Is the plan hidden from readers (T3-116), or the recruiting kept quiet so attackers do not come (T3-144)?
• Against T3-083: Is language used to keep rivals out (T3-116), or a gap bridged to deal with another room (T3-083)?
• Varies: From asking members to write only in Hindi to letter-and-number codes in Russian; a plan passed by private message because rival fans got in.
• Is not: Recruiting quietly to avoid attackers (T3-144).
• Exemplars: "Alright. Pm this to others, don't post it in the thread because the celtics fans are infiltrating" (lakers c0131, rivals c0130); "Bakchodon, belgium ke log hamare thread padh rahe hai or hamari strategy ko samajh rahe hai." (bakchodi c0121, rivals c0230 c0118); "как вы думаете, лучше нам говорит по русский чтобы нас голланцы не понимали?" (russia c0031, rivals c0033 c0032)

T3-132 spying in a rival's chat

Members watch a rival room's chat from inside, or an outsider watches theirs, and report what they see. Floor: babymetal and shitredditsays, unlike in size (babymetal holds 5,231 items in the window and shitredditsays 1,337, over twice as many).

• Must show: Someone inside another room's chat or thread as a watcher: joining a rival's Discord to learn its plans, reporting what is said there, an outsider announcing that they are watching.
• Must not show: Meeting other rooms in chat to talk terms (T3-153); hiding one's own plan (T3-116).
• Decide when both: A visit that is both open talks and watching: T3-153 when terms are talked, T3-132 when the report is what was overheard.
• Against T3-153: Is the visit open, to talk with the other room (T3-153), or hidden, to watch it (T3-132)?
• Against T3-116: Is the rival's plan read from inside (T3-132), or one's own plan kept from rivals (T3-116)?
• Against T3-087: Is an attack traced from the pixels and what others said (T3-087), or learned from inside the rival's chat (T3-132)?
• Against T3-176: Is the rival watched from inside (T3-132), or harmed from inside by a script (T3-176)?
• Varies: From one member undercover in the Void's Discord warning of an invasion to a member laughing at rivals panicking in their chat.
• Is not: A diplomat serving in the open across many servers (T3-194).
• Exemplars: "i am spying on their discord channel" (babymetal c0090); "I AM UNDERCOVER IN THE VOID DISCORD. THEY MAY INVADE CUBERS SOON. WATCH OUT" (cubers c0242); "Watched them freak out in their discord and laughed." (shitredditsays c0046)

T3-152 announcing what the chat decided

Members bring the chat's decisions back to the thread: the plan agreed, a change authorised, where to place next. Floor: radiohead and SwissNeutralityZone, unlike in size (radiohead holds 7,280 items in the window and SwissNeutralityZone 537, over twice as many).

• Must show: A report in the thread of what the chat decided or is doing: 'agreed on Discord', 'the Discord is working on it', the chat's next target, a change explained as approved there.
• Must not show: Moving into the chat (T3-014); disputing whether the chat may decide (T3-114); a decision put to the thread by vote (T3-066).
• Decide when both: The move into the chat is T3-014, the relay of its decisions T3-152; when both have concepts of their own, the larger is primary.
• Against T3-014: Are members sent into the chat (T3-014), or told in the thread what it decided (T3-152)?
• Against T3-114: Is the chat's decision reported (T3-152), or its right to decide contested (T3-114)?
• Against T3-066: Is a decision put to the room by vote or poll (T3-066), or a chat's decision reported (T3-152)?
• Varies: From one line saying a change was agreed on Discord to running relays of the chat's orders during an attack.
• Is not: A moderator putting a choice to a vote in the thread (T3-066).
• Exemplars: "Changing text for readability purpose as was agreed on discord" (radiohead c0175, rivals c0158 c0189); "the discord is working on this right now, the eyes are a legit change" (madokamagica c0030); "After some discussion on Discord, we figured out that the best thing to do right now, was to keep cleaning the flag, but move it at the same time one pixel up" (SwissNeutralityZone c0050)

T3-153 meeting other rooms in chat

Members meet other rooms in chats (their own, the other's or a shared council) to talk terms, borders or joint work. Floor: stardustcrusaders and epublica, unlike in size (stardustcrusaders holds 4,002 items in the window and epublica 149, over twice as many).

• Must show: Contact with another room through a chat: inviting its members to the room's Discord to talk, visiting theirs, joining a shared server or council, passing a template or a request there.
• Must not show: The room's own planning chat with no other room in it (T3-014); watching a rival's chat in secret (T3-132); the deal itself, when that is the doing (G14, G15).
• Decide when both: Meeting in chat and the deal made there: the deal's kind (T3-010, T3-150, T3-151) is primary, and T3-153 is added when the meeting in chat has concepts of its own.
• Against T3-014: Is another room in the chat (T3-153), or only the room's own members (T3-014)?
• Against T3-132: Is the visit open, to talk (T3-153), or hidden, to watch (T3-132)?
• Against T3-194: Is a member acting for the room toward another room as its envoy (T3-194), or are members meeting in a chat (T3-153)?
• Against T3-010: Is the theme the place of the talks (T3-153), or the border or space agreed (T3-010)?
• Varies: From an invite to talk borders in the Green Lattice Discord to diplomats on a world council server.
• Is not: A member spying in a rival's Discord (T3-132).
• Exemplars: "Just spoke to the Swiss on their discord and they strongly recommended getting permission/help from /r/ainbowroad" (stardustcrusaders c0204, rivals c0044); "We could come to some sort of agreement though. Come talk in the Green Lattice discord." (redhotchilipeppers c0057); "join us spacex people to discuss the border on spacex" (epublica c0056)

G04 calling people in to place

T3-002 calling members in to place

Members call the room's own members to come and place for its work: to start, build, finish or hold a picture, calls to placers who are not yet a group included. Floor: thebluecorner and dallasstars, unlike in size (thebluecorner holds 5,939 items in the window and dallasstars 790, over twice as many).

• Must show: Calls to the room's members, or to placers not yet gathered into a group, to come and place: 'come help', 'we need more people', 'everyone join', rallies to build, finish or repair a work, posts asking who is in.
• Must not show: Calls aimed at other subs (T3-062) or at another canvas room as a room (T3-084); welcoming canvas visitors into the sub (T3-044). The national flag as the room's mark carries T3-065; writing the sub's name carries T3-169.
• Decide when both: A call made mostly of coordinates or a template is T3-070, with T3-002 added when the call has concepts of its own; a call to defend a work under attack is T3-005 when the defence leads. When a theme holds two or more of these acts (an idea of what to make offered to the room, T3-033; hands called to place, T3-002; the work placed and its progress reported, T3-038), count the concepts of each: the act with the most concepts of its own is primary, and another is added under rule 0 only with concepts of its own. The opening post does not lead because it comes first. On a tie, T3-038 when the work was placed; else T3-002 when the mark was already chosen, T3-033 when it was not.
• Against T3-062: Are the room's own members called (T3-002), or the members of other subs (T3-062)?
• Against T3-005: Is the call to build or finish (T3-002), or to defend against an attack under way (T3-005)?
• Against T3-033: Count the concepts of each: is the larger share an idea of what to make offered to the room (T3-033), or hands called to a mark already chosen (T3-002)? The opening post does not lead because it comes first.
• Against T3-070: Is the call itself the doing (T3-002), or the coordinates and templates that tell placers what to place (T3-070)?
• Against T3-104: Are people asked to place (T3-002), or those already placing cheered on (T3-104)?
• Against T3-169: Is the work the sub's name written on the canvas (T3-169), whatever the call or report about it, or any other picture called for (T3-002)?
• Against T3-016: Is the event explained (T3-016), or are members called to come and place (T3-002)?
• Against T3-038: Count the concepts of each: is the larger share the work placed and its progress reported (T3-038), or hands called for it (T3-002)? An opening call does not lead because it comes first.
• Against T3-051: Are members asked to vote a post up (T3-051), or to come and place (T3-002)?
• Against T3-065: Is the work a flag of the land the room is named for or speaks for, a flag built in r/guatemala being Guatemala's unless its concepts name another (T3-065), or any other picture (T3-002)?
• Against T3-167: Is a time set for placing together (T3-167), or hands called with no time (T3-002)?
• Against T3-044: Are the room's own members called to come and place (T3-002), or outsiders brought to the sub by its mark and welcomed (T3-044)?
• Against T3-084: Are the room's own members called to place (T3-002), or another canvas room asked, as a group, for help (T3-084)?
• Against T3-144: Are hands called for in the open (T3-002), or recruited only inside friendly communities so the work draws no attackers (T3-144)?
• Varies: From one 'come help me out' that draws no reply to repeated rallies through a long build; calls to start, to finish, to repair; calls to placers repeating a pattern before any group exists.
• Is not: Calls to build the room's national flag (T3-065).
• Exemplars: "Here's what I have so far: http://i.imgur.com/z5Q6TwA.png Come help me out!" (dallasstars c0075); "wtf, we're outnumbered! we need more people!" (thebluecorner c0256); "Get everyone you can" (korea c0067)

T3-044 recruiting canvas visitors

The room's mark on the canvas brings outsiders to the sub; members welcome them, advertise the sub on the canvas for it, or count the newcomers. Floor: parahumans and livecounting, unlike in size (parahumans holds 1,829 items in the window and livecounting 192, over twice as many).

• Must show: Newcomers led to the sub by its canvas mark: visitors saying they came from r/place, members welcoming them, the sub's name placed so that viewers find it, subscriber growth counted.
• Must not show: The room's own members finding its mark already placed (T3-082); former fans returning (T3-196); calling members to place (T3-002).
• Decide when both: Whose eyes find the mark: outsiders led to the sub go to T3-044; the room's own members finding work they did not know of go to T3-082.
• Against T3-082: Are outsiders led to the sub by the mark (T3-044), or members finding their own room's mark already placed (T3-082)?
• Against T3-196: Is the newcomer new to the community (T3-044), or a former fan coming back (T3-196)?
• Against T3-169: Is the sub's name written to sign the work (T3-169), or to bring visitors in (T3-044)?
• Against T3-002: Are the room's own members called to come and place (T3-002), or outsiders brought to the sub by its mark and welcomed (T3-044)?
• Against T3-127: Is the notice of the creators sought (T3-127), or are canvas visitors led into the sub (T3-044)?
• Against T3-129: Is the mark meant to bring visitors to the sub (T3-044), or to make others notice a demand (T3-129)?
• Against T3-189: Are the newcomers the mark draws welcomed (T3-044), or feared (T3-189)?
• Varies: From a visitor saying the sign brought them in to members tracking subscriber stats day by day; welcomes in the room's own idiom.
• Is not: A member of the room discovering that the room's mark is already on the canvas (T3-082).
• Exemplars: "Hello, I just came from r/place. I don't think I'd ever come here if it wasn't for that sign" (parahumans c0041); "welcome to all visitors from /r/place!" (livecounting c0043, rivals c0004); "I'm happy that this sub decided to take part in /r/place. As a result I (and seemingly others) have found this great community" (npr c0035)

T3-062 recruiting kindred subs to help

Members take the room's call into other subs, mostly kindred ones (sister, regional, related fandoms), to bring more hands to the room's work. Floor: theblackvoid and epublica, unlike in size (theblackvoid holds 9,430 items in the window and epublica 149, over twice as many).

• Must show: The room's call for hands carried into other subs or communities, or proposed: 'ask r/X for help', threads opened in other subs, recruiting from related communities.
• Must not show: Calls to the room's own members (T3-002); one canvas room asking another, as a group, to help or make room (T3-084); a hub sub gathering kindred rooms (T3-013).
• Decide when both: A request to an organised canvas group, room to room, is T3-084; a call for hands posted to a community, T3-062.
• Against T3-002: Are the room's own members called (T3-002), or other subs' members (T3-062)?
• Against T3-084: Is another sub's membership asked for hands (T3-062), or another canvas group asked, as a group, to help with this room's work (T3-084)?
• Against T3-013: Is help sought for this room's work (T3-062), or are kindred rooms gathered into one hub (T3-013)?
• Against T3-011: Is help asked for (T3-062), or sent to another room's work (T3-011)?
• Against T3-064: Does the message to another sub carry the room's joke (T3-064), or ask that sub for help on the canvas (T3-062)?
• Against T3-128: Are hands sought for the room's work (T3-062), or for a streamer's attack (T3-128)?
• Against T3-137: Are other subs' members recruited to the room (T3-062), or does the room's member join another's build (T3-137)?
• Against T3-144: Is the call kept inside friendly communities for safety (T3-144), or carried to other subs to bring hands (T3-062)?
• Against T3-051: Are upvotes asked so a post climbs (T3-051), or the room's call for hands carried into other subs (T3-062)?
• Varies: From a suggestion to ask a neighbouring sports sub to threads posted across many subs by a dying faction.
• Is not: Sending the room's members to help another room's work (T3-011).
• Exemplars: "The void is dying, we have to recruit from other subreddits." (theblackvoid c0184); "Maybe get some help from r/clevelandcavs" (osu c0053); "He abierto un hilo en Plaza Podemos para pedir más ayuda" (epublica c0017)

T3-104 cheering the builders on

Members and passers-by cheer those placing: praise, encouragement and good wishes while the work goes on. Floor: monalisaclan and vermont, unlike in size (monalisaclan holds 1,148 items in the window and vermont 263, over twice as many).

• Must show: Encouragement aimed at builders during the work: 'keep going', 'nice work team', 'good luck', praise from members or from outsiders who may not place themselves.
• Must not show: Calls for more hands (T3-002); celebrating the finished work (T3-009); thanking or crediting helpers afterwards (T3-072, T3-043).
• Decide when both: Praise while the work goes on is T3-104; once the work is called finished, T3-009.
• Against T3-002: Are people asked to come and place (T3-002), or those placing encouraged (T3-104)?
• Against T3-009: Is the work going on (T3-104), or done and celebrated (T3-009)?
• Against T3-043: Are builders encouraged (T3-104), or the makers credited (T3-043)?
• Against T3-072: Are those placing cheered on while the work goes on (T3-104), or other rooms thanked for their help (T3-072)?
• Varies: From a passer-by's 'good job to everyone chipping in' to members keeping each other company through a night's building.
• Is not: Celebrating the finished mark (T3-009).
• Exemplars: "Keep going you glorious people and make this canvas a more civilised one!" (monalisaclan c0127); "Just thought I'd say that the carrots are inspiring and to keep it up!" (farmcarrots c0056); "Nice work team" (vermont c0028)

T3-129 making passers-by notice a demand

Members use the canvas to put a demand before passers-by: a wanted comeback, a new season, a sauce. Floor: rickandmorty and fxKorea, unlike in size (rickandmorty holds 34,483 items in the window and fxKorea 69, over twice as many).

• Must show: A mark planned or placed so that people viewing the canvas see a demand or announcement the room wants noticed by others (a company, a creator, Redditors at large).
• Must not show: The sub's name placed to bring visitors to the sub (T3-044); the room's emblem proposed as its mark (T3-033).
• Decide when both: A demand written over another room's art is T3-068 for the converting, with T3-129 added for the demand when it has a concept of its own.
• Against T3-044: Is the mark meant to bring visitors to the sub (T3-044), or to make others notice a demand (T3-129)?
• Against T3-033: Is a mark proposed as the room's emblem (T3-033), or as a message carrying a demand (T3-129)?
• Varies: From a wish that random Redditors notice a band's wanted comeback to a giant request for a fast-food sauce.
• Is not: A sub writing its own name for canvas visitors (T3-044).
• Exemplars: "If SM won't notice we want a comeback, maybe atleast some random Redditors will?" (fxKorea c0002); "We should go to /r/place and make a giant McDonald's Szechuan sauce request" (rickandmorty c0360, rivals c0431); "Everyone! Let's let our friends at /r/place who haven't heard that Season 3 is out!" (rickandmorty c0242, rivals c0360)

T3-144 recruiting quietly to avoid attackers

Rare tier. Members recruit only inside friendly communities and keep the work small, so that it draws no attackers.

• Must show: Recruiting held back or kept inside friendly communities because publicity might bring attackers; a small presence chosen for safety.
• Must not show: Hiding the plan's words from rival readers (T3-116); calling for hands in the open (T3-002, T3-062).
• Decide when both: Keeping the call quiet is T3-144; keeping the plan's text from readers is T3-116.
• Against T3-116: Is the recruiting kept quiet so attackers do not come (T3-144), or the plan hidden from rivals who read it (T3-116)?
• Against T3-062: Is the call kept inside friendly communities for safety (T3-144), or carried to other subs to bring hands (T3-062)?
• Against T3-002: Are hands called for in the open (T3-002), or recruited only inside friendly communities so the work draws no attackers (T3-144)?
• Against T3-191: Is the recruiting kept quiet (T3-144), or the name kept off the work (T3-191)?
• Varies: From weighing whether publicity would do more damage to recruiting through a few friendly chats.
• Is not: Writing the plan in a code so that rivals cannot read it (T3-116).
• Exemplars: "maintain our tiny presence and recruit mostly from within lolicon communities" (loliconsunite c0058, rivals c0057 c0088); "Would the publicity result in more damage?" (loliconsunite c0057, rivals c0058 c0088); "Nothing has been done through Discord except me bringing up our existence to a couple loli groups I'm in." (loliconsunite c0088, rivals c0057 c0058)

T3-159 rewarding helpers with prizes

Members reward those who helped the work with prizes: gold, medals, game codes, giveaways. Floor: kerbalspaceprogram and HomestarRunner, unlike in size (kerbalspaceprogram holds 2,930 items in the window and HomestarRunner 177, over twice as many).

• Must show: A prize offered or given for work on the canvas or for the room's effort: Reddit gold, mock medals, game codes, giveaways.
• Must not show: Thanks or credit with no prize (T3-072, T3-043); a tile offered as payment (T3-110).
• Decide when both: Thanks and a prize in one theme: T3-159 when the prize has a concept of its own, beside the thanking kind.
• Against T3-043: Is credit given in words (T3-043), or a prize given (T3-159)?
• Against T3-110: Is a prize given to helpers (T3-159), or a tile itself offered as payment (T3-110)?
• Against T3-131: Is a sale of the work argued over (T3-131), or helpers rewarded with prizes (T3-159)?
• Against T3-072: Are helpers given a prize (T3-159), or other rooms thanked with no prize (T3-072)?
• Varies: From gold offered before a feat to mock medals and a giveaway after.
• Is not: A pixel promised as thanks for help with something else (T3-110).
• Exemplars: "I offer a month of reddit gold to anyone who achieves the ramp thing." (kerbalspaceprogram c0073); "I hereby award gold medals to" (HomestarRunner c0143); "I sent you a Sydney code, great organization!" (paydaytheheist c0011)

T3-189 fearing newcomers the mark draws

Members fear what the canvas mark will bring into the sub: an influx of newcomers who do not read the rules or swamp the community. Floor: scp and parahumans, unlike in form (scp is a sub whose members write the fiction together, parahumans the fan sub of one author's web serial).

• Must show: Worry about the newcomers the mark draws: an influx that will swamp the sub or its site, newcomers who ignore the rules, the sub said to have gone downhill since.
• Must not show: Welcoming newcomers (T3-044); objecting that canvas posts flood the sub (T3-075).
• Decide when both: A theme that welcomes and fears the influx: the side with more concepts is primary, the other under rule 0.
• Against T3-044: Are the newcomers the mark draws welcomed (T3-044), or feared (T3-189)?
• Against T3-075: Is the complaint about canvas posts crowding the sub (T3-075), or about the people the mark brings in (T3-189)?
• Varies: From jokes that the Foundation cannot risk discovery to complaints that the influx ruined the sub.
• Is not: Members welcoming visitors who came from r/place (T3-044).
• Exemplars: "consider what happened to r/NoSleep. Too many people trying to submit without bothering" (scp c0106, rivals c0108); "yeah It would likely force them to halt all new articles entirely." (scp c0108, rivals c0106); "sure hope you at least made a buck off this influx because the subreddit has entirely gone to shit" (parahumans c0179)

T3-196 drawing lapsed fans back

The room's mark on the canvas brings former fans back to the community; members welcome them or hope it will. Floor: neopets and mindcrack, unlike in size (neopets holds 3,490 items in the window and mindcrack 1,133, over twice as many).

• Must show: Former members or fans returning because they saw the room's mark; members hoping the canvas will revive the sub.
• Must not show: Newcomers led to the sub by the mark (T3-044).
• Decide when both: A theme welcoming both: the larger group of concepts decides; the other is added under rule 0 when it has three or more concepts.
• Against T3-044: Is the person new to the community (T3-044), or a former fan coming back (T3-196)?
• Varies: From one returning fan's fond memories to a sub hoping the canvas wakes it up.
• Is not: A visitor who never knew the community (T3-044).
• Exemplars: "I forgot about neopets until I saw y'all's jub jub on r/place." (neopets c0101); "I forgot about this community until I saw this. Brought back memories :)" (mindcrack c0050, rivals c0044 c0042); "I dropped it a while back, and seeing it on /r/place reminded me of it." (parahumans c0113, rivals c0139)

G05 telling placers what to place

T3-034 asking for coordinates and instructions

Members ask where and how to place: coordinates, instructions, what to do with their pixel. Floor: fullcommunism and chess, unlike in size (fullcommunism holds 3,915 items in the window and chess 1,414, over twice as many).

• Must show: Requests for directions: where the work is, which coordinates, what to do, whether one is placing correctly; a pixel offered with a request to be told where to put it.
• Must not show: Coordinates, templates or how-to given (T3-070); asking what r/place is (T3-016).
• Decide when both: Questions and answers in one theme: the side with more concepts is primary, the other added under rule 0 when it has three or more.
• Against T3-070: Are directions asked for (T3-034) or given (T3-070)?
• Against T3-016: Is the question how and where to place for the room (T3-034), or what r/place is (T3-016)?
• Varies: From a newcomer asking how to join to a member demanding specific instructions before the room will act.
• Is not: Explaining what r/place is to members who have not seen it (T3-016).
• Exemplars: "Where? So the rest of us can help" (chess c0048, rivals c0062 c0042); "bir pikselim var milletime armağan olsun, söyleyin nereye koyayım?" (turkey c0082); "How does one join the whole placing tiles?" (fullcommunism c0146)

T3-066 putting decisions to a vote

A choice about the work is put to the room: a vote, a strawpoll, a call to decide together. Floor: argentina and farmcarrots, unlike in size (argentina holds 10,453 items in the window and farmcarrots 682, over twice as many).

• Must show: Members asked to decide together: votes, strawpolls and polls in the thread, 'we need to decide as a group', a leader letting the room choose; members casting votes.
• Must not show: The design settled by argument with no vote (T3-004); a chat's decision reported (T3-152); office-holders elected (T3-173).
• Decide when both: A design argument that ends in a vote: T3-004 primary when the arguing leads, T3-066 added when the vote has concepts of its own.
• Against T3-004: Is the design argued out (T3-004), or put to a vote or poll (T3-066)?
• Against T3-152: Is the decision taken by the room in the thread (T3-066), or reported from a chat (T3-152)?
• Against T3-173: Is a choice about the work voted (T3-066), or a person elected to an office (T3-173)?
• Against T3-101: Does the room decide (T3-066), or is one member put in charge (T3-101)?
• Varies: From a strawpoll between two backgrounds to an extended vote on what to paint next; leaders deferring to polls.
• Is not: A faction holding elections for its offices (T3-173).
• Exemplars: "We need to agree on one of these guys Created a strawpoll" (fireemblem c0308); "Ok guys we need to decide as a group whether or not we fix this" (farmcarrots c0137); "VOTEN YA! VOTACIÓN EXTENDIDA HASTA LAS 17:30. LO QUE GANE SERA PINTADO AL SUR DE URUGUAY!" (argentina c0391)

T3-070 sharing coordinates, templates and how-to

Members circulate what placers need to reproduce the work: coordinates, templates, grids, guides, colour, border and timing plans, and how-to. Floor: rickandmorty and startrek, unlike in size (rickandmorty holds 34,483 items in the window and startrek 3,498, over twice as many).

• Must show: Coordinates, templates, grid images, overlays, guides, colour plans, border plans, timings or how-to posted or updated for placers to follow by hand.
• Must not show: Insisting that the room use one template against rival versions (T3-091); scripts that place automatically (T3-028); asking for coordinates (T3-034).
• Decide when both: A call to place that carries coordinates: T3-070 when the directions lead, T3-002 when the call does; both with concepts of their own, rule 0.
• Against T3-091: Are directions shared for anyone to use (T3-070), or the room held to one official plan against others (T3-091)?
• Against T3-002: Is the doing the directions (T3-070), or the call for hands (T3-002)?
• Against T3-028: Is a picture or coordinates given for people to place by hand (T3-070), or a script that places (T3-028)?
• Against T3-004: Is the design still argued (T3-004), or its directions handed out (T3-070)?
• Against T3-016: Is the event explained for anyone (T3-016), or a guide, template or coordinates for the room's work posted to follow (T3-070)?
• Against T3-034: Are directions asked for (T3-034) or given (T3-070)?
• Against T3-103: Are directions given to all (T3-070), or parts handed to particular members (T3-103)?
• Against T3-038: Is the mark being placed and its progress reported, coordinates given as where the work in progress stands (T3-038), or are directions posted for placers to follow, coordinates, templates, guides or colour plans (T3-070)? A link that only shows where the finished work is points to it (T3-026), not a direction.
• Varies: From one pair of coordinates to step-by-step guides and colour-coordination threads; plans of colours, borders and timings are included.
• Is not: Arguing over which design to build (T3-004).
• Exemplars: "Update: Here is the guide: http://i.imgur.com/kAzcjIv.jpg" (startrek c0089); "The grid layout of our flag!" (canada c0228, rivals c0064); "Coords are (159,721) if anyone needs them" (rickandmorty c0353)

T3-091 keeping everyone on one template

Members hold the room to one official design or plan, against versions and placers that stray. Floor: cirkeltrek and msu, unlike in size (cirkeltrek holds 1,511 items in the window and msu 501, over twice as many).

• Must show: One plan declared official or current and members told to follow it: 'stick to the original', 'too many people do not follow the plan', an official design thread.
• Must not show: Coordinates or templates shared with no insistence on one (T3-070); choosing which design (T3-004).
• Decide when both: Choosing the design is T3-004; once it is chosen, keeping placers to it is T3-091.
• Against T3-070: Are directions shared for use (T3-070), or one plan imposed against others (T3-091)?
• Against T3-004: Is the design being chosen (T3-004), or the chosen design enforced (T3-091)?
• Against T3-049: Is the scattering complained of (T3-049), or one plan imposed as its remedy (T3-091)?
• Against T3-069: Are the room's pieces narrowed to fewer (T3-069), or placers held to one design of one piece (T3-091)?
• Against T3-089: Are hand placers held to the current plan (T3-091), or scripts brought into line with it (T3-089)?
• Against T3-103: Is everyone held to one plan (T3-091), or the plan cut into assigned parts (T3-103)?
• Varies: From one plea to keep the lettering to official coordination threads with updated plans.
• Is not: A member posting the latest template with no word on following it (T3-070).
• Exemplars: "For the love of god stick to the original lettering on the "Go Green"." (msu c0029); "Inderdaad, er zijn te veel mensen die het plan niet volgen." (cirkeltrek c0302); "Official Design thread" (monalisaclan c0016)

T3-101 putting one member in charge

The room puts one member, or a few, in charge of the work, or members ask for someone in charge. Floor: mls and TheGreatGreenBox, unlike in size (mls holds 12,324 items in the window and TheGreatGreenBox 178, over twice as many).

• Must show: A leader named, claimed, appointed or asked for: someone in charge of the work, project leads through whom decisions go, overseers or ministers appointed, a temporary leader.
• Must not show: Votes on the work (T3-066); a faction's elections for its offices (T3-173); disputes over who speaks for the room to others (T3-126).
• Decide when both: A leader appointed and then elected in form: T3-173 when the election is the doing, T3-101 when the leading is.
• Against T3-066: Does the room decide by vote (T3-066), or does one member lead (T3-101)?
• Against T3-173: Is a leader for the work named (T3-101), or are a faction's offices filled by election (T3-173)?
• Against T3-126: Is someone put in charge inside the room (T3-101), or is it disputed who speaks for the room to others (T3-126)?
• Against T3-172: Is a leader named for the work (T3-101), or the order's standing rules set (T3-172)?
• Against T3-187: Is one member put in charge (T3-101), or does the leader hand the work to all (T3-187)?
• Varies: From a demand for somebody clearly in charge to a faction appointing ministers and overseers.
• Is not: A faction's ritual elections (T3-173).
• Exemplars: "WE NEED A NEW THREAD WITH SOMEBODY CLEARLY IN CHARGE." (mls c0307); "I guess you can call me the leader of the pack as i organised us and did all the diplomacy and coordination." (starcraft c0139, rivals c0114); "I am the new temp leader in the discord chat please don't give up we will not lose our corner" (TheGreatGreenBox c0051)

T3-103 dividing the picture among teams

The work is divided: teams, colours, rows or areas of the picture assigned to members. Floor: dota2 and crusaderkings, unlike in size (dota2 holds 42,568 items in the window and crusaderkings 3,660, over twice as many).

• Must show: Parts of the work assigned: teams for areas, colours or rows; 'one team fixes, another expands'; members asking to be given a job.
• Must not show: One template for all with no division (T3-091); shifts by hour of the day (T3-141).
• Decide when both: Teams by part and shifts by hour in one theme: the larger part primary, the other under rule 0.
• Against T3-141: Is the work divided by part of the picture (T3-103), or by hours of the day (T3-141)?
• Against T3-070: Are directions given to all (T3-070), or parts handed to particular members (T3-103)?
• Against T3-091: Is everyone held to one plan (T3-091), or the plan cut into assigned parts (T3-103)?
• Varies: From a member asking to be assigned a job to colour armies and an icon split into 5x5 areas.
• Is not: Handing the defence to another time zone overnight (T3-141).
• Exemplars: "We need to make teams. One will fix trolling pixels. Another team to work on accuracy" (dota2 c0109); "Team Field - We will take care of the blue field." (AmericanFlaginPlace c0041); "We'll need 4 armies: 1 grey, 2 red, and one white." (crusaderkings c0006, rivals c0030)

T3-125 saying the room wings it

Members say the room has no plan or group: it goes with the flow, individuals placing on their own. Floor: australia and bisexual, unlike in size (australia holds 10,830 items in the window and bisexual 1,191, over twice as many).

• Must show: Statements that the room has no plan, organiser or group: 'we just wing it', 'go with the flow', 'no common group, all individuals'.
• Must not show: Complaints that the calls are scattered (T3-049); separating the room's plan from placers it does not control (T3-188).
• Decide when both: A room saying it has no plan and complaining of it: T3-125 when the lack is accepted, T3-049 when it is complained of.
• Against T3-049: Is the lack of a plan complained of (T3-049), or stated as the room's way (T3-125)?
• Against T3-188: Do members say they have no plan (T3-125), or set their plan apart from placers they do not control (T3-188)?
• Varies: From a cheerful 'we don't do organize' to a member who cannot find where any coordination happens.
• Is not: A room drawing the line between its coordinated members and placers it does not control (T3-188).
• Exemplars: "Yeah definitely we don't do organize, just go with the flow." (southafrica c0057); "not so far, just winging it." (australia c0278, rivals c0277); "Unfortunately, there's no like common group doing this; it's all individuals of the bi community" (bisexual c0063)

T3-141 covering the night shift

Members keep the work through the night and across time zones: night watches, the work handed to another continent while they sleep. Floor: dota2 and texas, unlike in size (dota2 holds 42,568 items in the window and texas 2,000, over twice as many).

• Must show: Watch kept over the hours when most members sleep: night watches, members volunteering to stay up, the work handed to members in other time zones, scripts left running overnight for the purpose.
• Must not show: Defence or repair with no word on hours or sleep (T3-005, T3-021); the picture divided into parts (T3-103).
• Decide when both: Keeping watch and repairing: T3-021 primary, T3-141 added when the hours and shifts have concepts of their own.
• Against T3-021: Is the work watched and repaired (T3-021), or watched through the hours others sleep (T3-141)?
• Against T3-103: Is the work divided by hour (T3-141), or by part of the picture (T3-103)?
• Against T3-005: Is an attack fought off (T3-005), or the night covered (T3-141)?
• Against T3-167: Do members place together at one time (T3-167), or take turns across the hours (T3-141)?
• Varies: From one member going to bed and hoping others hold to a German night shift over American pixels.
• Is not: A member repairing the work during the day (T3-021).
• Exemplars: "Europe, America's going to sleep. Hold the position!" (dota2 c0728); "Texan living abroad. Defending it will you sleep." (texas c0063); "Wenn wir schlafen gehen und die Amis wach sind kann vieles passieren. Ich sollte Nachtwache schieben." (placeDE c0101)

T3-167 timing a mass placement together

Members set a time to place together so that many pixels land at once. Floor: penguins and guatemala, unlike in size (penguins holds 2,046 items in the window and guatemala 46, over twice as many).

• Must show: A time fixed or proposed for members to place together: a start time so that a few are not overrun, a scheduled push, a jointly timed ending.
• Must not show: Calls to place with no time set (T3-002); watches across the night (T3-141).
• Decide when both: A call with a time: T3-167 when the time is the point, T3-002 otherwise.
• Against T3-002: Is a time set for placing together (T3-167), or hands called with no time (T3-002)?
• Against T3-141: Do members place together at one time (T3-167), or take turns across the hours (T3-141)?
• Varies: From a proposed start time for two placers to a faction's jointly timed white ending.
• Is not: Handing the watch to another time zone (T3-141).
• Exemplars: "We should also try to schedule a time that most users are free and online to work together to take over space." (penguins c0089); "We should create a time to start so it isn't just us two (also so we don't get overrun)" (guatemala c0003); "we will all paint this canvas white, together." (purplecorner c0057)

G06 strain, doubt and giving up

T3-036 judging the canvas too full

Members judge that the canvas is too full, or too far gone, for the room to join. Floor: schoolidolfestival and bigbang, unlike in size (schoolidolfestival holds 3,661 items in the window and bigbang 3, over twice as many).

• Must show: Statements that there is no space left, or that it is too late, to put the room's work on the canvas: 'no space for us now', 'the chart is too full', the canvas closed before the room began.
• Must not show: Searching for a spot (T3-020); doubting the room's strength (T3-136); asking a host room for space (T3-035).
• Decide when both: Searching for a spot while judging there is none: T3-020 when the search leads, T3-036 when the judgement does.
• Against T3-020: Is a spot looked for (T3-020), or is the canvas judged to have none (T3-036)?
• Against T3-136: Is the canvas too full (T3-036), or the room too weak (T3-136)?
• Against T3-035: Is space asked of a host room (T3-035), or is the canvas judged full (T3-036)?
• Varies: From a sad 'no space for us now' to a proposal to try a second canvas instead.
• Is not: A room giving up a spot it held under attack (T3-059, T3-181).
• Exemplars: "Would have been a good idea had we done that from the beginning but the chart is simply too full of pictures" (schoolidolfestival c0076, rivals c0083 c0077); "I'm trying as well. I don't think there's any space for us now... :(" (bigbang c0002); "The event is over unfortunately, r/place has closed." (chess c0078)

T3-059 urging others to give up

Members tell the room, or its defenders, to give the work up: it is lost, over, not worth the fight. Floor: apocalypserising and gameattack, unlike in size (apocalypserising holds 702 items in the window and gameattack 105, over twice as many).

• Must show: Calls on others in the room to stop, let the work go or accept the loss: 'it's over, just give up', 'let it go', 'burn it', 'a lost cause'.
• Must not show: A member quitting the effort themselves (T3-181); mourning the loss (T3-029); weighing whether to fight or move (T3-124).
• Decide when both: Urging and refusing in one theme: the side with more concepts is primary; refusing to yield the space to a neighbour is T3-123.
• Against T3-181: Are others told to give up (T3-059), or does the speaker quit (T3-181)?
• Against T3-123: Is giving up urged (T3-059), or refused (T3-123)?
• Against T3-029: Is the loss mourned (T3-029), or is giving up urged (T3-059)?
• Against T3-124: Is the room's next step weighed (T3-124), or giving up urged (T3-059)?
• Against T3-136: Is the room's strength doubted (T3-136), or giving up urged (T3-059)?
• Varies: From a gentle 'we made a good effort, let's have a beer' to scorn for a flag's last defenders.
• Is not: Members mourning a lost work after it is gone (T3-029).
• Exemplars: "Its over guys just give up." (apocalypserising c0035); "Guys, I think we made a good effort, but I think we need to just sit back and have a couple beers." (gameattack c0017); "Place is dead, let it go." (bardmains c0083)

T3-074 working around the timer

Members work around the one-pixel cooldown, too few hands and placing troubles while they build. Floor: vegan and bannedfromanime_irl, unlike in size (vegan holds 7,616 items in the window and bannedfromanime_irl 15, over twice as many).

• Must show: The pixel limit, the cooldown, too few placers or placing troubles worked around while building: what the limit lets the room do, designs scaled to the hands at hand, broken timers, mobile trouble, glitches that stop or delay placing.
• Must not show: Doubting that the room can manage a work at all (T3-136); placing beyond the limit by extra accounts or any other means (T3-088); explaining what r/place is (T3-016).
• Decide when both: Doubting whether the room can manage a work at all, even during the work, goes to T3-136; working around the timer and too few hands while building goes to T3-074. Glitches: explaining how the canvas or a glitch works is T3-016; using a glitch to place beyond the limit is T3-088; coping with a glitch that stops or delays placing is T3-074.
• Against T3-136: Is the room's capacity for the work doubted (T3-136), or are the timer and few hands worked around while building (T3-074)?
• Against T3-088: Is the limit worked within (T3-074), or broken by extra accounts or a glitch to place more (T3-088)?
• Against T3-016: Is the cooldown explained as how r/place works (T3-016), or worked around for the room's build (T3-074)?
• Varies: From one member's broken timer to a room scaling its panda to the few who place; finals, sleep and phones fitted around the five minutes.
• Is not: A member saying the room has too few people to make the logo at all (T3-136).
• Exemplars: "right now the sidebar says 330 r/yugioh subscribers are online but we probably have less than 10 people working" (yugioh c0108, rivals c0118); "if the timer doesn't show up it does't save unfortunately" (calgaryflames c0024); "The timer was removed which made it easier, but now it's up again. I'll check back in an hour." (vegan c0212)

T3-098 questioning the room's canvas presence

Members ask whether and how the room shows on the canvas: why it is absent, whether a work counts as the room's, how it compares with other rooms. Floor: overwatch and minecraft, unlike in size (overwatch holds 45,381 items in the window and minecraft 6,314, over twice as many).

• Must show: Questions about the room's presence: why the room has no work on the canvas, whether a picture counts as the room's, comparisons with other subs' marks, whether a duplicate or a small mark represents the room well.
• Must not show: A mark proposed (T3-033); the canvas judged worthless (T3-037); the room's strength doubted (T3-136).
• Decide when both: A question that ends in a proposal: T3-033 when the proposal leads, T3-098 added when the questioning has concepts of its own.
• Against T3-033: Is a mark proposed (T3-033), or the room's presence or absence questioned (T3-098)?
• Against T3-037: Is the canvas itself judged (T3-037), or the room's showing on it (T3-098)?
• Against T3-085: Is the room's presence questioned (T3-098), or the room weighed against the nations on the canvas (T3-085)?
• Against T3-136: Is it asked whether and how the room shows on the canvas (T3-098), or doubted that the room has the people or strength for a work (T3-136)?
• Varies: From 'why don't we have a quaggan?' to arguing whether a game's pictures count as the sub's participation.
• Is not: A member saying r/place is a waste of time (T3-037).
• Exemplars: "/r/TF2 has their logo on /r/place.. Why can't /r/overwatch organize and get a logo going there??" (overwatch c0507, rivals c0209 c0511); "People are recreating /r/place in Minecraft... why is nobody putting minecraft on /r/place?" (minecraft c0198, rivals c0172); "Why don't we have a quaggan in Place?" (GuildWars2 c0166)

T3-124 weighing fighting against moving

Members weigh, after a loss or under pressure, whether to fight for the spot, rebuild it there, or move elsewhere. Floor: battlecats and OrderOfTheKoi, unlike in size (battlecats holds 3,436 items in the window and OrderOfTheKoi 16, over twice as many).

• Must show: A choice put between fighting and moving, or between rebuilding in place and relocating: 'restore it where it was or move?', 'not this time, we fight back', a move proposed against holding on.
• Must not show: Moving after an attack as a thing done (T3-022); refusing a neighbour's request to yield (T3-123); urging the room to give up (T3-059).
• Decide when both: The weighing is T3-124 and the move made after it T3-022; when both have concepts of their own, rule 0.
• Against T3-022: Is the move weighed (T3-124), or made (T3-022)?
• Against T3-123: Is moving one option weighed (T3-124), or refused outright to a neighbour (T3-123)?
• Against T3-059: Is the room's next step weighed (T3-124), or giving up urged (T3-059)?
• Against T3-005: Is the attack fought off (T3-005), or is fighting one option weighed against another (T3-124)?
• Varies: From a quick 'move or restore?' to long arguments over raiding a neighbour or holding ground.
• Is not: Relocating the work once it has been decided (T3-022).
• Exemplars: "Guide is eaten, do we want to try to restore it where it was or move to a new location?" (terraria c0123); "While negotiating with different groups, I've made concessions on our side. Not this time. We fight back." (texas c0122); "think the void killed it, sorry about the effort it took, maybe put it in the taskbar?" (battlecats c0191)

T3-136 doubting the room's strength

Members doubt that the room has the people or strength for a work: too few, too small, outnumbered, the work impossible. Floor: paladins and dragonquest, unlike in size (paladins holds 5,823 items in the window and dragonquest 359, over twice as many).

• Must show: Doubt that the room can make or hold a work at all: too few people, a small sub against a large one, estimates of the hands a work needs, a design judged impossible; doubt during the work counts.
• Must not show: Working around the timer and few hands while building (T3-074); urging the room to give up (T3-059).
• Decide when both: Doubting whether the room can manage a work at all, even mid-work, goes to T3-136; working around the timer and too few hands while building goes to T3-074.
• Against T3-074: Is the room's capacity for the work doubted (T3-136), or are the timer and few hands worked around (T3-074)?
• Against T3-059: Is the room's strength doubted (T3-136), or giving up urged (T3-059)?
• Against T3-036: Is the room too weak (T3-136), or the canvas too full (T3-036)?
• Against T3-049: Is the room too few or too weak (T3-136), or too scattered (T3-049)?
• Against T3-069: Does the room put its pixels on fewer pieces (T3-069), or doubt it can manage any (T3-136)?
• Against T3-098: Is it asked whether and how the room shows on the canvas (T3-098), or doubted that the room has the people or strength for a work (T3-136)?
• Varies: From a hopeful 'now all we need is enough people' to a small sub conceding it cannot fight a larger one.
• Is not: A member explaining how few pixels the timer allows while the room builds (T3-074).
• Exemplars: "there is nothing our small ass subreddit can do to combat anything the Pats subreddit decides to do" (falcons c0110); "it needs at least 100 people working on it to make." (paladins c0150); "Trying to make a dragonlord but it seems impossible." (dragonquest c0024)

T3-181 quitting the effort under strain

Members quit the canvas work themselves: tired, stressed, beaten by scripts or rivals, or at odds with the room. Floor: fivenightsatfreddys and ockytop, unlike in size (fivenightsatfreddys holds 9,633 items in the window and ockytop 978, over twice as many).

• Must show: A member or members stopping their own part in the work: 'I give up', 'I'm done', 'they got tired of it', leaving over scripts or over a split in the room.
• Must not show: Telling others to give up (T3-059); mourning the lost work (T3-029); a faction splitting over doctrine (T3-190).
• Decide when both: Quitting and mourning in one theme: the larger part primary, the other under rule 0.
• Against T3-059: Does the speaker quit (T3-181), or tell others to give up (T3-059)?
• Against T3-029: Is the loss mourned (T3-029), or the effort abandoned (T3-181)?
• Against T3-190: Does a faction split over doctrine (T3-190), or does a member leave the effort (T3-181)?
• Against T3-187: Does a member quit under strain (T3-181), or pass the work on (T3-187)?
• Varies: From an embarrassed admission of giving up hours ago to workers quitting because it was too stressful; leaving because scripts took the fun out.
• Is not: A defender telling others that the work is a lost cause (T3-059).
• Exemplars: "I give up. We started strong. But just like tennessee tradition we are in the wrong place. I'm done." (ockytop c0045); "Everyone who were working on it got tired of it as it was too stressful." (fivenightsatfreddys c0480); "I'm ashamed to admit I gave up hours ago, great fucking job so far though" (denverbroncos c0090)

G07 choosing what to make and where

T3-004 settling the mark's design

Members work out what the mark should look like (picture, colours, size, lettering, details) and correct it against the plan. Floor: tagpro and pitt, unlike in size (tagpro holds 1,937 items in the window and pitt 315, over twice as many).

• Must show: Argument or work on the mark's look: which picture or version, colours, letters, fonts, size, outlines, details; corrections to make the placed work match the design.
• Must not show: Proposing that the room make a mark at all (T3-033); choosing where it goes (T3-020); holding everyone to a chosen template (T3-091); reshaping the mark against tampering (T3-055); a bigger or second piece (T3-041).
• Decide when both: Design argued and spot chosen in one theme: the larger part primary and the other under rule 0. A design argument settled by a vote adds T3-066 when the vote has concepts of its own.
• Against T3-033: Is a mark proposed to the room (T3-033), or is its look worked out (T3-004)?
• Against T3-020: Is the question what it looks like (T3-004), or where it goes (T3-020)?
• Against T3-091: Is the design being settled (T3-004), or the settled design enforced against strays (T3-091)?
• Against T3-055: Is the look changed for its own sake (T3-004), or to make the mark harder to tamper with (T3-055)?
• Against T3-041: Is the mark's own design settled (T3-004), or a bigger or second piece added (T3-041)?
• Against T3-066: Is the design argued out (T3-004), or put to a vote or poll (T3-066)?
• Against T3-070: Is the design still argued (T3-004), or its directions handed out (T3-070)?
• Against T3-077: Is a still design settled (T3-004), or a change over time planned (T3-077)?
• Against T3-169: Is the mark's design settled (T3-004), or its signature added (T3-169)?
• Against T3-038: Is the mark being placed and its progress reported (T3-038), or its look argued and corrected against the plan (T3-004)?
• Varies: From a one-pixel correction to long arguments over which picture represents the room; letters, fonts, colours and outlines.
• Is not: Holding placers to the agreed design against those who stray (T3-091).
• Exemplars: "I think the design should be changed. Nobody knows what the pups are." (tagpro c0152); "Making them 4 tiles wide like we were doing before looks a bit tacky" (pitt c0095); "I'm gonna give it an outline of white where there is non-rainbow to give it some definition!" (anaheimducks c0039)

T3-020 choosing a canvas spot

Members look for and choose where on the canvas the mark goes: open space, a corner, beside kindred marks, a new location. Floor: h3h3productions and mizzou, unlike in size (h3h3productions holds 16,925 items in the window and mizzou 72, over twice as many).

• Must show: Where the mark should go: free space found, corners and neighbours weighed, a location announced or changed before or while building.
• Must not show: Moving the work after an attack (T3-022); asking a host room for space (T3-035); judging there is no space left (T3-036).
• Decide when both: A new spot chosen after an attack is T3-022; a spot chosen in the first place, or for a further piece, is T3-020.
• Against T3-022: Is a spot chosen in the first place (T3-020), or a new one found after an attack (T3-022)?
• Against T3-035: Is space found on the open canvas (T3-020), or asked of a room that holds it (T3-035)?
• Against T3-036: Is a spot found (T3-020), or the canvas judged to have none (T3-036)?
• Against T3-004: Is the question where it goes (T3-020), or what it looks like (T3-004)?
• Varies: From a quick 'top right corner!' to long searches across a full canvas; spots beside kindred works; striking where the defence is weak.
• Is not: Relocating the work once attackers have taken its spot (T3-022).
• Exemplars: "We could get a tiny MU next to KSU with all the colleges but it will be a tight fit." (mizzou c0007); "there's still a pretty good amount of areas without anything significant in them." (h3h3productions c0054); "Locatie noua. Sus si putin stanga" (romania c0032)

T3-033 proposing the room's mark

A member offers the room an idea of what to make on the canvas, and calls the room to make it. Floor: leagueoflegends and stardewvalley, unlike in size (leagueoflegends holds 75,751 items in the window and stardewvalley 1,541, over twice as many).

• Must show: An idea of what the room should put on the canvas, offered to the room: 'we should put X on r/place', 'let's make a ...', a proposal with or without a picture; slogans and symbols proposed as the room's mark included.
• Must not show: Calls for hands to a mark already chosen (T3-002); the design of a chosen mark worked out (T3-004).
• Decide when both: When a theme holds two or more of these acts (an idea of what to make offered to the room, T3-033; hands called to place, T3-002; the work placed and its progress reported, T3-038), count the concepts of each: the act with the most concepts of its own is primary, and another is added under rule 0 only with concepts of its own. The opening post does not lead because it comes first. On a tie, T3-038 when the work was placed; else T3-002 when the mark was already chosen, T3-033 when it was not.
• Against T3-002: Count the concepts of each: is the larger share an idea of what to make offered to the room (T3-033), or hands called to a mark already chosen (T3-002)? The opening post does not lead because it comes first.
• Against T3-004: Is a mark proposed (T3-033), or a chosen mark's look worked out (T3-004)?
• Against T3-098: Is a mark proposed (T3-033), or the room's absence from the canvas questioned (T3-098)?
• Against T3-041: Is the room's first mark proposed (T3-033), or a second piece beside an existing one (T3-041)?
• Against T3-092: Is a mark proposed for the room to make (T3-033), or made alone and reported (T3-092)?
• Against T3-129: Is a mark proposed as the room's emblem (T3-033), or as a message carrying a demand (T3-129)?
• Against T3-038: Count the concepts of each: is the larger share an idea of what to make offered to the room (T3-033), or the mark placed and its progress reported (T3-038)? A proposal does not lead because it comes first.
• Varies: From one member's wish to put a symbol on the canvas to a series of picture proposals; political slogans proposed as such sit here.
• Is not: A call for help on a picture already started (T3-002).
• Exemplars: "we should put a plansewalker symbol on r/place" (magictcg c0138); "We need to rep Stardew Valley on https://www.reddit.com/r/place/ !!! Let's make a jumino or something!" (stardewvalley c0001); "We should make a pixel art for our lord and saviour on /r/place" (leagueoflegends c0383)

T3-055 reshaping the mark against tampering

Members change the mark's shape to make it harder to tamper with: borders, boxes, outlines, enlarging or compacting it, dropping parts easily griefed. Floor: vinesauce and armok, unlike in size (vinesauce holds 366 items in the window and armok 74, over twice as many).

• Must show: A design change made for protection: a border or box around the mark, an outline, the mark enlarged or compacted, a vulnerable part (a name, letters) dropped or replaced.
• Must not show: Repairing the mark as it was (T3-021); design changes for their own sake (T3-004); fighting off attackers (T3-005).
• Decide when both: Repair and protective reshaping in one theme: T3-021 primary when the repair leads, T3-055 added when the reshaping has concepts of its own.
• Against T3-021: Is the mark restored as it was (T3-021), or changed in shape so it resists tampering (T3-055)?
• Against T3-004: Is the change made for the look (T3-004), or for protection (T3-055)?
• Against T3-005: Are attackers fought off (T3-005), or the mark's shape changed against them (T3-055)?
• Against T3-042: Is the mark reshaped to resist tampering (T3-055), or expansion dropped for upkeep (T3-042)?
• Varies: From a green box around a mushroom to a name dropped as too easily griefed and a lattice built around the figure instead.
• Is not: Re-placing the pixels attackers changed (T3-021).
• Exemplars: "We should build a green box around the Vineshroom to protect it from vandalism" (vinesauce c0082); "The name was too easily griefed. Building Green Lattice around HULK now." (TheHulk c0020); "Before expanding more, I propose we try to squish the dwarves in as closely as possible for easier defense" (armok c0046)

T3-077 animating the mark in timelapse

Rare tier. Members plan a mark that moves or flashes when the canvas is watched as a timelapse.

• Must show: A plan to change the mark over time so that it animates in the timelapse: flashing colours, a walking figure, a scripted animation.
• Must not show: Saving the work in screenshots and timelapses (T3-105).
• Decide when both: A plan that animates the mark and saves the timelapse: T3-077 for the plan, T3-105 for the saving.
• Against T3-105: Is the timelapse used to keep the work (T3-105), or the work designed to move in it (T3-077)?
• Against T3-004: Is a still design settled (T3-004), or a change over time planned (T3-077)?
• Varies: From a toadstool flashing red and green to a scripted animation.
• Is not: Sharing a timelapse of the finished work (T3-105).
• Exemplars: "no one has tried to make a flashing or moving image when the whole thing is viewed in a timelapse." (Mario c0010, rivals c0011); "making the toadstool near the top on the very left flash from completely red to completely green would be a good start" (Mario c0011, rivals c0010); "met wat handig gescript animatie toe te passen" (PlaceNL c0087)

T3-092 making a tribute alone

One member makes a small mark for the room, or for someone they admire, on their own and reports it, often asking others to keep it. Floor: bangtan and SydneyFC, unlike in size (bangtan holds 1,691 items in the window and SydneyFC 34, over twice as many).

• Must show: A single member making a small piece alone and saying so: 'I wrote a small X, protect it', 'I added a little something for my bias', 'I decided to make a tribute'.
• Must not show: Members reporting their share of the room's work (T3-003); proposing a mark to the room (T3-033).
• Decide when both: A lone piece that the room then takes up: T3-092 for the lone making, T3-038 for the room's build. A piece begun alone and then offered to the room for others to join: T3-033 when the offer leads, T3-092 when the lone making is reported with no call.
• Against T3-003: Is the work one member's own small piece (T3-092), or a share in the room's work (T3-003)?
• Against T3-033: Is a mark proposed for the room to make (T3-033), or made alone and reported (T3-092)?
• Against T3-060: Is the piece added to a shared mark (T3-060), or made alone apart from one (T3-092)?
• Against T3-160: Is the tribute to someone who died (T3-160), or a lone member's tribute to anyone (T3-092)?
• Varies: From a tiny tribute made before a long drive to a small logo one member keeps alive.
• Is not: A member reporting how many pixels they placed on the room's flag (T3-003).
• Exemplars: "I've got a 12 hour drive ahead of me, so I decided to make a tribute to Datlof on r/place." (yogscast c0043); "I wrote a small "SYD FC" on r/place. Protect it" (SydneyFC c0019, rivals c0012); "I added a little something for my bias" (bangtan c0055)

T3-160 building memorials to the dead

Members make or protect memorials on the canvas to people who died: musicians, drivers, relatives, the victims of a disaster. Floor: ireland and davidbowie, unlike in size (ireland holds 12,112 items in the window and davidbowie 246, over twice as many).

• Must show: A work made, proposed or defended as a memorial to the dead, or an existing work recast as one.
• Must not show: Mourning the lost canvas work (T3-029); tributes to the living (T3-092).
• Decide when both: A memorial defended against neighbours: T3-160 primary when the memorial is the work's point, T3-005 added for the defence.
• Against T3-029: Is a dead person honoured by the work (T3-160), or the lost work mourned (T3-029)?
• Against T3-092: Is the tribute to someone who died (T3-160), or a lone member's tribute to anyone (T3-092)?
• Varies: From a road renamed for a flag designer who had died to drivers' and musicians' memorials defended against neighbours.
• Is not: Members mourning their own erased work (T3-029).
• Exemplars: "Our mission has become this much more important. The 'Gilbert Baker' Memorial Rainbow Road." (ainbowroad c0197); "Join the cause. RIP Fr. Derek Cassidy, and my Granda and Granny." (ireland c0158); "Our DB Memorial is now engraved into the history of Reddit" (davidbowie c0034)

T3-169 signing the sub's name

Members put the sub's name on or beside the work: r/name, a sign, a label. Floor: ss13 and drawhelix, unlike in size (ss13 holds 1,478 items in the window and drawhelix 99, over twice as many).

• Must show: The sub's name, or a short form of it, written on the canvas; the choice whether to write it; keeping it there.
• Must not show: Advertising the sub to bring visitors in, when that is the stated point (T3-044); leaving the name off on purpose (T3-191).
• Decide when both: Writing the sub's name is T3-169's doing; a call to write it is its form, and one concept carries one placement.
• Against T3-044: Is the name written to sign the work (T3-169), or to bring visitors to the sub (T3-044)?
• Against T3-191: Is the name put on (T3-169), or left off on purpose (T3-191)?
• Against T3-004: Is the mark's design settled (T3-004), or its signature added (T3-169)?
• Against T3-002: Is the work the sub's name written on the canvas (T3-169), whatever the call or report about it, or any other picture called for (T3-002)?
• Varies: From a short tag under a logo to arguments over which short name fits the space.
• Is not: Dropping the sub's name so that the work is no target (T3-191).
• Exemplars: "We should display our subreddit name" (PurplePixels c0074); "Just added in R/SS13, just need the Greytide worldwide bit." (ss13 c0009); "we could use /r/DRHE. It could probably fit right under Lord without taking up too much space from the rainbow." (drawhelix c0038)

T3-191 leaving the work unsigned

Rare tier. Members leave the sub's name off the work, so that it draws no attackers or because the builders are not the sub's.

• Must show: A decision to drop or omit the sub's name or label from the work, with its reason.
• Must not show: Writing the name on (T3-169).
• Decide when both: A theme that argues both: the side that prevails in the concepts decides.
• Against T3-169: Is the name put on (T3-169), or left off (T3-191)?
• Against T3-144: Is the recruiting kept quiet (T3-144), or the name kept off the work (T3-191)?
• Varies: From dropping a label that makes the room a target to saying the builders are not the sub's.
• Is not: Writing the sub's name beside the work (T3-169).
• Exemplars: "having "furry" right there in text makes us a prime target" (furry c0147, rivals c0131); "The people working on it aren't from r/furry. we can drop the r/furry from it." (furry c0131, rivals c0147)

T3-197 heeding the creator's wishes

Rare tier. The room shapes its canvas work around what the creator of its subject wants: the creator's name kept off, canvas talk moved out of the creator's way.

• Must show: The wishes of the person the sub is about (an author, an artist) passed on and followed in the canvas work: not using their name, keeping canvas talk out of their sub, not pinging them.
• Must not show: Moderators' rules for canvas posts with no creator's wish behind them (T3-063, T3-015).
• Decide when both: Canvas talk moved to a new sub for the creator's sake: T3-090 for the move, T3-197 for the reason when it has concepts of its own.
• Against T3-063: Are canvas posts handled under the sub's rules (T3-063), or shaped by the creator's wish (T3-197)?
• Against T3-090: Is a canvas sub opened for order (T3-090), or to keep the work out of the creator's way (T3-197)?
• Against T3-140: Do the moderators disown the work (T3-140), or does the room heed its creator (T3-197)?
• Against T3-127: Is the creator's notice sought (T3-127), or the creator's wishes followed (T3-197)?
• Against T3-015: Is the canvas talk moved or shaped because the creator of the room's subject asked (T3-197), or gathered into one thread with no creator's wish behind it (T3-015)?
• Varies: From passing on that the author wants his name kept out to asking members not to ping him.
• Is not: Moderators gathering canvas talk into a megathread for order (T3-015).
• Exemplars: "Am hearing S4hbbQtdz/cRgjTfqcESz5Bj8VM= would prefer if we kept his name out of it, so focus on the top part and protecting the bug." (parahumans c0033, rivals c0063); "the moderator of this sub and author of its subject matter has asked to keep all the /r/place stuff to the pinned" (parahumans c0079, rivals c0063); "Please don't ping S4hbbQtdz/cRgjTfqcESz5Bj8VM=. He gets enough spam as it is, and just distracts him from important stuff." (parahumans c0053, rivals c0063)

G08 building and growing the mark

T3-003 reporting one's own placing labour

Members report their own part in the placing: what they placed, fixed or defended, and when. Floor: overwatch and kingdomhearts, unlike in size (overwatch holds 45,381 items in the window and kingdomhearts 5,319, over twice as many).

• Must show: A member telling of their own placing: 'I helped', 'I put in my part', 'I placed my first pixel', what they fixed or defended, the hours they spent.
• Must not show: The progress of the room's work as a whole (T3-038); one member's lone tribute (T3-092); others credited (T3-043).
• Decide when both: A member's own share told inside a celebration: T3-009 primary when the celebrating leads, T3-003 when the member's share is the point.
• Against T3-038: Is the room's work reported (T3-038), or one member's share in it (T3-003)?
• Against T3-092: Is the share part of the room's work (T3-003), or a small piece the member made alone (T3-092)?
• Against T3-043: Does the member tell their own part (T3-003), or credit others (T3-043)?
• Against T3-009: Is the finished work celebrated (T3-009), or one's own part in it told (T3-003)?
• Varies: From 'I helped! Yay me!' to accounts of hours of repair; told during the work and after the close.
• Is not: A member making a small tribute alone (T3-092).
• Exemplars: "I helped with building the large one and defended both." (kingdomhearts c0199); "i put in my part." (overwatch c0086); "I placed my first pixel almost exactly 5 minutes before it closed." (liverpoolfc c0190, rivals c0189)

T3-026 announcing the mark is up

Members announce that the room's mark is on the canvas: 'we got on r/place', with a picture or its place. Floor: linux and genderfluid, unlike in size (linux holds 4,888 items in the window and genderfluid 30, over twice as many).

• Must show: Announcements that the room is on the canvas: 'we made it onto r/place', a screenshot or link showing the room's mark, others pointed to where it is.
• Must not show: Members discovering a mark of the room that they did not know of (T3-082); celebrating the finished work at or after the close (T3-009); reports of progress (T3-038).
• Decide when both: An announcement that is also a celebration: T3-026 while the work stands during placement, T3-009 when the finished work is celebrated.
• Against T3-082: Is the room's own work announced (T3-026), or a mark found that the room did not know of (T3-082)?
• Against T3-009: Is the mark announced as being up (T3-026), or the finished work celebrated (T3-009)?
• Against T3-038: Is the mark's progress reported (T3-038), or its presence announced (T3-026)?
• Against T3-065: Is the room's mark announced as up (T3-026), or is the work a flag of the land the room is named for or speaks for, announced, called for or built (T3-065)? A flag built in a room named for a land is that land's flag unless its concepts name another.
• Varies: From a one-line post to a weekly roundup that names the mark.
• Is not: A member finding that someone made the sub's logo without the room (T3-082).
• Exemplars: "We got on /r/place!" (genderfluid c0007); "We made it onto r/place" (calgaryflames c0110); "GNU/Linux on /r/place" (linux c0031)

T3-038 building and reporting the mark

Members build the mark and report its progress: started, half done, almost there, the next part. Floor: greenlattice and hyperlightdrifter, unlike in size (greenlattice holds 5,244 items in the window and hyperlightdrifter 170, over twice as many).

• Must show: Placing the mark and reports of its state: started, coordinates of the work in progress, half done, almost finished, the parts done and left.
• Must not show: Calls for hands (T3-002); the design argued (T3-004); the finished work celebrated (T3-009); repair after an attack (T3-021).
• Decide when both: Building with repairs: the larger part primary and the other under rule 0. When a theme holds two or more of these acts (an idea of what to make offered to the room, T3-033; hands called to place, T3-002; the work placed and its progress reported, T3-038), count the concepts of each: the act with the most concepts of its own is primary, and another is added under rule 0 only with concepts of its own. The opening post does not lead because it comes first. On a tie, T3-038 when the work was placed; else T3-002 when the mark was already chosen, T3-033 when it was not.
• Against T3-002: Count the concepts of each: is the larger share the work placed and its progress reported (T3-038), or hands called for it (T3-002)? An opening call does not lead because it comes first.
• Against T3-021: Is the mark built for the first time (T3-038), or restored after damage (T3-021)?
• Against T3-009: Is the work under way (T3-038), or finished and celebrated (T3-009)?
• Against T3-003: Is the room's mark reported (T3-038), or one member's own share (T3-003)?
• Against T3-073: Is the first build's progress reported (T3-038), or what happened to the work once it stood (T3-073)?
• Against T3-026: Is the mark's progress reported (T3-038), or its presence announced (T3-026)?
• Against T3-004: Is the mark being placed and its progress reported (T3-038), or its look argued and corrected against the plan (T3-004)?
• Against T3-033: Count the concepts of each: is the larger share an idea of what to make offered to the room (T3-033), or the mark placed and its progress reported (T3-038)? A proposal does not lead because it comes first.
• Against T3-070: Is the mark being placed and its progress reported, coordinates given as where the work in progress stands (T3-038), or are directions posted for placers to follow, coordinates, templates, guides or colour plans (T3-070)? A link that only shows where the finished work is points to it (T3-026), not a direction.
• Varies: From a start at given coordinates to running reports until the close.
• Is not: Restoring the mark after an attack (T3-021).
• Exemplars: "Making really good progress now. We are about half way done." (necrodancer c0014); "I've started to make one. Finished with the face and eyes in the vicinity of (886,563)" (hyperlightdrifter c0008); "WE ARE ALMOST THERE FELLOW GREENS!!!" (greenlattice c0109)

T3-041 extending the room's work

The room adds pieces to its work or enlarges it: a second picture, another album, a bigger logo, details around the first. Floor: masseffect and muse, unlike in size (masseffect holds 37,082 items in the window and muse 442, over twice as many).

• Must show: Proposals or work to add to the room's existing mark or to make another: a next piece, a bigger version, additions around the first.
• Must not show: The room's first mark proposed (T3-033); a member adding a personal piece to a shared mark (T3-060); spreading a faction's colour over others' work (T3-171).
• Decide when both: Additions argued as design: T3-004 when the existing mark's look is settled, T3-041 when a new piece or an enlargement is added.
• Against T3-033: Is the room's first mark proposed (T3-033), or more added beside or around it (T3-041)?
• Against T3-060: Does the room extend its own work (T3-041), or does a member add a personal piece to a shared mark (T3-060)?
• Against T3-042: Is growth pursued (T3-041), or set aside for upkeep (T3-042)?
• Against T3-004: Is the existing mark's look settled (T3-004), or a new piece or enlargement added (T3-041)?
• Against T3-061: Does the room grow into empty space or onto its own work (T3-041), or into a neighbour's space (T3-061)?
• Against T3-113: Is a further piece added to any work (T3-041), or a national emblem to the flag (T3-113)?
• Against T3-171: Is the room's work extended (T3-041), or a colour spread for its own sake (T3-171)?
• Varies: From a cake beside a logo to a run of album covers; enlarged letters; details added around a figure.
• Is not: The room's first proposal of a mark (T3-033).
• Exemplars: "Let's do College Dropout next on /r/place" (kanye c0147); "An idea to add the AI logo above the N7 logo" (masseffect c0182); "Just an update. The origin cover is next to it now :)" (muse c0078)

T3-042 choosing upkeep over expansion

The room puts keeping what it holds before growing: maintain, clean, defend first, no new fronts. Floor: greenlattice and armok, unlike in size (greenlattice holds 5,244 items in the window and armok 74, over twice as many).

• Must show: Upkeep chosen over growth: calls to maintain, clean or defend before expanding; refusals of new projects or attacks because the room cannot hold more; designs scaled to what can be defended.
• Must not show: Concentrating effort on fewer of the room's pieces (T3-069); repairs as such (T3-021); reining in the room's own attacks (T3-076).
• Decide when both: Choosing among the room's own pieces is T3-069; choosing holding over growing is T3-042.
• Against T3-069: Is one of the room's pieces dropped for another (T3-069), or growth set aside to keep what it holds (T3-042)?
• Against T3-041: Is growth pursued (T3-041), or set aside (T3-042)?
• Against T3-021: Is the work repaired (T3-021), or upkeep argued as the room's priority over growth (T3-042)?
• Against T3-076: Is the room's own attack on others stopped (T3-076), or upkeep put before expansion (T3-042)?
• Against T3-055: Is the mark reshaped to resist tampering (T3-055), or expansion dropped for upkeep (T3-042)?
• Varies: From a refusal to anger another sub to a faction's 'clean first' against its expansionists.
• Is not: Dropping one of the room's pieces to save pixels for another (T3-069).
• Exemplars: "To all you expansionists: CLEAN FIRST!" (greenlattice c0257, rivals c0530); "I'm focused on maintaining the current pattern for now" (armok c0035); "focus on keeping our small loli sign together before we decide to make any big plans." (loliconsunite c0051)

T3-060 adding a personal piece

Members add their own piece to a mark many share: a word, a heart, a drug's name, a character. Floor: drugs and TransFlagPlace, unlike in size (drugs holds 14,139 items in the window and TransFlagPlace 1,922, over twice as many).

• Must show: A member or a small group adding their own part to a shared mark: their word, symbol or character placed into a common work.
• Must not show: The room extending its own work (T3-041); a lone tribute apart from any shared mark (T3-092); converting a neighbour's art (T3-068).
• Decide when both: A personal addition the room then adopts: T3-060 for the adding, T3-041 when the room takes it up as its own extension.
• Against T3-041: Does the room extend its work (T3-041), or does a member add a personal piece to a shared mark (T3-060)?
• Against T3-092: Is the piece added to a shared mark (T3-060), or made alone apart from one (T3-092)?
• Against T3-056: Is a joint mark of kindred rooms made (T3-056), or a personal piece added inside it (T3-060)?
• Against T3-068: Does a member add their own piece to a mark many share (T3-060), or turn another room's art into the room's sign (T3-068)?
• Varies: From one drug's name in a molecule area to words and hearts added to a shared flag.
• Is not: A member making a tribute alone, away from any shared mark (T3-092).
• Exemplars: "I got the THC under DMT, working on PSILOCYBIN on top of the MDMA now." (shrooms c0017); "Help write "TRANS" above the flag" (TransFlagPlace c0211, rivals c0248); "TWEAKERS OF R/DRUGS, LETS CHANGE MDMA TO SAY METH BECAUSE WHY THE FUCK NOT" (drugs c0165)

T3-069 concentrating effort on fewer pieces

The room drops or pauses some of its pieces to put its pixels on one: one priority, one attack point, the rest abandoned. Floor: theblackvoid and day9, unlike in size (theblackvoid holds 9,430 items in the window and day9 361, over twice as many).

• Must show: Effort concentrated: one piece named the priority, others abandoned or paused, 'all focus on this', a design scaled down to fit the hands.
• Must not show: Upkeep chosen over growth with no piece dropped (T3-042); the room's strength doubted (T3-136); placers held to one template (T3-091).
• Decide when both: Concentrating and doubting in one theme: T3-069 when the room acts on the choice, T3-136 when it doubts.
• Against T3-042: Is one of the room's pieces dropped for another (T3-069), or growth set aside to keep what it holds (T3-042)?
• Against T3-136: Does the room put its pixels on fewer pieces (T3-069), or doubt it can manage any (T3-136)?
• Against T3-091: Are the room's pieces narrowed to fewer (T3-069), or placers held to one design of one piece (T3-091)?
• Varies: From abandoning a television to save a face to a faction's single attack point; pieces scaled down to the hands at hand.
• Is not: Refusing a new front to keep the existing mark (T3-042).
• Exemplars: "Should we abandon the TV? Just allow the Day [9] to survive?" (day9 c0021); "New Attack Point - ALL FOCUS ON THIS" (theblackvoid c0650); "The priority will always be BM and Sakura Gakuin." (babymetal c0242)

T3-082 finding the room's mark placed

Members find a mark of their room already on the canvas, made by others or without them, and point to it. Floor: globaloffensive and Madeon, unlike in size (globaloffensive holds 34,561 items in the window and Madeon 106, over twice as many).

• Must show: Members discovering the room's subject already drawn on the canvas: 'someone made our flag', 'found a Northwestern N', 'there already is one', asking who made it.
• Must not show: Outsiders led to the sub by its mark (T3-044); the room announcing work it made (T3-026).
• Decide when both: Whose eyes find the mark: the room's own members finding work they did not know of go to T3-082; outsiders led to the sub go to T3-044.
• Against T3-044: Do the room's members find their own mark (T3-082), or are outsiders led to the sub by it (T3-044)?
• Against T3-026: Is a mark found that the room did not know of (T3-082), or the room's own work announced (T3-026)?
• Against T3-175: Is the room's own subject found drawn (T3-082), or another's sign adopted as the room's (T3-175)?
• Against T3-052: Is another picture remarked on (T3-052), or the room's own mark found already placed (T3-082)?
• Varies: From surprise at a logo someone made to members joining the work they found.
• Is not: A visitor finding the sub through its mark (T3-044).
• Exemplars: "Found a Northwestern N on Reddit's new April Fool's project" (Northwestern c0001); "Someone made a 1g on /r/place" (globaloffensive c0224); "Look who's made an appearance on r/Place..." (Madeon c0032)

T3-175 adopting a sign others began

The room adopts as its own a sign others began: a neighbour's character made a mascot, a stray symbol claimed. Floor: portugal and httyd, unlike in size (portugal holds 5,785 items in the window and httyd 84, over twice as many).

• Must show: A work begun by others taken up by the room as its own: a mascot adopted, a character given the room's nationality or creed, a stray symbol claimed.
• Must not show: Another's art converted by placing over it (T3-068); the room's own subject found drawn (T3-082).
• Decide when both: Adopting with a recolouring: T3-068 when the art is placed over, T3-175 when it is claimed with little or no change.
• Against T3-068: Is another's art recoloured into the room's (T3-068), or adopted with little or no change (T3-175)?
• Against T3-082: Is the room's own subject found drawn (T3-082), or another's sign taken up as the room's (T3-175)?
• Against T3-071: Is the room's work adopted by a neighbour (T3-071), or another's sign adopted by the room (T3-175)?
• Against T3-137: Does the room take another's sign as its own (T3-175), or put its pixels into another group's build (T3-137)?
• Varies: From Squirtle made a Portuguese hero to a party parrot declared a comrade.
• Is not: Painting the room's flag over a neighbour's work (T3-068).
• Exemplars: "Squirtle Camões a mascote oficial do /r/portugal!" (portugal c0312); "Si Portugal tiene adoptó a Squirtle como su mascota, deberíamos adoptar al yoshi" (mexico c0118); "COMRADE PARTY PARROT DOING HIS PART IN BASHING THE FASH" (fullcommunism c0106, rivals c0141)

T3-187 handing the work over

A member who led the work hands it to the community: maintainership passed on, the project kept community-run, a leader stepping down. Floor: SquareSpiral and haskell, unlike in size (SquareSpiral holds 1,365 items in the window and haskell 635, over twice as many).

• Must show: A leader or organiser passing the work's care to the community, keeping it community-run, or stepping down from it.
• Must not show: A member quitting under strain (T3-181); one member put in charge (T3-101).
• Decide when both: A leader stepping down tired: T3-181 when strain is the reason, T3-187 when the work is passed on.
• Against T3-101: Is one member put in charge (T3-101), or does the leader hand the work to all (T3-187)?
• Against T3-181: Does a member quit under strain (T3-181), or pass the work on (T3-187)?
• Varies: From open-source maintainership passed to the community before a flight to a moderator retiring after a last tile.
• Is not: A member quitting because the work became stressful (T3-181).
• Exemplars: "I'm passing on this open source maintainership of these pixels to you the community." (haskell c0023); "though I like the idea of this being a community run thing with you guys." (splatoon c0087); "I'm retiring as mod and I've placed my last tile." (SquareSpiral c0113)

G09 defending and repairing the work

T3-005 defending the work against attackers

Members rally to defend the room's work against an attack under way: alarms, calls to fight back and hold, reports of attacks staved off. Floor: naruto and gatech, unlike in size (naruto holds 3,975 items in the window and gatech 919, over twice as many).

• Must show: An attack on the room's work and the room's answer: alarms, calls to defend or fight back, holding the line, reports of an attack repelled.
• Must not show: Watching for damage and repairing it, with or without an attacker in view, where no fight is called (T3-021); naming or tracing the attacker (T3-087); pleading with the attackers (T3-139); attacking others' work (G12).
• Decide when both: Defence and repair: T3-005 when the attack and the fight lead, T3-021 when the watching and fixing do; tracing who attacked in concepts of its own adds T3-087.
• Against T3-021: Is an attack fought (T3-005), or the work watched and fixed with or without an attacker in view (T3-021)?
• Against T3-087: Is the attack fought (T3-005), or its source traced (T3-087)?
• Against T3-139: Do members fight the attack (T3-005), or ask the attackers to stop (T3-139)?
• Against T3-006: Is the room's own work defended (T3-005), or another's work attacked (T3-006)?
• Against T3-081: Is the defence told as a fight (T3-005), or cast as a historic national war (T3-081)?
• Against T3-011: Is the room's own work defended (T3-005), or another room's work helped or defended by the room's members, a pledge to protect it included (T3-011)?
• Against T3-002: Is the call to build or finish (T3-002), or to defend against an attack under way (T3-005)?
• Against T3-055: Are attackers fought off (T3-005), or the mark's shape changed against them (T3-055)?
• Against T3-123: Is an attack fought off (T3-005), or a request to yield refused (T3-123)?
• Against T3-124: Is the attack fought off (T3-005), or is fighting one option weighed against another (T3-124)?
• Against T3-141: Is an attack fought off (T3-005), or the night covered (T3-141)?
• Against T3-195: Is an agreement already made invoked, spread or said to be broken (T3-195), or the room's own work defended, the pledge named only as the reason for the defence (T3-005)?
• Varies: From one alarm to day-long defence against bots, raids and the Void; defenders outnumbered or victorious.
• Is not: Cleaning stray pixels from the room's work with no attacker named (T3-021).
• Exemplars: "We are under attack by Virginia Tech. Stay strong!" (gatech c0007); "People are trying to kill our 4136121025 on Place. Let's get back to Place and fight them!" (homestuck c0105); "r/Naruto is under attack in r/Place! This is not a drill!" (naruto c0134)

T3-007 urging repair over retaliation

Rare tier. After an attack, members urge the room to repair its work rather than strike back.

• Must show: A call to answer damage by repairing instead of retaliating against the attacker.
• Must not show: Repairing with no word on retaliation (T3-021); stopping an attack the room itself started (T3-076).
• Decide when both: A theme that fights and then urges repair: T3-005 primary when the fight leads, T3-007 added when the call against retaliation has a concept of its own.
• Against T3-021: Is the work simply repaired (T3-021), or repair urged instead of striking back (T3-007)?
• Against T3-076: Is an attack the room started stopped (T3-076), or retaliation for damage it suffered declined (T3-007)?
• Varies: From one call to repair and coexist again to a member saying striking back is not the way.
• Is not: Telling members to stop an attack the room began unprovoked (T3-076).
• Exemplars: "Let's focus on repairing it on not attack what they've built." (sixers c0054); "striking back's not a good way to go." (parahumans c0007)

T3-008 messaging individual placers to stop

Members contact individual placers who damage the work, by private message or by name, and ask them to stop or tell them the plan. Floor: formula1 and necrodancer, unlike in size (formula1 holds 9,642 items in the window and necrodancer 321, over twice as many).

• Must show: Individual placers singled out and contacted: private messages to those placing wrong pixels, users named, a placer checked through their posting history and asked to stop.
• Must not show: Pleading with an attacking room as a whole (T3-139); tracing who changed the pixels with no contact (T3-087); banning the room's own vandals (T3-121).
• Decide when both: Tracing a placer and then messaging them: T3-087 when the tracing leads, T3-008 when the contact does.
• Against T3-139: Is a room asked to stop (T3-139), or individual placers contacted (T3-008)?
• Against T3-087: Is the placer only traced (T3-087), or contacted and asked to stop (T3-008)?
• Against T3-121: Is the placer asked (T3-008), or banned (T3-121)?
• Varies: From friendly private messages explaining the plan to naming repeat defacers in the thread.
• Is not: A post asking a whole room to stop its attack (T3-139).
• Exemplars: "PMing the users doing that." (formula1 c0131); "I've been repairing the art and PM-ing users that place grey pixels on top of the art letting them know what the plan is." (necrodancer c0083); "I've been sending every new one I see this and 95% of them have been stopping" (sixers c0056)

T3-021 watching and repairing the work

Members keep watch over the room's work and repair it: fixing changed and stray pixels, cleaning, keeping it intact over hours. Floor: newzealand and luxembourg, unlike in size (newzealand holds 8,226 items in the window and luxembourg 60, over twice as many).

• Must show: Upkeep of the work: watching it, fixing changed pixels, cleaning stray ones, routines of repair, reports of damage to be fixed. Repair during a raid counts here when the fixing leads and no fight is called.
• Must not show: An attack fought as such (T3-005); the mark reshaped against tampering (T3-055); watch through the night arranged as shifts (T3-141); a script that repairs (T3-028).
• Decide when both: Fight and upkeep: see T3-005. Upkeep with night shifts: T3-021 primary, T3-141 added when the shifts have concepts of their own.
• Against T3-005: Is the work watched and fixed (T3-021), or an attack fought (T3-005)?
• Against T3-141: Is the work kept (T3-021), or kept through the hours others sleep, in shifts (T3-141)?
• Against T3-055: Is the mark restored as it was (T3-021), or changed in shape against tampering (T3-055)?
• Against T3-038: Is the work first built (T3-038), or kept and restored (T3-021)?
• Against T3-028: Is it kept by hand (T3-021), or by a script (T3-028)?
• Against T3-007: Is the work simply repaired (T3-021), or repair urged instead of striking back (T3-007)?
• Against T3-042: Is the work repaired (T3-021), or upkeep argued as the room's priority over growth (T3-042)?
• Against T3-073: Is what happened told (T3-073), or the work watched and repaired (T3-021)?
• Against T3-146: Is a hate symbol or slur covered (T3-146), or the work repaired of other damage, obscene drawings included (T3-021)?
• Varies: From a morning routine of cleaning a logo to hours of watching one small figure.
• Is not: Running a script that restores the work (T3-028).
• Exemplars: "My morning routine the last couple days: Wake up, check the news, clean up the Florida logo" (floridagators c0114); "Yes, I've had my eye on it for the last 2 hours or so" (luxembourg c0013); "But most importantly we must keep the kiwi, text and boarder clean" (newzealand c0229)

T3-022 relocating after losing the spot

After the work is erased or overrun, the room moves it: a new spot, a smaller version elsewhere, starting again. Floor: aceattorney and seolhyun, unlike in size (aceattorney holds 987 items in the window and seolhyun 41, over twice as many).

• Must show: The work moved or restarted elsewhere because it was destroyed, overpowered or crowded out: new coordinates after a loss, 'we've moved', 'we will have to find someplace else'.
• Must not show: The first choice of a spot (T3-020); weighing whether to move (T3-124); moving because a neighbour asked for the space (T3-039).
• Decide when both: Weighing and then moving: T3-124 for the weighing, T3-022 for the move; both with concepts of their own, rule 0.
• Against T3-020: Is a spot chosen in the first place (T3-020), or a new one found after a loss (T3-022)?
• Against T3-124: Is the move weighed (T3-124), or made (T3-022)?
• Against T3-039: Does the room move because its work was lost (T3-022), or because a neighbour asked for the space (T3-039)?
• Against T3-054: Does the work move to a new spot on the same canvas (T3-022), or to another canvas (T3-054)?
• Against T3-029: Is the lost work grieved (T3-029), or moved or restarted elsewhere (T3-022)?
• Varies: From one quick move after an erasure to a run of moves and shrinkings as the canvas fills.
• Is not: Moving aside when a neighbour asks for room (T3-039).
• Exemplars: "nah, we've moved, some assholes erased all of it" (donaldglover c0047, rivals c0032); "Phoenixs finger is destroyed we will have to find someplace else" (aceattorney c0025); "At this point, I believe it's in our best interest to find a different location." (seolhyun c0007)

T3-139 pleading with attackers to stop

Members ask the room or group damaging their work to stop or spare it: 'please don't destroy our logo'. Floor: ainbowroad and mcgill, unlike in size (ainbowroad holds 9,887 items in the window and mcgill 498, over twice as many).

• Must show: Requests addressed to an attacking room or group to stop, spare the work, or let it live.
• Must not show: Fighting the attack (T3-005); messaging individual placers (T3-008); asking a host room for space before any damage (T3-035).
• Decide when both: Pleading inside a border deal: T3-010 primary when the deal leads, T3-139 added when the pleading has concepts of its own.
• Against T3-005: Do members fight the attack (T3-005), or ask the attackers to stop (T3-139)?
• Against T3-008: Is a group or room asked (T3-139), or individual placers contacted (T3-008)?
• Against T3-035: Is space asked for (T3-035), or an attack asked to stop (T3-139)?
• Against T3-046: Is the fairness of covering others' work argued (T3-046), or the covering asked to stop (T3-139)?
• Against T3-076: Are the room's own attackers stopped (T3-076), or another room's attackers asked to stop (T3-139)?
• Against T3-010: Is a line or space settled between neighbours (T3-010), or another room's attackers asked to stop (T3-139)?
• Varies: From a polite request posted in the attacker's own thread to angry demands that a faction end its expansion.
• Is not: A request to a host for room before any damage (T3-035).
• Exemplars: "Please don't destroy our N7 and Garrus logo please!" (placestart c0326, rivals c0435 c0412); "Red chiken wld happily live in one of ur tentacles pls stop severing chaken in half" (mcgill c0047); "Please don't delete the Darth Plagueis text" (ainbowroad c0624, rivals c1147)

G10 finding who changed the work

T3-058 blaming attackers after the close

After the canvas closes, members blame the room that destroyed or attacked their work, and keep the grievance alive. Floor: survivor and uoft, unlike in size (survivor holds 10,576 items in the window and uoft 1,966, over twice as many).

• Must show: Blame laid after the close (hour 73 on) on a named room or group for damage to the work: accounts of who destroyed it, curses, grievances kept up.
• Must not show: Tracing an attacker while placement goes on (T3-087); blaming moderators or admins (T3-118); mourning with no blame (T3-029).
• Decide when both: Blame and mourning after the close: T3-029 when the loss leads, T3-058 when the blame does.
• Against T3-087: Is the culprit sought during placement (T3-087), or blamed after the close (T3-058)?
• Against T3-029: Is the lost work mourned (T3-029), or a room blamed for it (T3-058)?
• Against T3-118: Is an attacking room blamed (T3-058), or the moderators or admins (T3-118)?
• Against T3-050: Are taunts traded with a rival as sport (T3-050), or blame laid for a loss (T3-058)?
• Against T3-030: Is a rival blamed for a loss (T3-058), or an ally's conduct disputed (T3-030)?
• Against T3-073: Is what happened to the work told (T3-073), or a named room blamed for its loss after the close (T3-058)?
• Varies: From a curse on a nation's sub kept alive as a meme to careful accounts of who ruined what in the last hour.
• Is not: Members working out during placement who is changing their pixels (T3-087).
• Exemplars: "Fuck Thailand But hey at least we made it onto a piece of Internet history." (uoft c0182); "in the final hour of the canvas being open, r/Denmark destroyed our logo... RIP" (survivor c0320); "Fuck /r/Denmark" (frankocean c0210, rivals c0203)

T3-087 tracing who changed the work

Members work out who changed their work or who sent a call: checking placers, naming rooms, reading signs of bots or scripts. Floor: smite and AcePlace, unlike in size (smite holds 14,286 items in the window and AcePlace 601, over twice as many).

• Must show: Finding out who is altering the work or who is behind a call: asking who keeps changing it, checking placers' posting histories, naming the room or bot responsible, members saying the damage is not the room's own.
• Must not show: Fighting the attack (T3-005); blame laid after the close (T3-058); an organised room setting its plan apart from placers it does not control (T3-188).
• Decide when both: Tracing with defence: T3-005 primary when the fight leads, T3-087 added when the tracing has concepts of its own. Members doubting that a damage was the room's own are tracing it (T3-087); an organised room telling others its plan does not cover such placers is T3-188.
• Against T3-005: Is the attack fought (T3-005), or its source traced (T3-087)?
• Against T3-058: Is the culprit sought during placement (T3-087), or blamed after the close (T3-058)?
• Against T3-188: Do members work out who did it (T3-087), or does an organised room tell others that such placers are not under its control (T3-188)?
• Against T3-170: Is the culprit sought (T3-087), or found to be a friend or one's own mistake (T3-170)?
• Against T3-132: Is the source traced from the pixels and what others say (T3-087), or learned from inside a rival's chat (T3-132)?
• Against T3-121: Do members find out or name who is damaging the work (T3-087), or exclude a member who did, by a ban, a kick or a call to moderators to throw them out (T3-121)?
• Against T3-008: Is the placer only traced (T3-087), or contacted and asked to stop (T3-008)?
• Against T3-045: Is who altered the work traced (T3-087), or who was at the spot first argued (T3-045)?
• Varies: From 'who keeps putting green in our logo?' to reading usernames and posting histories; bots and scripts suspected; who sent a call traced.
• Is not: An organised room telling a neighbour that placers in its name are not under its control (T3-188).
• Exemplars: "anyone know who keeps fucking with the letters?" (AcePlace c0053); "clicked on the user who put it on there.. and they have been posting on the smite reddit alot.." (smite c0370); "jeeze finland has a huge amount of space who keeps fucking putting green in our shit???" (chibears c0086)

T3-118 blaming moderators for a loss

Members blame the sub's moderators, or the site's admins, for a loss: their prank, their removals, help they denied, a rigged game. Floor: prequelmemes and anarcho_capitalism, unlike in size (prequelmemes holds 11,884 items in the window and anarcho_capitalism 2,937, over twice as many).

• Must show: Blame for the room's loss or failure laid on moderators or admins: their April Fools change, their removals, denied requests for help, the canvas said to be rigged.
• Must not show: Blame laid on an attacking room (T3-058); objections to a removal with no loss in view (T3-063, T3-185).
• Decide when both: A loss blamed on both a room and the moderators: the target with more concepts decides.
• Against T3-058: Is an attacking room blamed (T3-058), or the moderators or admins (T3-118)?
• Against T3-063: Is a removal contested (T3-063), or a loss laid at the moderators' door (T3-118)?
• Against T3-032: Is the moderators' joke objected to as a joke (T3-032), or blamed for a loss (T3-118)?
• Against T3-185: Are moderators or admins blamed for a loss (T3-118), or a change to the sub's posting rules made and argued with no loss in view (T3-185)?
• Varies: From a joke that a defeat will be the moderators' fault to suspicions that admins added touches to the canvas.
• Is not: Contesting a single removal under the sub's rules (T3-063).
• Exemplars: "If we lose it's the mods fault" (chelseafc c0048, rivals c0088 c0081); "When /r/prequelmemes mods pretend to be protectors of the /r/place Tragedy text after denying multiple requests for aid" (prequelmemes c0508); "I almost wonder if the admins helped some things or added in their final touches." (anarcho_capitalism c0165)

T3-121 excluding the room's own vandals

The room sanctions its own members who damage the work or the room by exclusion: bans from the chat or sub, kicking, shunning, calling them traitors. Floor: AmericanFlaginPlace and ufl, unlike in size (AmericanFlaginPlace holds 4,544 items in the window and ufl 290, over twice as many).

• Must show: Exclusion used as a sanction against the room's own members: bans from the Discord or the sub, kicking, shunning a 'traitor', members reported so moderators throw them out, such a ban challenged or reversed.
• Must not show: Messaging placers to stop (T3-008); posts removed under the sub's rules (T3-063); bigotry shut down in chat (T3-182).
• Decide when both: A ban for bigoted talk: T3-182 when the bigotry leads, T3-121 when the exclusion does.
• Against T3-008: Is the placer asked to stop (T3-008), or excluded (T3-121)?
• Against T3-063: Is a post removed under the sub's rules (T3-063), or a member excluded as a sanction (T3-121)?
• Against T3-182: Is bigotry in chat shut down (T3-182), or a member sanctioned by exclusion for damage to the work or the room (T3-121)?
• Against T3-076: Is the room's attack reined in by words (T3-076), or a member excluded (T3-121)?
• Against T3-087: Do members find out or name who is damaging the work (T3-087), or exclude a member who did, by a ban, a kick or a call to moderators to throw them out (T3-121)?
• Varies: From shunning a single traitor to a three-day cooling-off; a ban from the room's Discord challenged and reversed.
• Is not: A moderator removing a post that breaks the sub's rules (T3-063).
• Exemplars: "that guy was banned from the server" (roosterteeth c0088); "SHUN THE NONBELIEVER" (ufl c0031, rivals c0030); "Use that report button so our mods can throw out the trolls spreading disinformation" (AmericanFlaginPlace c0502)

T3-126 disputing who speaks for rooms

Members dispute who may speak or decide for a room toward others: false claims to be its moderator or representative, denials of being one, outsiders told not to decide for its work, no one yet able to speak for the placers. Floor: crusaderkings and rainbowgrid, unlike in size (crusaderkings holds 3,660 items in the window and rainbowgrid 33, over twice as many).

• Must show: Contest or statement about who represents a room toward others: a claimed representative or moderator challenged; someone denying they speak for the room; outsiders told they cannot decide for the room's work; members saying no group yet exists to speak for the placers.
• Must not show: Disputes over the room's own chat's authority inside the room (T3-114); an organised room disowning placers it cannot control (T3-188).
• Decide when both: Separating the organised plan from placers it does not control is T3-188; who may speak for the room is T3-126.
• Against T3-114: Is the room's own chat's power inside the room disputed (T3-114), or who speaks for the room to others (T3-126)?
• Against T3-188: Is the right to speak for the room disputed (T3-126), or placers outside the plan disowned (T3-188)?
• Against T3-194: Does a member act as the room's envoy (T3-194), or is the right to do so disputed or denied (T3-126)?
• Against T3-101: Is someone put in charge of the work (T3-101), or is it disputed who speaks for the room outward (T3-126)?
• Against T3-094: Is it disputed who speaks for a room (T3-126), or who may approve a spot (T3-094)?
• Against T3-180: Is it disputed who speaks for the room (T3-126), or who belongs to the nation (T3-180)?
• Varies: From a false moderator claim exposed to a random member denying they are the official mediator; a room telling other Discords not to decide for its art; a pattern's repeaters with no one to speak for them.
• Is not: A room telling a neighbour that rogue placers act against its plan (T3-188).
• Exemplars: "w-wait man im just some random guy not the official mediator" (jerma985 c0030); "Please don't pretend like you can make decisions about the artwork that was started by us." (crusaderkings c0051); "i don't think there's coordination yet of the people doing the rainbow grid??? unless i missed it??? so there's no way yet to get people to lay off of repeating the exact same grid" (rainbowgrid c0003)

T3-170 mistaking friendly work for vandalism

Members find that what looked like vandalism was friendly work or their own mistake, and own or forgive it. Floor: smite and placesnek, unlike in size (smite holds 14,286 items in the window and placesnek 470, over twice as many).

• Must show: Damage that turns out friendly: an ally's or neighbour's work taken for vandalism and then recognised; members' own misclicks or misplaced pixels owned and forgiven; help that went wrong.
• Must not show: Tracing a hostile attacker (T3-087); apologising to a neighbour for damage the room did to their work (T3-040); damage done for fun (T3-192).
• Decide when both: Tracing that ends in finding a friend: T3-087 when the search leads, T3-170 when the recognition and the owning do.
• Against T3-087: Is the culprit sought (T3-087), or found to be a friend or one's own mistake (T3-170)?
• Against T3-040: Is the friendly mistake inside the room's own or allied work (T3-170), or damage the room did to a neighbour's work (T3-040)?
• Against T3-192: Was the damage a mistake (T3-170), or done for fun (T3-192)?
• Varies: From a community's lettering undone as vandalism and then recognised to a newcomer's accidental pixel apologised for.
• Is not: Apologising to a neighbouring room for covering its art (T3-040).
• Exemplars: "something I'd been undoing earlier as vandalism was actually a community attempt to write "SNOOT BOOP"" (placesnek c0104); "We thought you were making a cross and tried to complete it!" (crusaderkings c0016); "I accidently did it im sorry D: I really did not mean to do it" (smite c0375)

T3-188 disowning placers outside the plan

An organised room tells others that placers acting in its name or against its plan are not under its control: rogues, the hivemind, individuals outside its chat. Floor: ainbowroad and gatech, unlike in size (ainbowroad holds 9,887 items in the window and gatech 919, over twice as many).

• Must show: A room, or its organisers, setting its plan apart from placers it does not control: 'we are not for that person', 'there are rogues outside our Discord', 'the hivemind works in mysterious ways', offers to repair what the rogues did.
• Must not show: A room saying it has no plan at all (T3-125); moderators disowning the canvas work as a whole (T3-140); members of a room doubting a damage was theirs, or a bare denial pointing at another room (T3-087).
• Decide when both: An outside room's denial counts when it separates its organised members from placers acting in its name (a fandom room's Danish members, a crusader room's Norwegian ally); a bare 'it was not us' that points to another room is tracing (T3-087). Separating the plan from such placers is T3-188; who may speak for the room is T3-126.
• Against T3-087: Does an organised room say the placers are not under its control (T3-188), or do members work out who did it, the room's own members doubting it was theirs included (T3-087)?
• Against T3-125: Does the room set its plan apart from placers outside it (T3-188), or say it has no plan (T3-125)?
• Against T3-126: Are placers outside the plan disowned (T3-188), or is the right to speak for the room disputed (T3-126)?
• Against T3-076: Does the room rein in its own attackers (T3-076), or say the placers are not its own (T3-188)?
• Against T3-140: Do moderators say the sub has no canvas project at all (T3-140), or does the room set its project apart from rogues (T3-188)?
• Against T3-195: Does an organised room say it does not control placers acting in its name (T3-188), or hold another room to an agreement (T3-195)?
• Against T3-049: Is the plan itself scattered (T3-049), or are placers acting against a plan set apart from the room (T3-188)?
• Varies: From one disowned rogue in a chat to national rooms saying their plans do not control every placer of their nation; offers to repair the rogues' damage.
• Is not: A room that says it has no plan and wings it (T3-125).
• Exemplars: "We are not for that person in the discord. We completely disagree with them entirely." (ainbowroad c0042, rivals c0386 c0593); "We are trying avoiding cutting through you guys, but there are some rogues outside our discord" (gatech c0077, rivals c0072); "There will always be some rogue kids ruining stuff. Just make sure to rebuild it." (denmark c0198, rivals c0285)

T3-192 griefing the work for fun

Members grief a work for fun, the room's own or another's, and own it or joke about it. Floor: pcmasterrace and paladins, unlike in size (pcmasterrace holds 40,459 items in the window and paladins 5,823, over twice as many).

• Must show: Damage done for amusement: letters or numbers changed into jokes, a dot kept in a logo to annoy defenders, griefing to watch others react; admissions and jokes about doing it, the room's own work included.
• Must not show: Attacks made for the room's ends (T3-006, T3-061); mistakes owned (T3-170).
• Decide when both: A joke defacement called for as the room's attack on a rival: T3-006; done by a member for amusement: T3-192.
• Against T3-006: Is a rival's work defaced for the room (T3-006), or any work, the room's own included, griefed for fun (T3-192)?
• Against T3-170: Was the damage a mistake (T3-170), or done for fun (T3-192)?
• Against T3-031: Is the joke played by damaging the work (T3-192), or told in talk (T3-031)?
• Against T3-177: Is the griefing for fun with no hate symbol (T3-192), or a swastika called for (T3-177)?
• Against T3-061: Is a work griefed for fun and owned as a joke (T3-192), or the room's work pushed into a neighbour's space for its own ends (T3-061)?
• Varies: From turning 60 into 69 on the room's own logo to griefing a rival's logo to hear its fans complain.
• Is not: A member admitting a misclick (T3-170).
• Exemplars: "Really sad how people take this so srsly, im griefing it a lot just to enjoy hearing the kiddos cry" (paladins c0215, rivals c0209); "I'm working on restoring the 60 fps. But i changed it to 69. because i have the mind of a 12 year old." (pcmasterrace c0889); "I'll admit it, I changed it to that a few times." (prequelmemes c0684)

G11 scripts, bots and extra accounts

T3-027 arguing whether scripts are fair

Members argue whether scripts and bots are fair: cheating or common practice, against the spirit of the canvas or the only way to hold ground. Floor: globaloffensive and Thegreatblackhole, unlike in size (globaloffensive holds 34,561 items in the window and Thegreatblackhole 187, over twice as many).

• Must show: Argument about scripts or bots as such: called cheating, embarrassing or beneath the room; defended as what every large community does; judged to spoil the canvas; bot rumours, and claims that a defence was scripts and not people.
• Must not show: Running or sharing a script with no argument over its fairness (T3-028); placing beyond the limit with extra accounts (T3-088).
• Decide when both: Running and arguing: T3-028 primary when the scripts are run, T3-027 added when the argument has concepts of its own. A bot rumour, or saying a defence was scripts rather than people, goes here when fairness is in question.
• Against T3-028: Are scripts run (T3-028), or is their fairness argued (T3-027)?
• Against T3-088: Are extra accounts used (T3-088), or the fairness of automation argued (T3-027)?
• Against T3-179: Is the fairness of scripts argued (T3-027), or a political ideology argued from the canvas (T3-179)?
• Against T3-037: Is the canvas's worth argued (T3-037), or the fairness of its scripts (T3-027)?
• Varies: From one jab at a rival's cheating to long threads on whether automation is moral; pride in hand work; rumours that a rival is botting.
• Is not: A member sharing a script and how to run it (T3-028).
• Exemplars: "Isn't it more embarrassing that you're cheating with scripts?" (unitedkingdom c0264); "what's unfair about it? every community that has big portions of the board uses a script" (globaloffensive c0824); "Our community must remain independent of bot trash. Those tactics are beneath us." (Thegreatblackhole c0078)

T3-028 running scripts for the work

Members write, share and run scripts or bots that place or keep the room's work. Floor: TheFarLeftSide and archlinux, unlike in size (TheFarLeftSide holds 3,737 items in the window and archlinux 976, over twice as many).

• Must show: Scripts or bots made, shared, installed or run for the room's work: links and instructions, the script repairing the mark, errors and updates.
• Must not show: Arguing whether scripts are fair (T3-027); extra accounts with no script (T3-088); stale scripts switched off (T3-089).
• Decide when both: Running and arguing: see T3-027. Stale scripts switched off in concepts of their own add T3-089; extra accounts add T3-088.
• Against T3-027: Are scripts run (T3-028), or is their fairness argued (T3-027)?
• Against T3-088: Is placing automated (T3-028), or multiplied by extra accounts (T3-088)?
• Against T3-089: Are scripts run for the plan (T3-028), or stopped because they fight it (T3-089)?
• Against T3-108: Is the bot the room's own (T3-028), or one target pooled with other rooms (T3-108)?
• Against T3-070: Is a template shared for placing by hand (T3-070), or a script that places (T3-028)?
• Against T3-021: Is it kept by hand (T3-021), or by a script (T3-028)?
• Against T3-120: Do members run the script on their own accounts (T3-028), or lend accounts for someone else's bot (T3-120)?
• Against T3-176: Is the script run for the room's own work (T3-028), or slipped to a rival against it (T3-176)?
• Varies: From one member offering a way to draw automatically to sub-wide bot armies with install guides; scripts that repair a mark overnight.
• Is not: A template posted for placing by hand (T3-070).
• Exemplars: "To use it, install TamperMonkey, load https://www.reddit.com/place?webview=true, and let the script do its work." (TheFarLeftSide c0506); "anyone wishing to join the bot army install the nodejs script" (archlinux c0157); "So I may or may not have a way to draw on /r/place automatically. Hit me up." (tagpro c0036)

T3-088 placing beyond the pixel limit

Members place more than the one-pixel limit allows: extra accounts, alts, throwaway accounts, glitches used to place more. Floor: bitcoin and uofm, unlike in size (bitcoin holds 11,315 items in the window and uofm 729, over twice as many).

• Must show: Placing beyond the limit by any means: alts and throwaway accounts made or used, many accounts per member, glitches exploited to place more.
• Must not show: Scripts as such (T3-028) unless they run on extra accounts; coping with the limit while building (T3-074); accounts lent to another's bot (T3-120).
• Decide when both: A script run on extra accounts: T3-028 for the script, T3-088 added when the accounts have concepts of their own. Glitches: using one to place beyond the limit is T3-088, coping with one that stops or delays placing is T3-074, explaining one is T3-016.
• Against T3-028: Is placing automated (T3-028), or multiplied by extra accounts or a glitch (T3-088)?
• Against T3-074: Is the limit worked within (T3-074), or broken (T3-088)?
• Against T3-120: Does a member place more with their own accounts (T3-088), or lend them to another's bot (T3-120)?
• Against T3-110: Are extra placements made (T3-088), or a tile offered as payment (T3-110)?
• Against T3-027: Are extra accounts used (T3-088), or the fairness of automation argued (T3-027)?
• Varies: From a reminder that alt accounts work too to plans for multi-account scripts; members insisting the work is manual despite many accounts.
• Is not: Working within the cooldown while building (T3-074).
• Exemplars: "Reminder that alt accounts work too." (bitcoin c0149); "I made two more reddit accounts to assist in protecting" (uofm c0008); "Lol spent better part of 2 hours and 3 accounts on this. XD" (zootopia c0100)

T3-089 switching off stale scripts

Members find the room's own scripts fighting its plan (old versions, wrong templates) and switch them off or update them. Floor: bitcoin and evex, unlike in size (bitcoin holds 11,315 items in the window and evex 120, over twice as many).

• Must show: The room's scripts or bots working against its own current plan: old versions overwriting, bots fighting each other or a neighbour's agreed space, calls to stop or update them.
• Must not show: Running scripts with no conflict (T3-028); a script edited to spare a neighbour as an agreed change (T3-168).
• Decide when both: Running and switching off in one theme: T3-028 primary, T3-089 added when the switching off has concepts of its own.
• Against T3-028: Are scripts run for the plan (T3-028), or stopped because they fight it (T3-089)?
• Against T3-168: Is a script stopped because it fights the room's own plan (T3-089), or edited to spare a neighbour (T3-168)?
• Against T3-091: Are hand placers held to the current plan (T3-091), or scripts brought into line with it (T3-089)?
• Varies: From one member stopping an old script that overwrote a flag to rooms finding their bots fighting each other after a template changed.
• Is not: A script revised to leave a neighbour's border alone (T3-168).
• Exemplars: "The old script writes over the american flag so I stopped it." (bitcoin c0481, rivals c0128); "Make sure to stop running the old script and update it" (evex c0083, rivals c0074); "Mja, borimo se proti lastnim botom in skriptam :D" (slovenia c0058)

T3-108 sharing one bot target

Rooms pool one bot map or target so that a shared script keeps several rooms' works. Floor: theitalyplace and aeon, unlike in size (theitalyplace holds 1,302 items in the window and aeon 27, over twice as many).

• Must show: A bot's target or map shared across rooms: other rooms' logos added to it, a target shared with another nation's room, scripts merged so another room can use them.
• Must not show: A room's own script (T3-028); members lending accounts to another room's bot (T3-120).
• Decide when both: A shared target agreed in a deal: T3-151 when the trade of help leads, T3-108 when the pooled target does.
• Against T3-028: Is the bot's target the room's alone (T3-028), or pooled with other rooms (T3-108)?
• Against T3-120: Do rooms share one target (T3-108), or do members lend their accounts to another's bot (T3-120)?
• Against T3-151: Is help traded between rooms (T3-151), or one bot target pooled (T3-108)?
• Varies: From kindred Linux rooms on one bitmap to Italy's script target shared with the English.
• Is not: A member lending their accounts to another room's bot (T3-120).
• Exemplars: "da adesso il target è condiviso con gli inglesi per una migliore difesa!" (theitalyplace c0155); "/r/place bot map for both tux and arch" (archlinux c0184, rivals c0187); "if someone wants to modify the script for the A&M flag then I'm happy to merge them together and get r/UTAustin using it" (aggies c0106)

T3-120 lending accounts to a bot

Members lend their accounts or machines to a bot, another room's or their own room's. Floor: rust and albania, unlike in size (rust holds 1,129 items in the window and albania 554, over twice as many).

• Must show: Accounts lent to a bot: members asked to run another's script or join a botnet, accounts handed over for someone else to run, manpower traded for a script.
• Must not show: Members running their own room's script on their own accounts (T3-028); a target shared among rooms (T3-108).
• Decide when both: Lending accounts in a trade between rooms: T3-151 when the trade leads, T3-120 added when the lending has concepts of its own.
• Against T3-028: Do members run the script on their own accounts (T3-028), or lend accounts for someone else's bot (T3-120)?
• Against T3-108: Do rooms share one target (T3-108), or do members lend accounts (T3-120)?
• Against T3-088: Does a member place more with their own accounts (T3-088), or lend them to a bot (T3-120)?
• Varies: From one member offering to set up lent accounts to a whole room trading its manpower for another's flag script.
• Is not: A room's members running its script on their own machines (T3-028).
• Exemplars: "DM Me if you want to lend any away (or just set them up running)" (gatech c0066); "Regardless, is there a way I can join the botnet?" (rust c0111); "Just run the script dude." (albania c0040, rivals c0039)

T3-168 editing scripts to spare neighbours

Members change the room's script so it spares a neighbour: a border left untouched, overlapping pixels removed, a shared image. Floor: rit and texastech, unlike in size (rit holds 565 items in the window and texastech 191, over twice as many).

• Must show: A script or bot edited, or asked to be edited, to leave a neighbour's work alone or keep an agreed border.
• Must not show: Turning off stale scripts that fight the room's own plan (T3-089); restraint kept by hand with no script (T3-024).
• Decide when both: A border agreed and written into the script: T3-010 for the agreement, T3-168 added when the script change has concepts of its own.
• Against T3-089: Is a script stopped because it fights the room's own plan (T3-089), or edited to spare a neighbour (T3-168)?
• Against T3-024: Is the restraint written into a script (T3-168), or kept by hand (T3-024)?
• Against T3-010: Is the border agreed (T3-010), or the script changed to keep it (T3-168)?
• Varies: From one pixel of a neighbour's border left alone to rooms checking that their scripts share one image.
• Is not: Stopping an outdated script that overwrites the room's own work (T3-089).
• Exemplars: "It leaves their 1 pixel black border" (metroid c0185); "edited the code so that your border is back to normal and we are shifted over" (texastech c0038); "Whoever set up the bots for the portal, can you make it a lighter shade of blue and remove the 2 pixels" (rit c0097)

T3-176 planting disguised scripts on rivals

Members plant a script on a rival that secretly works against it: the rival's own script modified to cover its logo, a psyop to sow distrust. Floor: completeanarchy and rit, unlike in size (completeanarchy holds 1,305 items in the window and rit 565, over twice as many).

• Must show: A script given or passed to a rival that harms it while seeming to help, and the telling of it.
• Must not show: Calls to deface a rival by hand (T3-006); running the room's own scripts (T3-028).
• Decide when both: A disguised script used in an attack the room called for: T3-006 for the call, T3-176 for the planted script.
• Against T3-006: Is the rival's work defaced by members placing (T3-006), or by a script planted on the rival (T3-176)?
• Against T3-028: Is the script run for the room's own work (T3-028), or slipped to a rival against it (T3-176)?
• Against T3-132: Is the rival watched from inside (T3-132), or harmed from inside by a script (T3-176)?
• Varies: From a rival's logo script modified to paint over it to a psyop that sowed distrust of all scripts.
• Is not: Calling members to cover a rival's logo by hand (T3-006).
• Exemplars: "I took WPI's script they are using for their logo and modified it to cover it with an orange rectangle." (rit c0081); "Then, later, when they got their own legit scripts, I told them about the psyop and sowed distrust of all scripts." (completeanarchy c0299, rivals c0298); "Haha, even a layman should have been able to see the pattern in that array of arrays." (utaustin c0176, rivals c0172)

G12 attacking others' work

T3-006 calling to deface rivals' work

Members call for, plan or carry out attacks that destroy, black out or erase another room's work. Floor: theblackvoid and UMiami, unlike in size (theblackvoid holds 9,430 items in the window and UMiami 1, over twice as many).

• Must show: Calls, plans or reports of attacks on another room's work meant to destroy or erase it: 'attack the Danish flag', 'wipe out Arizona', 'we must destroy the blue corner', strikes timed against a rival.
• Must not show: The room's work grown over a neighbour's space (T3-061); another's art turned into the room's own sign (T3-068); griefing for fun (T3-192); defending the room's work (T3-005).
• Decide when both: Replacing or attacking another room's mark, another nation's flag included: destroying or blacking it out is T3-006; turning it into the room's sign is T3-068; growing the room's work over the neighbour's space is T3-061. A theme with more than one: the larger part primary, the others under rule 0.
• Against T3-061: Is the rival's work destroyed (T3-006), or is its space taken for the room's own work (T3-061)?
• Against T3-068: Is the rival's work destroyed (T3-006), or turned into the room's own sign (T3-068)?
• Against T3-192: Is the attack called for the room (T3-006), or a member's griefing for fun (T3-192)?
• Against T3-005: Is another's work attacked (T3-006), or the room's own defended (T3-005)?
• Against T3-128: Is the call the room's own (T3-006), or a streamer's relayed (T3-128)?
• Against T3-076: Is an attack called for (T3-006), or reined in (T3-076)?
• Against T3-067: Is a rival attacked for the room (T3-006), or a third room's work bargained away to a neighbour (T3-067)?
• Against T3-085: Are flags attacked (T3-006), or weighed against the room's art (T3-085)?
• Against T3-086: Is a rival's work defaced (T3-006), or the community's own quarrel carried into the marks (T3-086)?
• Against T3-102: Is the attack called for by the room (T3-006), or pressed by a member against the room's word (T3-102)?
• Against T3-171: Is a rival's work destroyed (T3-006), or the faction's colour spread over whatever lies in its way (T3-171)?
• Against T3-176: Is the rival's work defaced by members placing (T3-006), or by a script planted on the rival (T3-176)?
• Against T3-177: Is a rival's work defaced (T3-006), or a swastika drawn (T3-177)?
• Against T3-178: Is a canvas work attacked (T3-006), or one person on another site (T3-178)?
• Varies: From one member's 'let's attack' to timed strikes with coordinates; rivalries of sport, nation, fandom and colour.
• Is not: Painting the room's colours or symbol into a neighbour's art (T3-068).
• Exemplars: "WIPE OUT ARIZONA ON r/place! B1G Only! Get Started Now!" (uofmn c0039); "Fellow erasers, we must destroy the blue corner!" (EraseThePlace c0038); "Lets attack the danish flag." (theblackvoid c1559, rivals c1721 c1009 c1177)

T3-061 pushing into a neighbour's space

The room grows its own work into space a neighbour holds: expanding over another flag or picture, taking a neighbour's ground. Floor: armenia and ChronoTrigger, unlike in size (armenia holds 1,333 items in the window and ChronoTrigger 363, over twice as many).

• Must show: The room's work extended over a neighbour's space, or proposals to take it: 'take over the Hungary flag', 'keep expanding west', 'wage war for space'.
• Must not show: Destroying a rival's work with no gain of space (T3-006); converting another's art into the room's own sign (T3-068); growing into empty canvas (T3-041).
• Decide when both: See T3-006.
• Against T3-006: Is the neighbour's space taken for the room's work (T3-061), or the neighbour's work destroyed (T3-006)?
• Against T3-068: Is the room's own work grown over the neighbour (T3-061), or the neighbour's art turned into the room's sign (T3-068)?
• Against T3-041: Does the room grow into empty space or onto its own work (T3-041), or into a neighbour's space (T3-061)?
• Against T3-010: Is the space taken (T3-061), or agreed (T3-010)?
• Against T3-171: Is a picture grown into a neighbour's space (T3-061), or a colour spread as the aim (T3-171)?
• Against T3-192: Is a work griefed for fun and owned as a joke (T3-192), or the room's work pushed into a neighbour's space for its own ends (T3-061)?
• Varies: From a proposal to fight for room beside a cloud to a nation's flag pushed across its neighbours' flags.
• Is not: Adding a second piece in empty canvas (T3-041).
• Exemplars: "we could wage war with that yellow thing next to the cloud for space for her" (ChronoTrigger c0092); "Lets take the mexican flag, now is our chance." (theitalyplace c0247); "I'm gonna keep expanding west im not giving up boys" (armenia c0028)

T3-067 trading away another room's work

Rare tier. In a deal with a neighbour, a room offers to remove a third room's work.

• Must show: A third room's work offered up in a bargain between two rooms: 'I'll help get rid of the frog if we can keep ...'.
• Must not show: Help bartered with no harm to a third room (T3-151); a rival attacked directly (T3-006).
• Decide when both: The bargain is T3-151 when no third party is harmed, T3-067 when one is offered up.
• Against T3-151: Is help traded between two rooms alone (T3-151), or a third room's work offered up in the trade (T3-067)?
• Against T3-006: Is a rival attacked for the room (T3-006), or a third room's work bargained away to a neighbour (T3-067)?
• Varies: One room's offer only.
• Is not: Trading help between two rooms with no third party harmed (T3-151).
• Exemplars: "Do you have peace agreements with the frog or do you want it gone? I'll help get rid of the frog" (thailand c0146)

T3-068 converting a neighbour's art

Members turn another room's art into the room's own sign: a logo changed into theirs, a flag recoloured into the room's flag, a symbol rewritten. Floor: gratefuldead and england, unlike in size (gratefuldead holds 916 items in the window and england 62, over twice as many).

• Must show: Another's mark altered into the room's own sign or joke: 'turn their symbol into ours', 'change Finland's flag into ours', a logo rewritten with the room's letters.
• Must not show: Destroying it (T3-006); taking its space for a separate work (T3-061); adopting it unchanged (T3-175).
• Decide when both: See T3-006. A national flag chosen as target for political reasons adds T3-130 when that choice has concepts of its own.
• Against T3-006: Is the other's art turned into the room's sign (T3-068), or destroyed (T3-006)?
• Against T3-061: Is the other's art converted (T3-068), or its space taken for the room's own work (T3-061)?
• Against T3-175: Is another's sign changed into the room's (T3-068), or adopted with little or no change (T3-175)?
• Against T3-130: Is the converting the doing (T3-068), or the national politics read into the choice of target (T3-130)?
• Against T3-071: Is the work taken in with consent (T3-071), or converted by placing over it (T3-068)?
• Against T3-060: Does a member add their own piece to a mark many share (T3-060), or turn another room's art into the room's sign (T3-068)?
• Varies: From a pokeball turned into a band's emblem to national flags recoloured into the room's flag.
• Is not: Adopting a neighbour's character as a mascot with no change (T3-175).
• Exemplars: "Should we change Finland's flag into ours?" (england c0021); "turning it into a dig logo rn" (TeamDignitas c0022); "we could turn this pokeball into a stealie?" (gratefuldead c0007)

T3-128 relaying a streamer's attack call

Rare tier. Members relay a streamer's call for the audience to attack another work, and join it.

• Must show: A streamer's call to attack passed on in the room: 'call to arms from Tyler1', a streamer named as leading an attack, members asked to join the streamer's army.
• Must not show: The room's own call to attack (T3-006).
• Decide when both: A streamer's call and the room's own in one theme: T3-128 when the streamer's call leads.
• Against T3-006: Is the call the room's own (T3-006), or a streamer's relayed (T3-128)?
• Against T3-062: Are hands sought for the room's work (T3-062), or for a streamer's attack (T3-128)?
• Varies: From a one-line call to arms to a streamer's army joined by allied factions.
• Is not: A room's own members calling an attack on a rival (T3-006).
• Exemplars: "Call To Arms from Tyler1" (ice_poseidon c0171, rivals c0147); "Destiny, talking about why he's telling everyone to destroy the sign on blue's corner." (destiny c0010); "A streamer named Destiny is leading an attack on the blue corner, join us in the battle!" (PurplePixels c0122)

T3-178 brigading one person off Reddit

Members propose or join harassing one person on another site: spamming an Instagram account, screwing with an actor on Twitter. Floor: dankmemes and startrek, unlike in size (dankmemes holds 51,339 items in the window and startrek 3,498, over twice as many).

• Must show: A named or pictured individual targeted on another site by members acting together.
• Must not show: Attacks on canvas works (T3-006); taunting a rival community (T3-050).
• Decide when both: A raid on a person within a taunting theme: T3-178 when the person is targeted on another site.
• Against T3-006: Is a canvas work attacked (T3-006), or one person on another site (T3-178)?
• Against T3-050: Is a rival community taunted (T3-050), or one person harassed (T3-178)?
• Varies: From a joke request to screw with an actor on Twitter to a planned spam raid on one Instagram user.
• Is not: Taunting a rival sub (T3-050).
• Exemplars: "Ok I propose that we take down one normie at a time after our april fools fiasco" (dankmemes c0491, rivals c0492 c0496); "yo can you help us screw with Garrett Wang for April Fools on twitter?" (startrek c0052)

G13 holding back from others' work

T3-024 refusing to cover others' work

Members keep the room's work off others' art: going around it, sparing it, sizing the work so it does not cover a neighbour. Floor: wholesomememes and placesnek, unlike in size (wholesomememes holds 6,915 items in the window and placesnek 470, over twice as many).

• Must show: Restraint toward others' work kept by the room's own choice: going around a neighbour's design, refusing to overwrite it, sizing or placing the work to spare it, respect for others' effort stated.
• Must not show: Moving because a neighbour asked (T3-039); reining in the room's members who are already attacking (T3-076); restraint written into a script (T3-168); an agreed border (T3-010).
• Decide when both: Restraint inside a border deal: T3-010 primary when the deal leads, T3-024 added when the restraint has concepts of its own. Sparing others' work by the room's own choice is T3-024; agreeing lines with a neighbour is T3-010.
• Against T3-010: Is a line or space agreed with a neighbour (T3-010), or others' work spared by the room's own choice (T3-024)?
• Against T3-039: Does the room yield when asked (T3-039), or keep off others' work unasked (T3-024)?
• Against T3-076: Is an attack under way stopped (T3-076), or others' work spared before any attack (T3-024)?
• Against T3-046: Is the fairness of covering argued (T3-046), or covering simply refused (T3-024)?
• Against T3-168: Is the restraint kept by hand (T3-024), or written into a script (T3-168)?
• Varies: From going around someone's chequered tiles to a room's rule of peace toward its neighbours' mascots.
• Is not: A room moving its work after a neighbour asks for the space (T3-039).
• Exemplars: "Going around someone's chequered tiles so not to spoil their design" (wholesomememes c0027); "Snek is happy to live in peace with anyone we can. We can curve around the corner of the AMD logo" (placesnek c0096); "Don't wanna destroy other people's work." (spacexmasterrace c0051)

T3-039 yielding space when asked

The room gives ground when a neighbour asks: moving, shifting or shrinking its work, giving a spot back. Floor: homestuck and paranatural, unlike in size (homestuck holds 2,518 items in the window and paranatural 58, over twice as many).

• Must show: A neighbour's request for space and the room yielding: moving the work over, shifting it, shrinking it, letting the neighbour take the spot back, forfeiting an attempt.
• Must not show: Refusing to yield (T3-123); moving after the work was lost to an attack (T3-022); restraint with no request (T3-024).
• Decide when both: Yielding inside a border deal: T3-010 primary when the deal leads, T3-039 added when the yielding has concepts of its own.
• Against T3-123: Does the room yield the space (T3-039), or refuse (T3-123)?
• Against T3-022: Does the room move because a neighbour asked (T3-039), or because its work was lost (T3-022)?
• Against T3-024: Does the room yield to a request (T3-039), or spare others' work unasked (T3-024)?
• Against T3-012: Does the room give up its own space (T3-039), or grant a neighbour room on its work (T3-012)?
• Against T3-010: Is a line or space settled between neighbours (T3-010), or the room's work moved, shrunk or given up because a neighbour asked (T3-039)?
• Varies: From a sign moved a few pixels left to a whole attempt forfeited to another room.
• Is not: Moving the work after an attack destroyed it (T3-022).
• Exemplars: "we should just move the libra/terezi sign to the left and let university of toronto take it back" (homestuck c0253); "we've successfully moved them from one-over-the-other to a side-by-side" (daftpunk c0045); "I forfeit my attempt at Totoro" (paranatural c0017)

T3-040 apologizing to neighbours for damage

Members apologise to a neighbouring room for damage the room or its members did to its work, often offering to help repair it. Floor: monsterhunter and TheHulk, unlike in size (monsterhunter holds 3,199 items in the window and TheHulk 114, over twice as many).

• Must show: An apology to another room for damage to its work by the room or people from it: 'sorry about that', apologies made in the other room's thread, offers to help redraw or rebuild.
• Must not show: Owning a mistake inside the room's own or an ally's work (T3-170); mourning art the room covered with no apology to its owners (T3-183).
• Decide when both: Apology inside a deal: T3-010 primary when the deal leads, T3-040 added when the apology has concepts of its own.
• Against T3-170: Is damage to a neighbour's work apologised for (T3-040), or a friendly mistake inside the room's own or allied work owned (T3-170)?
• Against T3-183: Is the apology made to the neighbour (T3-040), or the covered art mourned among members (T3-183)?
• Against T3-076: Is the damage apologised for (T3-040), or the attackers stopped (T3-076)?
• Against T3-047: Is damage to a neighbour's work apologised for (T3-040), or a quarrel between the subs closed (T3-047)?
• Against T3-119: Do the former attackers only apologise (T3-040), or help repair (T3-119)?
• Against T3-010: Is a line or space settled between neighbours (T3-010), or damage the room did to a neighbour's work apologised for (T3-040)?
• Varies: From a one-line 'I'm so sorry' to offers to redraw the character nearby; apologies made on behalf of a nation's members.
• Is not: A member admitting a misclick in the room's own work (T3-170).
• Exemplars: "Sorry about that, if you have the reference pixel art, some of us might be able to help you draw it nearby" (sakuragakuin c0047); "We're as sorry as Canadians that we forced you to relocate." (monsterhunter c0189); "I wanted to apologize, for what it's worth, for all of the asshole people from our subreddit that attacked you." (TheHulk c0109)

T3-046 arguing whether covering is fair

Members argue whether covering others' work is fair: an open canvas where anything goes, or a wrong done to others' effort. Floor: theblackvoid and placetardis, unlike in size (theblackvoid holds 9,430 items in the window and placetardis 227, over twice as many).

• Must show: Argument over covering others' work as such: 'it's an open canvas', 'that's the whole point', 'they put in passion, respect it', whether a neighbour may use the room's background.
• Must not show: Refusing to cover with no argument (T3-024); pleading to have one's own work spared (T3-139); arguing who had the spot first (T3-045).
• Decide when both: An argument that ends in restraint: T3-046 when the argument leads, T3-024 when the restraint does. Stopping the room's own attack is T3-076; arguing whether such covering is fair is T3-046.
• Against T3-024: Is covering refused (T3-024), or its fairness argued (T3-046)?
• Against T3-076: Is the room's attack stopped (T3-076), or the fairness of covering argued (T3-046)?
• Against T3-139: Does the speaker plead for their own work (T3-139), or argue whether covering is fair (T3-046)?
• Against T3-045: Is who came first argued (T3-045), or whether covering is fair at all (T3-046)?
• Varies: From a Void member calling erasure the point of the experiment to members weighing whether a neighbour may use their blank background.
• Is not: A member pleading that a rival spare their room's logo (T3-139).
• Exemplars: "Lol why did you think it was ruining it - the black void was central to the experiment." (theblackvoid c0801, rivals c1908); "C'è gente che c'ha messo dedizione, passione e creatività. Io questo lo rispetto" (italy c0162); "it seems silly to not let them go into our blank blue background." (placetardis c0028, rivals c0012)

T3-076 reining in the room's attackers

Members tell their own room's attackers to stop: no more attacks, leave the neighbours alone, stop vandalising. Floor: rocketleague and Temple, unlike in size (rocketleague holds 21,124 items in the window and Temple 246, over twice as many).

• Must show: The room's own members told to stop attacking or vandalising others' work, or an attack called off after an objection; rules against new wars.
• Must not show: Restraint before any attack (T3-024); pleading with another room's attackers (T3-139); excluding members as a sanction (T3-121); members acting against such a call (T3-102).
• Decide when both: An attack called for and then reined in: T3-006 primary when the attacking leads, T3-076 when the reining in does (rule 0 pairs them both ways).
• Against T3-024: Is an attack under way stopped (T3-076), or others' work spared before any attack (T3-024)?
• Against T3-139: Are the room's own attackers stopped (T3-076), or another room's attackers asked to stop (T3-139)?
• Against T3-102: Is the room's call to hold back made (T3-076), or defied (T3-102)?
• Against T3-188: Does the room rein in its own attackers (T3-076), or say the attackers are not its own (T3-188)?
• Against T3-046: Is the attack stopped (T3-076), or the fairness of covering argued (T3-046)?
• Against T3-195: Does the room stop its own attackers (T3-076), or hold another room to an agreement (T3-195)?
• Against T3-006: Is an attack called for (T3-006), or reined in (T3-076)?
• Against T3-007: Is an attack the room started stopped (T3-076), or retaliation for damage it suffered declined (T3-007)?
• Against T3-040: Is the damage apologised for (T3-040), or the attackers stopped (T3-076)?
• Against T3-042: Is the room's own attack on others stopped (T3-076), or upkeep put before expansion (T3-042)?
• Against T3-121: Is the room's attack reined in by words (T3-076), or a member excluded (T3-121)?
• Varies: From one 'stop messing with other schools' to moderators' rules against new wars; attacks withdrawn after an objection.
• Is not: A member asking another room's raiders to stop (T3-139).
• Exemplars: "No, stop messing with other schools" (Temple c0054); "Alot of people from this sub are vandalizing the art on place, this is getting annoying" (rocketleague c0365); "SEGERA HENTIKAN SERANGAN KE INTRODWARF" (indonesia c0130)

T3-102 defying the call for restraint

A member goes on attacking or breaks a treaty after the room told them to hold back. Floor: xcom and cavestory, unlike in size (xcom holds 1,535 items in the window and cavestory 397, over twice as many).

• Must show: A member refusing the room's restraint: attacking after being told no, calling to break the room's treaty, refusing to stop drawing over a neighbour.
• Must not show: The room's call to hold back itself (T3-076); attacks the room calls for (T3-006).
• Decide when both: A call to hold back and its defiance in one theme: the side with more concepts is primary, the other under rule 0.
• Against T3-076: Is the call to hold back made (T3-076), or defied (T3-102)?
• Against T3-006: Is the attack called for by the room (T3-006), or pressed by a member against the room's word (T3-102)?
• Against T3-195: Is a room held to its agreement (T3-195), or does a member break it (T3-102)?
• Varies: From 'Nah I'm going to hit the Bills' to a call to break a treaty.
• Is not: A room calling for an attack on a rival (T3-006).
• Exemplars: "Nah I'm going to hit the bills with green" (nyjets c0164); "we have to break the treaty now" (xcom c0113); "Never shall i stop drawing balrog." (cavestory c0053, rivals c0049)

T3-123 refusing to give up space

Members refuse to give up the room's space when a neighbour asks or presses: 'this is our space', 'we were here first', 'it stays'. Floor: uiuc and tinytardis, unlike in size (uiuc holds 1,862 items in the window and tinytardis 115, over twice as many).

• Must show: A refusal to move or yield ground to a neighbour: claims of first arrival, of a prior agreement or of work done; promises to defend the spot against the one asking.
• Must not show: Yielding (T3-039); arguing who had the spot first with no refusal (T3-045); fighting off an attack with no request to yield (T3-005).
• Decide when both: A refusal inside a border deal: T3-010 primary when the deal leads, T3-123 added when the refusal has concepts of its own.
• Against T3-039: Does the room yield the space (T3-039), or refuse (T3-123)?
• Against T3-045: Is who came first argued (T3-045), or is the space refused on any ground (T3-123)?
• Against T3-005: Is an attack fought off (T3-005), or a request to yield refused (T3-123)?
• Against T3-124: Is fighting set against moving (T3-124), or is moving refused outright (T3-123)?
• Against T3-059: Is giving up urged (T3-059), or refused (T3-123)?
• Against T3-010: Is a line or space settled between neighbours (T3-010), or a neighbour's demand for the room's space refused (T3-123)?
• Varies: From a polite 'we'd rather stay' to promises to defend the space against a named neighbour.
• Is not: A room moving after a neighbour asks (T3-039).
• Exemplars: "No, this is our space! We will defend it" (uiuc c0123, rivals c0114 c0126); "Yes- we mind. We've been working on protecting that TARDIS and the cube above it for quite a while." (tinytardis c0040); "Actually, we've fought hard for the area and had to negotiate with others when they were taking up part of our space." (qotsa c0029, rivals c0028)

T3-183 mourning art the room covered

Members mourn or regret art that their own room's work covered. Floor: AmericanFlaginPlace and armok, unlike in size (AmericanFlaginPlace holds 4,544 items in the window and armok 74, over twice as many).

• Must show: Grief or regret among members for another's art the room's own work displaced: 'RIP Blonde', a memorial post for a neighbour the room's expansion left no room for, members torn between the two works.
• Must not show: Apologising to the neighbour (T3-040); mourning the room's own lost work (T3-029).
• Decide when both: Mourning and apology together: T3-040 when the apology is addressed to the neighbour, T3-183 when the mourning stays among members.
• Against T3-029: Is the room's own lost work mourned (T3-029), or others' art the room covered (T3-183)?
• Against T3-040: Is the regret addressed to the neighbour as an apology (T3-040), or voiced among members (T3-183)?
• Varies: From a one-line 'RIP' to a member who worked on both the flag and the tree it covered.
• Is not: Members mourning their own room's erased logo (T3-029).
• Exemplars: "Sorry there wasn't room enough for both of us" (armok c0031); "RIP Blonde 😭" (kanye c0443); "PLEASE! I've worked on both the tree and the flag. Please. It's breaking my heart." (AmericanFlaginPlace c0117, rivals c0094)

G14 space and help between rooms

T3-010 settling borders with neighbours

Neighbouring rooms settle lines, overlaps, moves and spots between their works: borders drawn, a shift of a pixel or two, space shared. Floor: anarcho_capitalism and aromantic, unlike in size (anarcho_capitalism holds 2,937 items in the window and aromantic 44, over twice as many).

• Must show: A deal over lines and space between neighbouring works with no fight to end: borders agreed or asked for, shifts of a few pixels, overlaps accepted or refused, space shared.
• Must not show: A pact that ends or forestalls a fight (T3-149); an alliance for joint defence or a joint fight (T3-150); help traded (T3-151); an envoy's errand (T3-194); an agreement already made invoked (T3-195); restraint by the room's own choice (T3-024).
• Decide when both: A pact ending or forestalling a fight between rooms already in contact goes to T3-149; an agreement drawing borders or sharing space where no fight began goes to T3-010. A theme that holds several kinds of deal keeps the leading one as primary.
• Against T3-149: Does the deal end or forestall a fight between rooms in contact (T3-149), or settle lines and space where no fight began (T3-010)?
• Against T3-150: Do the rooms join for defence or a fight (T3-150), or settle where their works meet (T3-010)?
• Against T3-151: Is help given in return for help (T3-151), or a line or space settled (T3-010)?
• Against T3-194: Is a member acting as the room's envoy the doing (T3-194), or the line agreed (T3-010)?
• Against T3-195: Is a line settled now (T3-010), or an agreement already made invoked (T3-195)?
• Against T3-024: Is the line agreed with the neighbour (T3-010), or others' work spared by the room's own choice (T3-024)?
• Against T3-052: Is a neighbour remarked on (T3-052), or a border with it settled (T3-010)?
• Against T3-061: Is the space taken (T3-061), or agreed (T3-010)?
• Against T3-153: Is the theme the place of the talks (T3-153), or the border or space agreed (T3-010)?
• Against T3-168: Is the border agreed (T3-010), or the script changed to keep it (T3-168)?
• Against T3-012: Is a line or shared space agreed between the two rooms (T3-010), or a neighbour simply let onto the room's own work or area (T3-012)?
• Against T3-035: Is a line or space settled between neighbours (T3-010), or space or permission asked of the room that holds it (T3-035)?
• Against T3-039: Is a line or space settled between neighbours (T3-010), or the room's work moved, shrunk or given up because a neighbour asked (T3-039)?
• Against T3-040: Is a line or space settled between neighbours (T3-010), or damage the room did to a neighbour's work apologised for (T3-040)?
• Against T3-084: Is a line or space settled between neighbours (T3-010), or another room asked, as a group, to help with the work (T3-084)?
• Against T3-123: Is a line or space settled between neighbours (T3-010), or a neighbour's demand for the room's space refused (T3-123)?
• Against T3-139: Is a line or space settled between neighbours (T3-010), or another room's attackers asked to stop (T3-139)?
• Varies: From a request to shift a pixel or two to borders drawn with several neighbours at once; overlaps accepted with grumbling.
• Is not: A truce ending raids between two rooms (T3-149).
• Exemplars: "would it be possible to shift right like a pixel or two?" (Temple c0094); "All we're doing is pushing your border back 2 pixels to the left so we can keep our logo intact" (mindcrack c0074); "I don't mind the minecraft people making their shovel overlap the flag" (aromantic c0008)

T3-011 helping another room's work

Members send their pixels to another room's work: helping build, finish or defend it, with nothing asked in return. Floor: stardewvalley and drawhelix, unlike in size (stardewvalley holds 1,541 items in the window and drawhelix 99, over twice as many).

• Must show: The room's members helping another room's work, or called to: 'come help the farm at r/X', 'I'm helping r/Y', pixels sent to a neighbour's defence.
• Must not show: Help traded for help (T3-151); asking for help (T3-084); an alliance for joint defence (T3-150); joining another group's build as one's own (T3-137).
• Decide when both: Help given in return is T3-151; help given with nothing asked is T3-011.
• Against T3-151: Is help given in return for help (T3-151), or with nothing asked (T3-011)?
• Against T3-084: Is help asked for (T3-084), or sent (T3-011)?
• Against T3-150: Are the rooms allied for joint defence (T3-150), or is help sent to another's work (T3-011)?
• Against T3-137: Does the member help another's work while keeping the room's own (T3-011), or join another group's build as theirs (T3-137)?
• Against T3-005: Is the room's own work defended (T3-005), or another room's work helped or defended by the room's members, a pledge to protect it included (T3-011)?
• Against T3-056: Is help sent to another's own work (T3-011), or one mark made together (T3-056)?
• Against T3-062: Is help asked for (T3-062), or sent to another room's work (T3-011)?
• Against T3-078: Is help sent to any room's work (T3-011), or to a kin nation's flag as kin (T3-078)?
• Against T3-099: Is the bigger room sending help (T3-011), or the small room relying on it (T3-099)?
• Against T3-119: Is help sent with no prior attack (T3-011), or by those who attacked (T3-119)?
• Against T3-115: Is another room's request refused (T3-115), or its work helped (T3-011)?
• Against T3-195: Is an agreement already made invoked, spread or said to be broken (T3-195), or another room's work helped or defended, the pledge named only as the reason for the help (T3-011)?
• Varies: From one member placing for a neighbour to a room sending its spare pixels to a neighbour's defence.
• Is not: Help given in return for help received (T3-151).
• Exemplars: "I'm helping /r/stlouisblues. I wish I could do my party." (borussiadortmund c0027); "come help our farm over at r/farmcarrots/!" (stardewvalley c0003); "Please support their cause by maintaining the borders and defeating the people who keep trolling Helix's eyes" (drawhelix c0006)

T3-012 granting a neighbour room

The room grants a neighbour space on or beside its work: permission to build in its area, room made in its design. Floor: greenlattice and Goodboye, unlike in size (greenlattice holds 5,244 items in the window and Goodboye 248, over twice as many).

• Must show: A neighbour allowed onto the room's work or area: 'go for it', 'do what you want with that part', room made inside the design for another's art.
• Must not show: The room yielding its own space and moving (T3-039); a host ruling on many requests by its rules (T3-162).
• Decide when both: A grant inside a border deal: T3-010 primary when the deal leads, T3-012 added when the grant has concepts of its own.
• Against T3-039: Does the room move off and give up its spot (T3-039), or let a neighbour build on or beside its work (T3-012)?
• Against T3-162: Does a host rule on requests by its standing rules (T3-162), or does the room grant one neighbour room (T3-012)?
• Against T3-035: Is room asked for (T3-035), or granted (T3-012)?
• Against T3-115: Is another room's request refused (T3-115), or a neighbour granted space on or beside the room's work (T3-012)?
• Against T3-010: Is a line or shared space agreed between the two rooms (T3-010), or a neighbour simply let onto the room's own work or area (T3-012)?
• Varies: From permission for a rival school's logo beside the room's to orange space assigned to displaced groups.
• Is not: A room moving its work to give a neighbour its spot (T3-039).
• Exemplars: "Better FSU than USF, I say. Go for it." (ucf c0091); "Ok. Do what you want with the butthole. Just don't let them vandalise anything else" (Goodboye c0064); "Thank you r/greenlattice for allowing us to put our goof/gaff on your part of the map." (greenlattice c0781)

T3-035 asking a host for space

Members ask a room that holds space (a host, a faction, a neighbour) for room to build. Floor: ainbowroad and rpi, unlike in size (ainbowroad holds 9,887 items in the window and rpi 491, over twice as many).

• Must show: A request for space or permission addressed to the room that holds it: 'permission to make X in your lot', 'can we share and let us slip into that space'.
• Must not show: Choosing open space (T3-020); asking for help with the work (T3-084); pleading with attackers (T3-139).
• Decide when both: A request inside a border deal: T3-010 primary when the deal leads, T3-035 added when the request has concepts of its own.
• Against T3-020: Is space found on the open canvas (T3-020), or asked of the room that holds it (T3-035)?
• Against T3-084: Is space asked for (T3-035), or hands to help the work (T3-084)?
• Against T3-139: Is space asked for (T3-035), or an attack asked to stop (T3-139)?
• Against T3-012: Is room asked (T3-035), or granted (T3-012)?
• Against T3-036: Is space asked of a host room (T3-035), or is the canvas judged full (T3-036)?
• Against T3-094: Is space asked for (T3-035), or the right to approve it disputed (T3-094)?
• Against T3-010: Is a line or space settled between neighbours (T3-010), or space or permission asked of the room that holds it (T3-035)?
• Varies: From a one-line request in a faction's thread to delegations asking for a fixed square in a colour corner.
• Is not: Asking another room to send hands to help build (T3-084).
• Exemplars: "Permission to make JOHN CENA in your lot." (greenlattice c0947, rivals c0931 c0711 c0677); "get permission to build Aang somewhere on the road?" (ainbowroad c1385, rivals c1563 c1661); "why not share and let us slip into that space?" (rpi c0053)

T3-045 arguing who was there first

Members argue which room was at a spot first, with claims, timestamps and accusations of stealing. Floor: stlouis and bahrain, unlike in size (stlouis holds 1,647 items in the window and bahrain 132, over twice as many).

• Must show: Priority of place argued: 'we were there first', 'did you steal this spot', timestamped proof, a work built around whoever came first.
• Must not show: Refusing to give up space on other grounds (T3-123); arguing whether covering is fair at all (T3-046); disputing who may approve a spot (T3-094).
• Decide when both: First arrival claimed while refusing to move: T3-123 when the refusal leads, T3-045 when the argument over priority does.
• Against T3-123: Is the space refused (T3-123), or is who came first argued (T3-045)?
• Against T3-046: Is whether covering is fair argued (T3-046), or who came first (T3-045)?
• Against T3-094: Is the right to approve a spot disputed (T3-094), or who came first (T3-045)?
• Against T3-087: Is who altered the work traced (T3-087), or who was at the spot first argued (T3-045)?
• Varies: From 'the blue note was definitely first' to timestamped images offered as proof.
• Is not: A room refusing to move because of work done or an agreement (T3-123).
• Exemplars: "The blue note was definitely first. Fill it in guys." (stlouis c0026); "we were there way before anyone of your guys." (sadboys c0054); "Did you just steal this spot from Qatar?" (bahrain c0041)

T3-071 letting neighbours adopt the work

A room lets a neighbour take its work into theirs, and thanks them for keeping it. Floor: undertale and nuclearthrone, unlike in size (undertale holds 2,501 items in the window and nuclearthrone 380, over twice as many).

• Must show: The room's work adopted into a neighbour's: thanks for keeping and incorporating it, a neighbour's offer to incorporate a figure into its flag.
• Must not show: A room adopting another's sign as its own (T3-175, the receiving side); converting by force (T3-068).
• Decide when both: An adoption traded for help: T3-151 when the trade leads, T3-071 when the adoption does.
• Against T3-175: Is the room's work adopted by a neighbour (T3-071), or another's sign adopted by the room (T3-175)?
• Against T3-068: Is the work taken in with consent (T3-071), or converted by placing over it (T3-068)?
• Against T3-151: Is help traded (T3-151), or the room's work adopted into a neighbour's (T3-071)?
• Varies: From thanks for a figure kept inside a flag to an offer to incorporate a figure in exchange for help.
• Is not: Taking a neighbour's sign as the room's mascot (T3-175).
• Exemplars: "Thanks r/Ireland for keeping our temmie, and even incorporating it!" (undertale c0235); "We at /r/ireland will incorporate him into the flag if you help us with upwards expansion." (nuclearthrone c0037)

T3-084 asking other rooms for help

A room asks another canvas room, as a group, to help with its work: to build, defend or repair it. Floor: anime and mariokart, unlike in size (anime holds 35,920 items in the window and mariokart 65, over twice as many).

• Must show: A request from one room to another for help with the work: 'we could use your help', 'help us please', calls for reinforcements addressed to another room.
• Must not show: Carrying a call for hands into other subs' membership (T3-062); asking for space (T3-035); help asked in return for help given (T3-151).
• Decide when both: A request inside a deal: T3-010 primary when the deal leads, T3-084 added when the request has concepts of its own.
• Against T3-062: Is another sub's membership asked for hands (T3-062), or another canvas room asked as a group (T3-084)?
• Against T3-035: Is help with the work asked (T3-084), or space (T3-035)?
• Against T3-151: Is help asked in return for help (T3-151), or asked outright (T3-084)?
• Against T3-011: Is help asked for (T3-084), or sent (T3-011)?
• Against T3-002: Are the room's own members called to place (T3-002), or another canvas room asked, as a group, for help (T3-084)?
• Against T3-115: Is help asked (T3-084), or a request refused (T3-115)?
• Against T3-010: Is a line or space settled between neighbours (T3-010), or another room asked, as a group, to help with the work (T3-084)?
• Varies: From a tiny sub asking a big one for help to flag rooms petitioning a road for backup.
• Is not: Posting a call for hands in a kindred sub (T3-062).
• Exemplars: "we're a tiny subreddit, and we could use your help." (anime c0166); "We are the Italy Flag from r/Italy, help us please!" (ainbowroad c0911); "Guys! We need your help over at /r/Place. Pixel Mario Kart needs reinforcements!" (mariokart c0012)

T3-094 disputing who approves a spot

Members dispute whether a room needs another's approval to build, and who may give it. Floor: warframe and gameboy, unlike in size (warframe holds 9,718 items in the window and gameboy 614, over twice as many).

• Must show: Contest over approval for a spot: 'you are not even approved', 'we shouldn't need permission on an open canvas', warnings that a faction covers unapproved art, claims of approval.
• Must not show: Asking for space (T3-035); a host ruling on requests (T3-162); who had the spot first (T3-045).
• Decide when both: A host's ruling that is contested: T3-162 for the ruling, T3-094 for the contest when it has concepts of its own.
• Against T3-162: Does the host rule on requests (T3-162), or is the need for its approval disputed (T3-094)?
• Against T3-035: Is space asked for (T3-035), or the right to approve it disputed (T3-094)?
• Against T3-045: Is who came first argued (T3-045), or who may approve (T3-094)?
• Against T3-126: Is it disputed who speaks for a room (T3-126), or who may approve a spot (T3-094)?
• Varies: From 'we shouldn't need permission on an open canvas' to warnings that a faction covers art it has not approved.
• Is not: A faction ruling on a request to build in its space (T3-162).
• Exemplars: "We shouldn't need permission to draw what we want on a open canvas." (adventuretime c0101); "You guys are not even approved" (seahawks c0132); "The green lattice guys actively cover stuff up unless you get your art approved by them." (gameboy c0010)

T3-099 relying on a bigger neighbour

A small room relies on a bigger neighbour to protect its work, or seeks such protection. Floor: vietnam and bretagne, unlike in size (vietnam holds 374 items in the window and bretagne 38, over twice as many).

• Must show: The room counting on, seeking or being promised a larger room's protection: listed among a big flag's protected works, allied with a bigger room for a secure spot.
• Must not show: An alliance between rooms of like size for joint defence (T3-150); help bartered (T3-151).
• Decide when both: Protection given by the bigger room, told from its side, is not here: it sits with the help it is (T3-011) or the alliance (T3-150).
• Against T3-150: Do rooms of like size join for defence (T3-150), or does a small room rely on a bigger one (T3-099)?
• Against T3-151: Is protection repaid with help (T3-151), or relied on (T3-099)?
• Against T3-011: Is the bigger room sending help (T3-011), or the small room relying on it (T3-099)?
• Varies: From a Breton flag on France's list of protected flags to a small room asking a big one for a secure spot.
• Is not: Two rooms of like size agreeing to defend each other (T3-150).
• Exemplars: "On va le protéger, il est sur la liste des drapeaux autorisés sur le fond France." (bretagne c0016); "France is protecting us from the void" (vinesauce c0025); "Maybe asking and allies with /r/osugame :)" (vietnam c0009)

T3-115 turning away another room's request

Members refuse another room's request for help, space or a cause. Floor: anime and geometrydash, unlike in size (anime holds 35,920 items in the window and geometrydash 452, over twice as many).

• Must show: A request from another room or its members refused or sent back: 'no', 'we can not offer our assistance', 'post it on your own sub', a refusal on grounds of rivalry.
• Must not show: Requests granted (T3-012, T3-011); a host ruling on requests to build by its rules (T3-162).
• Decide when both: A request refused and then helped: the side with more concepts is primary.
• Against T3-162: Does a host rule on requests to build in its space by its rules (T3-162), or does a room refuse another's request for help or a cause (T3-115)?
• Against T3-084: Is help asked (T3-084), or a request refused (T3-115)?
• Against T3-138: Is a side refused to stay neutral between two rooms (T3-138), or one request refused (T3-115)?
• Against T3-011: Is another room's request refused (T3-115), or its work helped (T3-011)?
• Against T3-012: Is another room's request refused (T3-115), or a neighbour granted space on or beside the room's work (T3-012)?
• Varies: From a joke refusal over a capital letter to scorn for a colour; requests sent back to their own sub.
• Is not: A faction denying a request to build inside its space under its rules (T3-162).
• Exemplars: "You capitalized the G in georgia so unfortunately we can not offer our assistance at this time, best of luck in your endeavors." (gatech c0043); "As if I helped a filthy purple. Maybe if they changed the color." (anime c0004, rivals c0123); ">unturned post it on /r/unturned" (geometrydash c0077)

T3-137 joining an outside group's build

Members put their pixels into another group's build as their own effort: joining the Void, following another sub's plan, all pixels to another room's territory. Floor: catholicism and Jamaica, unlike in size (catholicism holds 4,836 items in the window and Jamaica 84, over twice as many).

• Must show: A member, or the room, joining another group's work as a participant: 'I joined the void', 'all my pixels go to r/X's territory', following an outside sub's plan.
• Must not show: Help sent while the room keeps its own work (T3-011); another's sign adopted as the room's (T3-175).
• Decide when both: Joining and helping in one theme: T3-137 when the member's effort moves to the other build, T3-011 when it stays the room's.
• Against T3-011: Does the member help another's work while keeping the room's own (T3-011), or join the other build as theirs (T3-137)?
• Against T3-175: Does the room take another's sign as its own (T3-175), or put its pixels into another group's build (T3-137)?
• Against T3-062: Are other subs' members recruited to the room (T3-062), or does the room's member join another's build (T3-137)?
• Varies: From one member's pixels given wholly to another room's territory to a room following an outside sub's design.
• Is not: Sending a few pixels to help a neighbour while building one's own (T3-011).
• Exemplars: "All my pixels are dedicated to the upkeep of r/PrequelMemes territory, sorry cives." (latin c0009); "I joined the void but I'm tired of the whole thing now" (Jamaica c0005); "PSA. This design was started by r/CKcrusaders. Please follow the plan." (catholicism c0040)

T3-162 vetting others' requests to build

A host room rules on others' requests to build in its space: approvals, denials, conditions, published rules. Floor: thebluecorner and orderofthebluecorner, unlike in size (thebluecorner holds 5,939 items in the window and orderofthebluecorner 69, over twice as many).

• Must show: A room that holds space deciding on requests: 'you can build it, but it has to be completely blue', 'denied', rules for which art stays, lists of approved art.
• Must not show: A single grant to one neighbour (T3-012); disputing the need for approval (T3-094); refusing a request for help (T3-115).
• Decide when both: A ruling that is contested: T3-162 for the ruling, T3-094 for the contest.
• Against T3-012: Is one neighbour granted room (T3-012), or many requests ruled on by the host's rules (T3-162)?
• Against T3-094: Does the host rule (T3-162), or is the need for its approval disputed (T3-094)?
• Against T3-115: Does a host rule on building in its space (T3-162), or does a room refuse a request for help (T3-115)?
• Varies: From one denial to published rules, approval documents and submissions closed.
• Is not: A room letting one neighbour build beside its work (T3-012).
• Exemplars: "You can build it, but it has to be completely blue." (orderofthebluecorner c0047, rivals c0052 c0064); "No new art in the lattice. Denied." (greenlattice c0292, rivals c1047); "Yes! It will go well with blue of his overalls too!" (thebluecorner c0338)

G15 pacts and envoys between rooms

T3-030 disputing how an alliance went

Members dispute an alliance's conduct or worth, often after the close: who kept their word, betrayal, never again. Floor: edmontonoilers and GreenCorner, unlike in size (edmontonoilers holds 2,350 items in the window and GreenCorner 243, over twice as many).

• Must show: Argument over an alliance's or deal's conduct or worth: broken word alleged, betrayal warned of, collaboration renounced.
• Must not show: Holding a room to its agreement so the work can go on (T3-195); arguing whether cooperation is surrender (T3-193); blaming an attacker for a loss (T3-058).
• Decide when both: A breach named mid-work: T3-195; the alliance judged as a whole: T3-030.
• Against T3-195: Is the agreement invoked so the work goes on (T3-195), or the alliance's conduct or worth disputed (T3-030)?
• Against T3-193: Is cooperation as such called surrender (T3-193), or one alliance's conduct disputed (T3-030)?
• Against T3-058: Is a rival blamed for a loss (T3-058), or an ally's conduct disputed (T3-030)?
• Varies: From 'that's the last time we collaborate with them' to warnings that a colour faction will betray its partner again.
• Is not: Reminding a neighbour mid-work of the border agreed (T3-195).
• Exemplars: "FUCK THE FLAMES that's the last time we collaborate with them" (edmontonoilers c0132, rivals c0142 c0136); "Red will turn on you again. You have been warned." (GreenCorner c0092, rivals c0088); "Your representatives haven't been faithful to their word, but hey, typical French." (spain c0061)

T3-047 making up with another sub

Two subs settle a quarrel: apologies, thanks and good wishes exchanged. Floor: canucks and japan, unlike in size (canucks holds 4,507 items in the window and japan 1,332, over twice as many).

• Must show: A quarrel between two subs closed by apology and acceptance, thanks or good wishes.
• Must not show: An apology for damage to a neighbour's work with repair offered (T3-040); a truce ending a fight on the canvas (T3-149).
• Decide when both: An apology for canvas damage that also closes a quarrel: T3-040 when the damage is the point, T3-047 when the quarrel is.
• Against T3-040: Is damage to a neighbour's work apologised for (T3-040), or a quarrel between the subs closed (T3-047)?
• Against T3-149: Is a fight on the canvas ended by truce (T3-149), or a quarrel made up (T3-047)?
• Against T3-122: Are greetings sent with no quarrel behind them (T3-122), or a quarrel made up (T3-047)?
• Against T3-119: Is a quarrel made up in words (T3-047), or damage repaired by its makers (T3-119)?
• Varies: From 'sorry, we were a bit salty, good luck' to an attack claim turned into apology and help.
• Is not: Apologising for covering a neighbour's art and offering to redraw it (T3-040).
• Exemplars: "ah yeah mate sorry about that - we were a bit salty. good luck with your project" (worldpowers c0038, rivals c0039); "Forgive me if I was mistaken." (japan c0085); "it seems you're being pretty polite. So I'd like to apologize." (canucks c0172)

T3-083 negotiating across a language gap

Members deal with another room across a language gap: translating, machine translation, too little of the language to negotiate. Floor: lithuania and RelientK, unlike in size (lithuania holds 183 items in the window and RelientK 40, over twice as many).

• Must show: Language as a problem in dealings between rooms: offers to translate, posts machine-translated, members unable to negotiate for lack of the language.
• Must not show: Writing in the room's own language to hide the plan (T3-116).
• Decide when both: A deal made across a language gap: the deal's kind is primary, T3-083 added when the gap has concepts of its own.
• Against T3-116: Is language used to keep rivals out (T3-116), or a gap bridged to deal with another room (T3-083)?
• Against T3-194: Is a member the room's envoy (T3-194), or is the language between rooms the problem met (T3-083)?
• Varies: From one Google-translated reply to a member offering to translate for all non-Spanish helpers.
• Is not: Writing in Hindi so that rivals cannot read the plan (T3-116).
• Exemplars: "That's fine I just used google translate so hopefully them get it haha." (RelientK c0013, rivals c0012); "to translate anything for you" (epublica c0026); "Google translate:" (lithuania c0032)

T3-119 turning attackers into helpers

A room that attacked a work, or members of it, turn to help repair it. Floor: foxes and TheHulk, unlike in size (foxes holds 314 items in the window and TheHulk 114, over twice as many).

• Must show: Former attackers helping the work they damaged: admitting the damage and helping rebuild, repairing a work they overwrote, a takeover followed by help to rebuild elsewhere.
• Must not show: An apology with an offer of help not yet acted on (T3-040); help with no prior attack (T3-011).
• Decide when both: Apology and repair together: T3-119 when the former attackers act, T3-040 when they only apologise.
• Against T3-040: Do the former attackers only apologise (T3-040), or help repair (T3-119)?
• Against T3-011: Is help sent with no prior attack (T3-011), or by those who attacked (T3-119)?
• Against T3-047: Is a quarrel made up in words (T3-047), or damage repaired by its makers (T3-119)?
• Varies: From one member who destroyed a figure helping bring it back to a room that took a spot by force and helped rebuild the work elsewhere.
• Is not: An apology for damage with a promise to help later (T3-040).
• Exemplars: "I'm one of the assholes who destroyed it and I feel like shit now but I'm helping to get it back." (TheHulk c0062); "we took it by force and then helped them to rebuild it in a new position" (Summit1G c0045); "we decided that building our logo and rebuilding yours elsewhere was dumb." (foxes c0040, rivals c0063)

T3-122 sending greetings to another room

Members send greetings, compliments and thanks to another room with no deal attached. Floor: germany and iastate, unlike in size (germany holds 1,637 items in the window and iastate 173, over twice as many).

• Must show: Greetings, compliments, love or thanks addressed to another room or its work, from or to neighbours.
• Must not show: Thanking allies and telling the alliance's story after the close (T3-072); an envoy's errand (T3-194); a quarrel made up (T3-047).
• Decide when both: Greetings that open a deal: the deal's kind is primary, T3-122 added when the greeting has a concept of its own.
• Against T3-072: Are allies thanked for help in the work, often after the close (T3-072), or greetings sent with no deal (T3-122)?
• Against T3-194: Is the visitor on an errand for their room (T3-194), or sending greetings (T3-122)?
• Against T3-047: Is a quarrel made up (T3-047), or are greetings sent with none behind them (T3-122)?
• Against T3-052: Do members remark on neighbouring pictures among themselves (T3-052), or send a message to another room (T3-122)?
• Against T3-155: Are greetings sent with no fight behind them (T3-122), or a rival saluted after one (T3-155)?
• Against T3-158: Is a greeting sent (T3-122), or a tie beyond the canvas proposed (T3-158)?
• Varies: From humble greetings from another nation's sub to love for a neighbour's sprites.
• Is not: Thanking allies for help in the war after the close (T3-072).
• Exemplars: "[/r/place] Humble greetings from /r/argentina!" (germany c0080); "yeah, sending love from /r/coldplay, I really loved your sprites /r/MadokaMagica <3" (madokamagica c0096); "GT student here, glad to be a neighbor with y'all" (iastate c0057)

T3-138 staying neutral between two rooms

A room keeps out of a fight between others or declares neutrality, or a member is torn between two rooms. Floor: gatech and epublica, unlike in size (gatech holds 919 items in the window and epublica 149, over twice as many).

• Must show: Neutrality: refusing to take sides, a declared neutral zone, a sub stating it neither supports nor attacks a project, members torn between two rooms they belong to.
• Must not show: Refusing a request for help on its own merits (T3-115); making peace with one's own rival (T3-149).
• Decide when both: Neutrality declared while making a truce with one side: T3-149 for the truce, T3-138 for the stance between others.
• Against T3-115: Is a request refused on its own merits (T3-115), or a side refused to stay neutral (T3-138)?
• Against T3-149: Does the room make peace with its own rival (T3-149), or keep out of others' fight (T3-138)?
• Against T3-150: Does the room join a side (T3-150), or stay out (T3-138)?
• Against T3-161: Does the member keep out of others' fight (T3-138), or help them reach terms (T3-161)?
• Varies: From a neutrality zone named for Switzerland to a fan of two rooms caught between them.
• Is not: Turning down a request for help on its own merits (T3-115).
• Exemplars: "MONA LISA ACCEPT OUR NEUTRALITY" (SwissNeutralityZone c0034, rivals c0114); "I also don't want to side against the void because that is nothing short of declaring war" (gatech c0042); "este otro proyecto no es apoyado ni atacado por la administración del sub" (epublica c0066)

T3-149 agreeing truces with rival rooms

Rooms already in contact end or forestall a fight with a truce: peace asked for, offered, agreed, honoured. Floor: ice_poseidon and landry, unlike in size (ice_poseidon holds 8,175 items in the window and landry 24, over twice as many).

• Must show: A pact to stop or avoid attacks between rooms already in contact: peace or a truce asked for, offered, agreed or celebrated; non-aggression pacts.
• Must not show: Lines and space settled where no fight began (T3-010); an alliance for joint defence or a joint fight (T3-150); a truce already made invoked against a breach (T3-195).
• Decide when both: A pact ending or forestalling a fight between rooms already in contact goes to T3-149; an agreement drawing borders or sharing space where no fight began goes to T3-010. A truce invoked against a breach is T3-195 when the invoking leads.
• Against T3-010: Does the pact end or forestall a fight (T3-149), or settle lines where no fight began (T3-010)?
• Against T3-150: Do the rooms stop fighting each other (T3-149), or join to fight or defend together (T3-150)?
• Against T3-195: Is a truce made now (T3-149), or one already made invoked (T3-195)?
• Against T3-138: Does the room make peace with its own rival (T3-149), or keep out of a fight between others (T3-138)?
• Against T3-151: Is a fight ended or forestalled by a pact (T3-149), or help given in return for help (T3-151)?
• Against T3-025: Is a fight ended (T3-149), or two rival marks set together with no fight (T3-025)?
• Against T3-047: Is a fight on the canvas ended by truce (T3-149), or a quarrel made up (T3-047)?
• Against T3-193: Is a truce made (T3-149), or is cooperation argued as surrender (T3-193)?
• Against T3-194: Does a member act for the room toward another room as envoy or representative (T3-194), or is the truce itself asked for, offered or agreed (T3-149)?
• Varies: From a quick 'can we have peace here?' between rival universities to non-aggression pacts with the Void.
• Is not: A border drawn between neighbours who never fought (T3-010).
• Exemplars: "We're all on the same team here. Just request a truce." (ice_poseidon c0207); "The rivalry was fun, but I'm glad we had a truce in the end" (uofm c0206, rivals c0143); "A message of peace" (finland c0008)

T3-150 forming alliances between rooms

Rooms join in an alliance for joint defence or a joint fight: alliances named, proposed, joined. Floor: naruto and AprilKnights, unlike in size (naruto holds 3,975 items in the window and AprilKnights 218, over twice as many).

• Must show: An alliance between rooms for defence or a fight: proposals and invitations, named alliances, rooms joining a front, promises to defend each other.
• Must not show: Help traded case by case (T3-151); help sent with nothing asked (T3-011); a small room relying on a bigger one (T3-099); a truce between rivals (T3-149).
• Decide when both: An alliance that trades help: T3-150 when joint defence or a fight is the frame, T3-151 when the swap of help is.
• Against T3-151: Is help swapped case by case (T3-151), or a standing alliance for defence or a fight formed (T3-150)?
• Against T3-149: Do rivals stop fighting (T3-149), or rooms join to fight or defend (T3-150)?
• Against T3-099: Does a small room rely on a bigger one (T3-099), or do rooms ally (T3-150)?
• Against T3-056: Do kindred rooms make one joint mark (T3-056), or ally for defence or a fight (T3-150)?
• Against T3-174: Is loyalty professed to a colour faction (T3-174), or an alliance made between rooms (T3-150)?
• Against T3-011: Are the rooms allied for joint defence (T3-150), or is help sent to another's work (T3-011)?
• Against T3-010: Do the rooms join for defence or a fight (T3-150), or settle where their works meet (T3-010)?
• Against T3-072: Is an alliance formed for the fight (T3-150), or thanked and told afterwards (T3-072)?
• Against T3-079: Is friendship drawn between flags (T3-079), or an alliance for defence formed (T3-150)?
• Against T3-138: Does the room join a side (T3-150), or stay out (T3-138)?
• Against T3-194: Does a member act for the room toward another room as envoy or representative (T3-194), or is the alliance itself proposed, named or joined (T3-150)?
• Against T3-195: Is an agreement already made invoked, spread or said to be broken (T3-195), or a new alliance proposed, named or joined (T3-150)?
• Varies: From a two-room defence pact to a United Red Front of many subs.
• Is not: Swapping repairs with a neighbour once (T3-151).
• Exemplars: "I come to propose a preemptive alliance to join forces in cleanup and construction of art" (thebluecorner c0537); "The Pirate-Ninja alliance!" (naruto c0146, rivals c0160); "Join us and together the red shall rein supreme over the tyrannical oppressors!" (AprilKnights c0045)

T3-151 bartering help with neighbours

Rooms trade help: repairs, defence, maintenance or room given in return for the same. Floor: theitalyplace and thepointing, unlike in size (theitalyplace holds 1,302 items in the window and thepointing 67, over twice as many).

• Must show: Help offered or asked in return for help: 'we'll help you move if you maintain ours', 'repay the favour', maintenance traded for room.
• Must not show: Help sent with nothing asked (T3-011); an alliance for joint defence (T3-150); a third room's work offered up in the bargain (T3-067).
• Decide when both: Help given in return is T3-151, help with nothing asked T3-011.
• Against T3-011: Is help given in return (T3-151), or with nothing asked (T3-011)?
• Against T3-150: Is help swapped (T3-151), or a standing alliance formed (T3-150)?
• Against T3-067: Is help traded between two rooms alone (T3-151), or a third room's work offered up (T3-067)?
• Against T3-010: Is help traded (T3-151), or a line settled (T3-010)?
• Against T3-108: Is help traded by hand (T3-151), or one bot target pooled (T3-108)?
• Against T3-149: Is help given in return for help (T3-151), or a fight ended or forestalled by a pact (T3-149)?
• Against T3-071: Is help traded (T3-151), or the room's work adopted into a neighbour's (T3-071)?
• Against T3-084: Is help asked in return for help (T3-151), or asked outright (T3-084)?
• Against T3-099: Is protection repaid with help (T3-151), or relied on (T3-099)?
• Against T3-194: Does a member act for the room toward another room as envoy or representative (T3-194), or is the trade of help itself offered or agreed (T3-151)?
• Against T3-195: Is an agreement already made invoked, spread or said to be broken (T3-195), or a new trade of help offered or agreed (T3-151)?
• Varies: From a one-off swap of repairs to running exchanges of maintenance for room.
• Is not: Sending pixels to a neighbour's defence unasked (T3-011).
• Exemplars: "We're willing to help you move if you help maintain ours afterwards." (thepointing c0011); "If you all can help preserve the Koi, we'd repay the favor by helping keep the Italian flag dot-free." (theitalyplace c0133); "Happy to help repair and maintain the yellow background in exchange for being allowed to exist in your realm." (TeamYellowPlace c0051)

T3-161 mediating between other rooms

Rare tier. A member acts as go-between for two other rooms.

• Must show: A member helping two other rooms reach terms: a go-between, attention brought to treaties between them.
• Must not show: Acting for one's own room toward another (T3-194).
• Decide when both: A member who is envoy for one room and go-between for two others: the role toward the two others is T3-161.
• Against T3-194: Does the member act for their own room (T3-194), or between two other rooms (T3-161)?
• Against T3-138: Does the member keep out of others' fight (T3-138), or help them reach terms (T3-161)?
• Varies: One member's account only.
• Is not: A room's own diplomat in another room's thread (T3-194).
• Exemplars: "so I got to be a go between" (skyrim c0165, rivals c0156); "I tried to be a good neighbor, bringing attention to treaties" (skyrim c0156, rivals c0165)

T3-193 arguing whether cooperation is surrender

Members argue whether cooperating with another room, or accepting a treaty, is surrender. Floor: france and eagles, unlike in size (france holds 16,236 items in the window and eagles 2,540, over twice as many).

• Must show: Argument over cooperation as weakness or surrender: refusals to submit, a treaty defended as sensible, cooperation defended as credit to both rooms.
• Must not show: A truce agreed with no such argument (T3-149); an ally's conduct disputed (T3-030).
• Decide when both: A truce argued over: T3-149 when the truce is made, T3-193 when its meaning as surrender is argued.
• Against T3-149: Is a truce made (T3-149), or is cooperation argued as surrender (T3-193)?
• Against T3-030: Is one alliance's conduct disputed (T3-030), or cooperation as such called surrender (T3-193)?
• Against T3-165: Is friendship with a historic national enemy debated (T3-165), or cooperation as such (T3-193)?
• Varies: From a nation's members refusing to submit to hearts and neighbours to a rival fandom's room defending a joint logo.
• Is not: Agreeing a truce with a rival with no argument over it (T3-149).
• Exemplars: "La France ne se soumettra pas !" (france c0179, rivals c0567 c0576 c0568); "Lets not look like dicks by being the ones to not agree to the peace treaty" (eagles c0217); "the logos were a cooperation between both communities" (starcitizen c0388)

T3-194 acting as envoys between rooms

A member acts for a room toward another room: envoy, diplomat, ambassador, representative, a proposal carried between threads. Floor: stardustcrusaders and Summit1G, unlike in size (stardustcrusaders holds 4,002 items in the window and Summit1G 229, over twice as many).

• Must show: A named role or errand between rooms: a member made the room's diplomat, a representative arriving in another room's thread, a council seat, a proposal carried from one room to another.
• Must not show: Members meeting other rooms in chat with no one acting for the room (T3-153); disputing who may speak for a room (T3-126); the deal itself (T3-010, T3-149, T3-150, T3-151).
• Decide when both: The envoy's errand is T3-194, the deal it carries T3-010 or its kin; when both have concepts of their own, the larger is primary.
• Against T3-153: Does a member act for the room toward another (T3-194), or do members meet other rooms in chat (T3-153)?
• Against T3-126: Does a member act as envoy (T3-194), or is the right to speak for the room disputed (T3-126)?
• Against T3-010: Is the errand the doing (T3-194), or the line it settles (T3-010)?
• Against T3-161: Does the member act for their own room (T3-194), or go between two other rooms (T3-161)?
• Against T3-083: Is a member the room's envoy (T3-194), or is the language between rooms the problem met (T3-083)?
• Against T3-122: Is the visitor on an errand for their room (T3-194), or sending greetings (T3-122)?
• Against T3-149: Does a member act for the room toward another room as envoy or representative (T3-194), or is the truce itself asked for, offered or agreed (T3-149)?
• Against T3-150: Does a member act for the room toward another room as envoy or representative (T3-194), or is the alliance itself proposed, named or joined (T3-150)?
• Against T3-151: Does a member act for the room toward another room as envoy or representative (T3-194), or is the trade of help itself offered or agreed (T3-151)?
• Varies: From one representative's arrival in a neighbour's thread to diplomats flaired on a council server across a dozen chats.
• Is not: Members of two rooms chatting in a shared Discord (T3-153).
• Exemplars: "Today, I became a diplomat for the Day Knights." (day9 c0033, rivals c0037); "Whelp, guess I'm officially our diplomat on the r/PlaceWorldCouncil discord" (stardustcrusaders c0044); "/r/BluePatch representative" (Summit1G c0062)

T3-195 holding rooms to their agreements

Members invoke an agreement already made: its terms spread to placers, the room reminded to honour it, a neighbour accused of breach, a lapsed deal restored. Floor: liverpoolfc and sheffield, unlike in size (liverpoolfc holds 8,929 items in the window and sheffield 105, over twice as many).

• Must show: An existing agreement invoked: 'we made an agreement with hearts', 'it was the original deal', 'we agreed you can have the flower, but ...', a broken deal named.
• Must not show: A new deal made (T3-010, T3-149, T3-150, T3-151); an alliance's conduct or worth disputed, often after the close (T3-030); a member breaking the room's agreement (T3-102).
• Decide when both: A theme that makes a deal and later invokes it keeps the larger part as primary and adds the other under rule 0.
• Against T3-010: Is an agreement made (T3-010), or one already made invoked (T3-195)?
• Against T3-149: Is a truce made (T3-149), or invoked against a breach (T3-195)?
• Against T3-030: Is the room held to its agreement so the work can go on (T3-195), or the alliance's conduct or worth disputed (T3-030)?
• Against T3-102: Is the agreement invoked (T3-195), or broken by a member (T3-102)?
• Against T3-188: Is another room held to an agreement (T3-195), or does an organised room say it does not control placers acting in its name (T3-188)?
• Against T3-076: Is another room held to an agreement (T3-195), or does the room stop its own attackers (T3-076)?
• Against T3-150: Is an agreement already made invoked, spread or said to be broken (T3-195), or a new alliance proposed, named or joined (T3-150)?
• Against T3-151: Is an agreement already made invoked, spread or said to be broken (T3-195), or a new trade of help offered or agreed (T3-151)?
• Against T3-011: Is an agreement already made invoked, spread or said to be broken (T3-195), or another room's work helped or defended, the pledge named only as the reason for the help (T3-011)?
• Against T3-005: Is an agreement already made invoked, spread or said to be broken (T3-195), or the room's own work defended, the pledge named only as the reason for the defence (T3-005)?
• Varies: From a quick 'no stop, we made an agreement' to accusations that a neighbour went over the logo after the deal.
• Is not: Agreeing a new border with a neighbour (T3-010).
• Exemplars: "Oi no stop we made an agreement with hearts" (liverpoolfc c0168, rivals c0169); "We agreed that you guys can have the flower there, but please stop removing Apollo's sleeve with your blue border" (sheffield c0038); "I think we should apologize to r/shyvanamains for going over their logo even after we had a deal." (weezer c0038, rivals c0093)

G16 kindred rooms and colour factions

T3-013 gathering kindred rooms together

Kindred rooms (a league's teams, a region's subs, sister fandoms) gather their canvas work in one hub sub or chat. Floor: warriors and sooners, unlike in size (warriors holds 6,401 items in the window and sooners 131, over twice as many).

• Must show: A hub for many kindred rooms used or proposed: 'everyone go to r/CFBplace', a regional place sub for several teams, one chat for a league, members sent to the hub for help.
• Must not show: A separate sub for one room's own work (T3-090); one joint mark made by two rooms (T3-056); calls for hands sent to kindred subs (T3-062).
• Decide when both: A hub that also makes a joint mark: T3-013 for the hub, T3-056 added when the joint mark has concepts of its own.
• Against T3-090: Is the new sub for this room's own work (T3-090), or a hub for many kindred rooms (T3-013)?
• Against T3-056: Do two or more rooms make one mark together (T3-056), or gather their separate works in a hub (T3-013)?
• Against T3-062: Are kindred subs asked for hands for this room (T3-062), or gathered into a common hub (T3-013)?
• Varies: From a college football place sub to a regional hub for a city's teams and a European chat server.
• Is not: A room opening its own canvas sub (T3-090).
• Exemplars: "#EVERYONE GO TO /r/CFBPLACE FOR THIS SORTA STUFF." (sooners c0038); "i asked for help in r/nbaplace" (warriors c0150); "Come discuss it over at /r/716Place" (ubreddit c0045)

T3-019 tallying kindred rooms' works

Members count which kindred rooms (teams, schools, bands) made it onto the canvas and which were lost. Floor: sixers and ucf, unlike in size (sixers holds 1,701 items in the window and ucf 384, over twice as many).

• Must show: An inventory of kindred rooms' marks on the canvas: which teams, schools or subs made it, which were covered, where they are.
• Must not show: Decoding the finished picture in general (T3-018); remarking on the pictures beside the room's own mark (T3-052).
• Decide when both: A tally inside a reading of the final canvas: T3-018 when the whole picture is read, T3-019 when the kindred rooms are counted.
• Against T3-018: Is the whole finished picture decoded (T3-018), or the kindred rooms' marks counted (T3-019)?
• Against T3-052: Are pictures beside the mark remarked on (T3-052), or kindred rooms' marks across the canvas tallied (T3-019)?
• Varies: From a guess that only two NBA teams made it to a list of hockey logos kept or covered.
• Is not: Explaining what each picture on the finished canvas is (T3-018).
• Exemplars: "Nucks made it, Wings recreated a smaller version of theirs." (wildhockey c0214); "I believe that us and the Lakers are the only NBA teams with our logo on there." (sixers c0137); "The bottom left corner seems to have a few" (ucf c0011)

T3-056 making joint marks with others

Two or more rooms make one mark together: a shared design, a combined flag, lettering finished for each other. Floor: h3h3productions and AvoArmy, unlike in size (h3h3productions holds 16,925 items in the window and AvoArmy 604, over twice as many).

• Must show: A mark designed or built jointly by two or more rooms: shared borders made into a design, flags combined, each finishing part of the other's work, a joint emblem.
• Must not show: Help sent to another room's own work (T3-011); a member adding a personal piece to a shared mark (T3-060); national flags joined by a heart (T3-079).
• Decide when both: A joint mark of two national flags joined by a heart: T3-079; any other joint mark: T3-056.
• Against T3-011: Is help sent to another's own work (T3-011), or one mark made together (T3-056)?
• Against T3-079: Are national flags joined with a heart (T3-079), or another joint mark made (T3-056)?
• Against T3-150: Do rooms ally for defence or a fight (T3-150), or make one mark together (T3-056)?
• Against T3-060: Is one mark made jointly by rooms (T3-056), or a personal piece added to it (T3-060)?
• Against T3-013: Do two or more rooms make one mark together (T3-056), or gather their separate works in a hub (T3-013)?
• Against T3-025: Do the rooms make one mark together (T3-056), or keep two rival marks side by side (T3-025)?
• Varies: From a beanie and lettering traded between two fandoms to ANZAC flags built together before the Americans woke.
• Is not: Sending pixels to a neighbour's defence (T3-011).
• Exemplars: "They're finishing our beanie and we're finishing their lettering." (h3h3productions c0133); "a row of heart-faced avocados wherever we meet up, and we maintain a strong border together" (AvoArmy c0053); "We are working together now on making a second flag to the left side." (newzealand c0143, rivals c0167 c0157)

T3-096 hailing the colour corners

Members of other subs cheer the colour corners and factions, or call people to their side. Floor: ice_poseidon and roosterteeth, unlike in size (ice_poseidon holds 8,175 items in the window and roosterteeth 3,628, over twice as many).

• Must show: Outsiders hailing or cheering a colour faction or corner, or calling others to its side, without being its own members.
• Must not show: A faction's own members professing loyalty (T3-174); spreading the colour (T3-171).
• Decide when both: A member of another sub who joins the faction and hails it: T3-163 for the joining, T3-096 for the hailing.
• Against T3-174: Do the faction's own members profess loyalty (T3-174), or do other subs' members cheer it (T3-096)?
• Against T3-171: Is the colour spread on the canvas (T3-171), or cheered in talk (T3-096)?
• Against T3-163: Does a member defect to the faction (T3-163), or only cheer it (T3-096)?
• Varies: From 'all hail blue corner' in a game sub to a streamer's sub calling its army to the purple side.
• Is not: The Blue Corner's own members hailing their empire (T3-174).
• Exemplars: "ALL HAIL BLUE CORNER" (roosterteeth c0018); "ALL HAIL BLUE CORNER!" (minecraft c0033); "Join us in our honorable fight against the blue scum!" (ice_poseidon c0083)

T3-163 defecting from a rival faction

Members announce that they have left a rival faction and joined this one. Floor: ainbowroad and Pigifs, unlike in size (ainbowroad holds 9,887 items in the window and Pigifs 82, over twice as many).

• Must show: Defection or conversion between canvas factions: 'defector from the Blue Corner', 'converting from the Void', joining the lattice's army with a first pixel.
• Must not show: A faction splitting over doctrine (T3-190); outsiders cheering a faction (T3-096).
• Decide when both: A member leaving over doctrine to found or join a splinter: T3-190 when the split is the doing, T3-163 when the member's crossing is.
• Against T3-190: Does a faction split over doctrine (T3-190), or does a member cross from a rival faction (T3-163)?
• Against T3-096: Does a member cross over (T3-163), or only cheer a faction (T3-096)?
• Against T3-174: Is loyalty professed by members (T3-174), or a member's crossing announced (T3-163)?
• Varies: From one defector's title post to convert stories told in a faction's thread.
• Is not: A faction splitting into rival doctrines (T3-190).
• Exemplars: "I'm converting from r/TheBlueCorner" (theblackvoid c1859); "Defector from the Blue Corner" (ainbowroad c0206, rivals c0634); "Defector from The Void" (greenlattice c0575, rivals c0482 c1079)

T3-171 spreading a faction's colour

A colour faction spreads its colour across the canvas: expanding the corner, covering others with its colour, tendrils and cores. Floor: theblackvoid and GreenCorner, unlike in size (theblackvoid holds 9,430 items in the window and GreenCorner 243, over twice as many).

• Must show: A colour, not a picture, spread as the faction's aim: calls to expand the corner, to cover the canvas in the colour, to grow tendrils, the colour treated as territory.
• Must not show: A room's picture extended into a neighbour's space (T3-061); a rival's work defaced (T3-006); loyalty to the faction professed in talk (T3-174).
• Decide when both: Spreading the colour over a rival's work: T3-171 when the colour's spread is the aim, T3-006 or T3-061 when the target is.
• Against T3-061: Is a picture grown into a neighbour's space (T3-061), or a colour spread as the aim (T3-171)?
• Against T3-006: Is a rival's work destroyed (T3-006), or the faction's colour spread over whatever lies in its way (T3-171)?
• Against T3-174: Is the colour spread on the canvas (T3-171), or loyalty to it professed (T3-174)?
• Against T3-041: Is the room's work extended (T3-041), or a colour spread for its own sake (T3-171)?
• Against T3-096: Is the colour spread on the canvas (T3-171), or cheered in talk (T3-096)?
• Varies: From a corner that grows a few rows to a Void meant to consume the whole canvas; red spread as a political colour.
• Is not: A room extending its logo into a neighbour's space (T3-061).
• Exemplars: "We shall spread the purple monarchy all over the canvas and defeat the blue usurpers!" (purplecorner c0006); "TWO TEAMS: ONE TO RID THE VOID OF ALL MATTER, ONE TO EXPAND OUR CANCER TO THE ENTIRE PLACE." (theblackvoid c0382); "Start expanding the green corner!" (GreenCorner c0048)

T3-172 renewing the order's oaths

A canvas-born order lays down or renews its rules, oaths and membership. Floor: PurplePixels and AprilKnights, unlike in size (PurplePixels holds 837 items in the window and AprilKnights 218, over twice as many).

• Must show: An order's or faction's own rules, commandments, oaths or membership rolls set or renewed: commandments for its members, a yearly renewal, officers appointed by the order.
• Must not show: Elections for office (T3-173); one member put in charge of the work (T3-101).
• Decide when both: Officers appointed under the order's rules: T3-172; officers voted in: T3-173.
• Against T3-173: Are offices filled by election (T3-173), or the order's rules and oaths laid down or renewed (T3-172)?
• Against T3-101: Is a leader named for the work (T3-101), or the order's standing rules set (T3-172)?
• Varies: From commandments for a purple faction to an order of knights meeting once a year.
• Is not: A faction voting in a new leader (T3-173).
• Exemplars: "1. Respect thy fellow Purple. 2. Spare the art, for it is beautiful. 3. Consume all blue." (PurplePixels c0140, rivals c0137); "we picked up some new members and we picked up some old members." (AprilKnights c0086, rivals c0096); "Basically we meet up once a year to shitpost with each other." (AprilKnights c0096, rivals c0086)

T3-173 holding elections for office

A canvas-born faction holds elections for its leaders and offices. Floor: GreenCorner and AprilKnights, unlike in form (GreenCorner is a sub made on the canvas for a colour faction, AprilKnights an order carried over from the 2015 Button event).

• Must show: Elections in a faction: a new leader elected, voter registration, a round of elections, objections to holding them.
• Must not show: Votes on the work (T3-066); one member put in charge with no vote (T3-101).
• Decide when both: A leader elected who then puts choices to polls: T3-173 for the election, T3-066 for the polls.
• Against T3-066: Is a choice about the work voted (T3-066), or a person elected to office (T3-173)?
• Against T3-101: Is a leader named with no vote (T3-101), or elected (T3-173)?
• Against T3-172: Are rules and oaths laid down (T3-172), or offices filled by vote (T3-173)?
• Varies: From an election held during an attack to voter registration after the event.
• Is not: A poll on whether to fight, expand or move (T3-066).
• Exemplars: "Election for new leader!" (GreenCorner c0045, rivals c0073); "With the April Fools Event over it is time to begin the election progress." (AprilKnights c0090); "YOUR HAVING FUCKING ELECTIONS WHILE WE'RE GETTING ATTACKED" (GreenCorner c0105)

T3-174 professing loyalty to a colour

A colour faction's members profess loyalty to it: hails, slogans, propaganda, the colour as faith or empire. Floor: theblackvoid and destiny, unlike in size (theblackvoid holds 9,430 items in the window and destiny 1,436, over twice as many).

• Must show: Members of a colour faction professing its cause: 'all hail the Bluempire', 'hail the all-consuming Void', the colour cast as faith, empire or calling, propaganda praised.
• Must not show: Other subs' members cheering the faction (T3-096); spreading the colour on the canvas (T3-171).
• Decide when both: Hails that call members to spread the colour: T3-171 when the spreading is called, T3-174 when loyalty is the point.
• Against T3-096: Do the faction's own members profess loyalty (T3-174), or other subs' members cheer it (T3-096)?
• Against T3-171: Is loyalty professed (T3-174), or the colour spread (T3-171)?
• Against T3-031: Is the joke the faction's colour cult (T3-174), or any running in-joke of the room (T3-031)?
• Against T3-150: Is loyalty professed to a colour faction (T3-174), or an alliance made between rooms (T3-150)?
• Against T3-163: Is loyalty professed by members (T3-174), or a member's crossing announced (T3-163)?
• Varies: From a one-line hail to the Void cast as a calling and a fit; propaganda posters.
• Is not: A game sub hailing the Blue Corner from outside (T3-096).
• Exemplars: "ALL HAIL THE BLUEMPIRE!!" (thebluecorner c0505); "Hail The All Consuming Void!" (theblackvoid c0833, rivals c1664); "10/10 propaganda. would vote for purple again" (destiny c0047)

T3-190 splitting a faction over doctrine

A canvas faction splits over what it stands for: pure colour or art, erasing or cleaning, the void or coexistence. Floor: thebluecorner and PurplePixels, unlike in size (thebluecorner holds 5,939 items in the window and PurplePixels 837, over twice as many).

• Must show: Dispute over a faction's doctrine that divides it: members leaving for a purer version, splinter subs founded, the faction's past and true nature argued.
• Must not show: A member defecting from a rival faction (T3-163); a member quitting under strain (T3-181).
• Decide when both: A member leaving over doctrine: T3-190 when the split in the faction is the doing, T3-163 when the crossing to another faction is.
• Against T3-163: Does a member cross from a rival faction (T3-163), or does the faction split over its doctrine (T3-190)?
• Against T3-181: Does a member quit under strain (T3-181), or over the faction's doctrine (T3-190)?
• Against T3-179: Is a political ideology argued from the canvas (T3-179), or a faction's own canvas doctrine (T3-190)?
• Varies: From one eraser leaving for the black to a colour faction arguing whether it was once the void.
• Is not: A member giving up because the work became stressful (T3-181).
• Exemplars: "Henceforth, going to begin spreading the black, as they are more true to the ideology I was seeking." (EraseThePlace c0154, rivals c0250); "We were once like the void, however we chose to coexist with others later on." (thebluecorner c0707, rivals c0643); "PLACE PURPLE ONLY PURPLE UNLESS IT'S SOME KIND OF BIG FACE" (PurplePixels c0213)

G17 nations and their flags

T3-065 building the homeland's flag

The room makes the flag of its nation, state or region its mark: calling hands to it, building, sizing and fixing it. A flag built in a room named for a land is that land's flag unless its concepts name another. Floor: argentina and DevonUK, unlike in size (argentina holds 10,453 items in the window and DevonUK 26, over twice as many).

• Must show: The flag of the room's own land (a nation, a state, a region or county) built as the room's mark: calls to make it, its proportions, its spot, its repair. Announcements that the flag has begun or is up, and calls for hands to it, go here too.
• Must not show: Calls for hands to any other picture (T3-002); emblems and pictures drawn beside or inside the flag (T3-113); helping another nation's flag (T3-078).
• Decide when both: The flag of the room's land as its mark is T3-065, calls for hands to any other picture T3-002. A flag with emblems drawn into it: T3-065 for the flag, T3-113 when the emblems have concepts of their own.
• Against T3-002: Is the work a flag of the land the room is named for or speaks for, a flag built in r/guatemala being Guatemala's unless its concepts name another (T3-065), or any other picture (T3-002)?
• Against T3-113: Is the flag itself built (T3-065), or emblems drawn beside or inside it (T3-113)?
• Against T3-078: Is the room's own flag built (T3-065), or a kin nation's helped (T3-078)?
• Against T3-145: Is the flag built (T3-065), or national feeling voiced through it (T3-145)?
• Against T3-026: Is the room's mark announced as up (T3-026), or is the work a flag of the land the room is named for or speaks for, announced, called for or built (T3-065)? A flag built in a room named for a land is that land's flag unless its concepts name another.
• Varies: From nation states to the flags of a US state, a French region or an English county; proportions argued; flags rebuilt after attacks.
• Is not: A room adding its nation's emblems inside a flag already built (T3-113).
• Exemplars: "To all Israel in r/place, let's gather up and make a big flag on the canvas and be proud of our-self" (israel c0190); "hagamos la bandera de argentina en un costado" (argentina c0001); "Need help expanding the Devon flag!" (DevonUK c0016)

T3-078 helping kin nations' flags

Members help the flags of kindred nations or regions: Baltic brothers, neighbours, a diaspora's homeland. Floor: europe and Dominican, unlike in size (europe holds 29,726 items in the window and Dominican 96, over twice as many).

• Must show: Help for another nation's or region's flag felt as kin: helping Baltic brothers restore their flags, asking a kin nation's sub for help, defending a brother nation's flag.
• Must not show: Help to any other room's work (T3-011); the room's own flag (T3-065).
• Decide when both: Help to a kin nation traded for help: T3-151 when the trade leads, T3-078 when kinship does.
• Against T3-011: Is help sent to any room's work (T3-011), or to a kin nation's flag as kin (T3-078)?
• Against T3-065: Is the room's own flag built (T3-065), or a kin nation's helped (T3-078)?
• Against T3-079: Is a kin nation's flag helped (T3-078), or two flags joined with a heart (T3-079)?
• Varies: From Lithuanians restoring the Estonian flag instead of making a third of their own to Dominicans asking help for Puerto Rican brothers.
• Is not: A sports sub helping a neighbouring logo (T3-011).
• Exemplars: "Padedam Estam atkurti savo vėliavą, vietoj darę trečią savo!" (lithuania c0114, rivals c0013 c0068); "Care to help out Estonia with their struggles against Tyler1's ugly face?" (latvia c0051); "anyway you can help our PR brothers? fucking NL are taking over their flag" (Dominican c0034)

T3-079 joining flags with a heart

Rooms join their national flags with a heart or another sign of friendship. Floor: romania and FaroeIslands, unlike in size (romania holds 4,754 items in the window and FaroeIslands 112, over twice as many).

• Must show: Hearts or friendship signs made between national flags: proposals, half-and-half hearts, hearts kept for alliances, friendship between nations drawn on the canvas.
• Must not show: Other joint marks (T3-056); debating friendship with a historic enemy (T3-165).
• Decide when both: A heart between historic enemies argued over: T3-165 when the argument leads, T3-079 when the heart is made.
• Against T3-056: Are national flags joined with a heart (T3-079), or another joint mark made (T3-056)?
• Against T3-165: Is the heart made (T3-079), or friendship with a historic enemy argued (T3-165)?
• Against T3-150: Is friendship drawn between flags (T3-079), or an alliance for defence formed (T3-150)?
• Against T3-078: Is a kin nation's flag helped (T3-078), or two flags joined with a heart (T3-079)?
• Varies: From one Faroese-Welsh heart to hearts traded as tokens of alliance among Balkan and Baltic flags.
• Is not: Two fandoms finishing each other's lettering (T3-056).
• Exemplars: "Would you be interested in making a heart between our two countries as a show of friendship?" (FaroeIslands c0045, rivals c0048 c0049); "Hai sa facem inima jumi-juma macar" (romania c0203, rivals c0018); "Can we create a beautiful friendship with Greece and Turkey including Netherlands." (europe c0515)

T3-085 weighing the room against nations

Members weigh the room's art against the nations' flags on the canvas: flags called bland or too big, a nation's size claimed as a right to space. Floor: suomi and metroid, unlike in size (suomi holds 5,336 items in the window and metroid 432, over twice as many).

• Must show: The room's mark set against national flags: flags called boring or bland, a portrait called a bigger show of power than a flag, a nation's population claimed as a right to a big flag.
• Must not show: Questioning the room's own presence (T3-098); attacks on flags (T3-006).
• Decide when both: A judgement on flags that leads to attacking them: T3-006 for the attack, T3-085 for the weighing when it has concepts of its own.
• Against T3-098: Is the room's own presence questioned (T3-098), or its art weighed against nations' flags (T3-085)?
• Against T3-006: Are flags attacked (T3-006), or weighed against the room's art (T3-085)?
• Against T3-037: Is the whole canvas judged (T3-037), or nations' flags against the room's art (T3-085)?
• Varies: From 'a flag doesn't need to be that big and is kind of boring' to a billion-person nation's claim to a big flag.
• Is not: A room asking why it has no logo on the canvas (T3-098).
• Exemplars: "Kekkosen muotokuva on paljon isompi vallan ja dominoinnin osoitus kuin joku laimee lippu mitä siel kaikil näyttää olevan" (suomi c0124); "Sure, I actually started first and a flag doesn't need to be that big and is kind of boring." (metroid c0030, rivals c0050); "we have a billion people in our nation... give us the rights to at least have a big flag." (metroid c0050, rivals c0030)

T3-113 drawing national emblems

Members draw their nation's emblems, figures and symbols beside or inside the flag: monuments, animals, the king's name, a coat of arms. Floor: romania and PlaceNL, unlike in size (romania holds 4,754 items in the window and PlaceNL 701, over twice as many).

• Must show: National emblems and pictures added to or beside the flag: figures of the nation's history or folklore, animals, monuments, the monarch's name, a coat of arms, national words.
• Must not show: The flag itself (T3-065); political symbols argued over (T3-080).
• Decide when both: A flag with emblems: see T3-065. A political emblem argued over: T3-080 when the argument leads. Veiled fascist emblems drawn into a national room's work sit here.
• Against T3-065: Is the flag built (T3-065), or the nation's emblems added to it (T3-113)?
• Against T3-080: Is an emblem added (T3-113), or a political symbol argued over (T3-080)?
• Against T3-041: Is a further piece added to any work (T3-041), or a national emblem to the flag (T3-113)?
• Varies: From Dracula on the Romanian flag to the Dutch king's full name beside the coat of arms; cedars, kiwis, roos.
• Is not: Members arguing whether a hammer and sickle belongs on the canvas (T3-080).
• Exemplars: "Avem mult spaţiu gol pe steag. Am putea să mai adăugăm 5-6 lucruri." (romania c0179, rivals c0170); "Petitie om onze koning zijn volledige naam een plek te geven rechts van ons wapen." (PlaceNL c0138); "Hai sa-l desenam pe Dracula pe steag!" (romania c0170, rivals c0179)

T3-145 feeling national through the canvas

Members feel and voice national belonging through the canvas work: pride in the flag, a nation standing together, fighting for it from abroad. Floor: ireland and latvia, unlike in size (ireland holds 12,112 items in the window and latvia 124, over twice as many).

• Must show: National feeling voiced through the work: pride and tears at the flag, the nation said to stand together, members abroad or by marriage fighting for it.
• Must not show: The flag built (T3-065); the finished work celebrated with no national feeling (T3-009); national politics read into the canvas (T3-130).
• Decide when both: A celebration in national terms: T3-009 when the work is celebrated, T3-145 when national belonging is voiced.
• Against T3-009: Is the finished work celebrated (T3-009), or national belonging voiced (T3-145)?
• Against T3-065: Is the flag built (T3-065), or feeling for the nation voiced through it (T3-145)?
• Against T3-130: Is national politics read into the canvas (T3-130), or belonging felt (T3-145)?
• Varies: From a tear in the eye at the Irish flag to a member defending Latvia's flag in honour of a spouse.
• Is not: A team sub celebrating its finished logo (T3-009).
• Exemplars: "Ive a tear in my eye, im so proud" (ireland c0061); "Ég hefði aldrei trúað því að við gætum staðið saman og haldið velli eins og þarna." (iceland c0075); "I may not be Latvian, but my wife is a native and I'm proud to keep up the fight" (latvia c0043)

T3-165 debating friendship with historic enemies

Members argue whether canvas friendship with a historic national enemy means anything, or should exist at all. Floor: korea and palestine, unlike in size (korea holds 2,773 items in the window and palestine 564, over twice as many).

• Must show: Debate over friendship or coexistence on the canvas with a nation the room counts a historic enemy: Greece and Turkey, Korea and Japan, Palestine and Israel.
• Must not show: A heart made with no such argument (T3-079); cooperation argued as surrender in general (T3-193).
• Decide when both: See T3-079.
• Against T3-079: Is the heart made (T3-079), or friendship with a historic enemy argued (T3-165)?
• Against T3-193: Is cooperation as such called surrender (T3-193), or friendship with a historic national enemy debated (T3-165)?
• Against T3-130: Is national politics read into the canvas generally (T3-130), or friendship with one historic enemy debated (T3-165)?
• Against T3-166: Is friendship with one historic enemy debated (T3-165), or the nation's own record (T3-166)?
• Varies: From Greeks thanking Turkey as a good neighbour to Palestinians asking why anyone supported flags side by side with Israel.
• Is not: A heart drawn between two friendly nations (T3-079).
• Exemplars: "I get why we would not want to attack the Israeli flag on a practical level, but why did anyone ever support the notion" (palestine c0059); "it is possible to be pro-Japan and pro-Korea" (korea c0030); "we managed to quickly learn to co-exist" (greece c0144, rivals c0147)

T3-180 disputing national belonging

Members dispute who belongs to the nation or region and who may speak or act for it on the canvas. Floor: korea and palestine, unlike in size (korea holds 2,773 items in the window and palestine 564, over twice as many).

• Must show: Contest over national or regional belonging: who counts as Korean, whether only Arabs may support Arabs, whether a university's attackers count as Texas, whether Quebec's flag is Canada's to overwrite.
• Must not show: Who speaks for a room (T3-126); national politics read into the canvas generally (T3-130).
• Decide when both: A dispute over who speaks for a national room: T3-126 when the room's voice is in question, T3-180 when membership in the nation is.
• Against T3-126: Is it disputed who speaks for the room (T3-126), or who belongs to the nation (T3-180)?
• Against T3-130: Is national politics read into the canvas (T3-130), or belonging to the nation disputed (T3-180)?
• Varies: From K-pop fans called koreaboos to Texans disowning a university's takeover.
• Is not: Members disputing who may speak for a sub (T3-126).
• Exemplars: "I'm not sure whether to find it funny or sad that you think your favorite manufactured kpop idol is part of your heritage." (korea c0160, rivals c0161); "They're not. Are only Arabs allowed to support Arabs?" (palestine c0078); "I'm from Texas and this is just another reason to hate UT" (giantbomb c0180)

G18 politics, history and hate symbols

T3-080 arguing over political symbols

Members argue over a political or religious symbol on the canvas: what it means, whether it belongs, whether to take it down. Floor: mexico and czech, unlike in size (mexico holds 4,564 items in the window and czech 672, over twice as many).

• Must show: A symbol argued over for its politics: the hammer and sickle as a sign of occupation, Deus Vult as an alt-right sign, a religious symbol judged too divisive, MH17 drawn on a flag, partisan marks on a shared flag.
• Must not show: National emblems added with no argument (T3-113); covering hate symbols (T3-146); ideology argued in general from the canvas (T3-179).
• Decide when both: A symbol argued over and then covered: T3-080 when the argument leads, T3-146 when it is a hate symbol and the covering leads.
• Against T3-113: Is a national emblem added (T3-113), or a political symbol's meaning argued (T3-080)?
• Against T3-146: Is a hate symbol covered (T3-146), or a symbol's politics argued (T3-080)?
• Against T3-179: Is one symbol on the canvas argued over (T3-080), or an ideology argued from the canvas as a whole (T3-179)?
• Against T3-130: Is one symbol's meaning argued (T3-080), or national politics read into the canvas at large (T3-130)?
• Against T3-177: Do members call for or draw swastikas and Nazi imagery (T3-177), or argue over what a political symbol means and whether it belongs (T3-080)?
• Varies: From Czechs calling the hammer and sickle a symbol of occupation to a Mexican room keeping religion off its mural.
• Is not: Painting over a swastika (T3-146).
• Exemplars: "The Hammer and Sickle is a symbol of murder, totality and occupation for many Czechs. Let's take it down." (czech c0122); "Det dekker flagget. Det er også symbol for alt-right bevegelsen, som /r/norge bør distansere seg fra." (norge c0210); "Muy polarizante, se sugerio en Discord. Religion solo puede escalar conflictos lamentablemente." (mexico c0197)

T3-081 casting fights as national history

Members cast canvas fights as their nations' historic wars: invasions repeated, old battles and songs replayed, occupation recalled. Floor: theitalyplace and bdsm, unlike in size (theitalyplace holds 1,302 items in the window and bdsm 308, over twice as many).

• Must show: A canvas fight told in the terms of a nation's real history of war or occupation: 'Russia is invading us again', a war song turned on black pixels, a takeover called a blitzkrieg reenactment, Kosovo again.
• Must not show: War language for fights between game fandoms or teams with no national history (T3-050, T3-005); national politics read into the canvas outside a fight (T3-130).
• Decide when both: A fight fought and told as history: T3-005 or T3-006 for the fighting, T3-081 added when the historical framing has concepts of its own.
• Against T3-005: Is the defence told as a fight (T3-005), or cast as a nation's historic war (T3-081)?
• Against T3-050: Are taunts traded as sport (T3-050), or the fight cast in a nation's war history (T3-081)?
• Against T3-130: Is the fight told as historic war (T3-081), or national politics read into the canvas (T3-130)?
• Against T3-135: Is the fight cast as a nation's history (T3-081), or as the fandom's story (T3-135)?
• Against T3-166: Is a canvas fight cast as historic war (T3-081), or the nation's whole record argued (T3-166)?
• Varies: From one line about an invasion again to running war narration with operations and battle names; Kosovo, Stalingrad, the Piave, blitzkrieg.
• Is not: A streamer's fans calling a raid on a rival logo a war: a game-fandom war has no national history.
• Exemplars: "Russia is invading us again!" (ukraine c0031); "Il Piave mormorò "Non passa il pixel nero!"." (theitalyplace c0272); "I'm more impressed with the blitzkrieg reenactment there, taking over the French flag" (bdsm c0002)

T3-086 carrying in the sub's quarrel

A community's own quarrel or rivalry is carried onto the canvas: one faction's slogan pushed over the other's, the rivalry fought in pixels. Floor: cfb and btc, unlike in size (cfb holds 18,716 items in the window and btc 6,327, over twice as many).

• Must show: A dispute or rivalry from the community's own life fought or argued on the canvas: a faction's mark pushed over another's, the rivalry declared to have reached r/place, members arguing whether outsiders will care.
• Must not show: Taunts traded with a rival community (T3-050); ideology argued (T3-179).
• Decide when both: A rivalry carried in and taunted: T3-050 when the taunts lead, T3-086 when the quarrel's marks do.
• Against T3-050: Are taunts traded (T3-050), or the community's own quarrel fought in marks (T3-086)?
• Against T3-179: Is a general ideology argued (T3-179), or the community's own dispute carried onto the canvas (T3-086)?
• Against T3-006: Is a rival's work defaced (T3-006), or the community's own quarrel carried into the marks (T3-086)?
• Varies: From the Bitcoin block-size split to old-school and current RuneScape players and college rivalries.
• Is not: Two sports subs trading taunts (T3-050).
• Exemplars: "Sorry, just pushing over the SegWit Sandcastle to build Fort Unlimited." (btc c0121, rivals c0183); "The rivalry has invaded r/place!" (cfb c0266); "No one outside r/bitcoin and r/btc will know what segwit is, or care even if they googled it." (bitcoin c0157)

T3-130 reading national politics in pixels

Members read their nation's politics into the canvas: referendums, elections, governments, migration, old regimes. Floor: europe and anarchocapitalism, unlike in size (europe holds 29,726 items in the window and anarchocapitalism 28, over twice as many).

• Must show: National politics brought to the canvas work: the pixel fight felt as a referendum campaign, a government disowned, elections and regimes joked about, a national choice of targets.
• Must not show: One political symbol argued over (T3-080); fights cast as historic wars (T3-081).
• Decide when both: A target chosen for national political reasons and converted, as when a national room puts its own flag over another nation's: T3-068 for the converting, T3-130 for the national reason when it has concepts of its own.
• Against T3-080: Is one symbol's meaning argued (T3-080), or national politics read into the canvas (T3-130)?
• Against T3-081: Is the fight cast as historic war (T3-081), or current national politics read into it (T3-130)?
• Against T3-145: Is national belonging felt (T3-145), or national politics argued (T3-130)?
• Against T3-068: Is the converting the doing (T3-068), or the national politics read into the choice of target (T3-130)?
• Against T3-165: Is national politics read into the canvas generally (T3-130), or friendship with one historic enemy debated (T3-165)?
• Against T3-180: Is national politics read into the canvas (T3-130), or belonging to the nation disputed (T3-180)?
• Varies: From Quebec's referendums to a Serbian election silence; a US member disowning the government while defending the flag.
• Is not: Arguing whether the hammer and sickle should be taken down (T3-080).
• Exemplars: "Je sais pas pourquoi mais j'ai été investi là dedans comme si c'était une campagne référendaire." (quebec c0140, rivals c0185); "Just because I was born in the US doesn't mean I agree with or approve of the current administration." (europe c0711); "This started in a small fun game of pixel art but ended being a literal political war." (canada c0286)

T3-142 making ethnic jokes about rivals

Members mock rival nations or peoples with ethnic jokes and slurs during the canvas fights. Floor: eve and loltyler1, unlike in size (eve holds 10,097 items in the window and loltyler1 1,815, over twice as many).

• Must show: Jokes, insults or slurs aimed at a rival people or nation: refugees, 'elf scum', a whole people cursed, national stereotypes used as abuse.
• Must not show: Taunts aimed at a rival community with no ethnic content (T3-050); arguing whether a taunt goes too far (T3-143).
• Decide when both: Taunts with some ethnic jokes: T3-050 when the taunting leads, T3-142 added when the ethnic jokes have concepts of their own.
• Against T3-050: Is the rival a community taunted as such (T3-050), or a people or nation mocked (T3-142)?
• Against T3-143: Is the joke made (T3-142), or argued as going too far (T3-143)?
• Against T3-182: Is bigotry voiced (T3-142), or shut down (T3-182)?
• Varies: From mock fantasy-race insults to visitors called refugees with an ableist slur; a whole people cursed for ruining everything.
• Is not: A sports sub taunting a rival team's fans (T3-050).
• Exemplars: "All these Estonian refugees getting boners because they beat us LUL" (loltyler1 c0191); "Fuck swedes. Always ruining everything." (eve c0256); "Indonesians are elf scum confirmed" (dwarffortress c0112)

T3-146 covering swastikas and hate symbols

Members cover swastikas, Nazi flags and other hate symbols or slurs placed on or near their work, or call others to. Floor: de and calvinandhobbes, unlike in size (de holds 14,899 items in the window and calvinandhobbes 401, over twice as many).

• Must show: Hate symbols or slurs on the canvas covered or reported: swastikas, Nazi flags, Hitler drawings, slur banners; calls for help against them; promises to cover them for others.
• Must not show: Calls to draw swastikas (T3-177); ordinary repair of stray pixels (T3-021).
• Decide when both: Hate symbols and slurs covered are T3-146; obscene drawings and ordinary insults covered are repair (T3-021). A theme that covers swastikas and refuses requests to draw them keeps T3-146 primary, with T3-177 added when the calls have concepts of their own.
• Against T3-177: Are swastikas called for (T3-177), or covered (T3-146)?
• Against T3-021: Is a hate symbol or slur covered (T3-146), or the work repaired of other damage, obscene drawings included (T3-021)?
• Against T3-080: Is a hate symbol covered (T3-146), or a political symbol's meaning argued (T3-080)?
• Against T3-182: Is a hate symbol on the canvas covered (T3-146), or bigoted talk shut down (T3-182)?
• Varies: From one member removing a swastika beside a flag to a leftist room promising to cover swastikas on another nation's flag.
• Is not: Members turning a rival's logo into a swastika (T3-177).
• Exemplars: "Trolls are trying to write swastikas on your flag on /r/places. We at farleftside have got you covered don't worry." (ukraine c0006); "/r/Eagles - We need your help with this Nazi Flag [/r/place]" (calvinandhobbes c0068); "Es gibt buchstäblich dünne Versuche ein Hakenkreuz neben die deutsche Flagge zu basteln" (de c0011, rivals c0459 c0460)

T3-166 arguing the nation's historical record

Rare tier. Members argue whether their nation has always been on the right side of history.

• Must show: Argument over the nation's historical record set off by the canvas: claims of always being right, massacres cited against them.
• Must not show: Fights cast as historic wars (T3-081); friendship with a historic enemy debated (T3-165).
• Decide when both: The record argued while debating a heart with an old enemy: T3-165 when the friendship leads, T3-166 when the record does.
• Against T3-081: Is a canvas fight cast as historic war (T3-081), or the nation's whole record argued (T3-166)?
• Against T3-165: Is friendship with one historic enemy debated (T3-165), or the nation's own record (T3-166)?
• Varies: One room's thread only.
• Is not: Casting a border fight as a repeat of an old war (T3-081).
• Exemplars: "Greeks have always been on the right side of history" (greece c0171, rivals c0184); "Εxcept for the massacres" (greece c0183, rivals c0171); "Nah Greeks were pretty much always on the right side of history" (greece c0184, rivals c0171)

T3-177 calling to draw swastikas

Members call for, or take part in, drawing swastikas and Nazi imagery on the canvas, the room's own logo included. Floor: pcmasterrace and funhaus, unlike in size (pcmasterrace holds 40,459 items in the window and funhaus 2,830, over twice as many).

• Must show: Calls or admissions to draw swastikas or Nazi images: turning a logo into a swastika, helping change a logo into one, proposing Hitler's face.
• Must not show: Covering hate symbols (T3-146); arguing over a political symbol's meaning (T3-080).
• Decide when both: See T3-146.
• Against T3-146: Are swastikas called for or drawn (T3-177), or covered (T3-146)?
• Against T3-192: Is the griefing for fun with no hate symbol (T3-192), or a swastika called for (T3-177)?
• Against T3-006: Is a rival's work defaced (T3-006), or a swastika drawn (T3-177)?
• Against T3-080: Do members call for or draw swastikas and Nazi imagery (T3-177), or argue over what a political symbol means and whether it belongs (T3-080)?
• Varies: From a proposal to turn a rival channel's logo into a swastika to members drawing one on their own room's logo.
• Is not: A room painting over a swastika (T3-146).
• Exemplars: "Let's make the logo on r/place a swastika" (funhaus c0236); "Anyone want to turn the FH logo into an actual swastika?" (roosterteeth c0218); "i was helping changing it to a swastika a few hours ago" (pcmasterrace c0643, rivals c0787)

T3-179 arguing ideology from the canvas

Members argue political ideology from the canvas: socialism, capitalism, anarchism, consensus, read into how the canvas was made. Floor: anarcho_capitalism and anarchocapitalism, unlike in size (anarcho_capitalism holds 2,937 items in the window and anarchocapitalism 28, over twice as many).

• Must show: Ideology argued with the canvas as evidence or occasion: r/place called decentralised socialism, capitalists said to destroy rather than build, left unity questioned, leaderless consensus praised.
• Must not show: One political symbol argued over (T3-080); a faction's own canvas doctrine (T3-190); the fairness of scripts (T3-027).
• Decide when both: A symbol argued in ideological terms: T3-080 when the symbol is the object, T3-179 when the ideology is.
• Against T3-080: Is one symbol on the canvas argued (T3-080), or an ideology argued from the canvas (T3-179)?
• Against T3-190: Is a canvas faction's doctrine split (T3-190), or a political ideology argued (T3-179)?
• Against T3-027: Is the fairness of scripts argued (T3-027), or political ideology (T3-179)?
• Against T3-086: Is a general ideology argued (T3-179), or the community's own dispute carried onto the canvas (T3-086)?
• Varies: From anarcho-capitalists conceding the canvas looks like socialism to leftists arguing Kronstadt.
• Is not: Czechs arguing that the hammer and sickle should come down (T3-080).
• Exemplars: "So r/place is basically decentralize socialism." (anarcho_capitalism c0154); "Yeah but what do you think about Kronstadt" (completeanarchy c0293, rivals c0271); "Typical capitalist, destroys others instead of building your own." (anarchocapitalism c0003)

T3-182 shutting down bigotry in chat

Members or moderators shut down bigoted speech in the room's thread or chat: slurs removed, a speaker shut down, racist claims answered. Floor: Rainbow6 and fullcommunism, unlike in size (Rainbow6 holds 20,801 items in the window and fullcommunism 3,915, over twice as many).

• Must show: Bigotry in the room's talk answered: anti-trans speech shut down in the Discord, a post removed for a slur, racist claims rebutted.
• Must not show: Hate symbols on the canvas covered (T3-146); members excluded for damage to the work (T3-121).
• Decide when both: A member banned for bigoted talk: T3-182 when the bigotry leads, T3-121 when the exclusion does.
• Against T3-146: Is a hate symbol on the canvas covered (T3-146), or bigoted talk shut down (T3-182)?
• Against T3-121: Is a member excluded for damage to the work or room (T3-121), or bigoted speech shut down (T3-182)?
• Against T3-142: Is bigotry voiced (T3-142), or shut down (T3-182)?
• Against T3-063: Posts removed for breaking the sub's rules (T3-063), or members shutting down bigotry in a chat (T3-182)?
• Varies: From a moderator removing a post for a slur to members shutting down an anti-trans speaker in the room's chat.
• Is not: Painting over a swastika on the canvas (T3-146).
• Exemplars: "someone joined the kanye discord and started spouting anti-trans shit. so we shut him down" (kanye c0277); "Your post was removed; it contained a slur." (fullcommunism c0239); "He is an uzbek as he is born in uzbekistan." (Rainbow6 c0403)

G19 taunts and victories over rivals

T3-025 placing rival marks together

Rare tier. A room puts its mark beside a rival's and keeps both standing without a war.

• Must show: The room's mark placed next to a rival community's mark on purpose, both defended together, the rivalry kept on the canvas without attacking.
• Must not show: Taunts traded (T3-050); a truce ending a fight (T3-149); a joint mark (T3-056).
• Decide when both: Rival marks side by side under a defence pact: T3-025 for the pairing, T3-150 for the pact when it has concepts of its own.
• Against T3-056: Do the rooms make one mark together (T3-056), or keep two rival marks side by side (T3-025)?
• Against T3-149: Is a fight ended (T3-149), or two rival marks set together with no fight (T3-025)?
• Against T3-050: Are taunts traded (T3-050), or the rivalry shown by marks placed side by side (T3-025)?
• Varies: One room's case: the Battle of Alberta kept on the canvas without a war.
• Is not: Two fandoms finishing each other's lettering (T3-056).
• Exemplars: "The Flames are a part of r/place we aren't, lets make the Oilers logo next to the Flames" (edmontonoilers c0037, rivals c0077 c0112); "I'm hoping we can both help each other out in defending them." (edmontonoilers c0077, rivals c0037); "Add PINK around both logos for BREAST CANCER awareness!!" (edmontonoilers c0112, rivals c0037)

T3-050 trading taunts with rivals

Members trade taunts, threats and mockery with a rival community over the canvas. Floor: calgaryflames and anarchocapitalism, unlike in size (calgaryflames holds 4,860 items in the window and anarchocapitalism 28, over twice as many).

• Must show: Taunts, threats or mockery aimed at a rival community over the canvas work: 'try your best', 'they will destroy you', jibes at a rival's scripts or logo.
• Must not show: Jokes about a people or nation (T3-142); blame laid for a loss after the close (T3-058); a community's own quarrel carried onto the canvas (T3-086).
• Decide when both: Taunts with ethnic jokes: T3-050 primary when taunting leads, T3-142 added when the ethnic jokes have concepts of their own.
• Against T3-142: Is a rival community taunted (T3-050), or a people or nation mocked (T3-142)?
• Against T3-058: Is a rival taunted as sport (T3-050), or blamed for a loss after the close (T3-058)?
• Against T3-086: Is a rival taunted (T3-050), or the community's own internal quarrel fought (T3-086)?
• Against T3-155: Is the rival mocked (T3-050), or saluted after the fight (T3-155)?
• Against T3-017: Is a rival community taunted (T3-050), or the sub's ordinary talk carried on with no rival in it (T3-017)?
• Against T3-025: Are taunts traded (T3-050), or the rivalry shown by marks placed side by side (T3-025)?
• Against T3-031: Is a rival mocked (T3-050), or the room's own joke played among its members (T3-031)?
• Against T3-081: Are taunts traded as sport (T3-050), or the fight cast in a nation's war history (T3-081)?
• Against T3-134: Are taunts traded in replies (T3-050), or one chant repeated as a flood (T3-134)?
• Against T3-143: Is the taunt made (T3-050), or argued over (T3-143)?
• Against T3-178: Is a rival community taunted (T3-050), or one person harassed (T3-178)?
• Varies: From friendly ribbing between schools to threats that an allied faction will destroy the rival.
• Is not: Mocking a rival nation's people (T3-142).
• Exemplars: "Lol try your best ya wank." (england c0023); "/r/thefarleftside will destroy you." (anarchocapitalism c0004); "But only super mature adults with lots of friends make scripts to cheat a fun community activity." (calgaryflames c0281)

T3-134 flooding rivals' threads with chants

Members flood a rival's thread with a chant or refrain: the Void's creed, a streamer's victory chorus, 'get gooned'. Floor: greenlattice and WPI, unlike in size (greenlattice holds 5,244 items in the window and WPI 108, over twice as many).

• Must show: A chant, refrain or slogan repeated by many members in another room's thread or in their own as a raid or victory chorus.
• Must not show: Taunts traded in ordinary replies (T3-050); the room's own in-jokes played among members (T3-031).
• Decide when both: A chant that is the room's own in-joke posted in a rival's thread: T3-134; posted among its own members: T3-031.
• Against T3-050: Are taunts traded in replies (T3-050), or one chant repeated as a flood (T3-134)?
• Against T3-031: Is the refrain played among the room's members (T3-031), or used to flood a rival's thread (T3-134)?
• Against T3-154: Is victory claimed in words (T3-154), or chanted as a chorus (T3-134)?
• Varies: From the Void's creed posted line after line in Green Lattice's thread to a streamer's fans chanting in chorus after a win.
• Is not: A room's members playing their own catchphrase among themselves (T3-031).
• Exemplars: "I AM ONE WITH THE VOID, THE VOID IS WITH ME" (greenlattice c0873, rivals c0894 c0863); "VI VON ZULUL" (Summit1G c0118, rivals c0137); "GET GOONED" (WPI c0030, rivals c0012 c0014)

T3-135 telling clashes as fandom lore

Members retell the canvas clashes in their fandom's own terms: as the game's battles, the show's factions, the band's season. Floor: skyrim and transformers, unlike in size (skyrim holds 4,956 items in the window and transformers 771, over twice as many).

• Must show: The canvas fight or its damage told in the fandom's own story terms: Autobots and Decepticons, battle scars, a game's release, a fictional war.
• Must not show: Fights cast as a nation's historic wars (T3-081); the room's in-jokes with no canvas clash (T3-031).
• Decide when both: A clash told in fandom terms with jokes: T3-135 when the clash is the subject, T3-031 when the joke is.
• Against T3-081: Is the fight cast as a nation's history (T3-081), or as the fandom's story (T3-135)?
• Against T3-031: Is it the room's running joke (T3-031), or the canvas clash retold in fandom terms (T3-135)?
• Against T3-073: Is the work's history recounted plainly (T3-073), or as fandom lore (T3-135)?
• Varies: From missing pixels called battle scars to a whole retelling as the game's Grand Battle.
• Is not: A Polish room calling a border fight a new partition (T3-081).
• Exemplars: "Those missing pieces are kind of like battle scars :)" (toolband c0211); "Skyrim, upon release, was an unfinished game for most people." (skyrim c0162); "No. Decepticon forever" (transformers c0084)

T3-143 judging whether a joke offends

Members argue whether a taunt or joke about the canvas goes too far: racist, cruel or just a joke. Floor: runescape and romania, unlike in size (runescape holds 15,369 items in the window and romania 4,754, over twice as many).

• Must show: Argument over a joke's or taunt's limits: called racist or horrible, defended as only a joke, 'you can't make a joke without offending someone'.
• Must not show: The taunt or joke itself (T3-050, T3-142); objecting to April Fools posts (T3-032).
• Decide when both: A taunt and the argument over it: T3-050 or T3-142 when the taunting leads, T3-143 when the argument does.
• Against T3-050: Is the taunt made (T3-050), or argued over (T3-143)?
• Against T3-142: Is the ethnic joke made (T3-142), or its limits argued (T3-143)?
• Against T3-032: Are April Fools posts objected to (T3-032), or a canvas joke's limits argued (T3-143)?
• Varies: From a joke about a former president's death called horrible to a flag joke defended against a charge of racism.
• Is not: Members telling the sub to stop its April Fools posts (T3-032).
• Exemplars: "being a dumb racist shitlord is supposed to be funny these days?" (eve c0268, rivals c0269); "Sunt asa oribile glumele astora cu Iliescu." (romania c0047); "Cause you can't make a joke without offending someone now a days." (runescape c0570)

T3-154 claiming victory over rival rooms

Members claim victory over rival rooms: outlasting them, defending against bigger subs, defeating them. Floor: starvstheforcesofevil and DevonUK, unlike in size (starvstheforcesofevil holds 4,950 items in the window and DevonUK 26, over twice as many).

• Must show: Victory claimed against named or implied rivals: a flag that outlasted a rival's, a small sub that held against bigger ones, rivals called defeated.
• Must not show: The finished work celebrated with no rival (T3-009); rivals saluted (T3-155).
• Decide when both: Celebration with a victory claim: T3-009 when the work is celebrated, T3-154 when victory over rivals is.
• Against T3-009: Is the finished work celebrated (T3-009), or victory over rivals claimed (T3-154)?
• Against T3-155: Is victory claimed (T3-154), or the rival saluted (T3-155)?
• Against T3-134: Is victory claimed in words (T3-154), or chanted as a flood (T3-134)?
• Varies: From a county flag outlasting its neighbour's to nationalist boasts of defeating a rival nation.
• Is not: A room celebrating its finished logo with no rival named (T3-009).
• Exemplars: "We did it, the flag lasted until the end and more importantly; lasted longer than Cornish flag" (DevonUK c0020); "Our smalll sub created pixel art and defended it from way bigger subs" (starvstheforcesofevil c0264); "After the Pakis were defeated in the second battle of cuckoldry" (bakchodi c0264)

T3-155 saluting rivals after the fight

Members salute their rivals once the fight is over: well played, good game, thanks for playing. Floor: vegan and loltyler1, unlike in size (vegan holds 7,616 items in the window and loltyler1 1,815, over twice as many).

• Must show: Respect or thanks addressed to a rival after the fight: 'well played', 'GG', 'thanks for playing', a loss conceded with good grace.
• Must not show: Taunts (T3-050); victory claimed (T3-154); greetings with no fight behind them (T3-122).
• Decide when both: Salutes mixed with taunts: the side with more concepts is primary.
• Against T3-050: Is the rival mocked (T3-050), or saluted (T3-155)?
• Against T3-154: Is victory claimed (T3-154), or the rival saluted (T3-155)?
• Against T3-122: Are greetings sent with no fight behind them (T3-122), or a rival saluted after one (T3-155)?
• Varies: From a streamer's fans telling Estonia 'well played' to a member conceding the loss to the vegans.
• Is not: Neighbours greeting each other with no fight between them (T3-122).
• Exemplars: "Well played Estonia, I think you deserve if after seeing these statistics xd" (loltyler1 c0195); "Yeah, Looks like I took the L here. Nice Job Vegans. GG" (vegan c0142); "Thanks for playing guys. /r/Norge send their regards." (texas c0265)

G20 looking at the canvas and its worth

T3-016 explaining what the canvas is

Members ask or explain what the canvas event is, why it is everywhere and how anyone places a pixel. Floor: leafs and baylor, unlike in size (leafs holds 10,209 items in the window and baylor 107, over twice as many).

• Must show: Questions or answers about the event itself: what r/place is, one pixel every few minutes, how to pick a colour and place, why subs are making pictures, the heat map or the rules of the event.
• Must not show: A guide or template for the room's own work (T3-070); calls to come and place (T3-002); what a particular picture means (T3-018); whether the canvas is worth it (T3-037).
• Decide when both: An explanation followed by the room's template: T3-016 when the event is explained to newcomers, T3-070 added when the template or coordinates have concepts of their own.
• Against T3-070: Is the event explained for anyone (T3-016), or a guide, template or coordinates for the room's work posted to follow (T3-070)?
• Against T3-002: Is the event explained (T3-016), or are members called to come and place (T3-002)?
• Against T3-018: Is the event as a whole explained (T3-016), or a particular picture's meaning worked out (T3-018)?
• Against T3-037: Is it said what the canvas is (T3-016), or argued whether it is worth anything (T3-037)?
• Against T3-074: Is the cooldown explained as a rule of the event (T3-016), or worked around by the room (T3-074)?
• Against T3-034: Is the question how and where to place for the room (T3-034), or what r/place is (T3-016)?
• Against T3-095: Is the claim tested whether r/place itself is Reddit's April Fools joke, answered by explaining what r/place is (T3-016), or a claim about anything else (T3-095)?
• Varies: From a bare 'what is r/place?' to a full account of the five-minute rule and subs planning pictures together.
• Is not: A post giving the room's coordinates and colour template (T3-070).
• Exemplars: "It's basically a subreddit where you can place one pixel every five minutes. Lots of subreddits are working together and make plans to get everyone to create a certain image." (leafs c0212); "You have to click a color square at the bottom and then pick a pixel." (virginiatech c0013); "Can I ask wtf is r/place and why is it popular all of a sudden?" (baylor c0012)

T3-018 decoding the finished picture's details

Members work out or explain what a particular picture or detail on the canvas shows, means or refers to. Floor: 2007scape and completeanarchy, unlike in size (2007scape holds 26,282 items in the window and completeanarchy 1,305, over twice as many).

• Must show: A particular image or detail decoded: what a reference means, whose character a figure is, what a colour or added piece says, what an image reads as.
• Must not show: The event as a whole explained (T3-016); neighbouring pictures named or admired with no meaning worked out (T3-052); the work's history told (T3-073).
• Decide when both: A detail decoded inside a celebration: T3-009 when the work is celebrated, T3-018 added when the decoding has concepts of its own.
• Against T3-016: Is a particular picture's meaning worked out (T3-018), or the event as a whole explained (T3-016)?
• Against T3-052: Is a detail's meaning worked out (T3-018), or a neighbouring picture noticed, named or admired (T3-052)?
• Against T3-073: Is what a detail means explained (T3-018), or what happened to the work told (T3-073)?
• Against T3-019: Is the whole finished picture decoded (T3-018), or the kindred rooms' marks counted (T3-019)?
• Varies: From a one-line note that a label is a fraternity joke to an argument over what a parrot's added cap says about its politics.
• Is not: A member listing the subs next to the room's mark (T3-052).
• Exemplars: "A q p w is something you'd type into the game chat one after another. The q p and w line up to make a penis shape." (2007scape c0858); "The broke phi broke fraternity (a reference to late reg.)" (sixers c0129); "but then somebody gave her Bookchin cap that made her overall colour scheme YPG/J-like, so she probably converted into the libertarian municipalism." (completeanarchy c0281)

T3-031 playing the room's in-jokes

Members play the room's own memes, catchphrases and running jokes in the canvas talk. Floor: paragon and Lugarix, unlike in size (paragon holds 7,305 items in the window and Lugarix 4, over twice as many).

• Must show: The room's own humour carried into canvas talk: a catchphrase, a running meme, a story riff, wordplay on the fandom, jokes about what the room drew.
• Must not show: April Fools fakes the room stages (T3-001); taunts at rivals (T3-050); one chant flooding a rival's thread (T3-134); clashes retold as fandom lore (T3-135); the finished work celebrated (T3-009); the sub's ordinary talk with no canvas in it (T3-017).
• Decide when both: Celebration full of in-jokes: T3-009 when the finished work is celebrated, T3-031 added when the jokes have concepts of their own.
• Against T3-009: Is the finished work celebrated (T3-009), or the room's joke played (T3-031)?
• Against T3-001: Is a fake staged for April Fools (T3-001), or the room's running joke played (T3-031)?
• Against T3-017: Does the sub's ordinary talk go on with no canvas in it (T3-017), or is the joke played around the canvas work (T3-031)?
• Against T3-050: Is a rival mocked (T3-050), or the room's own joke played among its members (T3-031)?
• Against T3-135: Is a canvas clash retold as fandom story (T3-135), or the room's joke played with no clash told (T3-031)?
• Against T3-053: Is the room's chant played in replies (T3-031), or spelled across the titles of many posts (T3-053)?
• Against T3-064: Is the in-joke played inside the room (T3-031), or taken out to other subs (T3-064)?
• Against T3-134: Is the refrain played among the room's members (T3-031), or used to flood a rival's thread (T3-134)?
• Against T3-156: Does a canvas detail become the room's sign (T3-156), or is the room's existing joke played (T3-031)?
• Against T3-174: Is the joke the faction's colour cult (T3-174), or any running in-joke of the room (T3-031)?
• Against T3-192: Is the joke played by damaging the work (T3-192), or told in talk (T3-031)?
• Varies: From a single catchphrase repeated under a post to a story riff that runs through a whole thread.
• Is not: A thread of 'we did it' posts celebrating the finished logo (T3-009).
• Exemplars: "Now the void seeks to return to the past, and undo the future that is AKU." (samuraijack c0318); "Before Monolith he could tank all five enemies and an inhibitor by himself! Buff Iggy!" (paragon c0082); "Frank Ocean Blonde??? That's independent!" (indieheads c0087)

T3-037 arguing the canvas's worth

Members argue whether the canvas, its fights or the time spent on it are worth anything. Floor: vegan and serbia, unlike in size (vegan holds 7,616 items in the window and serbia 2,621, over twice as many).

• Must show: The canvas weighed as a whole: a waste of time, stupid, pointless; or fun, art, a social experiment worth doing; a bare dismissal of a call to place.
• Must not show: Complaints that canvas posts crowd the sub (T3-075); the room's own showing questioned (T3-098); what working together meant (T3-157).
• Decide when both: A dismissal of the canvas inside a complaint about posts: T3-075 when the posts are the target, T3-037 when the canvas itself is.
• Against T3-075: Is the canvas itself judged worthless or worthwhile (T3-037), or are its posts objected to in the sub (T3-075)?
• Against T3-098: Is the canvas weighed as a whole (T3-037), or the room's showing on it questioned (T3-098)? A bare dismissal of a call, with nothing said about the room's own showing, is T3-037.
• Against T3-157: Is the canvas's worth argued (T3-037), or what working together meant reflected on (T3-157)?
• Against T3-016: Is it argued whether the canvas is worth anything (T3-037), or explained what it is (T3-016)?
• Against T3-027: Is the canvas's worth argued (T3-037), or the fairness of its scripts (T3-027)?
• Against T3-085: Is the whole canvas judged (T3-037), or nations' flags against the room's art (T3-085)?
• Varies: From 'a weird waste of time on nothing' to defending the canvas as an art project and once-a-year fun.
• Is not: A member asking that canvas posts go into one megathread (T3-075).
• Exemplars: "This subreddit is filled with redditards ready to waste a weird amount of time on nothing." (korea c0139); "Graffiti is defacement of someone else's property. You, however, participated in an art project." (vegan c0369); "Ceo Reddit se zajebava jednom u godini, i ti sad ulećeš sa nekim kmečanjem." (serbia c0097)

T3-052 remarking on neighbouring pictures

Members remark among themselves on the pictures beside or around their own mark. Floor: roosterteeth and yumenikki, unlike in size (roosterteeth holds 3,628 items in the window and yumenikki 142, over twice as many).

• Must show: Pictures around the room's mark noticed: neighbours named, asked about, liked or mocked; what appeared next to the mark pointed out.
• Must not show: A message sent to another room (T3-122); a detail's meaning worked out (T3-018); the room's own mark found placed (T3-082); a border settled (T3-010).
• Decide when both: Remarks on neighbours in a celebration: T3-009 when the work is celebrated, T3-052 added when the neighbours have concepts of their own.
• Against T3-122: Do members remark on neighbouring pictures among themselves (T3-052), or send a message to another room (T3-122)?
• Against T3-018: Is a neighbouring picture noticed or named (T3-052), or its meaning worked out (T3-018)?
• Against T3-082: Is another picture remarked on (T3-052), or the room's own mark found already placed (T3-082)?
• Against T3-010: Is a neighbour remarked on (T3-052), or a border with it settled (T3-010)?
• Against T3-019: Are pictures beside the mark remarked on (T3-052), or kindred rooms' marks across the canvas tallied (T3-019)?
• Varies: From a one-line question about the figure next to the room's character to a full map of the neighbours on every side.
• Is not: A room posting a greeting to the sub beside its mark (T3-122).
• Exemplars: "Who's the girl next to Madotsuki at r/place?" (yumenikki c0028); "I was so happy when I saw this next to Rick!" (roosterteeth c0122); "North West: r/uvic & r/simonfraser & r/UBC & r/japan & r/ShawnHate & r/SS13" (zootopia c0180, rivals c0177 c0174 c0179)

T3-057 remaking canvas art elsewhere

Members remake the canvas work or its fights in other media: Minecraft, LEGO, fan art, wallpapers, memes. Floor: minecraft and animalcrossing, unlike in size (minecraft holds 6,314 items in the window and animalcrossing 991, over twice as many).

• Must show: Canvas work or the canvas fight carried into another medium: rebuilt in a game, drawn as fan art, made into wallpapers, memes or copypasta, a design inspired by a canvas picture.
• Must not show: The work kept as it was in screenshots or timelapses (T3-105); the mark adopted as the room's emblem (T3-156); the work carried to a successor canvas (T3-054).
• Decide when both: A remake shared as a keepsake: T3-057 when the new medium is the point, T3-105 when the record of the work is.
• Against T3-105: Is the work kept as it was (T3-105), or remade in another medium (T3-057)?
• Against T3-156: Is the mark adopted as the room's emblem (T3-156), or remade in another medium (T3-057)?
• Against T3-054: Is the work carried to another canvas of the same kind (T3-054), or into another medium (T3-057)?
• Against T3-131: Is the work remade for its own sake (T3-057), or sold (T3-131)?
• Against T3-148: Is art the canvas never held imagined (T3-148), or the work that stood remade elsewhere (T3-057)?
• Varies: From one member's wallpaper of the room's spot to the whole canvas rebuilt block by block in Minecraft.
• Is not: A timelapse of the room's spot shared after the close (T3-105).
• Exemplars: "I recreated the entire /r/place in Minecraft (Download in comments!)" (minecraft c0188, rivals c0173 c0243); "Made some wallpapers from our spot on /r/place!" (touhou c0206, rivals c0225); "The r/prequelmemes drawing on r/place inspired me" (animalcrossing c0112)

T3-112 entering the work in atlases

Members get the room's work entered in a shared atlas, wiki or list of canvas works. Floor: stevenuniverse and redpandas, unlike in size (stevenuniverse holds 5,907 items in the window and redpandas 79, over twice as many).

• Must show: The room's work entered in an atlas, wiki or list of the canvas: asking someone to add it, writing the entry, finding it listed.
• Must not show: The room's own screenshots or timelapses (T3-105); credit given to the makers within the room (T3-043).
• Decide when both: An atlas entry shared with screenshots: T3-112 when the entry is the subject, T3-105 when the screenshots are.
• Against T3-105: Is the work kept in the room's own screenshots or timelapses (T3-105), or entered in a shared atlas or wiki (T3-112)?
• Against T3-043: Are the makers credited within the room (T3-043), or the work entered in a shared list (T3-112)?
• Varies: From a request that someone add the room to a wiki to a written atlas entry with its credits.
• Is not: A member posting a timelapse of the room's mark (T3-105).
• Exemplars: "Someone should probably add AOE to: https://www.erwinolie.nl/place/doku.php" (aoe2 c0208); "There's a project going on at r/placeatlas to preserve the artwork at the place." (stevenuniverse c0489); "We are in the unofficial wiki too." (redpandas c0063)

T3-127 seeking the creators' notice

Members hope or ask that the fandom's creators, streamer, team or staff notice the canvas work, and celebrate when they do. Floor: sakuragakuin and TeamDignitas, unlike in size (sakuragakuin holds 660 items in the window and TeamDignitas 66, over twice as many).

• Must show: The notice of the people the room is about sought or celebrated: showing the work to the staff, waiting for the streamer's reaction, 'they noticed us'.
• Must not show: The creator's wishes followed (T3-197); press coverage (T3-147); canvas visitors led to the sub (T3-044).
• Decide when both: A creator's notice inside a celebration: T3-009 when the work is celebrated, T3-127 added when the notice has concepts of its own.
• Against T3-197: Is the creator's notice sought (T3-127), or the creator's wishes followed (T3-197)?
• Against T3-147: Is the notice sought from the fandom's own creators (T3-127), or from the press (T3-147)?
• Against T3-044: Is the notice of the creators sought (T3-127), or are canvas visitors led into the sub (T3-044)?
• Varies: From hoping a streamer reacts on stream to a team account noticing the logo.
• Is not: Members keeping the author's name off the canvas as the author asked (T3-197).
• Exemplars: "Let the meme stay alive, let's see summit's reaction to this" (Summit1G c0038); "Can we show this to the staff room-teachers on Twitter?" (sakuragakuin c0035, rivals c0036); "They noticed us!!!!!!!" (TeamDignitas c0036)

T3-131 arguing over selling canvas art

Members argue over someone selling prints, posters or templates of the shared canvas work. Floor: kanye and heyyea, unlike in size (kanye holds 4,101 items in the window and heyyea 55, over twice as many).

• Must show: Sale of the canvas work argued: accusations of profiting from others' work, defences of the price, giveaways offered in answer, questions why anyone would pay.
• Must not show: Prizes for helpers (T3-159); the work kept as keepsakes with no sale (T3-105, T3-057).
• Decide when both: A sale answered with a giveaway: T3-131; prizes offered to those who placed: T3-159.
• Against T3-159: Is a sale of the work argued over (T3-131), or helpers rewarded with prizes (T3-159)?
• Against T3-057: Is the work remade for its own sake (T3-057), or sold (T3-131)?
• Against T3-105: Is the sale of prints or templates of the work argued (T3-131), or the work saved as it stood with no sale (T3-105)?
• Varies: From a plug for merchandise to a thread calling the seller a thief.
• Is not: A room giving a prize to its most active placer (T3-159).
• Exemplars: "You're profiting from the work of others, by definition, you are a thief." (donaldglover c0141, rivals c0139); "this is wack you're taking the work of multiple communities, printing it, and selling it back to them." (kanye c0445, rivals c0433 c0434); "Honest question, why would you need to buy the template?" (heyyea c0005)

T3-147 sharing the work's press coverage

Members share or remark on press, news or viral coverage that showed the room's work. Floor: suomi and AcePlace, unlike in size (suomi holds 5,336 items in the window and AcePlace 601, over twice as many).

• Must show: Coverage of the work by the press or a viral page shared or remarked: an article screenshot, a reporter teased, a story that featured the flag.
• Must not show: The fandom's creators noticing (T3-127); the finished work celebrated with no coverage (T3-009).
• Decide when both: Coverage shared in a celebration: T3-009 when the work is celebrated, T3-147 added when the coverage has concepts of its own.
• Against T3-127: Is the coverage by the press (T3-147), or the notice of the fandom's own creators (T3-127)?
• Against T3-009: Is the finished work celebrated (T3-009), or its coverage shared (T3-147)?
• Against T3-164: Is visibility felt on the canvas (T3-164), or press coverage shared (T3-147)?
• Varies: From pride that a story showed the flag to teasing the reporter who wrote it.
• Is not: A streamer reacting to the room's logo (T3-127).
• Exemplars: "The article with a...flattering title" (starlightstage c0122, rivals c0115); "Asexual pride featured on a story about /r/place!" (AcePlace c0041); "Hiljainen uutispäivä, kun Henrik Kärkkäisellä on aikaa katsella työaikana Kaarle Kustaan viiksien kasvamista redditissä" (suomi c0258)

G21 after the canvas closed

T3-009 celebrating the finished work

Members mark the room's own finished or nearly finished work as achieved: we did it, pride, congratulations, the final image. Floor: indieheads and crystalclear, unlike in size (indieheads holds 5,817 items in the window and crystalclear 18, over twice as many).

• Must show: The room's work marked as achieved: 'we did it', pride, congratulations, a final image posted as done, the work said to have lasted to the end.
• Must not show: Victory over rivals (T3-154); the makers credited by name or part (T3-043); allies thanked (T3-072); what working together meant (T3-157); the mark announced as up while the work goes on (T3-026); grief for a loss (T3-029).
• Decide when both: Celebration with thanks or credit: the side with more concepts is primary. T3-043, T3-072 or T3-157 is primary when the thanks, the allies or the reflection hold more concepts than the celebrating, and is added only where its part has concepts of its own.
• Against T3-154: Is the room's own work celebrated (T3-009), or victory over a rival claimed (T3-154)?
• Against T3-043: Is the work celebrated (T3-009), or its makers credited (T3-043)?
• Against T3-157: Is the finished work celebrated (T3-009), or what working together meant reflected on (T3-157)?
• Against T3-026: Is the work finished and celebrated (T3-009), or the mark announced as being up (T3-026)?
• Against T3-029: Is the work celebrated (T3-009), or its loss mourned (T3-029)?
• Against T3-003: Is the finished work celebrated (T3-009), or one's own part in it told (T3-003)?
• Against T3-031: Is the finished work celebrated (T3-009), or the room's joke played (T3-031)?
• Against T3-038: Is the work under way (T3-038), or finished and celebrated (T3-009)?
• Against T3-104: Is the work going on (T3-104), or done and celebrated (T3-009)?
• Against T3-105: Is the work celebrated (T3-009), or saved as a record (T3-105)?
• Against T3-117: Is the end marked (T3-117), or the work celebrated (T3-009)?
• Against T3-145: Is the finished work celebrated (T3-009), or national belonging voiced (T3-145)?
• Against T3-147: Is the finished work celebrated (T3-009), or its coverage shared (T3-147)?
• Against T3-164: Is the work celebrated (T3-009), or support felt through it (T3-164)?
• Against T3-186: Is the work celebrated online (T3-009), or a meeting in person proposed (T3-186)?
• Against T3-072: Is the room's own finished work celebrated (T3-009), or other rooms thanked for their help (T3-072)?
• Against T3-073: Is what happened to the work told (T3-073), or the finished work celebrated (T3-009)?
• Varies: From a one-line 'we did it' to long posts with the final image, pride and thanks.
• Is not: A county room boasting that its flag outlasted a rival's (T3-154).
• Exemplars: "We did it! Place is over and our tag is on it! :D" (crystalclear c0006); "297 finished, well done ladies and gents!" (puzzleanddragons c0142); "Truly a great achievement, we should all be proud" (indieheads c0197)

T3-029 mourning the lost work

Members grieve for the room's work, or a work they cared for, once it is covered, erased or left unfinished. Floor: overwatch and duckgame, unlike in size (overwatch holds 45,381 items in the window and duckgame 130, over twice as many).

• Must show: Grief or loss voiced for a work: RIP, it's gone, very sad, the lost flag that never stops hurting.
• Must not show: Blame laid after the close (T3-058); the end of the canvas itself mourned (T3-117); what happened told without grief (T3-073); the work moved elsewhere (T3-022).
• Decide when both: Grief with blame: T3-029 when grief leads, T3-058 added when blame has concepts of its own. Grief with an account: T3-029 when grief leads, T3-073 when the account does.
• Against T3-058: Is the loss grieved (T3-029), or blame laid for it (T3-058)?
• Against T3-117: Is a work's loss grieved (T3-029), or the end of the canvas itself (T3-117)?
• Against T3-073: Is grief voiced (T3-029), or what happened told without it (T3-073)?
• Against T3-009: Is the work mourned (T3-029), or celebrated (T3-009)?
• Against T3-059: Is the loss mourned (T3-029), or is giving up urged (T3-059)?
• Against T3-148: Is art that never stood imagined (T3-148), or work that stood mourned (T3-029)?
• Against T3-160: Is a dead person honoured by the work (T3-160), or the lost work mourned (T3-029)?
• Against T3-181: Is the loss mourned (T3-029), or the effort abandoned (T3-181)?
• Against T3-183: Is the room's own lost work mourned (T3-029), or others' art the room covered (T3-183)?
• Against T3-022: Is the lost work grieved (T3-029), or moved or restarted elsewhere (T3-022)?
• Varies: From a bare 'RIP' to a long lament for a lost flag and every lost fight.
• Is not: A member saying the canvas is over and it was fun (T3-117).
• Exemplars: "RIP the overwatch logo on r/place" (overwatch c1065); "RIP in peace, sombrero duck. You died too young." (duckgame c0052); "the flag we've lost, every fight we've lost. never stop hurting" (indonesia c0203)

T3-043 crediting who made the work

Members thank or credit the people who made, defended or perfected the work, or claim their own part in it. Floor: DestinyTheGame and hsv, unlike in size (DestinyTheGame holds 45,483 items in the window and hsv 229, over twice as many).

• Must show: Credit given for the work: thanks to those who helped, named makers, a member claiming a change they made, disputes over who made it.
• Must not show: Another room thanked as an ally (T3-072); the work celebrated with no one credited (T3-009); the work entered in an atlas (T3-112).
• Decide when both: Credit and celebration together: the side with more concepts is primary, the other added only where its part has concepts of its own; a thread whose concepts are mostly thanks to the makers is T3-043.
• Against T3-072: Are the room's own makers and helpers credited (T3-043), or another room thanked as an ally (T3-072)?
• Against T3-009: Are the makers credited (T3-043), or the work celebrated (T3-009)?
• Against T3-003: Is credit given or claimed after the work (T3-043), or one member's placing reported as it is done (T3-003)?
• Against T3-104: Are builders encouraged (T3-104), or the makers credited (T3-043)?
• Against T3-112: Are the makers credited within the room (T3-043), or the work entered in a shared list (T3-112)?
• Against T3-159: Is credit given in words (T3-043), or a prize given (T3-159)?
• Varies: From a general 'thanks to everyone who helped' to a dispute over who drew a figure.
• Is not: A room thanking a neighbouring room that defended its logo (T3-072).
• Exemplars: "I'd like to thank everyone who participated in creating, defending, and perfecting our Destiny Tricorn emblem in /r/place." (DestinyTheGame c0223); "i have to say i was the one that changes it from CS:6O to CS:GO shameless bragging" (globaloffensive c1108); "Thanks to everyone who helped, you know who you are!" (hsv c0092)

T3-054 carrying work to new canvases

Members take up or turn down a later canvas: rebuilding there, planning for next time, or declining to start again. Floor: terraria and CelticFc, unlike in size (terraria holds 1,747 items in the window and CelticFc 62, over twice as many).

• Must show: A later canvas answered either way: the work rebuilt on a clone site, members invited to one, plans for the next canvas, or a refusal to start again.
• Must not show: The sub given a new purpose with no canvas (T3-111); the work remade in another medium (T3-057); the end marked with a bare hope it returns (T3-117); a new spot on the same canvas after a loss (T3-022).
• Decide when both: A sub's future that includes a new canvas: T3-054 when the canvas is the plan, T3-111 when the sub's purpose is.
• Against T3-111: Is the work carried to another canvas (T3-054), or the sub given a new purpose (T3-111)?
• Against T3-057: Is the work carried to another canvas (T3-054), or remade in another medium (T3-057)?
• Against T3-117: Is a later canvas taken up, planned or turned down (T3-054), or the end marked with a hope the event returns (T3-117)?
• Against T3-022: Does the work move to a new spot on the same canvas (T3-022), or to another canvas (T3-054)?
• Against T3-148: Is missed art imagined (T3-148), or a later canvas planned (T3-054)?
• Varies: From a one-line link to a clone site to a room rebuilding its art there alone, and from eager plans to a refusal to start again.
• Is not: A room moving its logo to new coordinates after losing its spot (T3-022).
• Exemplars: "this website is essentially r/place v2, and has bot protection, I built night's edge in it by myself" (terraria c0146); "we can do this again..http://pxls.space/" (aoe2 c0160); "We should see about doing the Celtic logo next year." (CelticFc c0018)

T3-072 thanking the room's allies

Members thank other rooms that helped and tell the story of who stood with the room. Floor: mylittlepony and wales, unlike in size (mylittlepony holds 3,264 items in the window and wales 530, over twice as many).

• Must show: Another room thanked for help, or the alliance's story told: which rooms stood with the room, who tried to save the work, the alliance that made it.
• Must not show: The room's own makers credited (T3-043); ties proposed beyond the canvas (T3-158); greetings with no help behind them (T3-122); an alliance formed for a fight (T3-150).
• Decide when both: Thanks to allies inside a celebration: the side with more concepts is primary, T3-009 when the celebrating holds more; the other added only where its part has concepts of its own.
• Against T3-043: Is another room thanked as an ally (T3-072), or the room's own makers credited (T3-043)?
• Against T3-158: Are allies thanked for the canvas (T3-072), or ties proposed beyond it (T3-158)?
• Against T3-122: Is help thanked (T3-072), or a greeting sent with no help behind it (T3-122)?
• Against T3-150: Is an alliance formed for the fight (T3-150), or thanked and told afterwards (T3-072)?
• Against T3-009: Is the room's own finished work celebrated (T3-009), or other rooms thanked for their help (T3-072)?
• Against T3-157: Are allies thanked (T3-072), or the meaning of working together reflected on (T3-157)?
• Against T3-104: Are those placing cheered on while the work goes on (T3-104), or other rooms thanked for their help (T3-072)?
• Against T3-159: Are helpers given a prize (T3-159), or other rooms thanked with no prize (T3-072)?
• Varies: From one line of thanks to a named sub to the full story of a two-nation alliance.
• Is not: A thread thanking the members who placed the room's logo (T3-043).
• Exemplars: "Also, special thanks go out to the people at /r/SaveDashie !" (mylittlepony c0223); "With our alliance with r/FaroeIslands, we did it! Well done everyone!" (wales c0038); "Our creeper didn't get totally over-ran, thanks to you all (mindcrack and Dutch) here for trying to save him in the final hours." (mindcrack c0133)

T3-073 reporting how the work fared

Members report what happened to the work, live or after the close: what was covered, moved, repaired or survived. Floor: nintendo and toolband, unlike in size (nintendo holds 7,065 items in the window and toolband 1,155, over twice as many).

• Must show: What happened to the work told: live reports of changes and attacks, what survived, what was moved and why, the story of its fights afterwards.
• Must not show: Progress of the first build (T3-038); grief (T3-029); blame (T3-058); a celebration (T3-009); fights retold as fandom lore (T3-135); what a detail means (T3-018).
• Decide when both: An account with grief or celebration: the side with more concepts is primary.
• Against T3-038: Is the first build's progress reported (T3-038), or what happened to the work once it stood (T3-073)?
• Against T3-021: Is what happened told (T3-073), or the work watched and repaired (T3-021)?
• Against T3-029: Is the account plain (T3-073), or grief voiced (T3-029)?
• Against T3-135: Is the work's history told plainly (T3-073), or as fandom lore (T3-135)?
• Against T3-009: Is what happened to the work told (T3-073), or the finished work celebrated (T3-009)?
• Against T3-018: Is what a detail means explained (T3-018), or what happened to the work told (T3-073)?
• Against T3-058: Is what happened to the work told (T3-073), or a named room blamed for its loss after the close (T3-058)?
• Varies: From a live report that a figure is being turned into another to a written legacy of the work after the close.
• Is not: A member posting the coordinates of the half-built logo (T3-038).
• Exemplars: "The Mario on Rainbow Road has turned into Luigi and is currently being turned into Waluigi." (nintendo c0125); "I know, we had to move it. I spent about 8 hours making that one." (roosterteeth c0130); "It'a a part of the story. We literally had to work to do this." (toolband c0212)

T3-105 saving screenshots and timelapses

Members save or share the work as it stood: screenshots, timelapses, final images, requests to save it before it changes. Floor: placehearts and AprilKnights, unlike in size (placehearts holds 1,582 items in the window and AprilKnights 218, over twice as many).

• Must show: The work kept as it was: screenshots, timelapses, final images posted as records, requests that someone save it.
• Must not show: The work remade in another medium (T3-057); entered in an atlas (T3-112); adopted as the sub's emblem (T3-156); celebrated (T3-009).
• Decide when both: A final image posted in celebration: T3-009 when the celebration leads, T3-105 added when the record has concepts of its own.
• Against T3-057: Is the work kept as it was (T3-105), or remade in another medium (T3-057)?
• Against T3-112: Is the work kept in the room's own screenshots or timelapses (T3-105), or entered in a shared atlas or wiki (T3-112)?
• Against T3-156: Is the work kept as a record (T3-105), or put on the sub's banner, flair or sidebar (T3-156)?
• Against T3-009: Is the work celebrated (T3-009), or saved as a record (T3-105)?
• Against T3-077: Is the timelapse used to keep the work (T3-105), or the work designed to move in it (T3-077)?
• Against T3-100: Is the canvas work saved in screenshots and timelapses (T3-105), or an April Fools change kept in use (T3-100)?
• Against T3-131: Is the sale of prints or templates of the work argued (T3-131), or the work saved as it stood with no sale (T3-105)?
• Varies: From a request to screenshot the logo before night to a timelapse of the work from its first pixel.
• Is not: A Minecraft rebuild of the canvas (T3-057).
• Exemplars: "can someone screenshot it in case it gets removed overnight?" (nbaspurs c0205); "Time lapse video of Placehearts from the beginning" (placehearts c0253); "Screenshot of our logo and The Button in mint condition" (AprilKnights c0075)

T3-111 repurposing the canvas sub

Members decide what the sub or chat made for the canvas becomes once the canvas closes. Floor: TheFarLeftSide and loliconsunite, unlike in size (TheFarLeftSide holds 3,737 items in the window and loliconsunite 252, over twice as many).

• Must show: The canvas sub's or chat's future argued or decided: kept for another purpose, kept as a community, asked whether it will survive.
• Must not show: The work carried to a new canvas (T3-054); ties with other rooms proposed (T3-158); a canvas sub opened (T3-090).
• Decide when both: A sub's future that includes a new canvas: T3-054 when the canvas is the plan, T3-111 when the sub's purpose is.
• Against T3-054: Is the sub given a new purpose (T3-111), or the work carried to another canvas (T3-054)?
• Against T3-090: Is a sub opened for the canvas (T3-090), or its use after the canvas decided (T3-111)?
• Against T3-158: Is the room's own sub repurposed (T3-111), or ties with another room proposed (T3-158)?
• Varies: From a question whether the sub will survive to a vote to keep it for political discussion.
• Is not: A room inviting its members onto a clone canvas (T3-054).
• Exemplars: "Can we keep this subreddit post-place for united leftist discussion?" (TheFarLeftSide c0212, rivals c0357 c0637); "I vote we stay an sub, even though r/place has ended" (farmcarrots c0181); "Will this subreddit stay alive now that r/place has ended?" (loliconsunite c0080)

T3-117 marking the canvas's end

Members register that the canvas has ended: it's over, regret, signing off, hoping it returns. Floor: spacexmasterrace and earthbound, unlike in size (spacexmasterrace holds 1,463 items in the window and earthbound 547, over twice as many).

• Must show: The end of the canvas registered: 'place is over', regret at the end, signing off, a hope that it returns.
• Must not show: The room's work mourned (T3-029); the work celebrated (T3-009); a later canvas taken up or planned (T3-054).
• Decide when both: The end marked in a celebration: T3-009 when the work is celebrated, T3-117 added where the end has concepts of its own.
• Against T3-029: Is the end of the canvas marked (T3-117), or a work's loss grieved (T3-029)?
• Against T3-009: Is the end marked (T3-117), or the work celebrated (T3-009)?
• Against T3-054: Is the end marked with a hope it returns (T3-117), or a later canvas taken up, planned or turned down (T3-054)?
• Varies: From a bare 'it's over' to a sign-off hoping the event comes back next April.
• Is not: A room's lament that its logo was covered (T3-029).
• Exemplars: "Unfortunately, place is now over." (spacexmasterrace c0114); "Oh... well, it's over. It's been fun you guys o7" (earthbound c0069); "Maybe next April 1 again? :)" (sakuragakuin c0070)

T3-148 imagining art the canvas missed

Members imagine art the canvas never held: what the work was meant to look like, what they would have drawn. Floor: zelda and miamidolphins, unlike in size (zelda holds 9,309 items in the window and miamidolphins 1,351, over twice as many).

• Must show: Art that did not reach the canvas imagined: the work as it was supposed to look, a design shown too late, what might have been.
• Must not show: Plans for a later canvas (T3-054); grief for work that stood (T3-029); the work that stood remade elsewhere (T3-057).
• Decide when both: Imagined art with grief: T3-148 when the missed art is described, T3-029 when grief leads.
• Against T3-054: Is missed art imagined (T3-148), or a later canvas planned (T3-054)?
• Against T3-029: Is art that never stood imagined (T3-148), or work that stood mourned (T3-029)?
• Against T3-057: Is art the canvas never held imagined (T3-148), or the work that stood remade elsewhere (T3-057)?
• Varies: From a joke that the mushroom guys never got a spot to an edited final image showing the work as planned.
• Is not: Plans for what to build on the next canvas (T3-054).
• Exemplars: "I just took the final image and photoshopped what our 'place" was supposed to look like." (frc c0149); "Damn, that is pretty amazing. What if we would of got this on /r/place lol" (zelda c0198); "Imagine if we had left it as Sushi..." (miamidolphins c0155)

T3-156 adopting the mark as emblem

Members take the canvas mark into the sub's identity: banner, sidebar, flair, avatar or a room joke. Floor: bakchodi and TreePlace, unlike in size (bakchodi holds 2,741 items in the window and TreePlace 31, over twice as many).

• Must show: The canvas mark taken into the sub: a banner, header, sidebar, flair, emoji or avatar from the work, or a detail of the final image made the room's sign.
• Must not show: Screenshots or timelapses kept (T3-105); the work remade in another medium (T3-057); the room's existing joke played (T3-031).
• Decide when both: A banner request with a screenshot: T3-156 when the sub's look is the point, T3-105 when the record is.
• Against T3-105: Is the mark put on the sub's banner, flair or sidebar (T3-156), or kept as a record (T3-105)?
• Against T3-057: Is the mark adopted as the sub's sign (T3-156), or remade in another medium (T3-057)?
• Against T3-031: Does a canvas detail become the room's sign (T3-156), or is the room's existing joke played (T3-031)?
• Varies: From a request for a commemorative flair to the finished image set as the sub's header.
• Is not: A timelapse of the logo shared after the close (T3-105).
• Exemplars: "REPLACE THE CSS BANNER WITH COMPLETE ONE" (touhou c0148); "Can we get it on the banner pls, or the side bar?" (zootopia c0163); "we need a special flair to commemorate this event" (bakchodi c0241)

T3-157 reflecting on working together

Members say what the shared effort meant: strangers cooperating, the community as the point. Floor: wholesomememes and xcom, unlike in size (wholesomememes holds 6,915 items in the window and xcom 1,535, over twice as many).

• Must show: What working together meant: cooperation with strangers, the community effort as what made the work, redditors creating amid chaos.
• Must not show: The work celebrated (T3-009); allies thanked (T3-072); the canvas's worth argued (T3-037); support felt by a group (T3-164).
• Decide when both: Reflection inside a celebration: the side with more concepts is primary, T3-009 when the celebrating holds more; the other added only where its part has concepts of its own.
• Against T3-009: Is the finished work celebrated (T3-009), or what working together meant reflected on (T3-157)?
• Against T3-072: Are allies thanked (T3-072), or the meaning of working together reflected on (T3-157)?
• Against T3-037: Is the canvas's worth argued (T3-037), or what working together meant reflected on (T3-157)?
• Against T3-164: Is the meaning of working together reflected on (T3-157), or support and visibility felt by the group (T3-164)?
• Varies: From a line that the community effort made the flag to an essay on strangers linked by the event.
• Is not: A room's 'we did it' post with the final image (T3-009).
• Exemplars: "I still feel like a good outcome of the event is people talking to and cooperating with people they'd otherwise have no reason to." (xcom c0063); "The community effort is what made it amazing." (pakistan c0186); "When redditors come together to create something amidst chaos" (wholesomememes c0010)

T3-158 proposing ties beyond the canvas

Members carry a tie with another room past the canvas: trading recommendations, crossovers, sister cities, exchanges. Floor: parahumans and rhythmheaven, unlike in size (parahumans holds 1,829 items in the window and rhythmheaven 99, over twice as many).

• Must show: A tie with another room proposed or kept beyond the canvas: trading each other's games or books, crossover threads, cultural exchanges, friendships kept.
• Must not show: Allies thanked for the canvas (T3-072); the room's own sub repurposed (T3-111); greetings with nothing proposed (T3-122).
• Decide when both: Thanks to allies with a proposal: T3-072 when the thanks lead, T3-158 added when the proposal has concepts of its own.
• Against T3-072: Are allies thanked for the canvas (T3-072), or ties proposed beyond it (T3-158)?
• Against T3-111: Is a tie with another room proposed (T3-158), or the room's own sub repurposed (T3-111)?
• Against T3-122: Is a greeting sent (T3-122), or a tie beyond the canvas proposed (T3-158)?
• Against T3-186: Is a tie between rooms proposed (T3-158), or members invited to meet in person (T3-186)?
• Varies: From trading recommendations between two fandoms to finding that two cities are already sister cities.
• Is not: A thank-you to the neighbour that helped hold the logo (T3-072).
• Exemplars: "may ours try your game and yours try ours." (rhythmheaven c0075, rivals c0079); "Annapolis is actually already sister cities with Karlskrona, Sweden" (maryland c0273); "Came here on recommendation from /r/mylittlepony." (parahumans c0125)

T3-164 feeling supported through the canvas

Members find support, visibility or comfort through the canvas: a flag that says 'we are here', not being alone. Floor: asktransgender and AcePlace, unlike in size (asktransgender holds 6,413 items in the window and AcePlace 601, over twice as many).

• Must show: Support or visibility felt through the canvas: a group's flag as proof it is seen, comfort in hard times, not being alone.
• Must not show: What working together meant in general (T3-157); the work celebrated (T3-009); press coverage (T3-147).
• Decide when both: Visibility felt in a celebration: T3-009 when the work is celebrated, T3-164 added where the support has concepts of its own.
• Against T3-157: Is support or visibility felt by the group (T3-164), or the meaning of working together reflected on (T3-157)?
• Against T3-009: Is the work celebrated (T3-009), or support felt through it (T3-164)?
• Against T3-147: Is visibility felt on the canvas (T3-164), or press coverage shared (T3-147)?
• Varies: From trans and asexual members seeing their flag hold to a British member cheered amid Brexit by an alliance.
• Is not: A thread on how strangers cooperated on the canvas (T3-157).
• Exemplars: "Small victories are some of the best you can have. We have shown in some small way that we are here." (asktransgender c0139); "been rather depressed about brexit or the shit surrounding it. I just wanted to say seeing this tonight cheered me up immensely" (italy c0267); "the most space I've seen the Ace community take up on a public space" (AcePlace c0065)

T3-186 celebrating the feat in person

Rare tier. A member invites others to meet in person to celebrate the canvas work.

• Must show: An invitation to meet offline, for dinner, a drink or a barbecue, to celebrate what the room made.
• Must not show: Celebration online (T3-009); ties proposed between rooms (T3-158).
• Decide when both: An invitation inside a celebration: T3-186 when the meeting is proposed, T3-009 when it is not.
• Against T3-009: Is the work celebrated online (T3-009), or a meeting in person proposed (T3-186)?
• Against T3-158: Is a tie between rooms proposed (T3-158), or members invited to meet in person (T3-186)?
• Varies: One room's case: an invitation to dinner, beer or a barbecue.
• Is not: A thank-you post with the final image (T3-009).
• Exemplars: "If anyone would like to go out for dinner/beer or BBQ you should message me! It would be great to celebrate this feat in Person!" (SwissNeutralityZone c0108)

Three rooms first (stage C2, section 4), written at C2a-01

Each room is told from its own concepts, forest and timeline (mem.py room --no-canvas --blind, forest --blind, when), with no theme above the second tier. The rooms were drawn by the rules in notes-C2.md before any was opened. Hours are hours since the canvas opened; quotes are participants' words through cite.py.

ubc: the ordinary room

r/ubc is a university room of 1,475 items, 106 of them coded. Its April Fools joke ran beside the canvas all week: the sub was dressed as its rival, SFU, and members played along with fake campus stories and identities (t02, 31 concepts, h14 to h81).

The canvas work began with a question at h3.8 ("do you guys wanna get the UBC logo on /r/place?") and a second at h17.4: "Who wants to help make the UBC logo on /r/place?" [ubc/c0013]. The answers were small and practical. One member offered help if someone mapped the logo, another made a 21-by-30 pixel map, a third brought a logo from a Discord user, and a fourth set the anchor: "I wss thinking 820,322 as top left most red square" [ubc/c0005, h25.1]. Calls followed through the second day: "LETS MAKE THE CREST" (h39.6), a call to complete the Cairn (h32.3), "We did it!" (h35.7) and "We did it Reddit!" (h44.2).

From h40 the work had neighbours. A post from r/UofT declared war (h40.6). r/Thailand asked to make peace with the logo (h45.2). At h49 to h53, members called for help as the crest was attacked and as Polandball claimed the land. The room then drew lines rather than fights. Asked to recolour a neighbour's letters, a member refused: "No, they didn't mess with us and we won't mess with them." [ubc/c0065, h55.8]. To Thailand: "We defined our minimized border as per agreement, just draw around the black line." [ubc/c0076, h59.2], and later "We have an agreement with them, we won't mess with each other." [ubc/c0084, h64.5]. One member traded care for care: "I'm helping preserve the Thai flag. Just don't touch our crest either." [ubc/c0078, h61.2].

In the last day the room kept the crest by hand and by machine. A script was offered at h58.1 and reported working; members dug up spare accounts; one wrote "I got three accounts going right now, and an overdue essay I'm prioritizing over. We. Cannot. Give. In." [ubc/c0090, h65.7]. Help went out too, to SFU, UVic and r/tokyo, "when you can spare a pixel". At the close a member was one minute short of a repair: "Fuck, I was just placing a pixel to fix the thing. Just one minute. One measly minute." [ubc/c0099, h73.2]. The room then celebrated, renamed itself OBC in jest after the letters changed, and asked for a poster of the final canvas.

ultrahardcore: the room the scheme could not have predicted

r/ultrahardcore is a Minecraft community of 918 items, 212 coded, and its week was April Fools. From h7.7 to h40 the room was flooded with parody posts, upvote bargains ("100 UPVOTES I UPLOAD DISCOVERY SEASON 1"), mock moderation and taboo material. The recurring frame was the one-day licence: "this is the only day of the year i can post seal.mp4 please upvote" [ultrahardcore/c0011, h10.3]. 193 of its 212 coded items fall before h40 (mem.py when). Nothing in that stretch touches the canvas, except one member asking at h40 what the room had done there, and being told that a few people wrote "thicc" in a corner.

The canvas work came late, in one thread, and was over in minutes. At h57.6 a member asked: "I thought that we could think up a design to leave our mark on the place. Any suggestions?" [ultrahardcore/c0202]. Within half an hour the thread had a proposal ("Yeah, make that heart a hardcore heart" [c0204, h57.9]), a template, a member protecting an existing heart and redirecting the build, a spot at 382, 755, and an order: "That ones good. Make it completely red first." [c0209, h58.1]. One more turn followed at h59, and one at h71. There was no second call, no defence and no neighbour.

At the close the room wrote: "We almost did it! (/r/place)" [c0212, h73.1]. The author credited collaborators, recounted the unexpected closure, and took three hearts as consolation. A member who had been building elsewhere wrote: "Wish I knew you guys were doing something there. I was complete focused on touhou." [c0215, h80.4]. The form here is a play room that turned to the canvas once, late, and organized a design, a place and an order in one thread, with members who were already placing for other rooms.

day9: the room that stopped early

r/day9 is a gaming streamer's room of 361 items, 37 coded. Its coded turns run from h14.5 to h78.4, and 14 of the 37 coded items fall in the four hours from h48 (mem.py when).

A member had already started the logo: "Me and my friend Capnpie started it hours ago, for the glory of Day[9]." [day9/c0002, h14.7]. At h32 the room asked for an addition, and a member promised to maintain it. Then came neighbours. The room offered Norway terms: "We are a friendly and reasonable community. I'm sure we can come to an agreement. We only require 35x35 pixels. Maybe you could go up or down, rather than left?" [day9/c0005, h33.9]. A Crusader Kings diplomat proposed a treaty at h41.6, and a three-way proposal with Texas came at h44.1. Members cut the design to its core: "Better to focus on defending the core Day [9] TV logo and forget about "Be a better gamer"." [day9/c0014, h45.2].

The agreement broke at h48: "We had an agreement that we'd shrink it horizontally then you guys went ahead and decided you wanted a new flag where we were." [day9/c0016]. Members called for a script and posted "WE ARE BEING CONSUMED ON R/PLACE". Within two hours they chose to move: "I wanted to keep fighting for the spot we've had, but it looks like this is a losing battle. I'll help move it if we can decide on where." [day9/c0023, h49.7]. Two posts said "It has been an honour...". At h50.7 the move was made official: "It's official: we are relocating the Day9 logo to below the crusader Kings logo" [day9/c0027]. A plan and a Discord followed, and at h53.1 "The new location is finished!" [day9/c0031].

The room's last coordinating turn came there, at h53.3. It did not collapse. A member became a diplomat at h55, and at the close another recounted the week: "We successfully built "Be a Better Gamer", survived getting rofflestomped by a horde of rampaging Nordic vikings, and managed to diplomacy our way into a cozy little niche..." [day9/c0036, h74.1]. Here organizing stopped early because the second work was finished and held, not because the room gave up.