Forming: branch accounts | D5a-41

Handback, stage D5, the room forms (D5a-36 to D5a-41): a supplement to handback-D5.md

Written at D5a-41, 27 October 2026. handback-D5.md was written at D5b and covers the 35 branch accounts, the waterfall and survival; it stands unchanged. On J's word through the PI (departures.jsonl line 17), D5 ran once more, one account per room form of the six-form cut J ruled at D4a-08. The six accounts are room-form-A-account.md to room-form-F-account.md, beside the room-forms files and not in forms/ (line 18); their lines are in room-forms-D5.jsonl (6 lines: 705 rooms, 558 of them defining). The notes for the next stage are the six D5a-36 to D5a-41 sections of notes-D5.md, the last of which lists the six forms together.

The claim

The six forms are poles of a continuum, not kinds: the cut's stability on matched subsamples is about 0.21. Each gathers rooms by the part of the model they changed most, and in each the rooms' lines say that the model's order runs differently there.

• A, the terms between neighbours, with the plan announced (166 rooms). Rooms make terms at the border, and terms and plans bind only the placers they reach. A form in a weak sense.
• B, the work behind the thread (141). The chat, the scripts and raiding, held by different rooms at about chance. A grouping, not a form.
• C, the design and its marking (125). The design is settled for a time and reopened, and informed keepers refuse changes. A form in a narrow sense.
• D, keeping, with traded help and carrying on (119). Keeping is shared and checked; help is sent from surplus or owed; carrying on begins before the close and returns to the call. A form in a weak sense.
• E, the sub's April Fools play (98). The host sub's play is organized work beside the canvas; it marks where the model's scope ends. A form in a narrow sense, of the sub's play rather than of canvas organizing.
• F, the spot (56). Rooms ask for space before they build, move for the spot's reasons more than for too few hands, and build again. A form in a narrow sense, on few rooms.

The form that best supports the claim: C. One change, collective representation, is held by 97.9 per cent of its defining rooms, and its members' words show relations the model does not state.

The form that most threatens it: B. Its three signatures are held by different rooms at about chance, and no relation joins them. A cut can gather rooms that share nothing but being left over.

The condition between them is whether one change is held by nearly all of a form's defining rooms. Where it is (C 97.9, F 94.1 per cent), the form states relations. Where the signatures are held by under half each (B), the form is a list.

The return value

• Forms accounted: 6 of 6.
• Failed the form test: B, reported as a grouping.
• Names that survived the members' reading: A, B, C, E and F kept (C and E with a sharpening). D: a renaming proposal, keeping, with traded help or carrying on, because its two minor signatures are held together only at chance.
• The form whose reading disagreed most with the room models: none. In each account the room models I quoted agree with my reading of the members' lines.
• Where the uncomposed rooms sit (first-return verdicts, by the last ruling or else the readers' agreement): the one room that does not compose, r/picturegame (kind out of scope), is a thin room of E. Cannot tell: A 2, B 2, C 2, D 1, E 0, F 3; all ten are thin or core rooms.
• Arrow absences: none real. All 21 arrows are not-testable-here in every form; the largest expectation is 0.942 (form A), the smallest form's largest 0.318 (F).
• Propositions that failed against a real expectation: none. No findings.jsonl line is bounded from a form.
• Subform candidates for the next stage: A.2; B.2 and B.1.2; D.1 and D.2, with D.2.1 and D.2.2. None was cut.
• The mixture rule (logged at D5a-37): neither outcome at B, D and E; mixed at F (calls and border terms held by the same rooms, 8 against 6.2).

Survival by form (from the record, never the canvas; not compared here)

The most consequential difference between two forms

D and E. Both hold the sub's April Fools play: D's part D.2 changes keying in 66.7 per cent of its defining rooms, E in 71.4. But D.2's rooms kept their canvas work inside the play (repair work 73.8 per cent), and E's record is the play itself (repair work 32.1 per cent). D.2 lies 0.270 from D's centre and 0.611 from E's. So the frame does not decide a room's form; what the room did with its canvas work beside the frame does. The restrict sort shows the same divide from the other side: where the record holds the work, the arrow mostly fails as stated (F, 63 per cent of its lines); where the record holds the play, it most often cannot show the arrow at all (E, 37 per cent).

Licences exercised (METHOD.md)

• The path outside forms/ (departures line 18), so the stage's close-check, which reads forms/ as branch accounts, did not refuse the room-form accounts.
• The rules logged at D5a-36 and carried unchanged: thin and core rooms weigh less; representatives by distance to the centre; the split rule; the restrict sort's four classes, written to files before counting.
• The mixture rule, logged at D5a-37 and applied at B, D, E and F; d5f_mixture.py edited at D5a-41 to read a link signature, its earlier outputs unchanged in content.
• Descriptions beyond the walk, labelled so (d5f_split.py --start; the parts helpers at D and E; the propose lines read whole at E).
• At E and F the representative rule picked one room twice; three rooms were told.
• At F, rows below the table's floor reported and flagged.
• Before each account was written, its claims were checked against the sources by script and corrected (A to F: two rounds or one); after each was written, it was read whole and corrected by Edits, each logged.

Slips

Logged in the diary as they happened: Python writing a file from inside Bash, once (D5a-39); commands refused by the guard (a cut after a helper, a shell variable, one Python read at D5a-41 whose pattern the guard refused), redone without the refused form and with nothing written; a no-op shell variable at the head of a command (D5a-40); two Edits to the head in one turn (D5a-40); a count logged as 25 that was 26, corrected by an appended line (D5a-39).

The waterfall: one walk from the account to the quotes and back

Stage D5, leg D5b, 2026-10-26 UTC. The model is the one frozen at D3 (46384686…), the model every branch hangs from. The return was served at pass 15 (e15f9647…b3fecd). The two held proposals (QD4-001) are stated in full at the end of this file.

The walk goes down six steps: the account, one branch, one subform, one room's model, the room's adaptation lines and the room's quotes. At each step I say what the level adds and whether it contradicts the level above. Then I walk back up and say what each lower level does to the level above it. Last, I read the walk against prior.md's expectation of what the lower levels describe. The canvas comes after the walk, in its own section, and changes none of it (rule 7).

The rule, stated before the walk

I logged this rule in the diary before I read any of the room's files.

• The branch. Three top-level branches have subforms: F01 (five), F11 (three) and F17 (two). I take the one whose subforms together hold the largest share of its members, so that the walk passes through a subform that covers its parent. F11's subforms hold 38 of its 43 members, F17's hold 29 of 36, and F01's hold 68 of 103. The branch is F11.
• The subform. The parent's largest subform: F12, with 22 members.
• The room. The subform's member at the lower median of coded concepts. Among the 22 members the counts run from 18 (r/aeskwadraat) to 1,915 (r/theblackvoid). The lower median is r/forsen, with 114 coded concepts, against a population median of 101. I printed the sorted list before I fixed the even-count convention; the upper median would have been r/greyblob, with 115. The rule chooses neither by fit nor by size.

r/forsen is a streamer's sub. Its members built figures they named gachiGASM, monkaS and forsenE, and its room model reads these names as the room's own idiom [K04].

Down

1. The account (account.md, pass 15)

The account states the close in one paragraph. Placement stopped at hour 73. Before it, rooms celebrate and record the work, and they carry "the record on into banners, later canvases and groups announced to carry on in 113 of 145" rooms [A09, P13] (F-004). After hour 73, rooms curate the record. The account keeps the two acts apart: "Curating the record is a different act from carrying the work on into later groups [P13]."

What this level gives is a population pattern in counts. A09 is an arrow from recording (P12) to carrying on (P13). Its count is an order on the clock across rooms. It is not a cause shown inside each room. P13's own words, as stage D4 gives them, say that near the close and after it the room decides what of its effort to keep.

2. The branch: F11, carrying on as renewed work, begun before the close (43 members)

F11 shares one key: an add-step line on P13 at the fourth-order theme Transition (T4-028), one line per member. The branch adds that in these rooms carrying on is new work, not a choice about work already done. Members chose a venue, called others, posted coordinates, built, and lost or defended the work again. In 20 members it is building again on another canvas, in 10 a remake in other media, and in 7 the mark adopted into the room.

Does it contradict the account? In part. The account counts A09 as an order: the record, then carrying on. The branch's lines restrict A09 in 15 members, on the ground that no record is shown to have caused the carrying on (F11's section 7). Both can hold, since an order across rooms is not a cause inside one. But the branch gives no support for reading A09 as a mechanism. The branch's name also says more than its members show. By the first hour each key line cites, 11 of 43 members begin before the close and 32 after. F11's account proposes a renaming for that reason.

3. The subform: F12, the spine restarted on another canvas (22 members)

F12 narrows F11's key from the fourth-order theme to the third-order theme T3-054, "carrying work to new canvases". The scheme's gloss for T3-054 reads: "Members take up or turn down a later canvas: rebuilding there, planning for next time, or declining to start again." The subform adds that on the copy the model's spine runs again. Members recruit, choose a site, build, defend and lose work, as they did on the first canvas.

Does it contradict F11? No; it is one of F11's kinds. Does it contradict the account? No; it repeats the account's spine at a second site. One misfit is already on record. F12's account says that r/forsen and r/polska "sit under T3-054 but sought a song and a day of memes, not a canvas" (section 12), and it logged the point in notes-D5.md and defects.jsonl. The rule above chose r/forsen by its count of concepts before I read that sentence again.

4. The room's model: r/forsen (rooms/forsen/model-D-recheck.md)

The current room model is the one written at the re-check under 46384686. On the original model, r/forsen's verdict was composes with residue at the first return and composes at the re-check, which I ruled at D3b. The adapted model's grade is composes-with-residue. Its local status is unresolved, as for every room: local validation is not established.

The model's dimension D07 describes the close. Some members celebrate their labour and claim a win, while other posts announce a loss, list the figures that were left and share a timelapse [P11, P12]. For carrying on, the model reads: "Continuation is proposed through another pixel website and through a queued community gachi song." It keeps a finer step: members "would add bars in queue order rather than carry only a saved image forward". It marks A09 absent: "A saved record prompting those proposals remains not testable"; "similarity to the experiment and another site's availability are visible without a link to the timelapse or an inventory." And: "The replacement-site reply supplies practical uptake through its cooldown workaround, leaving sustained building unresolved."

The room adds its own history before the close, and a second medium after it. Members began building at hour 19: "We building gachiGASM in r/place CUM HELP" [forsen/c0002]. They repaired: "A few people have been vandalizing us so we have some repairing to do." [forsen/c0054]. In one thread a speaker from the Naruto fans' side announced a peace at hour 71.66 and threatened a raid at hour 72.22, and the model attributes such positions to speakers, not to a room [P08, P18]. At the close the room's last word on its work was loss: "r/place is over, the only thing that is left is Pastor LUL" [forsen/c0099].

Does the room contradict F12? Yes, in part. F12 says the spine runs again on another canvas. The room's model shows one call to another site and one reply, and it leaves building there unresolved. The room carries on in proposals, not in the spine's steps. Does it contradict F11? It fits F11's first half, since a queued song is new work of another kind. It does not fit the second half: both proposals come after the close, at hours 73.48 and 75.11.

5. The adaptation lines

r/forsen has 80 lines in the current ledger: instantiate 39, absent 25, restrict 7, add-condition 5 and add-step 4. Three concern carrying on.

• R-forsen-c50d02da9d56-061, instantiate P13: "Members propose continuing on another canvas or collaboratively making a song without demonstrating completion of either project."
• R-forsen-d98406bef832-062, add-step P13, lifted to t11, T3-054, T4-028 and D07: "Continuation transfers the participation format by queueing members to add musical bars rather than carrying only an image or venue."
• R-forsen-886800c12615-063, absent A09: "Successor proposals express similarity or site availability without demonstrating that a saved record prompted continuation."

This level adds the reason for membership. Line 062 alone puts r/forsen into F11, through its key at T4-028, and into F12, through its key at T3-054. The line is about the song. The key reaches T3-054 because the song's concepts sit in the room's second-order theme t11, "trying the shared project again after place", which the scheme places under T3-054.

Does this contradict the room model? No. The line states the model's finer step. It does explain the misfit two levels up. F12's name describes the half of T3-054 in which members take up a later canvas. The theme also holds turning one down, and r/forsen's line falls in that half: "instead of pixel art".

6. The quotes

I read these through cite.py.

At hour 73.48 a member proposed the song: "Why can't the Forsenbajs do something similar? But instead of pixel art, we make some community gachi." [forsen/c0097]. The same member set out the queue: "Then we gather a list of Force N Bouys who are willing to join the experiment and put them in a queue. Then in that queue order we are each responsible for adding 5-10 seconds/a couple of bars of our own gachi to said song until the song's full of gachi." [forsen/c0098].

At hour 75.11 another member posted: "PLACE IS BACK ON ANOTHER WEBSITE LETS GO" [forsen/c0102]. The reply, at hour 75.60, gave a way around the new site's wait: "You don't even need to wait 5 minutes on this site for a pixel,just refresh vpn for a new ip and it gets rid of the cooldown." [forsen/c0103].

Around these proposals the record holds talk about the close. A member announced a loss at hour 73.20: "PLACE HAS ENDED! VI LOST ZULUL" [forsen/c0095]. Members blamed the loss on missing allies: "Because idiots were too stupid to make alliances" [forsen/c0083]; "Yo i'm from forsen's side. Nobody made any alliances from our side." [forsen/c0084]. A timelapse came at hour 75.46: "Our dungeon on /r/place full 72h timelapse" [forsen/c0104]. A member mourned one figure at hour 78.48: "monkaS was gone instantly FeelsBadMan but it was pretty while it lasted FeelsGoodMan" [forsen/c0106].

The quotes add the words of the queue and the order on the clock. They do not contradict the lines or the model. One point the model does not stress: by the A1 rule the room's organizing ended with the song proposal itself. organizing_end-A1.jsonl gives hour 73.48 and names c0097 as both the last coordinating code and the only aftermath coordinating code. After it the record holds blame, a timelapse and mourning. No member reports placing on the other site.

Back up

• The quotes to the lines. The words carry line 062: a queue, with each member adding bars. They also carry line 063: neither proposal names a record. Holds.
• The lines to the room model. The model keeps the song as a finer step of P13 and leaves building on the other site unresolved. Holds.
• The room to the subform. A contradiction. F12 says the spine runs again on another canvas. r/forsen shows a call to another site, one reply about a way around the wait, and a proposal to stop drawing and make a song. Its membership rests on the line about the song. Going up, F12 cannot claim the spine's return for all its members: of 22, r/forsen and r/polska carried on in another form. F12 is a grouping, as its account says, and this walk confirms that its name does not hold for every member. The contradiction does not reach the model, since T3-054's gloss already holds "declining to start again".
• The subform to the branch. F11's first half holds for r/forsen: the song is new work. Its second half does not hold, since the proposals came after the close. This agrees with F11's own count (11 of 43 before the close) and with its renaming proposal.
• The branch to the account. The account's A09 states an order from the record to carrying on in 113 of 145 rooms. In r/forsen the first recording act, the loss announced at hour 73.20 [P12], comes before the song (73.48), so the order the account counts is present. The timelapse (75.46) comes after both proposals. The room's model finds no link between the record and the proposals. So r/forsen shows the order and no cause, which is all the account's count claims. It also agrees with the account's sentence that curating the record and carrying on are different acts.

Read against prior.md

prior.md section 2 records the operator's expectation: "Continuity at the top, drops at the bottom, a model all the way down; the lower levels will describe decline and continuity." It also records mine: "What follows organizing will be talk about it: credit, blame, mourning, and calls to rebuild on a successor canvas."

• A model all the way down. It held on this walk. Each level speaks in the model's terms (P12, P13, A09), and each adds a finer step without replacing the one above.
• Continuity at the top. The account's sentence on carrying on (113 of 145 rooms) describes continuity.
• Drops at the bottom. The subform's condition, another canvas, drops out at the room. What is left at the bottom is a proposal in another medium.
• Decline and continuity. r/forsen describes both within about five hours: a loss announced (73.20), a song proposed (73.48), a call to another site (75.11) and a figure mourned (78.48).
• Talk after organizing. r/forsen shows all four kinds I expected: credit, in a claim that the room still won [forsen/c0096]; blame, on missing alliances; mourning, for monkaS; and a call to a successor canvas.

The canvas, projected afterwards (rule 7)

This section comes after the walk and changes none of it. The atlas links four artworks to r/forsen, one of them named "monkaS and Van Darkholm". Members of the room placed 7,375 of the 63,915 placements in its region (share 0.115). The record says at hour 73.52 that only one figure was left [forsen/c0099], and at hour 78.48 that monkaS "was gone instantly" [forsen/c0106]. The atlas records what survived the last hour of the event. So the record and the canvas disagree about what stood at the freeze. I cannot tell from here whether the members spoke of an earlier loss, whether the atlas outlines a damaged figure, or whether members misjudged the final image. It is a question for the room's account, not a correction to either. The bias runs one way: a room enters the frame only through an artwork that survived, so the canvas cannot show a room that kept nothing. The atlas is not a measure of skill or of what the room intended, and it has no measure of whether the room went on.

The walk's contradictions

1. r/forsen against F12's name. Its membership rests on a line about a song, and its record shows no building on another canvas. This confirms a placement and wording question F12's account already logged; it reaches neither the account nor the model.
2. r/forsen against the second half of F11's name. Its carrying on began after the close, as in 32 of F11's 43 members.
3. The record against the canvas on what stood at the freeze. A question for the room's account.

No contradiction reaches the account or the model.

The held proposals (QD4-001; never served, not re-checked)

Copied in full from tree-D4.md, section "The held proposals". Neither proposal is part of the model the walk used.

Both were made at D4a-01 and reverted in the same leg. Neither was served to any room, and neither is re-checked. The model this tree hangs from holds P05 and A11 as frozen at D3.

• P05, move 198 (contrasting), history lines 173 to 176, reverted by line 181 (move 203). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." The status would be bounded. The bound would read: "It does not hold where the keepers read a planned change from its shape and stop repairing it with no telling: completeanarchy, polska, satania, halo, bangtan, thesilphroad (R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018), a candidate branch, 'the shape read' (F-024). It does not hold where informed members hold the change against keepers who do not know: armok, maryland, oneshot (R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013), a limit below the trigger, at three nodes. Amended at D4a-01, after the D3 freeze (46384686...); not re-checked: no room was served these words." Rooms: completeanarchy, polska, satania, halo, bangtan, thesilphroad, armok, maryland, oneshot. Lines: R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018, R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013.
• A11, move 199 (dropping working hypotheses), history lines 177 to 180, reverted by line 182 (move 203). The arrow from P02 to P04 would be withdrawn (status withdrawn, in_model false). Its reason, as written: "Rule 16 and rule 14: preserve what remains supported, and replace or withdraw what does not. No defensible formulation of A11 as an arrow survives the return. (1) The order between rooms never beat its null (111 of 185 rooms, 0.600; null p95 0.670; base_rate_beaten false), and C2 withdrew it, keeping a transition inside threads. (2) Inside threads, the return's census (D3a-38, re-run as _analysis/d4a01_a11_classes.json) shows the transition in 111 rooms and template first in 98 of the 228 rooms whose lines show both ends; across threads 19 more. The reverse order is nearly as common, so the arrow carries no direction. (3) The failure clause is present and stands alone in 117 rooms: talk only in 31 (berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia) and layout only in 86. (4) The mechanism's word 'settled' is contradicted by 261 accepted restrict lines whose 'how' says a template does not settle the design for good (rival templates, polls, later redesigns, placers who deviate). A reworded arrow (a layout answers design talk in its thread) would be a new claim, never served to any room, with its reverse nearly as common: a co-occurrence, not an arrow. What remains supported, that design talk and layouts meet in threads, is held by P02's and P04's statements and ranges ('a design argued over days and redone'; 'an official template the room asks everyone to follow against other versions'), which stand. The arrow's record keeps its evidence and reasoning." Rooms (the talk-only rooms of the failure clause): berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia. Lines (the first-return lines of the census classes talk only, layout only and template first, 216): 2007scape-012, 4chan-011, AMD-012, AmericanFlaginPlace-009, AvoArmy-011, AyyMD-041, CKCrusaders-041, CSUFoCo-015, DestinyTheGame-014, DevonUK-010, FinalFantasy-014, GuardiansOfDatBoi-009, HomestarRunner-015, MonkeyIsland-011, NewMexico-015, ScottPilgrim-015, Temple-041, TsundereSharks-048, adventuretime-041, aggies-050, albania-046, alberta-016, anaheimducks-015, animalcrossing-053, anime-012, argentina-051, armenia-030, bardmains-055, berkeley-038, berserk-012, bih-036, bisexual-012, bitcoin-012, blackmirror-046, borderlands-020, bostonbruins-052, brasil-011, canada-012, catalonia-009, catholicism-011, cfb-048, chibears-010, chicubs-010, cirkeltrek-013, clashroyale-045, completeanarchy-011, criticalrole-043, crusaderkings-039, cubers-014, cuboulder-008, czech-014, dankmemes-045, darksouls-042, detroitlions-049, edboxes-046, edmontonoilers-041, empiredidnothingwrong-013, england-045, ethereum-056, europe-050, eve-049, fivenightsatfreddys-012, flashtv-055, floridagators-035, flyers-035, formula1-048, forsen-010, ftlgame-044, fxKorea-010, gameattack-015, gamindustri-053, gatech-041, ghibli-010, globaloffensive-012, greenbaypackers-011, guatemala-010, habs-011, heyyea-010, hongkong-047, hsv-012, hyperlightdrifter-046, indieheads-056, indonesia-035, ireland-045, italy-035, katawashoujo-041, lakers-009, latvia-029, leagueoflegends-042, lifeisstrange-013, linux-015, littlewitchacademia-012, loliconsunite-010, lost-044, lovelive-041, lsu-049, luxembourg-012, madokamagica-041, magictcg-010, mechanicalkeyboards-042, metalgearsolid-013, mexico-041, miamidolphins-041, minecraft-017, mit-041, mizzou-018, mls-053, monalisaclan-013, morrowind-011, msu-011, muse-048, mylittlepony-011, nVade-013, naruto-010, nbaspurs-056, necrodancer-011, neopets-047, newzealand-046, nightinthewoods-012, nin-012, ockytop-042, opticgaming-012, overwatch-017, parahumans-013, parrots-013, pathofexile-012, pcmasterrace-013, pebble-007, penguins-055, philippines-052, pitt-041, placeDE-041, placecanada-013, placesnek-031, planetside-056, polska-054, portal-012, portugal-082, predators-010, purdue-051, puzzleanddragons-013, quebec-013, radiohead-010, rainbowgrid-006, rangers-045, re_zero-042, redpandas-018, rickandmorty-042, rit-011, rocketbeans-008, rocketleague-011, romania-015, roosterteeth-013, rpi-049, russia-052, rust-010, rutgers-012, samuraijack-047, scp-014, seahawks-014, serbia-051, singapore-016, slovenia-041, smite-010, southpark-012, spacexmasterrace-052, spain-035, ss13-016, ssbpm-012, stardewvalley-058, starryknights-041, stevenuniverse-012, straya-047, suomi-041, survivor-035, sweden-045, tampabaylightning-045, terraria-048, teslamotors-012, tf2-041, thebluecorner-016, theexpanse-012, theitalyplace-054, thepointing-043, thesimpsons-011, tinytardis-009, titanfall-013, torontoraptors-016, totallynotrobots-013, transformers-046, trees-013, turkey-055, twentyonepilots-012, ubc-046, ucf-050, uiuc-011, ultrahardcore-005, undertale-011, unitedkingdom-035, unturned-013, uofm-008, uofmn-035, uruguay-012, utahjazz-009, utaustin-013, uva-042, uwaterloo-011, vegan-043, virginiatech-043, weezer-053, wine-011, witcher-017, worldoftanks-015, xenoblade_chronicles-012, zelda-061, zootopia-012.

Survival per branch

Stage D5, leg D5b, 2026-10-26 UTC. This file reports, for each of the 35 branches, when the members' coordinating ended, how much of it came after the close, and what the members' own records say became of their work. It reports these from the record first. The canvas comes afterwards, in section 5, with the direction of its bias named (rule 7). Section 6 checks the dated changes in the branch narratives against prior.md's brackets and the members' placements by hour. Nothing here is a score, and a branch's size is not its importance.

1. The three measures, from the record

Stage A1 wrote three fields for every room (organizing_end-A1.jsonl), under the rules in prior.md section 5.

• organizing_end_hour. The hour of the room's last coordinating turn in the forest. It dates the last observed coordinating act. It does not show that all organizing stopped then, and work off the platform is not in it.
• The aftermath share. The share of the room's coded turns after hour 73 that coordinate rather than recount. The branch figure is the mean over members, as in branches-D5.jsonl.
• work_remained. The room's own last word on what became of its work: kept, lost or silent. Silence is an unknown outcome, and it counts.

The clock: placement was disabled at hour 73, and the last 24 hours of the 97-hour window are aftermath (prior.md section 4). Of the 476 rooms in a branch, 53 ended their coordinating before hour 64, 303 between hour 64 and the close, and 120 at hour 73 or later. For most rooms, then, the close is what the record shows stopping the coordinating. Over the 705 rooms the median end is hour 72.02; over the 476 in a branch it is 72.20.

2. work_remained, read again

prior.md section 5 measured the field's error before the scheme: right in 25 of 34 rooms. At D5a-33 to D5a-35 I found lines cited for the field that were about another room, that came before the close, or that said the opposite (defects lines 95, 97 and 99). So at this leg I read the field again for every room in a branch, by a rule I logged before the reading.

The rule. For each room I read the code or codes the field cites, with their hour and words, and gave one reading. Stood: a line at hour 72 or later says the room's own work, or its main work, was there at or after the close. Gone: a line at hour 72 or later says it was destroyed, missing or not kept at the end. During: a line before hour 72 reports the work finished, standing or lost during the event, so it cannot say what stood at the close. Other: the line does not concern the room's own work (another room's work, a post title, a remark). Unclear: the line cannot be read either way. Silent: no code. Where one line says one work stood and another was lost, the room's main work decides, and the reading is noted as mixed. While reading I adopted four conventions and applied them to all five pages: a celebration posted after the close counts as stood; an edit posted after the close is read by its content; hour 72 is applied strictly; a final canvas or final image posted without naming the room's work is unclear. Three readings were corrected after the files were written (r/detroitlions, r/placetardis and r/liverpoolfc, each to unclear), and the corrections are logged. The pages I read showed the field beside each line. Each reading is of the line's words, and the agreement with the field was computed afterwards (out/_analysis/d5b_survival.py).

What the reading shows. The field against the reading, for the 476 rooms:

The field and the reading agree in 248 of 476 rooms. Where the field says kept, a line after the close says the work stood in 146 of 253 rooms. Where it says lost, a line after the close says the work was gone in 40 of 161. In 115 rooms the cited line came before the close, and in 63 it concerned something other than the room's own work. Read again, the rooms' own words after the close say the work stood in 149 rooms and was gone in 43. The field over-reads both outcomes, and it over-reads loss more.

I report both, per branch, in section 3. The re-reading changes no ledger: branches-D5.jsonl keeps work_remained as the field gives it. The account's paragraph "Which keep the work alive" rests on the field (kept 347, lost 218, silent 140 of 705). Its shares are shares of a field that over-reads outcomes, so they are a question for the account at stage D6 (notes-D5.md, defects.jsonl).

3. Per branch, the record

Each row gives the branch's members; a room in two branches counts in both. "In a branch" counts each of the 476 rooms once.

The population row counts 696 end hours: nine rooms have no coordinating turn under the A1 rule (prior.md section 3), and none of them is in a branch.

The field beside the reading, per branch:

Four branches end late, and each is a branch whose key is carrying on: F12 (median hour 80.76; 14 of 22 members coordinated after the close), F23 (80.66; 24 of 30), F13 (74.88) and F11 (73.48; 23 of 43). That they end late restates the cut: the key that put them together is about work after the close. The earliest medians are F14 and F33 (70.59), F06 (71.05) and F03 (71.21). F18 is the only branch in which no member coordinated after the close. In the re-reading, F24 (stood 15, gone 1), F08 (17 and 2), F27 (12 and 2) and F09 (23 and 4) lean most to stood; F03 (3 and 4) and F30 (5 and 5) do not. F26 holds the largest share of members whose cited line came before the close (9 of 23).

4. Each branch's ending, in its own terms

For each branch I say what the last coordinating act was and what the members did after the close. The last act is each member's last_coordinating_code; the acts after the close are its aftermath_coordinating_codes. Both are read through the fourth-order themes their concepts sit under, as a share of the branch's acts against the population's, by the rule of D5a-01's theme script (a concept split evenly over its themes). Across the 705 rooms the last act is most often repair work (0.142 of last acts), then transition (0.119), negotiated order (0.113) and collective representation (0.098). After the close, transition leads (0.526), then collective memory (0.105) and completion ritual (0.078).

The themes, in plain words: repair work, fixing and defending the work; transition, taking the work or the group to a new place or form; negotiated order, terms with neighbours; collective representation, the room showing itself as a group; mobilization, calls for hands; workarounds, extra accounts, scripts and ways around the wait; completion ritual, marking the work done; collective memory, records and screenshots; boundary work, keeping canvas talk in its place in the sub; frame bridging, tying the canvas to the sub's other matters; reciprocity, help for help; sensemaking, asking how things work; backstage decision-making, choices made in a chat.

• F01, the play administered (103). The last act was most often repair work (0.21 of the branch's last acts, against 0.142). After the close 22 members coordinated, mostly in transition, with boundary work above the population's (0.143 against 0.043): members sent canvas posts to one thread or another sub (r/thenetherlands, r/stardustcrusaders). The play itself, the sub's April Fools frame, had ended with the day; the canvas work ended at the close like any room's.
• F02, the takeover run as a temporary regime (33). The last acts spread over transition, repair work and negotiated order near the population's shares. Nine members coordinated after the close, mostly toward later canvases (r/bindingofisaac, r/totallynotrobots, r/naruto), with r/thenetherlands again sending canvas posts elsewhere. The regime ran on the sub's pages, and the branch's narrative does not date its end.
• F03, the joke tested (18). The last act was most often repair work (0.25) and, above the population, territoriality (0.139 against 0.056). Three members coordinated after the close: directions to the logo (r/hunterxhunter), a second logo (r/magictcg) and the logo proposed again (r/warframe). The re-reading finds the work gone in 4 members and standing in 3.
• F04, the licence policed (13). Three members coordinated after the close, nearly all in transition (0.875): r/bindingofisaac, r/elitedangerous and r/magictcg. The branch's narrative does not date an end to the objections.
• F05, the styling ended (12). The last act was most often repair work (0.367). One member coordinated after the close (r/furry_irl, inviting the room to put its slogan on a new canvas). The branch's own ending, ordinary use restored to the sub, concerns the sub's styling, not the canvas, and the narrative does not date it.
• F06, the joke kept (8). The last act was most often a workaround (0.25 against 0.046). One member coordinated after the close (r/kanye, a tribute proposed for the sub's banner). These rooms asked that the joke's change last; the record does not say whether it did.
• F07, the telling clause not shown at the design (59). The last act was most often repair work (0.24) or collective representation (0.186 against 0.098). After the close 13 members coordinated, mostly in transition (r/factorio and r/croatia toward copies of the canvas), and frame bridging stood above the population's (0.117 against 0.016): r/AyyMD petitioned to restore the canvas so its logo could be fixed, and r/porterrobinson proposed an old logo before noticing the end.
• F08, machine hands kept on one target (50). The last act was most often a workaround (0.22 against 0.046): extra accounts, scripts or ways around the wait were the last coordinating act in these rooms. After the close 13 members coordinated, toward later canvases (r/AmericanFlaginPlace, r/loltyler1) and toward records and banners (r/mexico, r/bakchodi). In the re-reading the work stood in 17 members and was gone in 2.
• F09, the move returns to building (54). The last act was most often repair work (0.233). After the close 11 members coordinated, mostly in transition and, above the population, mobilization (0.125 against 0.02): a new letter on another site (r/calgaryflames), another spiral (r/SquareSpiral), a logo defended on a successor canvas (r/twice). The branch's sequence, moving and building again, ran once more on new canvases in these rooms. The re-reading finds the work stood in 23 members and was gone in 4.
• F10, a deal carried out as work (38). The last act was most often negotiated order (0.215 against 0.113), and reciprocity stood above the population (0.11 against 0.046): the deals' work went on to the end. Four members coordinated after the close, all in transition (r/fivenightsatfreddys, r/NewMexico, r/phish, r/placetardis). In 12 members the cited line came before the close.
• F11, carrying on as renewed work (43). The last act was most often transition (0.444 against 0.119): for these rooms carrying on was the last coordinating act. 23 members coordinated after the close, three quarters of it transition.
• F12, the spine restarted on another canvas (22). The last act was transition in 0.591 of members' last acts. 14 members coordinated after the close, and on the copies the spine ran again: r/theblackvoid recruited for new cores on another site until hour 95, r/greenlattice started a gold lattice and moved to a second copy, and r/bindingofisaac called for help when its new drawing was attacked.
• F13, the work remade in other media (9). Five members coordinated after the close: the canvas in real life and a building challenge (r/lego), a canvas of the sub's own (r/globaloffensive), a drawing on a second canvas (r/prequelmemes). The re-reading finds no member whose work was gone.
• F14, the mark adopted as the room's emblem (7). The last act was most often a workaround (0.286). Two members coordinated after the close; r/cgpgrey proposed stickers that keep the canvas mark. The emblem was the carrying on, and it began before the close.
• F15, the plan kept current (42). The last acts spread over negotiated order, transition and repair work near the population's shares. Eight members coordinated after the close, mostly toward later canvases (r/placestart, r/philippines, r/starryknights), and r/ockytop started again on a copy that banned bots.
• F16, the chat kept open (35). The last act was most often repair work (0.205), with backstage decision-making above the population (0.086 against 0.034). Eight members coordinated after the close: the finished work proposed as the sub's banner (r/de), a new flag on another canvas (r/TransFlagPlace), and sensemaking above the population (0.182 against 0.017).
• F17, the marking provisional and contested (36). The last act was most often negotiated order (0.199) or mobilization (0.139 against 0.065). Seven members coordinated after the close, toward copies (r/AcePlace, r/asexuality, r/fullcommunism) and toward records (r/rocketbeans).
• F18, success judged while upkeep continues (15). No member coordinated after the close. The last act was most often mobilization or completion ritual (0.2 each, against 0.065 and 0.034). These rooms judged their success and stopped at the close.
• F19, credit contested during the work (14). The last act was collective memory above the population (0.179 against 0.036). Four members coordinated after the close, half of it collective memory: r/rocketbeans sent a request for the drawing's bitmap to an archive, and r/Okami proposed adding a figure after the canvas had closed.
• F20, the close as news (10). The last act was most often collective representation (0.2). Two members coordinated after the close (r/Rainbow6 and r/re_zero), mostly in completion ritual. These rooms told late arrivals that placement had ended; the news was their ending.
• F21, the canvas call not a joke (32). Six members coordinated after the close, with completion ritual and repair work above the population: r/chile organized to keep its flag, r/patriots called to erase pixels from its work, and r/osu proposed carrying the final image to football games.
• F22, help conditional on the helper's own work (30). The last act was more often reciprocity than in the population (0.15 against 0.046). Six members coordinated after the close, mostly toward later canvases (r/gamindustri, r/furry_irl), and r/PlaceNL called to extend its flag after placement had ended.
• F23, the close scoped to the original canvas (30). The last act was transition in 0.622 of members' last acts. 24 members coordinated after the close, the most of any branch: a flag on a copy of the canvas (r/catholicism), a memorial, a group elsewhere and new land (r/thebluecorner), a replacement flag and an alliance renewed on another site (r/TheFarLeftSide).
• F24, machine hands debated (27). Five members coordinated after the close, with backstage decision-making above the population (0.2 against 0.029): r/placeportalpattern proposed organizing a second version in a chat, and r/frc called to save its logo and then to remake it on another site. The re-reading finds the work stood in 15 members and was gone in 1.
• F25, carrying on in talk (27). The last act was transition in 0.451 of last acts. Twelve members coordinated after the close, with completion ritual above the population (0.154 against 0.078): calls back to the canvas after it ended (r/gorillaz), a flag on a copy (r/czech), a logo continued elsewhere (r/starcitizen).
• F26, the telling clause not shown at the border (23). Six members coordinated after the close: r/miamidolphins called everyone to pack it up, and r/uiuc asked that the cleaned image go into the sub's theme. In 9 members the cited line came before the close.
• F27, the telling clause not shown in keeping (27). Eight members coordinated after the close, with frame bridging above the population (0.179 against 0.016): painters recruited for a copy (r/frankocean), a figure called for after the canvas had finished (r/pokemon), a new site (r/armok).
• F28, help at the border conditional (22). The last act was completion ritual above the population (0.114 against 0.034). Five members coordinated after the close: r/quebec called to destroy a neighbour's flag after placement had ended, and r/cloud9 recruited for a flag on a copy.
• F29, the chat's reach conditional (25). Twelve members coordinated after the close, with completion ritual above the population (0.243 against 0.078). r/osugame alone holds nine acts after the close: a replacement canvas, a chat with a template, the logo shown atop the sub, and a call to finish the logo on another site. r/EraseThePlace called for the erasing to continue on a copy.
• F30, the chat seen only through its invitations (24). Six members coordinated after the close, and transition is below the population's share (0.25 against 0.526); sensemaking and boundary work make up more of it (r/de, r/stardustcrusaders). Seven members are silent on their work.
• F31, hosting as one-off permission (22). The last act was most often collective representation (0.254 against 0.098). Four members coordinated after the close, nearly all in transition (r/frankocean, r/seahawks).
• F32, the marking returns to keeping (21). The last act was most often repair work (0.183), with reciprocity above the population (0.111 against 0.046). Four members coordinated after the close: r/starvstheforcesofevil recruited spare pixels for a template and started a sign on a copy, and r/ockytop started again on a copy. A last act of repair fits the branch's sequence, in which keeping came after the marking.
• F33, the plan kept current while the design settles (23). The last act was most often negotiated order (0.304 against 0.113). Four members coordinated after the close: r/tf2 proposed the canvas design as the sub's logo, and r/india called for help with a flag on an alternative site.
• F34, the design sized to the hands (22). The last act was most often repair work (0.238) or collective representation (0.23). Five members coordinated after the close, and three of them proposed smaller or second attempts: a smaller canvas on the sub's own site (r/aeskwadraat), another site (r/aoe2), a smaller copy and a successor canvas (r/farmcarrots).
• F35, the call made workable (18). The last act was most often mobilization (0.361 against 0.065): in these rooms the last coordinating act was a call. Four members coordinated after the close, nearly all in transition: another site (r/FlaggyFlag, r/purdue) and a logo on a successor canvas (r/homestuck).

5. The canvas, projected afterwards (rule 7)

What the canvas measures, in the contract's words (section 5): "The atlas records what survived the last hour of a 97-hour event. It is not a measure of skill, a large area is not evidence of anything a community intended, and it is what the drawing left behind: the instrument has no measure of whether the room went on, whether the arrangements held, whether anyone came back, and a null on the canvas is not a null on §1's last question." And: "Everything you can see is text, and most of the work left no text." Nothing below is a score, and no reading in sections 2 to 4 used the canvas.

The direction of the bias. The frame is built from artworks that survived the last hour. A room that organized, placed and was overwritten before the freeze has no row. So the canvas leans toward survival: it cannot show a room that kept nothing, and 475 of the 476 rooms in a branch have an artwork. A room's region is the union of its final artworks. Placements at a site the room left are not counted, so the canvas understates the early work of rooms that moved. Regions overlap, so a contested pixel counts for every room that claims it.

The percentile places the branch's median area among random groups of the same size drawn from the analysed set (tools/projections.py). The members' share is px_by_window_members over px_in_region_any: the share of a region's placements made by people who wrote in the room.

Read against the record.

• Stood and gone look alike on the canvas. By the re-reading, rooms whose own words say the work stood have a median area of 770 px (149 rooms), and rooms whose words say it was gone have 758 (43). All of them have an artwork. The canvas does not separate the two at this grain. One timing differs: in the gone rooms, members made 0.201 of their placements in hours 64 to 73, against 0.165 in the stood rooms. That is a timing, not a cause. The silent rooms are small (median 309 px).
• What the members placed. In a branch, members made 0.120 of the placements in their own regions (population 0.109); by branch, from 0.058 (F19) to 0.226 (F14). The account's paragraph on keeping says the record "is not a claim about what survived on the room's patch of the canvas, much of which was placed by people who never wrote in the room." The canvas agrees with that clause.
• F09. Its members made 0.056 of their placements in hours 8 to 32, against 0.175 in the population, the lowest share of the 35 branches but one (F20, 0.044). The narrative says these rooms lost a first work and built again. With the bias named, the figure fits that timing: the region is where they rebuilt, so the first site's placements are missing.
• F34 and F35. The members' placements peak at hour 72, and F34's members made 0.257 of theirs in hours 64 to 73, the largest share of the 35 branches. Both branches left smaller works than random groups of their size (23rd and 13th percentiles). The members' words, designs sized to the hands and calls answered with a request for a task, were not found from the canvas, and the canvas does not show why the placing came late.
• F08. The members' placements peak at hour 71, and 0.228 of them fall in hours 64 to 73. The narrative says scripts' targets were kept current to the end. The canvas cannot tell a script's placement from a hand's, and it overstates these rooms' hands.
• Large works follow room size. F13, F23 and F29 sit at the 100th percentile of area; their median members have large records. Each account said so.

What the model implies a room keeps. The account's spine says keeping follows building in 148 of 190 rooms [A03] and that keeping holds the known form [P05]. A room that keeps should end with its known form in place. The canvas shows a final artwork. It cannot tell a kept form from a late rebuild or a changed design, so it does not test P05. For F32, whose rooms marked the work and then kept it, section 6 checks the timing: members' placements went on after the marking in five of seven rooms, fell in one (r/httyd), and were empty in one (r/ockytop).

6. Dated changes against prior.md's brackets and the placements by hour

The rule (logged before computing). A dated change is a sentence in a branch narrative (section 1 of the account) that dates an act on the canvas by a named room's members: placing, building, fixing, changing the design, moving the work, or a marking followed by keeping. Remarks, requests, invitations and acts at or after hour 73 are not. For each act I compare the room's px_by_window_members in the four hourly bins before the act's bin with the four bins from it, as rates per bin. The placements move if the ratio is 1.5 or more, or 0.67 or less, and the larger side has 10 placements or more. Each act's implied direction was set before computing: building, fixing or a design change implies a rise; moving the work away or ceasing to defend implies a fall; a marking followed by keeping implies no fall. One amendment, made after seeing the output and logged: a window with no member placement on either side is empty and corroborates nothing.

Of 25 acts, 2 are not checkable because the placement series ends at hour 72. Of the 23 checked, the canvas corroborates the timing of 15, contradicts 4, does not show 3, and is empty for 1. Three acts fall in the April Fools hours (r/india at 11.74, r/tagpro at 25.41, r/faeria at 29.15); the rest fall later in the placement bracket. A corroborated timing is only that: the members' placements moved at the hour the narrative dates. It says nothing about why.

The contradicted timings, each a question for its account.

• r/thebluecorner, hour 39 (F23, F25). The narratives read the call to a copy of the canvas as something to do beside it, while members waited for the cooldown. The members' placements in the room's region fell from 2,404 in the four hours before to 1,396 in the four hours from it. Did the copy draw members off the canvas?
• r/hawks, hour 61.14 (F27). A member announced colour detail being added to the feathers. The members' placements fell from 646 to 252. Was the detail added by a few hands while the rest stopped?
• r/faeria, hour 29.15 (F31). A member announced pasture secured for the room's figure on another room's flag. The members' placements fell from 11 to 4. The counts are small, and the region is the final artwork, so placements made elsewhere are not in it.
• r/httyd, hour 52.45 (F32). The room marked its work done. The members' placements fell from 183 to 118. In this member the keeping that F32 names is not seen as continued placing at that hour.

7. What this file does not say

Kept, lost and silent are the rooms' own words, and the canvas is what the drawing left behind. Neither is a score of a form. The re-reading of work_remained changes no ledger, and the branch lines keep the field as the ledger gives it. A branch whose rooms end late or carry on after the close does so because its key is about carrying on; that is the cut, restated. The canvas corroborates some timings and contradicts four; it never shows a mechanism.

Room form A, the terms between neighbours, with the plan announced: the form account

Written at D5a-36, 26 October 2026. The model is the version frozen at D3 (46384686d6173fdeb4c749667478c1363e675bc6b52bb6f4fdc211d387e68525). Form A is one of the six room forms of the cut J ruled at D4a-08 (room-forms-D4a08c.*); how every room reaches its form is in room-forms-allocation.md. It holds 166 of the 705 analysed rooms. 135 are defining rooms: rooms with 5 or more selected changes, which shaped the form. 28 are thin rooms (1 to 4 selected changes) and 3 are core rooms (no selected change), placed afterwards. Thin and core rooms weigh less: every share, signature, theme count, representative choice and split below is read on the 135 defining rooms, and the thin and core rooms are named in section 15.

A room form is not a branch. A branch of stage D4 gathers the rooms that share one change key. A room form gathers rooms by the whole mix of their changes (two thirds) and their codes (one third), so the 35 branches are the level below it (section 12). The form is a pole of a continuum, not a kind: 35 of its 135 defining rooms lie nearer another form's centre (section 13). This file sits beside the room-forms files, not in forms/, because the stage's close-check reads every account in forms/ as a branch account (departures.jsonl line 18). Hours are counted from the start of the event (h+).

1. How these rooms organized, as a narrative

In these 166 subreddits the room built beside other rooms' work and settled with its neighbours what each could have. The settling came early. Often it came while the room was still building, before it had anything to keep.

Members warned the neighbour before they built over its work. In r/cavestory a member wrote, "we should tell /r/tampabaylightning about balrog because we're going to end up running over their logo" [cavestory/c0032]. Another agreed to a plan "as long as r/ainbowroad gets word of the project." [cavestory/c0021]. Neighbours came to them as well. A r/stardewvalley thread received a visitor: "Hey, I'm from the HotS team and your chicken is touching our border." [stardewvalley/c0074]. A member answered, "I'm sure we don't mind the bum of our chicken getting cut off a little bit if it can work with your border." [stardewvalley/c0075]. The visitor replied, "I think we can figure something out. I think it looks nice enough." [stardewvalley/c0076].

The rooms decided what they could give. In r/placetardis a member drew the line between the picture and its frame: "The black border and blue background isn't "content"" [placetardis/c0013]. The room let a neighbour expand into its background: "They've agreed not to go over the actual TARDIS, but it seems silly to not let them go into our blank blue background. Please let them do their thing." [placetardis/c0028]. Size entered the terms. A neighbour asked r/redhotchilipeppers to move, taking it for the bigger sub. A member answered, "we only have 3 people working on this so it will be difficult" [redhotchilipeppers/c0065], and the neighbour gave way: "My group said it's fine then." [redhotchilipeppers/c0066]. In r/israel's thread an artist who could not win gave pixels instead: "Fair. I could not win anyway, I would just be a thorn in your side. So, I will devote pixels to help you in hope that I receive help." [israel/c0061].

A few members made a deal, and the rest of the placers had to learn it. A r/poland member reported a peace: "we won't bother each other, but it will take some time for everyone to get the news" [poland/c0039]. In r/ManningPlace a member admitted that "there might be some who haven't gotten the memo." [ManningPlace/c0055]. In r/clg a neighbour's member wrote, "it seems we still have uninformed broncos fans going on your border. I'm messaging them individually about our truce" [clg/c0067]. Some placers were out of reach. "There is compromise with most of the swedes on discord but not the rouge ones." [stardewvalley/c0086]. In r/FloydVsVoid a member answered a neighbour's complaint: "many of our contributors arent on our sub or discord and thusly arent under our direct control" [FloydVsVoid/c0128].

Restraint often came before any deal. A r/oneshot member asked the room to wait: "until we receive word from them, please do not damage it." [oneshot/c0025]. Members apologised when they learned what they had covered. "Yay! My apologies to /r/Cornwall - I didn't realise!" [Dorset/c0006]. "Sorry, that was my bad. I didn't know the black border was important. Sorry again!" [stardewvalley/c0090].

The room's own plan met the same problem. A change had to reach the members who placed and repaired. A r/monalisaclan member wrote, "I was trying to help out but because I didn't know there was a newer design I was messing it up. please delete the posts or put a warning on them and link to the new design." [monalisaclan/c0105]. In r/philippines a placer was scolded for one pixel: "Damn there should be a pinned post about r/place plans. Somebody PMed me for putting 1 red pixel on it." [philippines/c0449]. A r/FloydVsVoid member corrected the room's own instructions: "That's still the wrong plan in the main post. Here's the new one" [FloydVsVoid/c0153].

Not every term held. A neighbour offered r/FloydVsVoid a truce on hard terms: "Truce and you help me get my letters over your prism" [FloydVsVoid/c0089]. The room refused: "The prism with a copypasta on top is not an option, we'll have to find another way" [FloydVsVoid/c0202]. The neighbour answered, "Then I will be removing your prism, sorry. I was offering you a way to keep it." [FloydVsVoid/c0203].

The rooms marked the work as it went, and then went back to keeping it. A r/stardewvalley member thanked the room: "It only took about a day, and three moves, but in the end it was worth it to see our little guy on that canvas." [stardewvalley/c0098]. The next reply turned to defence: "Yay! So proud of our team work! Lets do our best to defend the little guy." [stardewvalley/c0099].

2. What the form does

These elements are instantiated in 80 per cent of the defining members or more (_analysis/d5f_model.py, current ledger, particular lines included). The model's prose says them so.

• P01 (135 of 135; 100 per cent of the 558): "The room calls its own members, and kindred subs, to come and place for a work: to start it, build it, finish it or hold it."
• P02 (135 of 135; 100 per cent of the 558): "The room settles what its mark will show of it: a member proposes a picture, the room argues its design, makes its land's flag or emblems the mark, signs it or leaves it unsigned, claims a mark others made, adds to it or enlarges it, or adds a personal piece to a shared mark."
• P03 (132 of 135; 97 per cent of the 558): "The room builds its mark, and members report its state to the thread: what is placed, done or missing, and where."
• P05 (132 of 135; 93 per cent of the 558): "The room keeps its placed work against erosion: members watch it and repair changed pixels, and the room rallies to defend it under attack, covers the night, hardens its shape and puts upkeep before growth. Repair restores the form the keepers know. A change the room has planned or agreed (P02) is therefore repaired away as damage until its keepers are told of it, and it is lost or given up where the telling does not reach them."
• P11 (131 of 135; 96 per cent of the 558): "When a work is up, the room marks it: announces it, celebrates it, credits makers and helpers, reports members' own parts and says what working with strangers meant."
• P12 (131 of 135; 97 per cent of the 558): "The room records what happened to its work and to the canvas around it: screenshots and timelapses, reports of its fate, mourning, imagined art, atlas entries, the end marked."
• P04 (130 of 135; 97 per cent of the 558): "Members circulate a template that lays out the mark pixel by pixel, or coordinates that locate it, ask for them, and ask strays to keep to them."
• R01 (128 of 135; 96 per cent of the 558): "The starter: a member who proposes the mark, maps it or begins placing it. Others joining is not part of the role: it is the answer to the room's call (P15), in the order A02 and A01 state."
• P07 (127 of 135; 89 per cent of the 558): "Rooms spare their neighbours' work, rein in their own attackers, apologise for damage and appeal to attackers to stop."
• P08 (127 of 135; 86 per cent of the 558): "Rooms propose, settle and contest borders, truces and deals with neighbours by talk, through envoys, and hold each other to them."
• P15 (127 of 135; 91 per cent of the 558): "A member answers a call or proposal in one line that joins, assents, reports a part done or thanks, and the line asks for nothing back."
• P16 (126 of 135; 91 per cent of the 558): "Rooms help one another's works and trade help: they give pixels to a neighbour's mark, ask other rooms for help, barter help for space or repair, thank their allies, greet them, and turn requests away."
• P06 (120 of 135; 87 per cent of the 558): "Members work out who changed their work and why: they trace placers and rooms, find friendly fire or their own mistake, blame officers, or disown placers acting in their name."
• K02 (114 of 135; 82 per cent of the 558): "The room judges that it has too few hands or too little room for the work it wants: doubt, a canvas judged too full, a work judged absent or outclassed."
• P24 (114 of 135; 89 per cent of the 558): "Members ask what the canvas is, how to place, what a call or a name means and what a picture shows, and others explain the rule, the timer, the controls, whose mark a picture is and what happened. They ask before, during and after the close, and some questions get no answer."
• R02 (113 of 135; 81 per cent of the 558): "The envoy: a member who acts for a room toward another room, carrying a proposal between threads or chats."

The model takes a room from building to keeping (A03), from keeping to talk with its neighbours (A04), and from a settled border to sparing (A05) and to traded help (A14). These rooms do all of it. They do the talk with neighbours more than other rooms do. P08, the borders, truces and deals, is instantiated in 127 of 135 defining members, against 86 per cent of the 558 defining rooms. P21, members stating the limits of who may commit the room to an agreement, is instantiated in 45 of 135 (33 per cent), against 24 per cent.

3. What it does differently, element by element and arrow by arrow

The change signature. The form's defining members change three fourth-order themes more than the defining population does (at 1.5 times its share or more, in a third of the members or more). Negotiated order is changed by 86.7 per cent of them, against 58.1 per cent of the 558 (share ratio 1.75). Completion ritual is changed by 51.1 per cent, against 37.6 (ratio 1.58). Standardization of output is changed by 37.0 per cent, against 18.8 (ratio 2.06). These come from the allocation's columns (room-forms-D4a08c.jsonl).

Element by element and arrow by arrow. The table gives every element or arrow and op that 14 defining members or more change, at 1.2 times the defining population's share or more (_analysis/d5f_facts.py). A selected line specifies the model (add-condition, add-step), restricts it (restrict), connects two of its parts (link) or contradicts it. The kind of a line is not relied on (J: kappa 0.08).

No defining member holds a contradict line, so these rooms replace nothing in the model. They specify it, restrict it and connect its parts. I read the lines behind the table whole (_analysis/d5f_dump.py: 98 lines on the negotiated order, 70 on keeping, 73 on the plan and the marking).

• P08, borders, truces and deals: specified (add-step 21 members, add-condition 14) and connected (link 16). The added steps are the work of making terms. Members warn a neighbour before building over its work, discuss a border inside the room before contacting the neighbour, decide which pixels can be ceded, find the channel through which to reach the other room, and carry the news of an agreement past the venue where it was made. r/placetardis: "Members distinguished expendable background and border pixels from recognizable picture content when deciding what space could be ceded." r/poland: "Agreement news must be transmitted beyond its negotiating venue, and participants explicitly describe that transmission as still incomplete." The added conditions say whom an agreement binds. r/bostonbruins: "An agreement's effective reach depends on placers knowing and accepting its plan, because uninformed numbers can overwhelm negotiated coexistence." The links put the talk inside the building. r/cowchop: "Anticipated collision during construction provides a stated reason for overlap negotiation before the core image is secured."
• P07, sparing: specified (add-step 12 members, add-condition 16). Restraint is offered before any agreement settles the overlap, and it is selective. r/oneshot: "Restraint also operates while permission is pending, preserving neighbouring work before an agreement settles the overlap." r/hsv: "Appeals to spare the room can redirect destruction elsewhere, making restraint selective rather than protection of every neighbour."
• P05, keeping: specified (add-condition 37 members) and connected (link 27). Two things recur in the conditions. Keeping can mean undoing one's own pixels to spare a neighbour. r/opticgaming: "Explains cooperative upkeep that permits removing one's own bricks when preserving them would destroy neighbouring art." And the telling clause of P05 (a planned change is repaired away until the keepers are told) works from the other side as well: told keepers can refuse. r/de: "Telling keepers about a planned change does not secure acceptance when they knowingly reject it as a takeover." The links send the marking back to keeping. r/japan: "A completion announcement explicitly requires continued protection, adding a feedback from accomplishment to maintenance."
• A05, from a settled border to sparing: restricted (39 members) and specified (add-condition 15). Section 7 reads the restrictions. The added conditions say that an agreement spares a neighbour only where its terms reach the placers and their scripts. r/ManningPlace: "A border decision guides coordinated restraint only where its terms reach placers, since some reportedly have not gotten the memo." r/TheFarLeftSide: "An agreement must reach human keepers and bot targets before it can reliably become their restraint rather than another construction they erase."
• A14, from border talk to traded help: restricted (15 members, 1.72 times the defining population's share). Help came before the terms, or the record shows an offer and not the help given (section 7).
• P04, P11 and P12, the plan and its marking: specified (add-step 32, 21 and 16 members). The plan is kept current and announced, so that keepers do not undo a change. r/monalisaclan: "Helpers request warnings on obsolete templates and links to current designs so intended repair does not undo the plan." r/philippines: "Members propose pinned plans, direct messages and recognizable outlines to inform cleaners before they undo new work." The work is marked while it goes on. r/anime: "Credit is actively checked and corrected during ongoing work rather than appearing only at the close."

What a room of this form does that the model would not predict. The model has every element these rooms use, and the arrows' bounds already allow talk with neighbours, and sparing, to come first (A04 and A05; section 7). What the model does not say is what making terms takes, and whom terms bind. A room of this form makes terms while it builds, before it has a mark to keep. It finds out that an agreement, and its own plan, bind only the placers and scripts they reach. And it works to reach them: it messages placers, posts warnings, updates templates and retires stale calls. In the lines I read, 29 defining members state that terms or a plan hold only where they reach the placers. They are listed with their lines in _analysis/d5a36_reach_rooms.txt and counted by script; the list is a reading, not a ledger count. That is a fifth of the members, so it is a pattern inside the form, not the form.

The rooms that show this best are r/FloydVsVoid and r/stardewvalley, and the one that shows it least well is r/futanari (section 11, by the rule stated there).

What the claim rests on. The form is a cut of the allocation (changes two thirds, codes one third, Ward's method, six forms by J's ruling). It is validated only as far as that cut is: its stability on matched subsamples is about 0.21, and 35 of its defining rooms lie nearer another form's centre. The table's counts are the ledger's. That members made terms while building and told placers of them is a claim on their words, through cite.py, in sections 1, 4 and 11. One kind of evidence does not stand in for the other.

The name, read against the members. The name is "the terms between neighbours, with the plan announced". The strongest argument that it names the cut rather than what the rooms did: it joins the names of two of the eight forms of D4a-08b (the terms between neighbours, and the plan made and announced), merged at seven. A reader who suspected the name would look for members with no terms in their record, and for the plan held apart from the terms. The first exist: r/futanari's record shows a piece shown, praised and captured, and nothing between neighbours (section 11). The second does not: the part that leans to the plan still holds the negotiated order in 82 per cent of its defining members (section 14). The members support the name. I make no renaming proposal. One candidate reading, terms and plans that hold only where they reach the placers, goes to notes-D5.md for D6, as a pattern of a fifth of the members.

4. The concepts it employs

First-order concepts for each change the form leans to, through cite.py:

• Terms made while building. "Is it possible to move the carrots below us to another spot, to make room for Balrog?" [cavestory/c0034]. A neighbour opens the talk: "yall are kinda interfering with the raps logo.wanna talk abt it?" [vermont/c0022].
• What may be ceded. "The black border and blue background isn't "content", and if people ask to take our background or border for actual content, I'm all for it." [placetardis/c0013].
• Terms that must reach the placers. "We are putting up an announcement on the main page but if you guys can message them about our truce because they've missed it somehow" [clg/c0068]. "Contact r/ainbowroad to get them to put this on their official live thread." [drawhelix/c0024].
• Restraint before a deal. "until we receive word from them, please do not damage it." [oneshot/c0025], then "Update: we have been given the go-ahead to finish the sprite and outline where it touches the rainbow." [oneshot/c0026].
• Keeping that spares the neighbour. "I'm having to defend ireland's flag from people extending the rainbow too far!" [FloydVsVoid/c0140].
• The plan kept current. "Mods, can you PLEASE update the official design?" [monalisaclan/c0141]. "Revised plan for the Mona Lisa (please take note of new changes thnx guys)" [monalisaclan/c0196].
• The marking during the work, and back to keeping. "I'm so damn proud of you all!" [FloydVsVoid/c0151]. "Yay! So proud of our team work! Lets do our best to defend the little guy." [stardewvalley/c0099].

5. Composition here

Three judgments are kept apart.

The original global model (historical). verdicts-D.jsonl, by the last analyst ruling or else the readers' agreement. All 166 members: composes 74, composes with residue 90, does not compose 0, cannot tell 2. The 135 defining members: composes 59, composes with residue 76, does not compose 0, cannot tell 0. The two that cannot tell are core rooms, r/Lugarix and r/yerbamate, with 5 and 1 coded concepts. These verdicts describe the unadapted model at the first return.

The adapted local accounts. By adaptation-returns.jsonl and the current model hash (46384686), as vlib.local_return_states reads them, all 166 members are unresolved; none is validated and none has insufficient evidence. The limit D3 named is the same for each: the labelers marked every local account unresolved, and prior.md section 3's measure of local validation was not computed (J after the D3c interview). The unresolved members are:

r/2007scape, r/AcePlace, r/adventuretime, r/ainbowroad, r/animalcrossing, r/anime, r/asexuality, r/auburn, r/batman, r/berserk, r/bostonbruins, r/buffalobills, r/carletonu, r/catalunya, r/cavestory, r/CelticFc, r/ChronoTrigger, r/cirkeltrek, r/clg, r/compsoc, r/Cornwall, r/cowchop, r/croatia, r/DCFU, r/de, r/detroitredwings, r/DevonUK, r/Dorset, r/drawhelix, r/Dustforce, r/edboxes, r/empiredidnothingwrong, r/epublica, r/evedreddit, r/faeria, r/finland, r/fireemblem, r/FloydVsVoid, r/forsen, r/foxes, r/ftlgame, r/funhaus, r/furry, r/futanari, r/germany, r/ghibli, r/giantbomb, r/Goodboye, r/gravityfalls, r/greenlattice, r/halo, r/hatsune, r/hellointernet, r/heyyea, r/hsv, r/hungary, r/iceland, r/indonesia, r/ireland, r/israel, r/Jamaica, r/japan, r/jerma985, r/k_on, r/kamenrider, r/kcroyals, r/kilian, r/kurdistan, r/lakers, r/landry, r/lifeisstrange, r/littlewitchacademia, r/loliconsunite, r/lsu, r/luciomains, r/Lugarix, r/malaysia, r/mamamoo, r/ManningPlace, r/MiamiHurricanes, r/mindcrack, r/monalisaclan, r/MonkeyIsland, r/monsterhunter, r/Moondye7, r/mordhau, r/morrowind, r/mysterydungeon, r/necrodancer, r/neopets, r/neutralmilkhotel, r/norway, r/npr, r/nVade, r/Okami, r/onepunchman, r/oneshot, r/opticgaming, r/orderofthebluecorner, r/osugame, r/pansexual, r/parabola, r/paranatural, r/Peru, r/peterdraws, r/philippines, r/PinkUnion, r/placehearts, r/placeportalpattern, r/placetardis, r/poland, r/prequelmemes, r/rainbowgrid, r/raocow, r/ravens, r/ReBoot, r/redhotchilipeppers, r/redvsblue, r/RelientK, r/rhythmheaven, r/ripcity, r/riskofrain, r/rocketbeans, r/roosterteeth, r/seolhyun, r/seventeen, r/signal, r/sonicthehedgehog, r/sooners, r/soylent, r/stardewvalley, r/starryknights, r/starvstheforcesofevil, r/Summit1G, r/SwissNeutralityZone, r/switzerland, r/taiwan, r/TeamYellowPlace, r/telegram, r/texastech, r/thailand, r/TheB1G, r/theexpanse, r/TheFarLeftSide, r/TheHulk, r/tinytardis, r/toolband, r/transformers, r/TsundereSharks, r/twice, r/ubreddit, r/ucf, r/uiuc, r/utahjazz, r/utaustin, r/uva, r/VelvetUnderground, r/vermont, r/Villanova, r/vinesauce, r/vocaloid, r/winnipegjets, r/witcher, r/xcom, r/xenoblade_chronicles, r/yerbamate

The shared form explanation: unresolved. The form's members share a lean, not one change: 86.7 per cent of the defining members change the negotiated order, and their changes specify the model's own elements. Much of what they restrict, the arrows' bounds already state (section 7). And 35 of the 135 defining members lie nearer another form's centre. So the form describes these rooms jointly as a lean of the population. It does not yet explain them as one shared change would. Every member's own adapted account is unresolved as well. A verdict of composes with residue on the original model is not a current local or shared failure.

6. How the model runs here

Counts are of defining members with a current-ledger line, particular lines included (_analysis/d5f_model.py); they count any line of an op.

The elements that do the work. The elements of section 2, with P08 above the population's rate (94 per cent against 86) and P21 above it (33 per cent against 24).

The elements that sit idle. P34 is absent in 134 of 135 defining members, P30 in 120, P33 in 115, P28 and P29 in 106, C02 in 105, K03 in 104 and A21 in 103. They are idle in the population too (between 69 and 99 per cent), and their idleness does not mark the form.

The elements that fit less here. K01, the April Fools frame, is instantiated in 54 of 135 (40 per cent), against 57 per cent of the 558. P20, the host's line, is instantiated in 50 (37 per cent), against 49 per cent. These rooms worked on the canvas between neighbours more than on their sub's play or its host's rules.

What these rooms do that the model has no place for. 37 of 135 defining members carry 47 propose lines, against 210 of the 558 defining rooms. The propose lines are not part of the form's lean.

Where the room models and my reading disagree. They agree. r/FloydVsVoid's model reads A04 "only at that local contact step rather than proving upkeep caused every alliance", and r/stardewvalley's model says that its neighbour's "we can figure something out" "remains prospective". My reading of the members' lines is the same: the terms are visible, and whether they were kept often is not.

The held proposals (QD4-001; never served to any room, not re-checked). The model above is the frozen version. J ruled that both held proposals are stated in full wherever the model is reported. They are, as the tree file states them:

• P05, move 198 (contrasting), history lines 173 to 176, reverted by line 181 (move 203). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." The status would be bounded. The bound would read: "It does not hold where the keepers read a planned change from its shape and stop repairing it with no telling: completeanarchy, polska, satania, halo, bangtan, thesilphroad (R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018), a candidate branch, 'the shape read' (F-024). It does not hold where informed members hold the change against keepers who do not know: armok, maryland, oneshot (R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013), a limit below the trigger, at three nodes. Amended at D4a-01, after the D3 freeze (46384686...); not re-checked: no room was served these words." Rooms: completeanarchy, polska, satania, halo, bangtan, thesilphroad, armok, maryland, oneshot. Lines: R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018, R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013.
• A11, move 199 (dropping working hypotheses), history lines 177 to 180, reverted by line 182 (move 203). The arrow from P02 to P04 would be withdrawn (status withdrawn, in_model false). Its reason, as written: "Rule 16 and rule 14: preserve what remains supported, and replace or withdraw what does not. No defensible formulation of A11 as an arrow survives the return. (1) The order between rooms never beat its null (111 of 185 rooms, 0.600; null p95 0.670; base_rate_beaten false), and C2 withdrew it, keeping a transition inside threads. (2) Inside threads, the return's census (D3a-38, re-run as _analysis/d4a01_a11_classes.json) shows the transition in 111 rooms and template first in 98 of the 228 rooms whose lines show both ends; across threads 19 more. The reverse order is nearly as common, so the arrow carries no direction. (3) The failure clause is present and stands alone in 117 rooms: talk only in 31 (berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia) and layout only in 86. (4) The mechanism's word 'settled' is contradicted by 261 accepted restrict lines whose 'how' says a template does not settle the design for good (rival templates, polls, later redesigns, placers who deviate). A reworded arrow (a layout answers design talk in its thread) would be a new claim, never served to any room, with its reverse nearly as common: a co-occurrence, not an arrow. What remains supported, that design talk and layouts meet in threads, is held by P02's and P04's statements and ranges ('a design argued over days and redone'; 'an official template the room asks everyone to follow against other versions'), which stand. The arrow's record keeps its evidence and reasoning." Rooms (the talk-only rooms of the failure clause): berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia. Lines (the first-return lines of the census classes talk only, layout only and template first, 216): 2007scape-012, 4chan-011, AMD-012, AmericanFlaginPlace-009, AvoArmy-011, AyyMD-041, CKCrusaders-041, CSUFoCo-015, DestinyTheGame-014, DevonUK-010, FinalFantasy-014, GuardiansOfDatBoi-009, HomestarRunner-015, MonkeyIsland-011, NewMexico-015, ScottPilgrim-015, Temple-041, TsundereSharks-048, adventuretime-041, aggies-050, albania-046, alberta-016, anaheimducks-015, animalcrossing-053, anime-012, argentina-051, armenia-030, bardmains-055, berkeley-038, berserk-012, bih-036, bisexual-012, bitcoin-012, blackmirror-046, borderlands-020, bostonbruins-052, brasil-011, canada-012, catalonia-009, catholicism-011, cfb-048, chibears-010, chicubs-010, cirkeltrek-013, clashroyale-045, completeanarchy-011, criticalrole-043, crusaderkings-039, cubers-014, cuboulder-008, czech-014, dankmemes-045, darksouls-042, detroitlions-049, edboxes-046, edmontonoilers-041, empiredidnothingwrong-013, england-045, ethereum-056, europe-050, eve-049, fivenightsatfreddys-012, flashtv-055, floridagators-035, flyers-035, formula1-048, forsen-010, ftlgame-044, fxKorea-010, gameattack-015, gamindustri-053, gatech-041, ghibli-010, globaloffensive-012, greenbaypackers-011, guatemala-010, habs-011, heyyea-010, hongkong-047, hsv-012, hyperlightdrifter-046, indieheads-056, indonesia-035, ireland-045, italy-035, katawashoujo-041, lakers-009, latvia-029, leagueoflegends-042, lifeisstrange-013, linux-015, littlewitchacademia-012, loliconsunite-010, lost-044, lovelive-041, lsu-049, luxembourg-012, madokamagica-041, magictcg-010, mechanicalkeyboards-042, metalgearsolid-013, mexico-041, miamidolphins-041, minecraft-017, mit-041, mizzou-018, mls-053, monalisaclan-013, morrowind-011, msu-011, muse-048, mylittlepony-011, nVade-013, naruto-010, nbaspurs-056, necrodancer-011, neopets-047, newzealand-046, nightinthewoods-012, nin-012, ockytop-042, opticgaming-012, overwatch-017, parahumans-013, parrots-013, pathofexile-012, pcmasterrace-013, pebble-007, penguins-055, philippines-052, pitt-041, placeDE-041, placecanada-013, placesnek-031, planetside-056, polska-054, portal-012, portugal-082, predators-010, purdue-051, puzzleanddragons-013, quebec-013, radiohead-010, rainbowgrid-006, rangers-045, re_zero-042, redpandas-018, rickandmorty-042, rit-011, rocketbeans-008, rocketleague-011, romania-015, roosterteeth-013, rpi-049, russia-052, rust-010, rutgers-012, samuraijack-047, scp-014, seahawks-014, serbia-051, singapore-016, slovenia-041, smite-010, southpark-012, spacexmasterrace-052, spain-035, ss13-016, ssbpm-012, stardewvalley-058, starryknights-041, stevenuniverse-012, straya-047, suomi-041, survivor-035, sweden-045, tampabaylightning-045, terraria-048, teslamotors-012, tf2-041, thebluecorner-016, theexpanse-012, theitalyplace-054, thepointing-043, thesimpsons-011, tinytardis-009, titanfall-013, torontoraptors-016, totallynotrobots-013, transformers-046, trees-013, turkey-055, twentyonepilots-012, ubc-046, ucf-050, uiuc-011, ultrahardcore-005, undertale-011, unitedkingdom-035, unturned-013, uofm-008, uofmn-035, uruguay-012, utahjazz-009, utaustin-013, uva-042, uwaterloo-011, vegan-043, virginiatech-043, weezer-053, wine-011, witcher-017, worldoftanks-015, xenoblade_chronicles-012, zelda-061, zootopia-012.

2 of form A's rooms are among the rooms of the P05 proposal (r/halo, r/oneshot). 3 are among the talk-only rooms of the A11 proposal's failure clause: r/edboxes, r/ireland, r/morrowind.

7. The restrict lines: the arrow fails here, or the record cannot show it

The rule, logged before reading. I read every restrict line on an arrow held by a defining member, 432 lines, and sorted each how sentence (_analysis/d5f_restricts.py; my sort in d5a36_sort_1.json to d5a36_sort_6.json, joined in d5a36_restrict_sorted.json). The arrow fails here: the line says the consequent came without the antecedent, from another source or in another order, or that the antecedent did not lead to it. The record cannot show it: the line says the order, the link or the step is not visible, not dated or not established in the record. Both, where it says both. Neither, where it states a condition or a scope, or says that the two acts coincide or overlap. This is one reader's sort, mine; no second coder read it (J: no readers for the rest of the run).

The form's own arrows: the arrow fails as stated, inside bounds the model already writes. A04 runs from keeping to border talk. In 27 of its 35 restrict lines here the arrow fails: talk with the neighbour came while the room was building, from an overlap it expected, or before it had anything to keep. r/hsv: "Border negotiation can arise during building into occupied ground without defence of an established mark as its immediate cause." A04's own bound already says that rooms which came to a full canvas talk with neighbours first. So these lines restate the bound. They do not find a new failure. A05 runs from a settled border to sparing. In 17 of its 39 lines the arrow fails: restraint came before any agreement, from a norm or an apology. r/MonkeyIsland: "An agreement is unnecessary to explain this restraint because the speaker directly states avoiding conflicting portions." A05's bound already says that sparing often comes first and tacit. In 16 more the line states a scope: the agreement binds only the placers it reaches. r/placetardis: "Settlement produces restraint only when placers receive and recognize the agreement, as missed plans and stops after discovery demonstrate." That is what P21 holds, and it is instantiated here above the population's rate.

The arrows every form restricts. A10 (judging too few hands, then the move) fails here in 37 of 50 lines: the shortage led to recruiting, holding or resizing, and the moves had other causes. A11 (a template settles a design) fails in 38 of 61: the template did not settle the design. That is the ground of the held A11 proposal. A07 (a work up, then the marking) fails in 12 of 16: the rooms celebrated before the work was done. These rates are not this form's own; A10 and A11 are restricted at the population's rate here (section 3's table holds neither).

Where the record cannot show it. The record cannot show who joined because of a call (A01, 12 of 20 lines). It cannot show whether help arrived (A13, 17 of 30; A14, 9 of 15), or whether a script ran (A06, 12 of 25). It cannot show that a call turned members against a rival (A15, 10 of 13), or what every reader owed an answer (A12, 15 of 30). In these lines the coders saw an offer, a request or a call, and not what followed it.

So the two readings divide by kind. Where the line concerns the order of two acts the rooms report (talk and keeping, a border and sparing, a template and a design), it mostly says the arrow fails as stated. Where it concerns delivery or cause (help given, scripts run, members recruited), it mostly says the record cannot show it. Across all 432 lines: the arrow fails here in 201, the record cannot show it in 136, both in 34, neither in 61.

8. The one relationship that runs differently here

A04 runs from P05 (keeping) to P08 (borders, truces and deals). Its connection: "in a room carrying both, the first act of upkeep or defence comes before the first border talk, truce or deal". Its mechanism: "Keeping a mark against erosion brings the room up against the neighbours whose pixels erode it, and the room turns to talk with them."

In r/stardewvalley it runs as stated. A defender asked for help at h+34.22: "the Junimo is getting rekt I don't think I can do this alone. EDIT2: I really need some help here." [stardewvalley/c0024]. At h+49.38 the same member reported terms: "I just made a deal with /r/luciomains and they've agreed to build around the Junimo but there is still random people trying to destroy it." [stardewvalley/c0025].

In r/cavestory it runs the other way. At h+43.74 a member proposed talk before the room built over a neighbour: "we should tell /r/tampabaylightning about balrog because we're going to end up running over their logo" [cavestory/c0032]. In r/redhotchilipeppers the terms came before the room had a secure mark: "we only have 3 people working on this so it will be difficult" [redhotchilipeppers/c0065]. The coders' line: "Disclosing few active builders changes a neighbour's answer from requesting movement to accepting the location."

In 35 of 135 defining members a current-ledger line restricts A04, against 22.9 per cent of the 558. A04's bound already admits rooms that talk first. What runs differently here is the share of rooms whose talk with neighbours is the work of building, not of keeping.

This is description, not a test. A04's expectation in form A is 0.471 (2 within-case datings over 705 rooms, times 166), so A04 is not-testable-here (section 10).

9. Fourth-order themes over- and under-represented

The rule was logged at D5a-01 before it ran (_analysis/d5_themes.py), and it is applied here to the defining members' codes (_analysis/d5f_facts.py). A member's coded concepts are counted by the fourth-order themes of their second-order theme's placements, and the form's pooled share on a theme is set against the pooled share over all 705 rooms. Over-represented: a ratio of 1.5 or more, with the theme present in 5 members or more. Under-represented: a ratio of 0.67 or less, with a population share of 1 per cent or more. These are shares of what the coders coded in these rooms, never a property of the rooms (contract section 5).

Over-represented (5).

• Symbolic boundaries: 0.8 per cent of the defining members' coded concepts against 0.4 per cent (ratio 1.77), in 12 members.
• Negotiated order: 16.3 per cent of the defining members' coded concepts against 9.7 per cent (ratio 1.68), in 129 members.
• Territoriality: 6.1 per cent of the defining members' coded concepts against 3.8 per cent (ratio 1.63), in 62 members.
• Standardization of output: 3.2 per cent of the defining members' coded concepts against 2.1 per cent (ratio 1.54), in 66 members.
• Repair work: 15.5 per cent of the defining members' coded concepts against 10.2 per cent (ratio 1.51), in 124 members.

In the rooms' words, from members holding the largest share on each theme (_analysis/d5f_theme_quotes.py): Negotiated order, "Is it possible to move the carrots below us to another spot, to make room for Balrog?" [cavestory/c0034]. Territoriality, "The Vineshroom is gone..." [vinesauce/c0057]. Standardization of output, "I say Lechuck to the left of guybrush, under bender. we can get most of him." [MonkeyIsland/c0010]. Repair work, "We need to get a black border around the V" [Villanova/c0016]. Symbolic boundaries, "Our Night's Watch did a good job :)" [philippines/c0354].

Under-represented (4): Keying (ratio 0.33), Neo-tribes (ratio 0.40), Meta-organization (ratio 0.57), Workarounds (ratio 0.62).

Negotiated order is the form's change signature, so its excess in the codes partly restates the cut; the codes are a third of the distance. Keying, the April Fools frame, is coded at a third of the population's share. These rooms talked about the canvas and its neighbours more, and about their sub's play, its tribes and its coalitions less.

10. Arrows present, absent or not-testable-here

Section 1's arithmetic, declared at D5a-01: an arrow's expectation in a form is its within-case datings (its subs, counted over the 705 analysed rooms) over 705, times the form's n, here 166. Below one the arrow is not-testable-here, and no absence, boundary condition or failed proposition may be written from it. In form A the expectations run from 0.000 to 0.942:

• A01 (P01 to P03): 2 datings, expected 0.471; not-testable-here
• A02 (R01 to P01): 2 datings, expected 0.471; not-testable-here
• A03 (P03 to P05): 2 datings, expected 0.471; not-testable-here
• A04 (P05 to P08): 2 datings, expected 0.471; not-testable-here
• A05 (P08 to P07): 3 datings, expected 0.706; not-testable-here
• A06 (P05 to P14): 3 datings, expected 0.706; not-testable-here
• A07 (P03 to P11): 2 datings, expected 0.471; not-testable-here
• A08 (P11 to P12): 2 datings, expected 0.471; not-testable-here
• A09 (P12 to P13): 2 datings, expected 0.471; not-testable-here
• A10 (K02 to P10): 2 datings, expected 0.471; not-testable-here
• A11 (P02 to P04): 2 datings, expected 0.471; not-testable-here
• A12 (P01 to P15): 3 datings, expected 0.706; not-testable-here
• A13 (P05 to P16): 4 datings, expected 0.942; not-testable-here
• A14 (P08 to P16): 4 datings, expected 0.942; not-testable-here
• A15 (P01 to P09): 4 datings, expected 0.942; not-testable-here
• A16 (P09 to P07): 4 datings, expected 0.942; not-testable-here
• A17 (P09 to P08): 4 datings, expected 0.942; not-testable-here
• A18 (P09 to P18): 4 datings, expected 0.942; not-testable-here
• A19 (P05 to P17): 4 datings, expected 0.942; not-testable-here
• A20 (P01 to P20): 3 datings, expected 0.706; not-testable-here
• A21 (P08 to P21): 0 datings, expected 0.000; not-testable-here

Present: none. Absent: none. Not-testable-here: all 21. Form A is the largest of the six forms, and still no arrow reaches an expectation of one. Members' current-ledger lines on an arrow (sections 7 and 8) are description only. Members among an arrow's within-case datings: r/clg (A18); r/foxes (A06); r/lakers (A08); r/littlewitchacademia (A14); r/monsterhunter (A03); r/paranatural (A10); r/roosterteeth (A05); r/sooners (A14, A17); r/switzerland (A04); r/thailand (A17); r/TheFarLeftSide (A06); r/uiuc (A09). That is arithmetic about the model's own evidence, and it tests nothing in the form.

Propositions. N01, N02, N03, N04, N05, N06, N07, N08, N09; the highest expectation among the arrows they rest on is 0.942. Every proposition is not testable here; none holds and none fails against a real expectation. No findings.jsonl line is bounded from this form.

11. How representative members do the work

The rule, logged at this leg's opening before it ran (_analysis/d5f_facts.py). Fit is a defining member's distance to the form's centre in the allocation's 892 columns. The best two are the nearest members whose selected changes and coded concepts are at or above the form's defining medians (10 changes, 99 concepts), so that each record can be told. The least well is the farthest defining member. The member read at length is, among the ten nearest, the one with the most selected changes not read at length earlier in stage D5. The rule chose r/FloydVsVoid twice, as the best fit and as the member read at length.

Best fit, read at length: r/FloydVsVoid (distance 0.690; 26 selected changes; 205 coded concepts; first-return verdict composes, re-check grade composes with residue; in F15, F30 and F31). I read it at length because the rule chose it, and because it holds every part of the form. Its members built a prism and a rainbow against a rival room, the Void, whose members declared the room's resistance futile. The opening call: "We're Taking on the Void! Join the Fight!" [FloydVsVoid/c0001]. Their terms ran in several directions at once. They made a deal for space: "we will help maintain the blackness in the core" [FloydVsVoid/c0077]. They asked whether they could reach another neighbour at all: "Can we even reach out to them?" [FloydVsVoid/c0079]. They agreed a line with the Swiss flag's builders: "instead of blending the mountains with the prism can we just do like a black line that separates the prism from the mountains." [FloydVsVoid/c0204], answered "sure thing!" [FloydVsVoid/c0205]. The Swiss gave their reason for helping: "You guys were great to incorporate our prism into your mountains and I would like to see the cheese stay intact." [FloydVsVoid/c0110]. An alliance post told members what to leave alone: "Leave /r/place logo and Anime Poot" [FloydVsVoid/c0088]. When r/ireland complained, "Please stop invading the Irish flag" [FloydVsVoid/c0126], a member repaired the flag, "im using some of my pixels to replace flag pixels" [FloydVsVoid/c0129], and stated the limit of the room's terms: placers outside the sub and the chat "arent under our direct control" [FloydVsVoid/c0128]. The plan had to reach the members as well: "That's still the wrong plan in the main post. Here's the new one" [FloydVsVoid/c0153]. When the room lost a piece of the work, a member asked for the chat to spread the word: "Is anyone on the Discord chat who can let everyone know?" [FloydVsVoid/c0161]. Another answered, "I've sent about 100 messages in the last hour. i think we're making headway." [FloydVsVoid/c0162]. What is unrepresentative about it: it organized against a rival room as well as with its neighbours, and its record is larger than most. It holds 205 coded concepts against the form's defining median of 99, and 26 selected changes against 10.

Second best fit: r/stardewvalley (distance 0.704; 11 selected changes; 126 coded concepts; first-return verdict composes, re-check grade composes with residue; in F09, F15, F21, F28 and F32). Its members built small figures, a Junimo and a chicken, among larger works, and they settled with each neighbour in turn. A member was "in contact with the redditors over on" another sub "regarding their Lucio pixel art right above our Junimo." [stardewvalley/c0010]. A neighbour asked one of its builders to move: "Considering Stardew already had a Junimo, and we were making it first, could you move it somewhere else?" [stardewvalley/c0036]. The builder left: "I've stopped working on it and now working on the starfruit next to the Junimo." [stardewvalley/c0037]. The room offered to trim its chicken for the HotS border (section 1), offered to trade defence for upkeep, "would you be willing to help defend our other properties in exchange for help maintaining your logo" [stardewvalley/c0114], and said where its terms stopped: "There is compromise with most of the swedes on discord but not the rouge ones." [stardewvalley/c0086].

Least well: r/futanari (distance 1.383; 5 selected changes; 14 coded concepts; first-return verdict composes; in no branch; its point lies nearer form D's centre than form A's). Its record is one piece. A member showed it, "Place thing I did over a couple hours" [futanari/c0001], gave its place, "It's over at 163, 262 if you all want to add or check it out." [futanari/c0002], and received praise: "Very gud" [futanari/c0003]. After the close another member saved it: "Our place on r/place is gone, but I captured its most perfect form" [futanari/c0012]. Its five lines restrict the call, the marking and the record (A01, A07, A08, P11, P12). Nothing in it is between neighbours. It is in form A because Ward's method put it there; by the centres it lies between forms A and D.

12. The branches its rooms come from

J asked that stage D6 build on the forms with the 35 branches as the level below. The branches do not nest in the forms: a branch was cut on one shared key, a form gathers rooms by the whole mix of their changes and codes. The table gives, for every branch, how many of its rooms are in form A, and the branch's share in A against A's share of the 705 rooms (166 of 705, 0.235). A ratio of 1 is what a branch would show if its rooms fell in the forms at random.

What the table shows. Ten branches lean to form A at 1.5 times its share or more. They are the branches of the order between rooms and of the plan:

• F19, credit contested during the work: 8 of 14.
• F26, the telling clause not shown at the border: 13 of 23.
• F28, help at the border conditional: 12 of 22.
• F15, the plan kept current: 20 of 42.
• F10, a deal carried out as work: 17 of 38.
• F17, the marking provisional and contested: 16 of 36.
• F32, the marking returns to keeping: 9 of 21.
• F30, the chat seen through its invitations: 10 of 24.
• F18, success judged while upkeep continues: 6 of 15.
• F31, hosting as one-off permission: 8 of 22.

None of the 103 rooms of F01, the April Fools play, and none of its five subforms is in form A. No branch lies mostly in form A: the largest share is F19's, 0.571. So the branches below form A are its facets, each shared with other forms.

Rooms in no branch. 60 rooms (36 defining): r/2007scape, r/ainbowroad, r/auburn (thin), r/batman, r/carletonu (thin), r/cirkeltrek (thin), r/compsoc (thin), r/Cornwall (thin), r/detroitredwings, r/DevonUK (thin), r/Dorset, r/evedreddit (thin), r/finland, r/fireemblem, r/futanari, r/germany, r/giantbomb, r/Goodboye, r/halo, r/hsv, r/iceland (thin), r/ireland, r/k_on, r/landry (thin), r/Lugarix (core), r/MiamiHurricanes, r/monsterhunter, r/mordhau (thin), r/mysterydungeon, r/neutralmilkhotel (thin), r/norway, r/npr, r/nVade, r/oneshot, r/orderofthebluecorner, r/pansexual (thin), r/parabola (thin), r/paranatural, r/peterdraws (thin), r/PinkUnion, r/placehearts, r/rainbowgrid, r/ReBoot (thin), r/redvsblue (thin), r/roosterteeth, r/seventeen (thin), r/signal (core), r/sonicthehedgehog, r/Summit1G (thin), r/TeamYellowPlace (thin), r/telegram, r/texastech, r/TheB1G (thin), r/uva, r/VelvetUnderground (thin), r/vermont, r/Villanova, r/winnipegjets, r/xenoblade_chronicles, r/yerbamate (core).

13. The nearest form and what separates them

The nearest form is B, the work behind the thread: the chat, the scripts and raiding. The distances between form A's centre and the others are B 0.366, C 0.394, D 0.407, F 0.567, E 0.852. In the tree, A stays a form of its own down to four forms; at three it joins B and C (the design and its marking), and the April Fools play (E) is the last to join the rest. A and B are separated by what the rooms changed: A's members change the order between rooms and the plan, B's the chat, the scripts and attack calls.

The rooms between forms. C 14, B 12, D 7, F 1, E 1: these are the forms whose centres lie nearer than A's to its defining members, 35 rooms in all. The room that could have gone either way, the defining member with the smallest margin to another centre, is r/drawhelix (7 selected changes, 67 coded concepts, in F10). Its point lies nearer form C's centre. Its record has both: a border with a neighbour to settle, "Contact r/ainbowroad to get them to put this on their official live thread." [drawhelix/c0024], discussed in the room first, "And I do plan on contacting them, but wanted to discuss it here." [drawhelix/c0025], and a figure revised and kept, which is form C's work.

14. The split below the form

The rule, logged at this leg's opening before it ran (_analysis/d5f_split.py, on room-forms-tree-rooms.tsv). A split reads as a split when both parts hold 10 defining rooms or more and each part has a fourth-order change column (a node or a link) at 1.5 times the parent's defining share or more, held by a third of the part or more and by fewer in the other part. The walk descends only while splits read.

Form A's first split, at seven forms, does not read as a split. A.2 (61 defining rooms, 70 rooms in all) leans its own way: to the completion ritual, the standardization of output and mobilization. It is the eight-form cut's "plan made and announced". A.1 (74 defining rooms, 96 in all) has no column of its own at 1.5 times the form's share. It is the form's centre: the terms between neighbours. Both hold the form's signature. The share of defining rooms holding each signature theme in each part: A.1: Negotiated order 0.905, Completion ritual 0.324, Standardization of output 0.081; A.2: Negotiated order 0.820, Completion ritual 0.738, Standardization of output 0.721. So A.2 is the terms with the plan added, not a second kind of room, and the walk stops at the form. A.2 is a candidate subform for D6 (notes-D5.md), not cut here.

15. The thin and core rooms placed here

Thin rooms (28), placed by the whole mix of their changes and codes at the nearest form centre: r/auburn (4 changes, 49 concepts), r/carletonu (3 changes, 7 concepts), r/CelticFc (1 change, 18 concepts), r/cirkeltrek (3 changes, 308 concepts), r/compsoc (2 changes, 9 concepts), r/Cornwall (1 change, 11 concepts), r/croatia (4 changes, 237 concepts), r/DevonUK (2 changes, 24 concepts), r/Dustforce (4 changes, 47 concepts), r/evedreddit (1 change, 30 concepts), r/hungary (4 changes, 64 concepts), r/iceland (1 change, 77 concepts), r/landry (4 changes, 12 concepts), r/mamamoo (1 change, 10 concepts), r/mordhau (3 changes, 34 concepts), r/neutralmilkhotel (3 changes, 25 concepts), r/onepunchman (4 changes, 130 concepts), r/pansexual (3 changes, 21 concepts), r/parabola (3 changes, 20 concepts), r/peterdraws (3 changes, 10 concepts), r/ReBoot (2 changes, 4 concepts), r/redvsblue (3 changes, 41 concepts), r/seolhyun (3 changes, 38 concepts), r/seventeen (2 changes, 12 concepts), r/Summit1G (4 changes, 148 concepts), r/TeamYellowPlace (3 changes, 63 concepts), r/TheB1G (4 changes, 52 concepts), r/VelvetUnderground (2 changes, 15 concepts).

Their 77 selected lines weigh less and enter no share above. The most frequent are P03 link 6 (r/auburn, r/Cornwall, r/Dustforce, r/redvsblue, r/seolhyun); A04 restrict 6 (r/auburn, r/croatia, r/neutralmilkhotel, r/redvsblue, r/Summit1G, r/TheB1G); P08 add-step 5 (r/Dustforce, r/onepunchman, r/seolhyun, r/VelvetUnderground); P11 link 4 (r/hungary, r/neutralmilkhotel, r/ReBoot, r/seventeen); P05 add-step 4 (r/mordhau, r/neutralmilkhotel, r/parabola, r/TeamYellowPlace); P02 link 4 (r/carletonu, r/iceland, r/parabola, r/VelvetUnderground); P04 add-step 3 (r/cirkeltrek, r/compsoc, r/Dustforce); P07 add-step 3 (r/pansexual, r/seventeen, r/TeamYellowPlace). They lean the same way as the defining members, to border talk while building (A04 restricted in 6) and to the steps of making terms (P08 add-step in 4).

Core rooms (3), with no selected change, placed by their codes alone at the nearest centre in the code columns: r/Lugarix (5 concepts; verdict cannot-tell), r/signal (6 concepts; verdict composes), r/yerbamate (1 concept; verdict cannot-tell). Their placement rests on 1 to 6 coded concepts each and is weak. Two of them are the form's only rooms whose verdict is cannot tell.

16. The form test

The constructs. P08 (borders, truces and deals), P07 (sparing) and P05 (keeping), joined at the fourth-order theme T4-016 (Negotiated order), with P21 (who may commit the room) and the arrows A04, A05 and A14. For the part A.2, P04 (the template), P11 (the marking) and P12 (the record).

The relations. The rooms make terms with neighbours while they build, and they spare neighbours before any terms are made. The terms bind only the placers, and the scripts, they reach, and the rooms work to reach them. The same holds for the room's own plan. The first relation is the form's: the negotiated order is changed by 86.7 per cent of its defining members. The second is held by 29 of 135 in the lines I read. The relations restate bounds the model already writes for A04 and A05, and they add the work of making and spreading terms that the model leaves unstated.

Is it falsifiable? Yes. A room that made terms only after keeping, or whose agreements bound placers who never heard of them, would fall outside the relations. Such rooms exist in the population: A04's within-case datings, r/switzerland (a member here) and r/DestinyTheGame, are rooms whose first upkeep came before their first border talk.

The four organizing problems. The form binds information provision: terms and plans must reach the placers, and the rooms' added steps are the means (messages, warnings, updated templates, retired calls). It binds the division of tasks between rooms: a border divides the canvas between two works. It leaves the allocation of members to tasks free, and it touches reward only through traded help (A14), which the record mostly shows as offers. A remainder is supported: restraint that rests on a norm, offered before any terms, and apology when a room learns what it covered. None of the four problems names it.

What varies among members. Whether the plan is announced as well as the terms (A.2 against A.1, section 14), whether the room also organized against a rival room (r/FloydVsVoid), and how far its terms reached. No subform stands on the rule; A.2 is a candidate for D6.

Result: a lean of the population, and a form in a weak sense. The form binds constructs of canvas organizing and states their relations, and the members' words show them. But its members share a lean, not one change. Its relations mostly restate the bounds of two arrows, and about a quarter of its defining rooms (35 of 135) lie nearer another centre. I report it as a pole of the continuum: the rooms whose organizing was mostly about the order between rooms.

17. What would make you doubt this is a form at all

Four things make me question it.

First, the cut. The form is one of six poles that J ruled for a short appendix, cut from a distance whose stability is about 0.21. Its largest part, A.1, is the centre of a continuum, and 35 of its defining rooms lie nearer another centre. A different weighting would move many of its rooms (room-forms-allocation.md, section 5).

Second, my sort of the restrict lines. One reader sorted 432 lines, and no second reader checked them. The line between the arrow fails here and neither (a scope or a condition) is a judgement in many lines on A05 and A10.

Third, the arrows' bounds. The form's most frequent restrictions, on A04 and A05, restate what the model already says in those arrows' bounds. What sets the form apart may be how often its rooms talked with neighbours, not a different way of doing it.

Fourth, the survival figures, from the record, never from the canvas. The median organizing end is hour 71.99 for the 163 members with one, and the mean aftermath share is 0.0159. The coded work_remained field says kept in 79 members, lost in 47 and silent in 40. These figures are not compared here, and nothing in this account rests on them.

What would undo the form: a cut on a different weighting in which the rooms of form A scatter evenly over the other forms, or a reading of the members' threads in which the terms they made were no different from those of rooms in other forms that talked with neighbours.

Room form B, the work behind the thread: the chat, the scripts and raiding: the form account

Written at D5a-37, 27 October 2026. The model is the version frozen at D3 (46384686d6173fdeb4c749667478c1363e675bc6b52bb6f4fdc211d387e68525). Form B is one of the six room forms of the cut J ruled at D4a-08 (room-forms-D4a08c.*); how every room reaches its form is in room-forms-allocation.md. It holds 141 of the 705 analysed rooms. 113 are defining rooms: rooms with 5 or more selected changes, which shaped the form. 23 are thin rooms (1 to 4 selected changes) and 5 are core rooms (no selected change), placed afterwards. Thin and core rooms weigh less: every share, signature, theme count, representative choice and split below is read on the 113 defining rooms, and the thin and core rooms are named in section 15.

Form B is the labelled mixture of the six-form cut. Its three signatures are each held by under half of its defining rooms. The principal investigator asked that its account come first among the forms in one respect: whether the chat, the scripts and raiding stand apart inside it. Section 14 answers. A room form is not a branch: it gathers rooms by the whole mix of their changes (two thirds) and their codes (one third), and the 35 branches are the level below it (section 12). The form is a pole of a continuum: 43 of its 113 defining rooms lie nearer another form's centre (section 13). This file sits beside the room-forms files, not in forms/, because the stage's close-check reads every account in forms/ as a branch account (departures.jsonl line 18). Hours are counted from the start of the event (h+).

1. How these rooms organized, as a narrative

In these 141 subreddits much of the work was done away from the thread. Members moved their planning into chats, ran scripts that placed pixels for them, and called each other to attack a rival's work. The three did not always go together. Some rooms did one of them, some did two, and a few did all three.

Members opened chats to plan. A r/AmericanFlaginPlace member wrote, "I made a discord server where we can coordinate our efforts live so as to make the best use of our manpower." [AmericanFlaginPlace/c0060]. A r/quebec member reported that members had gathered in another room's chat to work on their flag: "plusieurs de nos membres se sont regroupés sur la chaîne Discord de /r/placecanada afin de travailler méticulement sur notre drapeau." [quebec/c0091]. The chat needed upkeep. Invitations expired: "Invite has expired." [AprilKnights/c0012]. A r/GranColombia member asked for a new one, since the old one no longer worked: "Puedes mandar otra invitación de Discord? Esa ya no es valida." [GranColombia/c0034]. In r/reddevils: "Can't seem to join the discord channel" [reddevils/c0231]. What the chat decided came back to the thread: "We on the AFIP discord are going to be following this design for the banner." [AmericanFlaginPlace/c0268]. Not everyone went in. A r/reddevils member welcomed the room's script and stayed out of the chat: "Good, I'm glad it's running ! I won't be creating a discord account though." [reddevils/c0123]. After the close a r/masseffect member wrote, "Everyone counted - you could tell we had way more people placing pixels than who was in the little discord." [masseffect/c0231].

Members ran scripts, and the scripts had to be kept in step. "Everyone is using scripts. We're being attacked by scripts. If we don't adapt, we lose." [AmericanFlaginPlace/c0473]. Old copies fought new ones: "an older version that sleeping people had on and it's conflicting with a newer version" [AmericanFlaginPlace/c0407]. A r/quebec member warned that everyone running a script would have to change at the same time, or the scripts would fight the new design: "tout le monde qui ont des scripts vont devoir changer en même temps parce que sinon ils vont se battre contre le nouveau design." [quebec/c0127]. Then: "Ensuite on se synchronise sur une heure de changement." [quebec/c0137]. A change to the work had to reach the bot. "There is a bot running to maintain it. You will need to get him to edit his pattern before you can add this." [zootopia/c0122]. Later: "Bot template updated!" [zootopia/c0124]. A neighbour complained to r/virginiatech, "Could you please stop adding orange to ruin the border of our A?" [virginiatech/c0087], and a member answered, "We have bots running, but as soon as our guy is awake, they will stop" [virginiatech/c0088].

The rooms argued over the scripts. A r/evex member had taken a rival's bot and changed it to fit the room's banner, and asked, "Do you guys think it would be in the spirit of evex to use the script to clean up the vandalism?" [evex/c0059]. Another answered, "Yeah, I think given the circumstances, that's reasonable." [evex/c0060]. In r/placecanada a member defended the scripts: "A lot of well intentioned Canadians were unknowingly messing it up." [placecanada/c0177]. Another left: "Well, I'm done with /r/placecanada then, I think we've missed the point of place altogether. It's a social experiment, not an opportunity to have bots maintain our image." [placecanada/c0178]. In r/bakchodi a member refused to run another's script: "Running your script would mean, you can change anything and do anything which is too much power for one person/group." [bakchodi/c0154].

Members called attacks. A r/quebec member called the room to arms against the Canadian flag: "CONFRÈRE ET CONSŒUR, CECI EST UN APPEL AUX ARMES! À L'ATTAQUE DU DRAPEAU CANADIEN! SORTEZ LES PIXELS BLEU!" [quebec/c0041]. In r/ohio the first calls were to attack and to build, two minutes apart: "Help us get rid of the UM flag on /r/place" [ohio/c0008]; "Help create Ohioan flag!" [ohio/c0009]. A r/england member posted a script to convert a neighbour: "this should replace the scottish flag with he english :D" [england/c0012]. Members also refused. A r/alberta member proposed an attack, "Currently a Quebec flag has invaded a proud Canadian flag at 347/253." [alberta/c0015], and was told, "What? No. Go away." [alberta/c0019]. In r/AmericanFlaginPlace: "No no I don't condone changing other flags" [AmericanFlaginPlace/c0220]. In r/reddevils, a call, "anybody up for destroying the chelsea badge" [reddevils/c0193], was answered, "the fuck? get a life, you weirdo." [reddevils/c0194].

Rivalry ran on after the canvas. A r/reddevils member thanked a rival room "who agreed to the truce and showed respect for the 96." [reddevils/c0207]. The same post went on, "Now that /r/place is over, we can stop pretending be nice and resume normality. Ya cunts." [reddevils/c0208].

2. What the form does

These elements are instantiated in 80 per cent of the defining members or more (_analysis/d5f_model.py, current ledger, particular lines included). The model's prose says them so.

• P01 (113 of 113; 100 per cent of the 558): "The room calls its own members, and kindred subs, to come and place for a work: to start it, build it, finish it or hold it."
• P02 (112 of 113; 100 per cent of the 558): "The room settles what its mark will show of it: a member proposes a picture, the room argues its design, makes its land's flag or emblems the mark, signs it or leaves it unsigned, claims a mark others made, adds to it or enlarges it, or adds a personal piece to a shared mark."
• P03 (110 of 113; 97 per cent of the 558): "The room builds its mark, and members report its state to the thread: what is placed, done or missing, and where."
• P05 (109 of 113; 93 per cent of the 558): "The room keeps its placed work against erosion: members watch it and repair changed pixels, and the room rallies to defend it under attack, covers the night, hardens its shape and puts upkeep before growth. Repair restores the form the keepers know. A change the room has planned or agreed (P02) is therefore repaired away as damage until its keepers are told of it, and it is lost or given up where the telling does not reach them."
• P07 (108 of 113; 89 per cent of the 558): "Rooms spare their neighbours' work, rein in their own attackers, apologise for damage and appeal to attackers to stop."
• P12 (108 of 113; 97 per cent of the 558): "The room records what happened to its work and to the canvas around it: screenshots and timelapses, reports of its fate, mourning, imagined art, atlas entries, the end marked."
• P04 (107 of 113; 97 per cent of the 558): "Members circulate a template that lays out the mark pixel by pixel, or coordinates that locate it, ask for them, and ask strays to keep to them."
• P11 (106 of 113; 96 per cent of the 558): "When a work is up, the room marks it: announces it, celebrates it, credits makers and helpers, reports members' own parts and says what working with strangers meant."
• P16 (106 of 113; 91 per cent of the 558): "Rooms help one another's works and trade help: they give pixels to a neighbour's mark, ask other rooms for help, barter help for space or repair, thank their allies, greet them, and turn requests away."
• R01 (104 of 113; 96 per cent of the 558): "The starter: a member who proposes the mark, maps it or begins placing it. Others joining is not part of the role: it is the answer to the room's call (P15), in the order A02 and A01 state."
• P09 (103 of 113; 78 per cent of the 558): "Rooms attack others' work by the recurring moves the canvas affords: erasing, encroaching, converting a sign, raiding on a streamer's call, planting a script, altering a work as a joke."
• P15 (102 of 113; 91 per cent of the 558): "A member answers a call or proposal in one line that joins, assents, reports a part done or thanks, and the line asks for nothing back."
• P24 (100 of 113; 89 per cent of the 558): "Members ask what the canvas is, how to place, what a call or a name means and what a picture shows, and others explain the rule, the timer, the controls, whose mark a picture is and what happened. They ask before, during and after the close, and some questions get no answer."
• P06 (99 of 113; 87 per cent of the 558): "Members work out who changed their work and why: they trace placers and rooms, find friendly fire or their own mistake, blame officers, or disown placers acting in their name."
• P08 (99 of 113; 86 per cent of the 558): "Rooms propose, settle and contest borders, truces and deals with neighbours by talk, through envoys, and hold each other to them."
• R02 (97 of 113; 81 per cent of the 558): "The envoy: a member who acts for a room toward another room, carrying a proposal between threads or chats."
• K04 (91 of 113; 70 per cent of the 558): "The room acts as a body it was before the canvas, or as a faith in a colour: it argues the nation's history, belonging and politics beyond its flag, carries in the sub's quarrel, lore, jokes or ideology, or professes and spreads a colour."
• P23 (91 of 113; 69 per cent of the 558): "Members move the room's planning into a chat, an existing server or a new one, and invite helpers to it. They bring the chat's designs, decisions and warnings back to the thread. They argue which chat to use, whether a chat is needed or secure, whether it is official, and whether it may decide for the work or bind placers."
• P26 (91 of 113; 78 per cent of the 558): "Members make new jokes out of the canvas work, its mistakes, its damage and its neighbours: puns on the mark, mock names and titles for a figure, and jokes about attackers and bots. The room takes the jokes up, and some members want a joke kept in the work."

The model brings members to a room by calls, has them build and keep a mark, and has some of them turn against a rival (A15). It holds the chat as a candidate (P23), scripts as machine hands (P14) that follow upkeep under strain (A06), and attack calls (P09) met by restraint (A16). These rooms do all of it, and more of the contest. P09, attacks on others' work, is instantiated in 103 of 113 defining members (91 per cent), against 78 per cent of the 558 defining rooms. P18, the contest carried in talk, is instantiated in 88 (78 per cent), against 61. P17, coalitions, in 77 (68 per cent), against 52. P23, the chat, in 91 (81 per cent), against 69. P14, scripts, in 59 (52 per cent), against 40.

3. What it does differently, element by element and arrow by arrow

The change signature. The form's defining members change three fourth-order themes more than the defining population does (at 1.5 times its share or more, in a third of the members or more). Workarounds, the theme of scripts and spare accounts, is changed by 43.4 per cent of them, against 24.9 per cent of the 558 (share ratio 2.06). Backstage decision-making, the theme of the chat, by 42.5 per cent, against 22.8 (ratio 2.29). Repertoire of contention, the theme of attack calls, by 35.4 per cent, against 17.2 (ratio 2.35). Each is held by under half the members. That is why D4a-08c named the form a mixture.

Element by element and arrow by arrow. The table gives every element or arrow and op that 14 defining members or more change, at 1.2 times the defining population's share or more (_analysis/d5f_facts.py). A selected line specifies the model (add-condition, add-step), restricts it (restrict), connects two of its parts (link) or contradicts it. The kind of a line is not relied on (J: kappa 0.08).

No defining member holds a contradict line, so these rooms replace nothing in the model. I read the lines behind the table whole (_analysis/d5f_dump.py: 87 lines on scripts, the chat and withdrawal).

• P14, scripts: specified (add-step 33 members, 29 per cent against 14). The added steps are the coordination scripts need. Members keep script versions and targets in step, route changes through the person who sets the targets, and stop scripts that undo a neighbour's work. r/AmericanFlaginPlace: "Synchronizing script versions and coordinates prevents outdated targets and off-by-one links from wasting placements by repairing one another." r/zootopia: "A proposed revision must reach the operator and be encoded in the target before automated upkeep stops undoing it." Members also argue who may change a shared target and whether bots are fair. r/bakchodi: "Runners evaluate who may change shared targets and refuse to concentrate mutable script power in an untrusted person or group." And scripts serve attacks. r/argentina: "Members propose their own bots to overcome automated resistance to an attempted erasure, not only to maintain their placed work."
• P23, the chat: specified (add-step 20 members, add-condition 17). The steps keep the chat reachable: replacing expired invitations, repairing links, screening who may enter, and relaying between the chat and the thread. r/GranColombia: "Maintaining chat access requires replacing invalid invitations and repairing a failed official link." r/TransFlagPlace: "Admission to the planning venue can require showing pixels already worked on, distinguishing entry screening from merely circulating an invitation." The conditions say whom the chat reaches. r/masseffect: "Chat coordination must reach placers outside the chat, as wider participation and a wished-for sticky reveal an acknowledged communication gap."
• P32, a member stepping away or a quarrel repaired: restricted (12 members, 2.04 times the defining population's share). The lines restrict the element's account of strain. A member who left did so on a principle, not under strain. r/placecanada: "A member leaves because scripts violate the activity's purpose, so departure here must include principled objection rather than assume strain or personal mistreatment."
• A15, from a call to an attack: restricted (18 members, 1.39 times). The record does not show recruited builders turning into attackers (section 7).
• A05, P07 and P08, terms and sparing: specified (add-condition 16, 15; add-step 18). As in form A, an agreement spares a neighbour only where its terms reach the placers, and here the scripts. r/FederationPlace: "A negotiated concession requires updating active bot targets rather than assuming assent immediately controls every running version"; that line restricts A05.

What the model would not predict. The model has machine hands, a chat candidate and attack calls. It does not say that each of them needs its own coordination. A room of this form keeps its scripts in step and argues who controls them. It keeps its chat open and carries the chat's decisions to the thread. It calls attacks, and members refuse some of them, often without a reason. And the same condition runs through the scripts and the chat as through form A's terms: a change binds only the placers, and the running scripts, it reaches.

The rooms that show the form best, by the rule in section 11, are r/quebec and r/reddevils; the one that shows it least well is r/lofihiphop.

What the claim rests on. The form is a cut of the allocation (changes two thirds, codes one third, Ward's method, six forms by J's ruling). Its stability on matched subsamples is about 0.21, and 43 of its defining rooms lie nearer another form's centre. The table's counts are the ledger's. That members kept scripts and chats in step, and called and refused attacks, is a claim on their words, through cite.py, in sections 1, 4 and 11.

The name, read against the members. The name is "the work behind the thread: the chat, the scripts and raiding". The strongest argument that it names the cut rather than what the rooms did: it lists three signatures that are each held by under half the members, and joins two of the eight forms of D4a-08b (the chat and the scripts; raiding as the work). A reader who suspected the name would look for members who hold none of the three. There are 20 of 113 (section 14). The name is accurate as a list, and it says what the form is: a mixture. I keep it, and I make no renaming proposal.

4. The concepts it employs

First-order concepts for each change the form leans to, through cite.py:

• The scripts kept in step. "Since the scripts both scan right to left then top to bottom, people running the scripts get to that point, and if the opposite one ran first, they use your place to "fix" it... so that's wasting some effort." [AmericanFlaginPlace/c0469]. "Right now, we need anyone to stop using old scripts and move to the new one above." [ukplace/c0027].
• Who controls a script. "I agree I could change it, but you will have to take a leap of faith my friend." [bakchodi/c0153]. "we were planning on centering the logo today. Your best bet is talking to y8QbrYsfrOW9rkt8Y4nNv2jQhxA= he has been setting the bot scripts for us." [minnesotavikings/c0231].
• The chat kept open. "looks like I also had the wrong link." [AprilKnights/c0014]. "Can you link to pixels you've worked on?" [TransFlagPlace/c0184].
• The chat's decisions brought back. "Spread the word to the discord" [dwarffortress/c0126]. "Si vous avez une meilleure idée venez la faire valoir sur le discord." [quebec/c0123].
• The attack called. "can we plzzzz get rid of the commie flag" [AmericanFlaginPlace/c0007].
• The attack refused. "What? No. Go away." [alberta/c0019].

5. Composition here

Three judgments are kept apart.

The original global model (historical). verdicts-D.jsonl, by the last analyst ruling or else the readers' agreement. All 141 members: composes 58, composes with residue 81, does not compose 0, cannot tell 2. The 113 defining members: composes 43, composes with residue 70, does not compose 0, cannot tell 0. The two that cannot tell are r/Braveryjerk, a thin room with one selected change and 4 coded concepts, and r/wario, a core room with 1. These verdicts describe the unadapted model at the first return.

The adapted local accounts. By adaptation-returns.jsonl and the current model hash (46384686), as vlib.local_return_states reads them, all 141 members are unresolved; none is validated and none has insufficient evidence. The limit D3 named is the same for each: the labelers marked every local account unresolved, and prior.md section 3's measure of local validation was not computed (J after the D3c interview). The unresolved members are:

r/aeon, r/afip, r/albania, r/alberta, r/AmericanFlaginPlace, r/anarchism, r/AprilKnights, r/archlinux, r/argentina, r/armenia, r/armok, r/aromantic, r/asexual, r/austria, r/AyyMD, r/azores, r/bakchodi, r/bangladesh, r/bees, r/belgium, r/brasil, r/Bravenewbies, r/Braveryjerk, r/canucks, r/cardinals, r/catalonia, r/chibears, r/chile, r/cloud9, r/counting, r/cuboulder, r/czech, r/darksouls, r/DatBoi, r/destiny, r/Dominican, r/duckgame, r/dwarffortress, r/england, r/EraseThePlace, r/evex, r/falcons, r/FaroeIslands, r/FederationPlace, r/floridagators, r/france, r/freedomplanet, r/fullcommunism, r/GranColombia, r/GreenCorner, r/GuardiansOfDatBoi, r/HomestarRunner, r/Homura, r/hyperlightdrifter, r/ik_ihe, r/india, r/indieheads, r/kanye, r/latvia, r/lebanon, r/linux, r/liquicity, r/lithuania, r/littlebusters, r/livecounting, r/lofihiphop, r/loltyler1, r/luxembourg, r/madokamagica, r/masseffect, r/megaman, r/mexico, r/minnesotavikings, r/monero, r/msu, r/nerf, r/neu, r/norge, r/ockytop, r/ohio, r/OKState, r/OrderOfTheKoi, r/pakistan, r/parahumans, r/pathofexile, r/pgang, r/Pigifs, r/PinkVomitMonster, r/placecanada, r/placehfarts, r/PlaceNL, r/placesnek, r/placestart, r/polska, r/purplecorner, r/PurplePixels, r/quebec, r/quq, r/reddevils, r/russia, r/Russiaclan, r/sakartvelo, r/serbia, r/shitredditsays, r/simonfraser, r/singapore, r/Slovakia, r/slovenia, r/spain, r/spongebob, r/stlouis, r/stlouisblues, r/straya, r/sweden, r/tagpro, r/TeamDignitas, r/theblackvoid, r/thebluecorner, r/Thegreatblackhole, r/TheGreatGreenBox, r/theitalyplace, r/touhou, r/TransFlagPlace, r/turkey, r/udub, r/ukplace, r/ukraine, r/UMiami, r/undertale, r/unitedkingdom, r/uofm, r/uofmn, r/virginiatech, r/wales, r/wallstreetbets, r/wario, r/WisconsinBadgers, r/worldpowers, r/WPI, r/wsu, r/zootopia

The shared form explanation: unresolved. The form's members share no single lean. Each of its three signatures is held by under half its defining members, and the three are held by different rooms at about the rate chance would give (section 14). 43 of the 113 defining members lie nearer another form's centre. So the form describes these rooms as a group whose work ran behind the thread in one of three ways. It does not explain them jointly. Every member's own adapted account is unresolved as well. A verdict of composes with residue on the original model is not a current local or shared failure.

6. How the model runs here

Counts are of defining members with a current-ledger line, particular lines included (_analysis/d5f_model.py); they count any line of an op.

The elements that do the work. The elements of section 2, with the contest above the population's rate: P09 (91 per cent against 78), P18 (78 against 61), P17 (68 against 52), P23 (81 against 69) and P14 (52 against 40).

The elements that sit idle. P34 is absent in 111 of 113 defining members, P30 in 99, A21 in 98, K07 in 92, P28 in 89, P33 in 87 and P29 in 78. They are idle in the population too. One idle arrow marks the form: A10, from judging too few hands to the move, is absent in 79 of 113 (70 per cent), against 53 per cent of the 558. These rooms seldom moved.

The elements that fit less here. K01, the April Fools frame, is instantiated in 45 of 113 (40 per cent), against 57 per cent of the 558.

What these rooms do that the model has no place for. 28 of 113 defining members carry 37 propose lines, against 210 of the 558 defining rooms. The propose lines are not part of the form's signatures.

Where the room models and my reading disagree. They agree. r/quebec's model keeps "the executable-target condition because a script must actually update", and r/AmericanFlaginPlace's model says that "Coordinate errors and mutually correcting scripts also require technical synchronization beyond merely telling people the latest intention". My reading of the members' lines is the same.

The held proposals (QD4-001; never served to any room, not re-checked). The model above is the frozen version. J ruled that both held proposals are stated in full wherever the model is reported. They are, as the tree file states them:

• P05, move 198 (contrasting), history lines 173 to 176, reverted by line 181 (move 203). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." The status would be bounded. The bound would read: "It does not hold where the keepers read a planned change from its shape and stop repairing it with no telling: completeanarchy, polska, satania, halo, bangtan, thesilphroad (R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018), a candidate branch, 'the shape read' (F-024). It does not hold where informed members hold the change against keepers who do not know: armok, maryland, oneshot (R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013), a limit below the trigger, at three nodes. Amended at D4a-01, after the D3 freeze (46384686...); not re-checked: no room was served these words." Rooms: completeanarchy, polska, satania, halo, bangtan, thesilphroad, armok, maryland, oneshot. Lines: R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018, R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013.
• A11, move 199 (dropping working hypotheses), history lines 177 to 180, reverted by line 182 (move 203). The arrow from P02 to P04 would be withdrawn (status withdrawn, in_model false). Its reason, as written: "Rule 16 and rule 14: preserve what remains supported, and replace or withdraw what does not. No defensible formulation of A11 as an arrow survives the return. (1) The order between rooms never beat its null (111 of 185 rooms, 0.600; null p95 0.670; base_rate_beaten false), and C2 withdrew it, keeping a transition inside threads. (2) Inside threads, the return's census (D3a-38, re-run as _analysis/d4a01_a11_classes.json) shows the transition in 111 rooms and template first in 98 of the 228 rooms whose lines show both ends; across threads 19 more. The reverse order is nearly as common, so the arrow carries no direction. (3) The failure clause is present and stands alone in 117 rooms: talk only in 31 (berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia) and layout only in 86. (4) The mechanism's word 'settled' is contradicted by 261 accepted restrict lines whose 'how' says a template does not settle the design for good (rival templates, polls, later redesigns, placers who deviate). A reworded arrow (a layout answers design talk in its thread) would be a new claim, never served to any room, with its reverse nearly as common: a co-occurrence, not an arrow. What remains supported, that design talk and layouts meet in threads, is held by P02's and P04's statements and ranges ('a design argued over days and redone'; 'an official template the room asks everyone to follow against other versions'), which stand. The arrow's record keeps its evidence and reasoning." Rooms (the talk-only rooms of the failure clause): berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia. Lines (the first-return lines of the census classes talk only, layout only and template first, 216): 2007scape-012, 4chan-011, AMD-012, AmericanFlaginPlace-009, AvoArmy-011, AyyMD-041, CKCrusaders-041, CSUFoCo-015, DestinyTheGame-014, DevonUK-010, FinalFantasy-014, GuardiansOfDatBoi-009, HomestarRunner-015, MonkeyIsland-011, NewMexico-015, ScottPilgrim-015, Temple-041, TsundereSharks-048, adventuretime-041, aggies-050, albania-046, alberta-016, anaheimducks-015, animalcrossing-053, anime-012, argentina-051, armenia-030, bardmains-055, berkeley-038, berserk-012, bih-036, bisexual-012, bitcoin-012, blackmirror-046, borderlands-020, bostonbruins-052, brasil-011, canada-012, catalonia-009, catholicism-011, cfb-048, chibears-010, chicubs-010, cirkeltrek-013, clashroyale-045, completeanarchy-011, criticalrole-043, crusaderkings-039, cubers-014, cuboulder-008, czech-014, dankmemes-045, darksouls-042, detroitlions-049, edboxes-046, edmontonoilers-041, empiredidnothingwrong-013, england-045, ethereum-056, europe-050, eve-049, fivenightsatfreddys-012, flashtv-055, floridagators-035, flyers-035, formula1-048, forsen-010, ftlgame-044, fxKorea-010, gameattack-015, gamindustri-053, gatech-041, ghibli-010, globaloffensive-012, greenbaypackers-011, guatemala-010, habs-011, heyyea-010, hongkong-047, hsv-012, hyperlightdrifter-046, indieheads-056, indonesia-035, ireland-045, italy-035, katawashoujo-041, lakers-009, latvia-029, leagueoflegends-042, lifeisstrange-013, linux-015, littlewitchacademia-012, loliconsunite-010, lost-044, lovelive-041, lsu-049, luxembourg-012, madokamagica-041, magictcg-010, mechanicalkeyboards-042, metalgearsolid-013, mexico-041, miamidolphins-041, minecraft-017, mit-041, mizzou-018, mls-053, monalisaclan-013, morrowind-011, msu-011, muse-048, mylittlepony-011, nVade-013, naruto-010, nbaspurs-056, necrodancer-011, neopets-047, newzealand-046, nightinthewoods-012, nin-012, ockytop-042, opticgaming-012, overwatch-017, parahumans-013, parrots-013, pathofexile-012, pcmasterrace-013, pebble-007, penguins-055, philippines-052, pitt-041, placeDE-041, placecanada-013, placesnek-031, planetside-056, polska-054, portal-012, portugal-082, predators-010, purdue-051, puzzleanddragons-013, quebec-013, radiohead-010, rainbowgrid-006, rangers-045, re_zero-042, redpandas-018, rickandmorty-042, rit-011, rocketbeans-008, rocketleague-011, romania-015, roosterteeth-013, rpi-049, russia-052, rust-010, rutgers-012, samuraijack-047, scp-014, seahawks-014, serbia-051, singapore-016, slovenia-041, smite-010, southpark-012, spacexmasterrace-052, spain-035, ss13-016, ssbpm-012, stardewvalley-058, starryknights-041, stevenuniverse-012, straya-047, suomi-041, survivor-035, sweden-045, tampabaylightning-045, terraria-048, teslamotors-012, tf2-041, thebluecorner-016, theexpanse-012, theitalyplace-054, thepointing-043, thesimpsons-011, tinytardis-009, titanfall-013, torontoraptors-016, totallynotrobots-013, transformers-046, trees-013, turkey-055, twentyonepilots-012, ubc-046, ucf-050, uiuc-011, ultrahardcore-005, undertale-011, unitedkingdom-035, unturned-013, uofm-008, uofmn-035, uruguay-012, utahjazz-009, utaustin-013, uva-042, uwaterloo-011, vegan-043, virginiatech-043, weezer-053, wine-011, witcher-017, worldoftanks-015, xenoblade_chronicles-012, zelda-061, zootopia-012.

2 of form B's rooms are among the rooms of the P05 proposal (r/armok, r/polska). 12 are among the talk-only rooms of the A11 proposal's failure clause: r/HomestarRunner, r/indieheads, r/latvia, r/mexico, r/msu, r/placesnek, r/polska, r/quebec, r/slovenia, r/spain, r/unitedkingdom, r/zootopia.

7. The restrict lines: the arrow fails here, or the record cannot show it

The rule, logged at D5a-36 before reading, unchanged. I read every restrict line on an arrow held by a defining member, 292 lines, and sorted each how sentence (_analysis/d5f_restricts.py; my sort in d5a37_sort_1.json to d5a37_sort_4.json, joined in d5a37_restrict_sorted.json). The arrow fails here: the line says the consequent came without the antecedent, from another source or in another order, or that the antecedent did not lead to it. The record cannot show it: the line says the order, the link or the step is not visible, not dated or not established in the record. Both, where it says both. Neither, where it states a condition or a scope, or says that the two acts coincide or overlap. This is one reader's sort, mine; no second coder read it (J: no readers for the rest of the run).

The form's own arrows. A06 runs from keeping to scripts: scripts follow upkeep under strain. In 11 of its 18 restrict lines here the arrow fails, and in 4 more it fails and the record cannot show the rest. Scripts and spare accounts came for building or for attack, before any strain. r/TeamDignitas: "Spare accounts are used before the first maintenance call, so upkeep pressure cannot explain the onset of their observed use." A06's own bound already says that where a room scripted its building from the start, machine hands come before any upkeep, and that spare accounts can serve an attack first. So these lines restate the bound. A15 runs from a call to an attack. In 11 of its 18 lines the record cannot show it: the members called builders and called attacks, but the record does not show the same hands turned from one to the other. r/chile: "Recruitment and attack calls coexist without identifying recruits diverted from construction into attack." A16 runs from an attack call to restraint. In 7 of its 10 lines the arrow fails as its mechanism states it: the refusal came bare, or the proposer withdrew. r/serbia: "This refusal gives no reason, preserving a local exception to the model's usual reason-giving pattern without contradicting its statistical qualification." The mechanism says a refusal usually comes with a reason, so these lines are inside it too.

The arrows every form restricts. A11 (a template settles a design) fails here in 34 of 56 lines, and A10 (judging too few hands, then the move) in 15 of 20. They are restricted here at or below the population's rate; A10 far below it, because these rooms seldom moved. A12 (a call, then a bare answer) fails in 12 of 21 lines: acceptances came with a question or a condition, refusals without a reason.

Where the record cannot show it. The record cannot show who joined because of a call (A01, 8 of 11 lines), that a call turned members against a rival (A15, 11 of 18), or whether help arrived (A13, 7 of 24).

So the two readings divide by kind, as in form A. Where the line concerns the order of two acts the rooms report (keeping and scripts, a template and a design, an attack call and its answer), it mostly says the arrow fails as stated, and mostly inside bounds the model already writes. Where it concerns cause (recruited hands turned to attack, help delivered), it mostly says the record cannot show it. Across all 292 lines: the arrow fails here in 135, the record cannot show it in 83, both in 22, neither in 52.

8. The one relationship that runs differently here

A06 runs from P05 (keeping) to P14 (machine hands). Its connection: "in a room carrying both, the first act of upkeep or defence comes before the first script, bot or extra account". Its mechanism: "Upkeep under attack outruns what one pixel per interval can hold, and members turn to scripts and spare accounts to keep up."

In r/AmericanFlaginPlace it runs as stated, in the members' words. The room built its flag and turned to keeping it: "We have built the American flag. Now we must maintain it." [AmericanFlaginPlace/c0128]. Under attack, a member argued for scripts: "Everyone is using scripts. We're being attacked by scripts. If we don't adapt, we lose." [AmericanFlaginPlace/c0473].

In r/placecanada it runs on another ground. The scripts kept the room's own members from undoing the design: "Yes, we are using several scripts. It was the only way we could get our maple leaf to retain it's shape. A lot of well intentioned Canadians were unknowingly messing it up." [placecanada/c0177]. The strain came from friendly hands, not from an attack, and it cost the room a member (section 1). In r/england a script served a conversion, not upkeep: "this should replace the scottish flag with he english :D" [england/c0012].

In 18 of 113 defining members a current-ledger line restricts A06, against 17.0 per cent of the 558; the form does not restrict it more than the population does. What runs differently here is what follows the script: the rooms of this form give the script its own coordination (P14 add-step in 33 members, section 3). The model has scripts follow upkeep. In these rooms the scripts are themselves kept, updated and argued over.

This is description, not a test. A06's expectation in form B is 0.600 (3 within-case datings over 705 rooms, times 141), so A06 is not-testable-here (section 10).

9. Fourth-order themes over- and under-represented

The rule was logged at D5a-01 before it ran (_analysis/d5_themes.py), and it is applied here to the defining members' codes (_analysis/d5f_facts.py). A member's coded concepts are counted by the fourth-order themes of their second-order theme's placements, and the form's pooled share on a theme is set against the pooled share over all 705 rooms. Over-represented: a ratio of 1.5 or more, with the theme present in 5 members or more. Under-represented: a ratio of 0.67 or less, with a population share of 1 per cent or more. These are shares of what the coders coded in these rooms, never a property of the rooms (contract section 5).

Over-represented (10).

• Neo-tribes: 4.4 per cent of the defining members' coded concepts against 1.1 per cent (ratio 4.14), in 8 members.
• Decided order: 0.8 per cent of the defining members' coded concepts against 0.3 per cent (ratio 2.72), in 14 members.
• Meta-organization: 3.5 per cent of the defining members' coded concepts against 1.6 per cent (ratio 2.22), in 39 members.
• Repertoire of contention: 6.7 per cent of the defining members' coded concepts against 3.0 per cent (ratio 2.21), in 76 members.
• Flagging the nation: 1.7 per cent of the defining members' coded concepts against 0.8 per cent (ratio 2.18), in 27 members.
• Workarounds: 4.2 per cent of the defining members' coded concepts against 2.1 per cent (ratio 1.99), in 70 members.
• Backstage decision-making: 4.2 per cent of the defining members' coded concepts against 2.4 per cent (ratio 1.78), in 69 members.
• Symbolic boundaries: 0.8 per cent of the defining members' coded concepts against 0.4 per cent (ratio 1.75), in 16 members.
• Rivalry: 1.7 per cent of the defining members' coded concepts against 1.0 per cent (ratio 1.67), in 31 members.
• Live and let live: 3.5 per cent of the defining members' coded concepts against 2.1 per cent (ratio 1.65), in 50 members.

In the rooms' words, from members holding the largest share on each theme (_analysis/d5f_theme_quotes.py): Workarounds, "Right now, we need anyone to stop using old scripts and move to the new one above." [ukplace/c0027]. Backstage decision-making, "Here is a discord server I just created just for this sub." [bangladesh/c0025]. Repertoire of contention, "Ayncraps trying to steal our flag on /place is like a visual representation of their relationship to the actual anarchist movement." [anarchism/c0055]. Live and let live, "There's a massive difference between untouched, and bumming someone else's work." [worldpowers/c0025]. Meta-organization, "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]. Flagging the nation, "making a hearth between the flags, like sweden and norway. wanna join?" [lithuania/c0077].

Under-represented (2): Keying (ratio 0.23), Direct information sharing (ratio 0.46).

The three signature themes restate the cut in part; the codes are a third of the distance. Beside them the coders coded more of the canvas as a field of nations, rivals and tribes, and of the argument over what may be covered (Live and let live). They coded less of the April Fools frame and less posting of the mark's state to the thread (Direct information sharing). That fits rooms whose work ran in chats and scripts, without showing why.

10. Arrows present, absent or not-testable-here

Section 1's arithmetic, declared at D5a-01: an arrow's expectation in a form is its within-case datings (its subs, counted over the 705 analysed rooms) over 705, times the form's n, here 141. Below one the arrow is not-testable-here, and no absence, boundary condition or failed proposition may be written from it. In form B the expectations run from 0.000 to 0.800:

• A01 (P01 to P03): 2 datings, expected 0.400; not-testable-here
• A02 (R01 to P01): 2 datings, expected 0.400; not-testable-here
• A03 (P03 to P05): 2 datings, expected 0.400; not-testable-here
• A04 (P05 to P08): 2 datings, expected 0.400; not-testable-here
• A05 (P08 to P07): 3 datings, expected 0.600; not-testable-here
• A06 (P05 to P14): 3 datings, expected 0.600; not-testable-here
• A07 (P03 to P11): 2 datings, expected 0.400; not-testable-here
• A08 (P11 to P12): 2 datings, expected 0.400; not-testable-here
• A09 (P12 to P13): 2 datings, expected 0.400; not-testable-here
• A10 (K02 to P10): 2 datings, expected 0.400; not-testable-here
• A11 (P02 to P04): 2 datings, expected 0.400; not-testable-here
• A12 (P01 to P15): 3 datings, expected 0.600; not-testable-here
• A13 (P05 to P16): 4 datings, expected 0.800; not-testable-here
• A14 (P08 to P16): 4 datings, expected 0.800; not-testable-here
• A15 (P01 to P09): 4 datings, expected 0.800; not-testable-here
• A16 (P09 to P07): 4 datings, expected 0.800; not-testable-here
• A17 (P09 to P08): 4 datings, expected 0.800; not-testable-here
• A18 (P09 to P18): 4 datings, expected 0.800; not-testable-here
• A19 (P05 to P17): 4 datings, expected 0.800; not-testable-here
• A20 (P01 to P20): 3 datings, expected 0.600; not-testable-here
• A21 (P08 to P21): 0 datings, expected 0.000; not-testable-here

Present: none. Absent: none. Not-testable-here: all 21. Members' current-ledger lines on an arrow (sections 7 and 8) are description only. Members among an arrow's within-case datings: r/czech (A17); r/DatBoi (A15); r/france (A20); r/lebanon (A12); r/mexico (A09); r/PlaceNL (A16, A17); r/reddevils (A03); r/stlouis (A15); r/touhou (A07); r/udub (A11); r/unitedkingdom (A18); r/wallstreetbets (A11). That is arithmetic about the model's own evidence, and it tests nothing in the form.

Propositions. N01, N02, N03, N04, N05, N06, N07, N08, N09; the highest expectation among the arrows they rest on is 0.800. Every proposition is not testable here; none holds and none fails against a real expectation. No findings.jsonl line is bounded from this form.

11. How representative members do the work

The rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_facts.py). Fit is a defining member's distance to the form's centre in the allocation's 892 columns. The best two are the nearest members whose selected changes and coded concepts are at or above the form's defining medians (10 changes, 131 concepts). The least well is the farthest defining member. The member read at length is, among the ten nearest, the one with the most selected changes not read at length earlier in stage D5. For a mixture the centre lies between its patterns: nine of the ten nearest rooms change two or three of the form's signature themes.

Best fit: r/quebec (distance 0.766; 22 selected changes; 203 coded concepts; first-return verdict composes, re-check grade composes with residue; in F28 and F29). Its selected changes hold the chat and the scripts, and its record holds an attack call as well. Its first post proposed the flag: "je ne vous propose rien de moins que de créer le drapeau du Québec sur /r/place." [quebec/c0001]. Members moved into another room's chat, and later made one of their own, because those who had worked on the flag wanted to keep in touch: "Ceux qui ont travaillé ensemble sur le drapeau avons décidé de garder contact entre nous et avons créé une chaîne Discord dédiée à /r/quebec." [quebec/c0092]. Friendly hands overwrote the design: "On a des problèmes de coordination. Beaucoup de Québécois remplacent notre patriote par du bleu." [quebec/c0124]. A member proposed an official design, "Bon, alors faisons la stratégie officielle de faire un joli drapeau Patriote." [quebec/c0125], and warned that the scripts would fight it unless they changed together: "ceux qui sont sur le script vont se battre automatiquement contre parce que c'est pas dans le plan vert blanc rouge." [quebec/c0199]. The room called an attack on the Canadian flag (section 1), and members argued against spending effort that way: "Tout ce que je dis c'est que plus on met de l'effort à endommager leur drapeau plutôt que de défendre le notre, plus on aura de trouble." [quebec/c0027]. It spared a square once a member explained that someone had made it for a dead friend: "Ok on laisse faire, c'est bien la moindre des choses." [quebec/c0170].

Second best fit: r/reddevils (distance 0.799; 22 selected changes; 236 coded concepts; first-return verdict composes with residue, re-check grade composes with residue; in F01, F03, F29 and F30; by the centres its point lies nearer form D's than form B's). A member pointed the room to its chat and asked for a script: "We also need a script or someone who can design a code for our crest to help fend off these attacks." [reddevils/c0149]. The script came, and a member welcomed it while refusing the chat (section 1). Members asked that a truce be posted so that placers would learn it: "Make a post quick about the truce so people like me stop trying to overtake them due ignorance." [reddevils/c0144]. One asked whether a truce was needed at all: "Do they outnumber us? Because if they don't I think there's no reason for a truce." [reddevils/c0236]. An attack call was turned down without a reason (section 1), and after the close the room's rivalry with a neighbour resumed in talk (section 1).

Least well: r/lofihiphop (distance 1.415; 6 selected changes; 12 coded concepts; first-return verdict composes; in F15, F21 and F30; its point lies nearer form E's centre). Its record is a few exchanges. Its first posts were April Fools jokes: "#HAH NICE APRIL FOOLS JOKE" [lofihiphop/c0002]. A member was confused by the plan, "im confused" [lofihiphop/c0006], and received an image. Late on the last day another proposed a takeover, "Let's take over the upper right hand corner for r/lofihiphop!!!" [lofihiphop/c0009], and was sent back to the existing plan and to the chat: "Peep discord and forums for updates on our plan." [lofihiphop/c0011]. Its lines touch the chat twice and hold no script and no attack call. It is in form B because Ward's method put it there.

Read at length: r/AmericanFlaginPlace (distance 0.807; 23 selected changes; 609 coded concepts; first-return verdict composes with residue, re-check grade composes with residue; in F08, F23 and F29). The rule chose it: among the ten nearest it has the most selected changes and was not read at length earlier. Its selected changes hold the chat and the scripts, and its record holds attack calls and their refusal. The room was made to build a large flag. A member opened a chat "to make the best use of our manpower" [AmericanFlaginPlace/c0060], and the chat's choices returned to the thread (section 1). The chat itself had to be kept: "Void raid on our discord server as of 8:43 am EST" [AmericanFlaginPlace/c0505]. Once the flag stood, members turned to keeping it: "We have built the American flag. Now we must maintain it." [AmericanFlaginPlace/c0128]. Under attack they turned to scripts (section 8), and the scripts had to be kept in step: "the one that i linked in the comment though was apparently off by one pixel and messing with the other one. i removed my comment, hopefully things will get sorted out" [AmericanFlaginPlace/c0470]. Members called attacks, "can we plzzzz get rid of the commie flag" [AmericanFlaginPlace/c0007], and members refused them (section 1). The room held a truce, "We have a truce with the tree and therefore RR. Also indie heads for their album cover. The flag is not to be expanded." [AmericanFlaginPlace/c0173], and admitted that some members broke it: "Some folks did get too aggressive with the expansion, despite pleas to hold back" [AmericanFlaginPlace/c0216]. It kept a political group's name off the flag while thanking that group for its help: "We are thankful for their help with building the flag, but getting political will only anger people which may lead to the flag being hurt." [AmericanFlaginPlace/c0151]. A member called the defence a losing battle and kept the script running: "I'll keep the script running, but that's losing battle." [AmericanFlaginPlace/c0465]. An hour later: "I was totally wrong." [AmericanFlaginPlace/c0466]. At the close a member was still calling defenders, "Please stay focused on the main goal- PROTECT THE FLAG!" [AmericanFlaginPlace/c0573], and was told, "Dude the war is over go home :)" [AmericanFlaginPlace/c0574]. What is unrepresentative about it: its record is the largest of the ten nearest, 609 coded concepts against the form's defining median of 131, and its record holds all three parts at once, where most members' changes hold one or two.

12. The branches its rooms come from

J asked that stage D6 build on the forms with the 35 branches as the level below. The branches do not nest in the forms: a branch was cut on one shared key, a form gathers rooms by the whole mix of their changes and codes. The table gives, for every branch, how many of its rooms are in form B, and the branch's share in B against B's share of the 705 rooms (141 of 705, 0.200). A ratio of 1 is what a branch would show if its rooms fell in the forms at random.

What the table shows. Six branches lean to form B at 1.5 times its share or more. They are the branches of machine hands and the chat:

• F08, machine hands kept on one target: 27 of 50.
• F16, the chat kept open: 15 of 35.
• F29, the chat's reach conditional: 10 of 25.
• F15, the plan kept current: 14 of 42.
• F30, the chat seen only through its invitations and returned reports: 8 of 24.
• F20, the close as news: 3 of 10.

No branch was cut on attack calls, so raiding has no branch to come from. 5 of the 103 rooms of F01, the April Fools play, are in form B. No branch lies mostly in form B: the largest share is F08's, 0.540.

Rooms in no branch. 54 rooms (33 defining): r/albania (thin), r/alberta, r/anarchism, r/argentina, r/armenia, r/aromantic (thin), r/asexual, r/austria, r/azores (thin), r/bangladesh, r/bees (thin), r/brasil, r/Bravenewbies (thin), r/Braveryjerk (thin), r/cardinals, r/counting (thin), r/cuboulder (thin), r/DatBoi, r/Dominican, r/duckgame, r/england, r/floridagators, r/france, r/GreenCorner, r/HomestarRunner, r/Homura (thin), r/latvia, r/littlebusters (thin), r/madokamagica, r/norge (thin), r/pathofexile, r/pgang (core), r/Pigifs (thin), r/PinkVomitMonster, r/placecanada, r/placehfarts (thin), r/placesnek, r/quq (core), r/Russiaclan, r/sakartvelo (core), r/singapore, r/Slovakia, r/stlouisblues, r/straya, r/sweden (thin), r/TeamDignitas, r/Thegreatblackhole, r/TheGreatGreenBox (thin), r/theitalyplace, r/UMiami (core), r/wales, r/wario (core), r/worldpowers, r/wsu (thin).

13. The nearest form and what separates them

The nearest form is A, the terms between neighbours, with the plan announced. The distances between form B's centre and the others are A 0.366, C 0.374, D 0.391, F 0.547, E 0.809; A and C lie at nearly the same distance. In the tree, B joins C (the design and its marking) at five forms, and the two join A at three. A and B are separated by what the rooms changed: A's members change the order between rooms and the plan, B's the chat, the scripts and attack calls. Both forms' lines carry the same condition, that a change binds only the placers and scripts it reaches.

The rooms between forms. D 19, A 15, C 6, F 3: these are the forms whose centres lie nearer than B's to its defining members, 43 rooms in all, more than a third. The room that could have gone either way, the defining member with the smallest margin to another centre, is r/kanye (14 selected changes, 471 coded concepts). Its point lies nearer form D's centre, the form of keeping. In its record a moderator turned down cheating during an attack; the coders' line: "A moderator rejects cheating during an attack, so maintenance pressure alone cannot establish accepted automation."

14. The split below the form, and whether the chat, the scripts and raiding stand apart

The split rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_split.py, on room-forms-tree-rooms.tsv). A split reads as a split when both parts hold 10 defining rooms or more and each part has a fourth-order change column (a node or a link) at 1.5 times the parent's defining share or more, held by a third of the part or more and by fewer in the other part. The walk descends only while splits read.

Form B's first split, at eight forms, does not read as a split. B.2 (25 defining rooms, 34 in all) leans to the repertoire of contention: 96 per cent of its defining rooms hold attack calls, against 18 per cent of B.1. It is the eight-form cut's "raiding as the work". B.1 (88 defining rooms, 107 in all) has no column of its own at 1.5 times the form's share. The share of defining rooms holding each signature theme in each part: B.1: Workarounds 0.375, Backstage decision-making 0.489, Repertoire of contention 0.182; B.2: Workarounds 0.640, Backstage decision-making 0.200, Repertoire of contention 0.960. The walk stops at the form.

Whether the chat, the scripts and raiding stand apart. The rule for this question was logged at this leg's opening, before any script ran (_analysis/d5f_mixture.py, d5a37_mixture.json). It takes the three signature columns, the defining members that hold each, their overlaps against independence, and where each set falls in the tree.

• They are held by different rooms, at about chance. Workarounds (the scripts; anchored elements P14, K05, K06) is held by 49 defining members, Backstage decision-making (the chat; P23, P33) by 48, and Repertoire of contention (attack calls; P09, C02, P33) by 40. The scripts and the chat overlap in 19 members, against 20.8 if the two were independent. The scripts and attack calls overlap in 18, against 17.3. The chat and attack calls overlap in 14, against 17.0. All three meet in 7, against 7.4. 20 members hold none of the three. 19 hold only the scripts, 22 only the chat and 15 only attack calls.
• The tree sorts them one level down, not at the first split. At the first split, 43 of the 48 chat members and 33 of the 49 script members fall in B.1, and 24 of the 40 attack members fall in B.2. At the second level they part: the chat sits in B.1.1 (35 of its 48 members; 54 defining rooms), the scripts in B.1.2 (24 of 49; 34 defining rooms) and in B.2.1 (15), and attack calls in B.2 (24 of B.2's 25 rooms hold them).
• By the split rule no part is a subform. Run from B.1, as a description beyond the walk (d5a37_split_B1.json), B.1's own split at twelve forms does not read either. B.1.2 leans to the scripts (2.20 times B.1's share; 0.706 of the part against 0.167) and to the negotiated order (0.824 against 0.407). B.1.1, the chat, has no lean of its own; it is the form's centre.
• The rule's outcome. I set it before any script ran: the patterns stand apart if their holders overlap no more than independence gives and the tree's first split sorts them into different parts; they are mixed if the holders overlap more than independence or neither condition holds. The overlaps are at independence, within a room. The first split does not sort the three into different parts: the chat and the scripts fall together in B.1. So the rule gives neither outcome. It did not foresee this case, and I report it as what the counts show: three patterns held by different rooms, which the tree sorts only at its second level, and none of them a subform by the split rule. Raiding is the nearest to a part of its own (B.2), the scripts come next (B.1.2), and the chat is the form's centre (B.1.1).

So the answer to the question is yes, as patterns, and no, as subforms. The chat, the scripts and raiding are three different things that rooms did behind the thread. Few rooms did all three. The allocation put them in one form; the counts above do not say why, and I have not measured it. B.2 (raiding) and B.1.2 (the scripts, with the terms) are candidate subforms for D6 (notes-D5.md), not cut here.

15. The thin and core rooms placed here

Thin rooms (23), placed by the whole mix of their changes and codes at the nearest form centre: r/afip (3 changes, 75 concepts), r/albania (3 changes, 69 concepts), r/aromantic (2 changes, 9 concepts), r/azores (1 change, 4 concepts), r/bees (1 change, 5 concepts), r/Bravenewbies (2 changes, 7 concepts), r/Braveryjerk (1 change, 4 concepts), r/counting (2 changes, 143 concepts), r/cuboulder (1 change, 35 concepts), r/destiny (4 changes, 96 concepts), r/Homura (1 change, 30 concepts), r/ik_ihe (2 changes, 15 concepts), r/littlebusters (1 change, 4 concepts), r/livecounting (4 changes, 61 concepts), r/norge (1 change, 302 concepts), r/Pigifs (4 changes, 38 concepts), r/placehfarts (1 change, 15 concepts), r/sweden (4 changes, 835 concepts), r/TheGreatGreenBox (4 changes, 57 concepts), r/ukraine (3 changes, 51 concepts), r/WisconsinBadgers (4 changes, 30 concepts), r/WPI (3 changes, 57 concepts), r/wsu (3 changes, 15 concepts).

Their selected lines weigh less and enter no share above. The most frequent are P14 add-step 4 (r/albania, r/livecounting, r/ukraine, r/WPI); P01 add-step 2 (r/Bravenewbies, r/Pigifs); P01 link 2 (r/afip, r/Bravenewbies); P04 link 2 (r/Braveryjerk, r/WisconsinBadgers); A11 restrict 2 (r/albania, r/WisconsinBadgers); P05 add-condition 2 (r/afip, r/ukraine); P03 add-step 2 (r/aromantic, r/ik_ihe); P11 link 2 (r/azores, r/cuboulder). Four of them add steps to scripts, as the defining members do.

Core rooms (5), with no selected change, placed by their codes alone at the nearest centre in the code columns: r/pgang (8 concepts; verdict composes-with-residue), r/quq (8 concepts; verdict composes), r/sakartvelo (5 concepts; verdict composes), r/UMiami (2 concepts; verdict composes), r/wario (1 concept; verdict cannot-tell). Their placement rests on 1 to 8 coded concepts each and is weak. r/wario is one of the form's two rooms whose verdict is cannot tell; the other, r/Braveryjerk, is a thin room.

16. The form test

The constructs. P14 (machine hands), P23 (the chat) and P09 (attack calls), at the fourth-order themes T4-009 (Workarounds), T4-010 (Backstage decision-making) and T4-020 (Repertoire of contention), with P18 (the contest in talk), P17 (coalitions) and the arrows A06, A15 and A16.

The relations. Within each part there is a relation. Scripts need their targets kept in step and their control argued; the chat needs its access kept and its decisions brought back; attack calls are answered, often by a refusal without a reason. Across the parts, a change binds only the placers and running scripts it reaches. But the three parts are not related to each other: their holders overlap at chance (section 14). So the form binds three sets of constructs, each with its own relations, and no relation among the sets.

Is it falsifiable? Within the parts, yes. A room whose scripts ran without anyone keeping their targets, or whose chat's decisions never returned to the thread, would fall outside them. As a form, the claim that the three belong together is already contradicted by the overlap counts.

The four organizing problems. The scripts and the chat bind information provision: a change must reach the running scripts and the placers outside the chat. The scripts bind the allocation of tasks to machines and the question of who may set them. Raiding binds nothing of the four on its own; it is the contest, a remainder the four problems do not name. Division of labour between rooms and reward are left free.

What varies among members. Which of the three a room did. That is the whole of the form's variation, and it is sorted by the tree at the second level.

Result: a grouping, not a form. The form holds three patterns that rooms did apart, at about chance overlap, and no relation joins them. Each pattern binds constructs and relations of its own, and two of them (raiding, B.2; the scripts, B.1.2) are candidate subforms for D6. I report form B as a grouping of the rooms whose work ran behind the thread, as D4a-08c named it.

17. What would make you doubt this is even a grouping

Three things.

First, the cut. 43 of the 113 defining rooms lie nearer another form's centre, more than in form A, and the stability of the cut is about 0.21. Form B is what remains between the other five forms as much as what its rooms share.

Second, my sort of the restrict lines and my mixture rule. One reader sorted 292 lines. And the mixture rule did not foresee the case the counts showed; the answer in section 14 is a description of the counts, not the rule's outcome.

Third, the survival figures, from the record, never from the canvas. The median organizing end is hour 72.30 for the 140 members with one, and the mean aftermath share is 0.0387. The coded work_remained field says kept in 72 members, lost in 42 and silent in 27. These figures are not compared here, and nothing in this account rests on them.

What would undo the grouping: a cut on a different weighting in which raiding and the scripts each form a group of their own and the chat falls into another form.

Room form C, the design and its marking: the form account

Written at D5a-38, 27 October 2026. The model is the version frozen at D3 (46384686d6173fdeb4c749667478c1363e675bc6b52bb6f4fdc211d387e68525). Form C is one of the six room forms of the cut J ruled at D4a-08 (room-forms-D4a08c.*); how every room reaches its form is in room-forms-allocation.md. It holds 125 of the 705 analysed rooms. 96 are defining rooms: rooms with 5 or more selected changes, which shaped the form. 27 are thin rooms (1 to 4 selected changes) and 2 are core rooms (no selected change), placed afterwards. Thin and core rooms weigh less: every share, signature, theme count, representative choice and split below is read on the 96 defining rooms, and the thin and core rooms are named in section 15.

A room form is not a branch: it gathers rooms by the whole mix of their changes (two thirds) and their codes (one third), and the 35 branches are the level below it (section 12). The form is a pole of a continuum: 28 of its 96 defining rooms lie nearer another form's centre (section 13). This file sits beside the room-forms files, not in forms/, because the stage's close-check reads every account in forms/ as a branch account (departures.jsonl line 18). Hours are counted from the start of the event (h+).

1. How these rooms organized, as a narrative

In these 125 subreddits much of the talk was about what the mark should show. Members proposed a picture, argued its colours and its size, held polls, and changed the design while they built it. The design was seldom settled for good. When a part was finished, someone proposed the next.

The work began with a proposal. "Lets get r/cubers into the pixel art going on at r/place. How about this design?" [cubers/c0018]. The design had to fit the hands the room had. A r/bardmains member wrote, "since we don't have THAT many people, I think something small like this is okay." [bardmains/c0006]. A r/esperanto member found the room had gone too big: "Yup. Seems like we went too big. This subreddit doesn't have enough people to do this properly :/" [esperanto/c0013]. It had to fit the canvas too. A r/hongkong member wrote, "removed 3 rows to not have to overwrite FREEUAB to the north. Now a 29 width x 26 height rectangle." [hongkong/c0030].

Members argued over details, and some tried to settle them by vote. In r/AMD: "Stop changing the color of the arrow! There is a strawpoll. Let's settle this and all get on one page." [AMD/c0277]. A r/aggies member was told to decide quickly, "because it is really ambiguous whether this is an attack by trolls/takeover." [aggies/c0132]. The organiser decided for the night: "Im just going to make it a white line get people unified and if they hate it it can be discussed tomorrow." [aggies/c0134]. Some choices were made by what was already on the canvas. Asked about a darker orange, the member who had started the r/bardmains mask answered, "Way too late to switch colors. We stayed with yellow just because there was a preexisting yellow blob when we started." [bardmains/c0015]. Members planned the order of the work so the design would hold while it changed: "Maybe if we change the letters to white first, so it still contrasts, then switch the black to blue." [sheffield/c0041].

A change to the design met the room's own keepers. In r/cubers a member proposed a wider cube, "Let's upgrade!" [cubers/c0169]. A builder found that "people think I'm just messing with it" [cubers/c0172], and gave up: "Yeah I gave up. I think some people like the newer design, but others are happy with the way it is, so I guess it stays." [cubers/c0173]. In r/trees: "Trying to get a bigger pattern going on the pineapple, but everyone keeps 'fixing' it" [trees/c0351]. In r/vegan a member saw new pixels removed "because some will think it's sabotage, so for now let's just aim for the 3-pixel G." [vegan/c0190]. Not every keeper who undid a change was uninformed. A r/FlaggyFlag member had seen the change and reversed it: "I tried this a little while ago, and it doesn't look good with the white part, so I started changing it back to blue." [FlaggyFlag/c0008]. A r/uvic member, asked whether to change the logo, answered, "I like what we have right now. I think it should stick" [uvic/c0052].

When the work was up, the rooms marked it, and often started again. "We built one logo. What does r/factorio do when we finish a build? We make a new one twice as big!" [factorio/c0058]. A r/gatech member celebrated that the canvas "will Forever have our Mark!" [gatech/c0070], and the next reply proposed more: "Now let's write r/gatech above it" [gatech/c0071]. At the close a r/bardmains member wrote, "It ended and someone put a red point in Bard's eye so we can't fix it face palm" [bardmains/c0072]. Another answered, "Still proud of what we made together though!" [bardmains/c0075].

2. What the form does

These elements are instantiated in 80 per cent of the defining members or more (_analysis/d5f_model.py, current ledger, particular lines included). The model's prose says them so.

• P01 (96 of 96; 100 per cent of the 558): "The room calls its own members, and kindred subs, to come and place for a work: to start it, build it, finish it or hold it."
• P02 (96 of 96; 100 per cent of the 558): "The room settles what its mark will show of it: a member proposes a picture, the room argues its design, makes its land's flag or emblems the mark, signs it or leaves it unsigned, claims a mark others made, adds to it or enlarges it, or adds a personal piece to a shared mark."
• P03 (96 of 96; 97 per cent of the 558): "The room builds its mark, and members report its state to the thread: what is placed, done or missing, and where."
• P04 (95 of 96; 97 per cent of the 558): "Members circulate a template that lays out the mark pixel by pixel, or coordinates that locate it, ask for them, and ask strays to keep to them."
• P11 (95 of 96; 96 per cent of the 558): "When a work is up, the room marks it: announces it, celebrates it, credits makers and helpers, reports members' own parts and says what working with strangers meant."
• P12 (95 of 96; 97 per cent of the 558): "The room records what happened to its work and to the canvas around it: screenshots and timelapses, reports of its fate, mourning, imagined art, atlas entries, the end marked."
• P05 (92 of 96; 93 per cent of the 558): "The room keeps its placed work against erosion: members watch it and repair changed pixels, and the room rallies to defend it under attack, covers the night, hardens its shape and puts upkeep before growth. Repair restores the form the keepers know. A change the room has planned or agreed (P02) is therefore repaired away as damage until its keepers are told of it, and it is lost or given up where the telling does not reach them."
• R01 (92 of 96; 96 per cent of the 558): "The starter: a member who proposes the mark, maps it or begins placing it. Others joining is not part of the role: it is the answer to the room's call (P15), in the order A02 and A01 state."
• P06 (90 of 96; 87 per cent of the 558): "Members work out who changed their work and why: they trace placers and rooms, find friendly fire or their own mistake, blame officers, or disown placers acting in their name."
• P15 (90 of 96; 91 per cent of the 558): "A member answers a call or proposal in one line that joins, assents, reports a part done or thanks, and the line asks for nothing back."
• P16 (89 of 96; 91 per cent of the 558): "Rooms help one another's works and trade help: they give pixels to a neighbour's mark, ask other rooms for help, barter help for space or repair, thank their allies, greet them, and turn requests away."
• P07 (86 of 96; 89 per cent of the 558): "Rooms spare their neighbours' work, rein in their own attackers, apologise for damage and appeal to attackers to stop."
• P08 (82 of 96; 86 per cent of the 558): "Rooms propose, settle and contest borders, truces and deals with neighbours by talk, through envoys, and hold each other to them."
• P24 (82 of 96; 89 per cent of the 558): "Members ask what the canvas is, how to place, what a call or a name means and what a picture shows, and others explain the rule, the timer, the controls, whose mark a picture is and what happened. They ask before, during and after the close, and some questions get no answer."
• K02 (80 of 96; 82 per cent of the 558): "The room judges that it has too few hands or too little room for the work it wants: doubt, a canvas judged too full, a work judged absent or outclassed."
• K05 (79 of 96; 79 per cent of the 558): "Members place on their own time and with their own devices. They fit placing around sleep, study, exams, work and travel. They cannot place from a phone or while away, they leave when the wait is too long, they save pixels under the timer, they find the work addictive, and they report what it cost them."
• P26 (78 of 96; 78 per cent of the 558): "Members make new jokes out of the canvas work, its mistakes, its damage and its neighbours: puns on the mark, mock names and titles for a figure, and jokes about attackers and bots. The room takes the jokes up, and some members want a joke kept in the work."
• R02 (78 of 96; 81 per cent of the 558): "The envoy: a member who acts for a room toward another room, carrying a proposal between threads or chats."

The model has the room settle what its mark shows (P02), circulate a template (P04) that settles the design in a thread (A11), build it (P03), keep it (P05) and mark it when it is up (P11). These rooms do all of it. The difference is not in which elements they hold: P02 is instantiated in all 96 defining members, and in 99.5 per cent of the 558. It is in what they change.

3. What it does differently, element by element and arrow by arrow

The change signature. The form's defining members change one fourth-order theme more than the defining population does (at 1.5 times its share or more, in a third of the members or more): Collective representation, the theme of what the mark shows. 97.9 per cent of them change it, against 52.7 per cent of the 558 (share ratio 2.63). It is the clearest single lean of any form so far.

Element by element and arrow by arrow. The table gives every element or arrow and op that 14 defining members or more change, at 1.2 times the defining population's share or more (_analysis/d5f_facts.py). A selected line specifies the model (add-condition, add-step), restricts it (restrict), connects two of its parts (link) or contradicts it. The kind of a line is not relied on (J: kappa 0.08).

No defining member holds a contradict line, so these rooms replace nothing in the model. I read the lines behind the table whole (_analysis/d5f_dump.py: 113 lines on the design, keeping and templates).

• P02, the design: specified (add-step 21 members, 22 per cent against 11) and connected (link 19). The added steps are how a room settles a design for now: a poll, a provisional choice made overnight, a design sequenced so it holds while it changes, a design sized to the hands. r/aggies: "An organizer fixes a provisional design overnight and defers reconsideration instead of waiting for a completed vote." r/bitcoin: "The work is sequenced into logo, lettering and background to reduce simultaneous pixel demands." The links run from a finished part back to design. r/factorio: "A finished mark explicitly warrants making another larger one, returning completion to design and planning rather than only toward preservation." r/criticalrole: "Celebrating completed lettering is followed by d20 and logo proposals, so a finished stage can reopen design work."
• P05, keeping: restricted (46 members, 48 per cent against 37). All but one of these 47 lines restrict P05's telling clause: a change the room planned is repaired away until its keepers are told of it. Two things recur. Informed members disagreed with the change, so telling them would not have settled it. r/hentai: "Telling keepers about a redesign cannot alone secure it when informed participants explicitly oppose the temporary change's risk." r/calvinandhobbes: "Conflicting repair cannot be attributed solely to uninformed keepers when participants explicitly disagree about the intended design." Or the record does not show what the keepers knew. r/earthbound: "The information-deficit mechanism requires evidence of keeper knowledge because different repair targets alone cannot distinguish ignorance, dissent, or behaviour after an instruction."
• A11, from design talk to a template that settles it: restricted (58 members, 60 per cent against 48). Section 7 reads these lines: the template did not settle the design.
• P04, the template: specified (add-step 22 members). Keeping the template current: retiring old posts, reconciling rival corrections, messaging those who overwrite. r/tf2: "Standardization includes retiring outdated posts, announcing changed locations and stopping work on obsolete outlines."
• P01, the call: connected (link 14 members). A call returns after a finished part or a move.

What the model would not predict. The model has a template settle a design in a thread, and keeping restore the form the keepers know until they are told of a change. In these rooms the design is settled for a time and then reopened, often after each finish. And the telling clause meets disagreement as well as ignorance: some keepers knew of the change and did not want it. Of the 47 lines that restrict P05 (in 46 members), all but one restrict its telling clause, and none shows a change lost only because its keepers were not told; they say that telling was not enough, or that the record cannot tell ignorance from dissent.

The rooms that show the form best, by the rule in section 11, are r/cubers and r/PUBATTLEGROUNDS; the one that shows it least well is r/kuwait.

What the claim rests on. The form is a cut of the allocation (changes two thirds, codes one third, Ward's method, six forms by J's ruling). Its stability on matched subsamples is about 0.21, and 28 of its 96 defining rooms lie nearer another form's centre. The table's counts are the ledger's. That members argued, settled and reopened their designs, and that keepers knew of changes they undid, is a claim on their words, through cite.py, in sections 1, 4 and 11.

The name, read against the members. The name is "the design and its marking". The strongest argument that it names the cut rather than what the rooms did: the form has one signature, collective representation, and the name restates it. A reader who suspected the name would look for members whose record is not about the design. The least fitting member, r/kuwait, is about where to put a flag, not what it shows (section 11). But 97.9 per cent of the defining members change the design's theme, and the marking appears in the links from a finished part back to design. The name holds. I make no renaming proposal. One sharpening goes to notes-D5.md: the design settled for a time and reopened.

4. The concepts it employs

First-order concepts for each change the form leans to, through cite.py:

• The design proposed and sized. "I'm not an excellent pixel artist, and since we don't have THAT many people, I think something small like this is okay." [bardmains/c0006].
• The design settled for now. "Im just going to make it a white line get people unified and if they hate it it can be discussed tomorrow." [aggies/c0134]. "We're heading in this direction unless people are opposed." [bardmains/c0084].
• The design reopened after a finish. "We did it Reddit! (Again)" [factorio/c0071]. "Now let's write r/gatech above it" [gatech/c0071].
• A change repaired away. "Tried to do the same, but people think I'm just messing with it" [cubers/c0172].
• A change refused by those who knew of it. A member recalled a design agreed with a neighbour, "I even posed a mockup", refused by at least one member of the room, "so I gave up and deleted the posts." [cubers/c0309].
• The template kept current. "this post is out of date, follow the design of the stickied post or visit the discord" [tf2/c0297].

5. Composition here

Three judgments are kept apart.

The original global model (historical). verdicts-D.jsonl, by the last analyst ruling or else the readers' agreement. All 125 members: composes 55, composes with residue 68, does not compose 0, cannot tell 2. The 96 defining members: composes 42, composes with residue 54, does not compose 0, cannot tell 0. The two that cannot tell are thin rooms, r/bigbang (2 selected changes, 3 coded concepts) and r/watchmen (1, 2). These verdicts describe the unadapted model at the first return.

The adapted local accounts. By adaptation-returns.jsonl and the current model hash (46384686), as vlib.local_return_states reads them, all 125 members are unresolved; none is validated and none has insufficient evidence. The limit D3 named is the same for each: the labelers marked every local account unresolved, and prior.md section 3's measure of local validation was not computed (J after the D3c interview). The unresolved members are:

r/49ers, r/aceattorney, r/aeskwadraat, r/aggies, r/AMD, r/anaheimducks, r/aoe2, r/araragi, r/australia, r/austriahungary, r/AvoArmy, r/bardmains, r/bdsm, r/bigbang, r/bisexual, r/bitcoin, r/blackmirror, r/bretagne, r/bulgaria, r/calvinandhobbes, r/chicago, r/CKCrusaders, r/Clannad, r/coldplay, r/colombia, r/colorado, r/criticalrole, r/crusaderkings, r/crystalclear, r/CSUFoCo, r/cubers, r/daftpunk, r/davidbowie, r/dofus, r/dragonquest, r/drugs, r/earthbound, r/eder, r/egypt, r/esperanto, r/eve, r/factorio, r/farmcarrots, r/FlaggyFlag, r/fxKorea, r/GabrielDropout, r/gatech, r/greenland, r/GrowTheTree, r/guatemala, r/h3h3productions, r/harrypotter, r/hentai, r/Honduras, r/hongkong, r/katawashoujo, r/kindafunny, r/konosuba, r/korea, r/kuwait, r/leafs, r/malta, r/maryland, r/metalgearsolid, r/metroid, r/miamidolphins, r/mit, r/montenegro, r/muse, r/NewMexico, r/newzealand, r/nin, r/notredame, r/NovaScotia, r/overwatch, r/palestine, r/pitt, r/placeDE, r/PORTUGALCARALHO, r/ProfessorLayton, r/PUBATTLEGROUNDS, r/pusheen, r/puzzleanddragons, r/rangers, r/re_zero, r/redpandas, r/rickandmorty, r/rpi, r/sakuragakuin, r/satania, r/scotland, r/ScottPilgrim, r/sheffield, r/shield, r/sixers, r/skyrim, r/southafrica, r/spacexmasterrace, r/splatoon, r/ss13, r/ssbpm, r/starbound, r/starcraft, r/strangerthings, r/suomi, r/superman, r/SydneyFC, r/tampabaylightning, r/teamcube, r/tetris, r/texas, r/tf2, r/TheAdventuresofTintin, r/thepointing, r/timbers, r/torontoraptors, r/trees, r/truestl, r/ubc, r/unturned, r/uvic, r/vegan, r/vietnam, r/watchmen, r/weezer

The shared form explanation: supported as a lean, unresolved as an explanation. One change binds nearly every defining member: 97.9 per cent change collective representation, the most uniform signature of the six forms so far. The changes say what the model does not: the design is settled for a time and reopened, and keepers undo changes they know of as well as changes they do not. But the same changes are frequent in the population (52.7 per cent), 28 of the 96 defining members lie nearer another form's centre, and every member's own adapted account is unresolved. A verdict of composes with residue on the original model is not a current local or shared failure.

6. How the model runs here

Counts are of defining members with a current-ledger line, particular lines included (_analysis/d5f_model.py); they count any line of an op.

The elements that do the work. The elements of section 2. P27, choosing the spot before any loss, is instantiated in 76 of 96 (79 per cent), against 72; P06, working out who changed the work, in 90 (94 per cent), against 87.

The elements that sit idle. P34 is absent in 95 of 96 defining members, P30 in 90, P33 in 88, P28 in 81, P29 in 80, K07 in 74, A21 in 73 and K03 in 68. They are idle in the population too, and their idleness does not mark the form.

The elements that fit less here. P22, contesting which version of the canvas is kept after the close, is instantiated in 20 of 96 (21 per cent), against 32 per cent of the 558. These rooms argued their design during the work more than after it.

What these rooms do that the model has no place for. 33 of 96 defining members carry 62 propose lines, against 210 of the 558 defining rooms. The propose lines are not part of the form's lean.

Where the room models and my reading disagree. They agree. r/cubers' model keeps the condition that "communication alone cannot secure implementation", and r/bardmains' model holds that its "strengthened claim that uninformed keepers erase an agreed change remains unresolved". My reading of the members' lines is the same.

The held proposals (QD4-001; never served to any room, not re-checked). The model above is the frozen version. J ruled that both held proposals are stated in full wherever the model is reported. They are, as the tree file states them:

• P05, move 198 (contrasting), history lines 173 to 176, reverted by line 181 (move 203). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." The status would be bounded. The bound would read: "It does not hold where the keepers read a planned change from its shape and stop repairing it with no telling: completeanarchy, polska, satania, halo, bangtan, thesilphroad (R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018), a candidate branch, 'the shape read' (F-024). It does not hold where informed members hold the change against keepers who do not know: armok, maryland, oneshot (R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013), a limit below the trigger, at three nodes. Amended at D4a-01, after the D3 freeze (46384686...); not re-checked: no room was served these words." Rooms: completeanarchy, polska, satania, halo, bangtan, thesilphroad, armok, maryland, oneshot. Lines: R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018, R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013.
• A11, move 199 (dropping working hypotheses), history lines 177 to 180, reverted by line 182 (move 203). The arrow from P02 to P04 would be withdrawn (status withdrawn, in_model false). Its reason, as written: "Rule 16 and rule 14: preserve what remains supported, and replace or withdraw what does not. No defensible formulation of A11 as an arrow survives the return. (1) The order between rooms never beat its null (111 of 185 rooms, 0.600; null p95 0.670; base_rate_beaten false), and C2 withdrew it, keeping a transition inside threads. (2) Inside threads, the return's census (D3a-38, re-run as _analysis/d4a01_a11_classes.json) shows the transition in 111 rooms and template first in 98 of the 228 rooms whose lines show both ends; across threads 19 more. The reverse order is nearly as common, so the arrow carries no direction. (3) The failure clause is present and stands alone in 117 rooms: talk only in 31 (berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia) and layout only in 86. (4) The mechanism's word 'settled' is contradicted by 261 accepted restrict lines whose 'how' says a template does not settle the design for good (rival templates, polls, later redesigns, placers who deviate). A reworded arrow (a layout answers design talk in its thread) would be a new claim, never served to any room, with its reverse nearly as common: a co-occurrence, not an arrow. What remains supported, that design talk and layouts meet in threads, is held by P02's and P04's statements and ranges ('a design argued over days and redone'; 'an official template the room asks everyone to follow against other versions'), which stand. The arrow's record keeps its evidence and reasoning." Rooms (the talk-only rooms of the failure clause): berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia. Lines (the first-return lines of the census classes talk only, layout only and template first, 216): 2007scape-012, 4chan-011, AMD-012, AmericanFlaginPlace-009, AvoArmy-011, AyyMD-041, CKCrusaders-041, CSUFoCo-015, DestinyTheGame-014, DevonUK-010, FinalFantasy-014, GuardiansOfDatBoi-009, HomestarRunner-015, MonkeyIsland-011, NewMexico-015, ScottPilgrim-015, Temple-041, TsundereSharks-048, adventuretime-041, aggies-050, albania-046, alberta-016, anaheimducks-015, animalcrossing-053, anime-012, argentina-051, armenia-030, bardmains-055, berkeley-038, berserk-012, bih-036, bisexual-012, bitcoin-012, blackmirror-046, borderlands-020, bostonbruins-052, brasil-011, canada-012, catalonia-009, catholicism-011, cfb-048, chibears-010, chicubs-010, cirkeltrek-013, clashroyale-045, completeanarchy-011, criticalrole-043, crusaderkings-039, cubers-014, cuboulder-008, czech-014, dankmemes-045, darksouls-042, detroitlions-049, edboxes-046, edmontonoilers-041, empiredidnothingwrong-013, england-045, ethereum-056, europe-050, eve-049, fivenightsatfreddys-012, flashtv-055, floridagators-035, flyers-035, formula1-048, forsen-010, ftlgame-044, fxKorea-010, gameattack-015, gamindustri-053, gatech-041, ghibli-010, globaloffensive-012, greenbaypackers-011, guatemala-010, habs-011, heyyea-010, hongkong-047, hsv-012, hyperlightdrifter-046, indieheads-056, indonesia-035, ireland-045, italy-035, katawashoujo-041, lakers-009, latvia-029, leagueoflegends-042, lifeisstrange-013, linux-015, littlewitchacademia-012, loliconsunite-010, lost-044, lovelive-041, lsu-049, luxembourg-012, madokamagica-041, magictcg-010, mechanicalkeyboards-042, metalgearsolid-013, mexico-041, miamidolphins-041, minecraft-017, mit-041, mizzou-018, mls-053, monalisaclan-013, morrowind-011, msu-011, muse-048, mylittlepony-011, nVade-013, naruto-010, nbaspurs-056, necrodancer-011, neopets-047, newzealand-046, nightinthewoods-012, nin-012, ockytop-042, opticgaming-012, overwatch-017, parahumans-013, parrots-013, pathofexile-012, pcmasterrace-013, pebble-007, penguins-055, philippines-052, pitt-041, placeDE-041, placecanada-013, placesnek-031, planetside-056, polska-054, portal-012, portugal-082, predators-010, purdue-051, puzzleanddragons-013, quebec-013, radiohead-010, rainbowgrid-006, rangers-045, re_zero-042, redpandas-018, rickandmorty-042, rit-011, rocketbeans-008, rocketleague-011, romania-015, roosterteeth-013, rpi-049, russia-052, rust-010, rutgers-012, samuraijack-047, scp-014, seahawks-014, serbia-051, singapore-016, slovenia-041, smite-010, southpark-012, spacexmasterrace-052, spain-035, ss13-016, ssbpm-012, stardewvalley-058, starryknights-041, stevenuniverse-012, straya-047, suomi-041, survivor-035, sweden-045, tampabaylightning-045, terraria-048, teslamotors-012, tf2-041, thebluecorner-016, theexpanse-012, theitalyplace-054, thepointing-043, thesimpsons-011, tinytardis-009, titanfall-013, torontoraptors-016, totallynotrobots-013, transformers-046, trees-013, turkey-055, twentyonepilots-012, ubc-046, ucf-050, uiuc-011, ultrahardcore-005, undertale-011, unitedkingdom-035, unturned-013, uofm-008, uofmn-035, uruguay-012, utahjazz-009, utaustin-013, uva-042, uwaterloo-011, vegan-043, virginiatech-043, weezer-053, wine-011, witcher-017, worldoftanks-015, xenoblade_chronicles-012, zelda-061, zootopia-012.

2 of form C's rooms are among the rooms of the P05 proposal (r/maryland, r/satania). 6 are among the talk-only rooms of the A11 proposal's failure clause: r/bitcoin, r/eve, r/guatemala, r/placeDE, r/suomi, r/torontoraptors.

Both held proposals bear on this form. The A11 proposal would withdraw the arrow these rooms restrict most (section 7). The P05 proposal would bound the telling clause these rooms restrict in 46 members.

7. The restrict lines: the arrow fails here, or the record cannot show it

The rule, logged at D5a-36 before reading, unchanged. I read every restrict line on an arrow held by a defining member, 301 lines, and sorted each how sentence (_analysis/d5f_restricts.py; my sort in d5a38_sort_1.json to d5a38_sort_4.json, joined in d5a38_restrict_sorted.json). The arrow fails here: the line says the consequent came without the antecedent, from another source or in another order, or that the antecedent did not lead to it. The record cannot show it: the line says the order, the link or the step is not visible, not dated or not established in the record. Both, where it says both. Neither, where it states a condition or a scope, or says that the two acts coincide or overlap. This is one reader's sort, mine; no second coder read it (J: no readers for the rest of the run).

The form's own arrow: A11, the template that settles the design. In 40 of its 58 restrict lines here the arrow fails: the template did not settle the design. Members went on disputing details, revised the template, or settled the design another way. r/eve: "Templates do not settle collective agreement while helpers lack the model, letters require revision and members oppose the corner design." r/PUBATTLEGROUNDS: "Design disagreement is settled by choosing an already circulated image under space constraints rather than necessarily posting a new pixel template." In 16 more the line states a condition: the template settles the design only for placers who recognize its current version. r/trees: "Posting a template settles design only for informed participants, since helpers unaware of the revision keep restoring the previous version." That is P05's telling clause again, met at the template. A11's mechanism uses the word "settled", and the held A11 proposal would withdraw the arrow on these grounds. The share of defining members that restrict A11 is higher here, 60 per cent, than in the forms read before (form A 45, form B 50).

The arrows every form restricts. A10 (judging too few hands, then the move) fails here in 28 of 36 lines; A13 (keeping under strain, then help) in 20 of 30, where help came from spare capacity or reciprocity; A04 (keeping, then border talk) in 18 of 21, where talk came during building.

Where the record cannot show it. The record cannot show that celebration caused the record of the work (A08, 10 of 19 lines), that help was delivered (A14, 7 of 9), or that a call turned members against a rival (A15, 6 of 9).

So the two readings divide by kind, as in forms A and B. Where the line concerns the order of two acts the rooms report (a design and its template, keeping and talk, a shortage and a move), it mostly says the arrow fails as stated. Where it concerns cause (celebration and record, help delivered), it mostly says the record cannot show it. Across all 301 lines: the arrow fails here in 172, the record cannot show it in 68, both in 13, neither in 48.

8. The one relationship that runs differently here

A11 runs from P02 (the design) to P04 (the template). Its connection: "in a room carrying both, the first design talk comes before the first template (tested, not beaten: 0.556 against a null mean of 0.557)". Its mechanism: "Design talk in a thread is settled by someone posting a template that lays out the agreed design pixel by pixel."

In r/PUBATTLEGROUNDS a posted image settled a dispute. Two members disagreed over the logo's G. One pointed to a posted image and to the space the room had: "Yea, but even AWM said that this was the one we should go for. AWM was the one who posted that pic if you look down a bit, plus we are cramped for space in both vertical and horizontal directions." [PUBATTLEGROUNDS/c0103]. The other agreed: "Oh alright" [PUBATTLEGROUNDS/c0104]. The image was already in circulation; it settled the dispute when the room pointed back to it.

In r/cubers a posted design did not settle the work. A member posted a wider design, "Let's upgrade!" [cubers/c0169]. Builders began, "I'm starting on the yellow face at the bottom. Let's do that and work our way up." [cubers/c0171]. Keepers took the change for damage, and the builder gave up because the room was divided: "I think some people like the newer design, but others are happy with the way it is, so I guess it stays." [cubers/c0173].

In 58 of 96 defining members a current-ledger line restricts A11, against 47.7 per cent of the 558. What runs differently here is that the design does not end at the template. It is settled by a poll, an organiser's choice, the space or the existing pixels, and it reopens.

This is description, not a test. A11's expectation in form C is 0.355 (2 within-case datings over 705 rooms, times 125), so A11 is not-testable-here (section 10).

9. Fourth-order themes over- and under-represented

The rule was logged at D5a-01 before it ran (_analysis/d5_themes.py), and it is applied here to the defining members' codes (_analysis/d5f_facts.py). A member's coded concepts are counted by the fourth-order themes of their second-order theme's placements, and the form's pooled share on a theme is set against the pooled share over all 705 rooms. Over-represented: a ratio of 1.5 or more, with the theme present in 5 members or more. Under-represented: a ratio of 0.67 or less, with a population share of 1 per cent or more. These are shares of what the coders coded in these rooms, never a property of the rooms (contract section 5).

Over-represented (2).

• Collective representation: 17.2 per cent of the defining members' coded concepts against 10.2 per cent (ratio 1.69), in 94 members.
• Collective efficacy: 0.6 per cent of the defining members' coded concepts against 0.4 per cent (ratio 1.61), in 12 members.

In the rooms' words, from members holding the largest share on each theme (_analysis/d5f_theme_quotes.py): Collective representation, "removed 3 rows to not have to overwrite FREEUAB to the north. Now a 29 width x 26 height rectangle." [hongkong/c0030]. Collective efficacy, "Trolls threaten to destroy the still being made shield logo. Anyone want to help stop them?" [shield/c0070].

Under-represented (3): Neo-tribes (ratio 0.03), Visibility returns (ratio 0.42), Rivalry (ratio 0.64).

Collective representation is the form's change signature, so its excess in the codes partly restates the cut. The coders coded less rivalry and fewer tribes here than in the population. These rooms talked about their own picture more than about their rivals.

10. Arrows present, absent or not-testable-here

Section 1's arithmetic, declared at D5a-01: an arrow's expectation in a form is its within-case datings (its subs, counted over the 705 analysed rooms) over 705, times the form's n, here 125. Below one the arrow is not-testable-here, and no absence, boundary condition or failed proposition may be written from it. In form C the expectations run from 0.000 to 0.709:

• A01 (P01 to P03): 2 datings, expected 0.355; not-testable-here
• A02 (R01 to P01): 2 datings, expected 0.355; not-testable-here
• A03 (P03 to P05): 2 datings, expected 0.355; not-testable-here
• A04 (P05 to P08): 2 datings, expected 0.355; not-testable-here
• A05 (P08 to P07): 3 datings, expected 0.532; not-testable-here
• A06 (P05 to P14): 3 datings, expected 0.532; not-testable-here
• A07 (P03 to P11): 2 datings, expected 0.355; not-testable-here
• A08 (P11 to P12): 2 datings, expected 0.355; not-testable-here
• A09 (P12 to P13): 2 datings, expected 0.355; not-testable-here
• A10 (K02 to P10): 2 datings, expected 0.355; not-testable-here
• A11 (P02 to P04): 2 datings, expected 0.355; not-testable-here
• A12 (P01 to P15): 3 datings, expected 0.532; not-testable-here
• A13 (P05 to P16): 4 datings, expected 0.709; not-testable-here
• A14 (P08 to P16): 4 datings, expected 0.709; not-testable-here
• A15 (P01 to P09): 4 datings, expected 0.709; not-testable-here
• A16 (P09 to P07): 4 datings, expected 0.709; not-testable-here
• A17 (P09 to P08): 4 datings, expected 0.709; not-testable-here
• A18 (P09 to P18): 4 datings, expected 0.709; not-testable-here
• A19 (P05 to P17): 4 datings, expected 0.709; not-testable-here
• A20 (P01 to P20): 3 datings, expected 0.532; not-testable-here
• A21 (P08 to P21): 0 datings, expected 0.000; not-testable-here

Present: none. Absent: none. Not-testable-here: all 21. Members' current-ledger lines on an arrow (sections 7 and 8) are description only. Members among an arrow's within-case datings: r/aceattorney (A13); r/criticalrole (A19); r/dragonquest (A13); r/leafs (A16); r/metroid (A01); r/notredame (A14); r/rpi (A18); r/suomi (A07); r/ubc (A05, A06); r/weezer (A13). That is arithmetic about the model's own evidence, and it tests nothing in the form.

Propositions. N01, N02, N03, N04, N05, N06, N07, N08, N09; the highest expectation among the arrows they rest on is 0.709. Every proposition is not testable here; none holds and none fails against a real expectation. No findings.jsonl line is bounded from this form.

11. How representative members do the work

The rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_facts.py). Fit is a defining member's distance to the form's centre in the allocation's 892 columns. The best two are the nearest members whose selected changes and coded concepts are at or above the form's defining medians (10 changes, 119.5 concepts). The least well is the farthest defining member. The member read at length is, among the ten nearest, the one with the most selected changes not read at length earlier in stage D5.

Best fit: r/cubers (distance 0.741; 12 selected changes; 320 coded concepts; first-return verdict composes, re-check grade composes with residue; in F11 and F12). Its members built a puzzle cube. The design was proposed in the first post (section 1). A neighbour offered terms on the design itself: "How about you change your colors to be more like this http://imgur.com/GpMEXP6 and we move out of the way and even help you with the cube?" [cubers/c0032]. The starter agreed: "I'm good with this compromise. Better than trying to run you off into the Black Sea. :)" [cubers/c0034]. When the cube was up, a member wrote, "We did it guys! Now just keep it!" [cubers/c0072]. Later a wider design was proposed and repaired away (section 8). A member proposed telling the room's chat "to reduce infighting" [cubers/c0204]. Another design was turned down because the keepers could not hold it: "too hard to do without reference, makes protecting it hard" [cubers/c0187]. Its maker answered, "Oh, I havent thought about that, lol. Was just going for the looks :/" [cubers/c0188]. After the close a member recalled a design agreed with a neighbour and refused by a member of the room (section 4).

Second best fit: r/PUBATTLEGROUNDS (distance 0.742; 14 selected changes; 161 coded concepts; first-return verdict composes with residue, re-check grade composes with residue; in F01, F03 and F07). Its members built a game's logo letter by letter. When the first spot failed, they moved and reused what they had: "Yeah, we can re-purpose the B and G into P U and go from there." [PUBATTLEGROUNDS/c0087]. One letter took hours: "However is changing the G is making me lose my mind. Been trying to make the proper g for 2 hours. Lemme handle the g fam" [PUBATTLEGROUNDS/c0097]. The dispute over it was settled by pointing to a posted image (section 8). When a member proposed building on a neighbour's corner, another refused for the neighbour's work: "Leave top left alone, that Runescape connection lost is great" [PUBATTLEGROUNDS/c0121].

Least well: r/kuwait (distance 1.221; 10 selected changes; 26 coded concepts; first-return verdict composes; in F33; its point lies nearer form B's centre). Its record is about where to put the flag and whether helpers could find it. A member found a spot and was told, "We tried that, the rainbow people just quickly delete it." [kuwait/c0009]. Another gave coordinates: "Here: https://www.reddit.com/r/place#x=454&y=619 Help with the red line as it will make the bottom border and the red stripe of our flag." [kuwait/c0011]. A helper on a phone could not find it: "i can't really find it where the flag would be, i'm on mobile." [kuwait/c0020]. A neighbour asked for help and thanked the room: "Yes we did Al7mdlillah. 💪😎 thanks! GCC for life <3" [kuwait/c0026]. Its lines place a flag; they do not argue its design. It is in form C because Ward's method put it there.

Read at length: r/bardmains (distance 0.733; 16 selected changes; 85 coded concepts; first-return verdict composes with residue, re-check grade composes with residue; in F07, F23 and F34). The rule chose it: among the ten nearest it has the most selected changes and was not read at length earlier. Its members, players of one game character, built a small mask. The design was sized to the hands (section 1) and kept to the colour already on the canvas (section 1). Lettering went down rough, to hold the space: "Yeah I kinda fucked it up already, but I'm just getting it there before someone fills it with something else." [bardmains/c0043]. The design stayed open to the room: "We're heading in this direction unless people are opposed." [bardmains/c0084]; "We can let the masses decide." [bardmains/c0067]. Members could not always tell a change from damage: "Some people are trying to change the 3 brown parts to the yellowish thing, that's not us doing that, is it?" [bardmains/c0028]. A neighbour's beam crossed the mask, and a member settled the design with the neighbour: "I'm okay with you kinda going through us, I think this laser beam is a funny idea, but want to keep our bardmask somewhat intact. Thank you!" [bardmains/c0064]. The room marked the work, "GJ guys! Bard is just about done!" [bardmains/c0021], and at the close regretted the last pixel (section 1). A member started again on another canvas, "I started on the Bard mask and this time we can maybe aim for a full body? maybe chimes & meeps!" [bardmains/c0082], and was told, "Place is dead, let it go." [bardmains/c0083]. What is unrepresentative about it: its record is small, 85 coded concepts against the form's defining median of 119.5, so its design talk is short. It is a member of F07 and F34 both, the two design branches that lean to this form.

12. The branches its rooms come from

J asked that stage D6 build on the forms with the 35 branches as the level below. The branches do not nest in the forms: a branch was cut on one shared key, a form gathers rooms by the whole mix of their changes and codes. The table gives, for every branch, how many of its rooms are in form C, and the branch's share in C against C's share of the 705 rooms (125 of 705, 0.177). A ratio of 1 is what a branch would show if its rooms fell in the forms at random.

What the table shows. Four branches lean to form C at 1.5 times its share or more. Three are branches of the design:

• F07, the telling clause not shown at the design: informed members reject the planned change: 34 of 59.
• F33, the plan kept current while the design settles: 12 of 23.
• F34, the design sized to the hands: 11 of 22.
• F14, the mark adopted as the room's emblem while it is still placed: 3 of 7.

F07 is the largest share any branch has in any form read so far, 0.576: more than half its rooms are here. So the branch of informed members rejecting a planned change is, more than any other, a branch of this form. 6 of the 103 rooms of F01, the April Fools play, are in form C.

Rooms in no branch. 37 rooms (21 defining): r/aceattorney, r/aggies, r/araragi, r/austriahungary (thin), r/bdsm (thin), r/bigbang (thin), r/bitcoin, r/blackmirror (thin), r/bretagne, r/bulgaria, r/CKCrusaders, r/Clannad (thin), r/daftpunk, r/dofus (thin), r/drugs (thin), r/GabrielDropout (thin), r/greenland (core), r/GrowTheTree (thin), r/guatemala, r/Honduras, r/leafs, r/malta, r/NovaScotia (core), r/overwatch, r/ProfessorLayton, r/sakuragakuin, r/ScottPilgrim, r/suomi, r/SydneyFC (thin), r/teamcube, r/tetris (thin), r/TheAdventuresofTintin (thin), r/trees, r/truestl, r/vegan, r/vietnam (thin), r/watchmen (thin).

13. The nearest form and what separates them

The nearest form is B, the work behind the thread. The distances between form C's centre and the others are B 0.374, A 0.394, D 0.430, F 0.563, E 0.777. In the tree, C joins B at five forms, and the two join A at three. C and B are separated by what the rooms changed: C's members change the design, B's the chat, the scripts and attack calls.

The rooms between forms. D 11, A 8, B 5, F 2, E 2: these are the forms whose centres lie nearer than C's to its defining members, 28 rooms in all. The room that could have gone either way, the defining member with the smallest margin to another centre, is r/overwatch (23 selected changes, 1,198 coded concepts, in no branch). Its point lies nearer form E's centre, the April Fools play.

14. The split below the form

The split rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_split.py, on room-forms-tree-rooms.tsv). A split reads as a split when both parts hold 10 defining rooms or more and each part has a fourth-order change column (a node or a link) at 1.5 times the parent's defining share or more, held by a third of the part or more and by fewer in the other part. The walk descends only while splits read.

Form C's first split, at eleven forms, does not read as a split. C.2 (15 defining rooms, 37 in all) leans to collective representation, held by every one of its defining rooms against 97.5 per cent of C.1. That is a lean on a theme the whole form already holds. C.1 (81 defining rooms, 88 in all) has no column of its own. The share of defining rooms holding the signature theme in each part: C.1: Collective representation 0.975; C.2: Collective representation 1.000. C.2 holds more placed rooms than defining ones: 22 of its 37 are thin or core rooms. The walk stops at the form, and I write no subform candidate. Form C is one pattern with variation.

15. The thin and core rooms placed here

Thin rooms (27), placed by the whole mix of their changes and codes at the nearest form centre: r/aeskwadraat (3 changes, 18 concepts), r/aoe2 (2 changes, 245 concepts), r/austriahungary (1 change, 2 concepts), r/bdsm (2 changes, 15 concepts), r/bigbang (2 changes, 3 concepts), r/blackmirror (4 changes, 62 concepts), r/Clannad (2 changes, 18 concepts), r/colombia (4 changes, 81 concepts), r/colorado (3 changes, 35 concepts), r/crystalclear (2 changes, 8 concepts), r/davidbowie (4 changes, 43 concepts), r/dofus (1 change, 14 concepts), r/drugs (3 changes, 199 concepts), r/eder (2 changes, 17 concepts), r/egypt (4 changes, 27 concepts), r/GabrielDropout (4 changes, 74 concepts), r/GrowTheTree (4 changes, 60 concepts), r/montenegro (3 changes, 14 concepts), r/PORTUGALCARALHO (3 changes, 60 concepts), r/strangerthings (3 changes, 147 concepts), r/superman (2 changes, 32 concepts), r/SydneyFC (2 changes, 19 concepts), r/tetris (3 changes, 16 concepts), r/TheAdventuresofTintin (3 changes, 12 concepts), r/ubc (3 changes, 107 concepts), r/vietnam (2 changes, 11 concepts), r/watchmen (1 change, 2 concepts).

Their selected lines weigh less and enter no share above. The most frequent are P05 add-step 6 (r/Clannad, r/colorado, r/crystalclear, r/davidbowie, r/egypt, r/strangerthings); P02 add-condition 5 (r/aeskwadraat, r/aoe2, r/crystalclear, r/PORTUGALCARALHO, r/strangerthings); P02 link 4 (r/bdsm, r/drugs, r/GrowTheTree, r/vietnam); P25 add-step 3 (r/eder, r/GrowTheTree, r/SydneyFC); P16 add-condition 3 (r/colombia, r/egypt, r/ubc); P04 add-step 3 (r/colorado, r/davidbowie, r/superman); P02 add-step 3 (r/drugs, r/tetris, r/vietnam); P25 link 2 (r/SydneyFC, r/TheAdventuresofTintin). They lean the same way as the defining members, to the design (P02 add-condition, link and add-step).

Core rooms (2), with no selected change, placed by their codes alone at the nearest centre in the code columns: r/greenland (3 concepts; verdict composes), r/NovaScotia (4 concepts; verdict composes). Their placement rests on 3 and 4 coded concepts and is weak.

16. The form test

The constructs. P02 (the design), P04 (the template) and P05 (keeping), at the fourth-order theme T4-006 (Collective representation), with the arrow A11 and P05's telling clause.

The relations. The room settles its design for a time, by a poll, an organiser's choice, the space or the pixels already placed, and reopens it after each finish. A template does not end the design: it settles it only for the placers who recognize its current version. Keeping restores the known form, so a change is repaired away, by keepers who do not know of it and by keepers who know of it and do not want it.

Is it falsifiable? Yes. A room whose design was fixed by its first template and never reopened, or whose keepers undid changes only when uninformed, would fall outside the relations. Such rooms could be looked for in the population, among rooms with as much design talk; I have not looked for them here. A11's two within-case datings (r/udub, r/wallstreetbets) show only that design talk came before the template, not that the design stayed fixed.

The four organizing problems. The form binds information provision: the current design must reach the keepers. And it shows the limit of information: some keepers know the design and refuse it, so the form also touches the division of authority over the design (polls, an organiser's overnight choice), which the four problems treat as a matter of task division. It leaves the allocation of members to tasks and reward free. A remainder is supported: the design is never finished. The rooms treat a finished part as the start of the next, and none of the four problems names that.

What varies among members. How the design is settled for now (a poll, an organiser, the space, the pixels already there), and whether the room's keepers refused or only missed a change. The tree finds no split that reads. The variation is accommodated by the form.

Result: a form, in a narrow sense. The form binds constructs of canvas organizing and states their relations, and nearly every defining member's lines show its one lean. Its relations add to the model what it does not say: the design is reopened, and telling is not enough where keepers disagree. Two limits stay. The changes are frequent in the population, and more than a quarter of the defining rooms (28 of 96) lie nearer another centre. And the claim rests on my reading of the lines and the members' words, with every local account unresolved.

17. What would make you doubt this is a form at all

Three things.

First, the base rate. Collective representation is changed by 52.7 per cent of the 558 defining rooms. Form C may be the rooms where design talk was most of the record, not rooms that did the design differently. The ratio (2.63) says they changed it more; it does not say they changed it in another way.

Second, my sort of the restrict lines. One reader sorted 301 lines. And the line between the template did not settle the design and it settles only for those who recognize it is a judgement in many A11 lines.

Third, the survival figures, from the record, never from the canvas. The median organizing end is hour 71.66 for the 123 members with one, and the mean aftermath share is 0.0164. The coded work_remained field says kept in 71 members, lost in 36 and silent in 18. These figures are not compared here, and nothing in this account rests on them.

What would undo the form: rooms outside it with as much design talk whose designs were settled once and kept; or a reading of the members' threads in which the keepers who undid changes were, after all, uninformed.

Room form D, keeping, with traded help and carrying on: the form account

Written at D5a-39, 27 October 2026. The model is the version frozen at D3 (46384686d6173fdeb4c749667478c1363e675bc6b52bb6f4fdc211d387e68525). Form D is one of the six room forms of the cut J ruled at D4a-08 (room-forms-D4a08c.*); how every room reaches its form is in room-forms-allocation.md. It holds 119 of the 705 analysed rooms. 96 are defining rooms: rooms with 5 or more selected changes, which shaped the form. 20 are thin rooms (1 to 4 selected changes) and 3 are core rooms (no selected change), placed afterwards. Thin and core rooms weigh less: every share, signature, theme count, representative choice and split below is read on the 96 defining rooms, and the thin and core rooms are named in section 15.

A room form is not a branch: it gathers rooms by the whole mix of their changes (two thirds) and their codes (one third), and the 35 branches are the level below it (section 12). The form is a pole of a continuum: 32 of its 96 defining rooms lie nearer another form's centre (section 13). Form D is the first form read so far whose split below the form reads as a split (section 14). This file sits beside the room-forms files, not in forms/, because the stage's close-check reads every account in forms/ as a branch account (departures.jsonl line 18). Hours are counted from the start of the event (h+).

1. How these rooms organized, as a narrative

In these 119 subreddits members kept their work, and the keeping reached past the room. They watched the mark in shifts, checked what it should look like before they repaired it, helped neighbours when their own work was safe, and carried the work on, before the canvas closed and after it. In two thirds of the defining rooms the subreddit also played April Fools with its own members.

The keeping was shared out by the hour. A r/metalcore member wrote, "I'll work the night shift" [metalcore/c0124]. Another wrote, "Night shift for some, im about to start work, I'll be able to help keep an eye throughout the day too" [metalcore/c0125]. A r/glasgow member handed the watch on: "I'm away now, so my watch has ended. Keep up the good work!" [glasgow/c0014]. When the r/warriors logo was finished, a member wrote, "lets see if we can keep defending it alright I gotta get some sleep. Gonna need some people to defend it." [warriors/c0034].

Keepers checked before they repaired. A r/chicubs member wrote, "I just try to refresh right before placing something, if I've had it sitting for a while" [chicubs/c0114]. In r/radiohead a member asked, "I'm guessing we're not trying to turn the Radiohead symbol red right?" [radiohead/c0198], and was told, "No the red is legit" [radiohead/c0199]. A r/OnePiece member who was helping neighbours asked, "Could you give us a picture of what its supposed to look like so we know what to do?" [OnePiece/c0220]. The same member later posted "a comprehensive guide on what everyones art looks like" [OnePiece/c0253].

Help went out when the room's own work was safe. A r/furry_irl member wrote, "I'd say we should all go help them maintain that one as our two aren't in too much danger right now." [furry_irl/c0086]. A r/mylittlepony member set the terms: "As long as Dash is fairly clean, I'll help you out." [mylittlepony/c0082]. In r/OnePiece a neighbour asked for help with its lattice "as a second priority to keeping your own art clean, of course" [OnePiece/c0087]. In another thread a member wrote, "(Obviously our flag takes priority). Lets give them a hand." [OnePiece/c0123]. Help was also refused. In r/mylittlepony, when a request brought a quarrel inside the requesting community, members wrote, "I feel like we're being roped into the unpopular side of a civil war." [mylittlepony/c0186] and "You guys need to resolve this before asking us for help." [mylittlepony/c0187].

The work was carried on, and carrying on often began before the close. A r/lovelive member posted "r/place Honk in profile pic form." [lovelive/c0034] at h+53.6, while placing went on. After the close, a r/catholicism member wrote, "We can still make the Vatican Flag!" [catholicism/c0124], and another answered, "I've started helping, hope we can do it this time!" [catholicism/c0132]. A r/gamindustri member started again on another canvas: "I've started work on Lastation, up and to the right of Planeptune." [gamindustri/c0171]. The r/denmark moderators kept the room's Discord for ordinary use: "Fremover vil vi gerne opfordre folk til at forsætte med at bruge discord, så der kan komme regelmæssig aktivitet." [denmark/c0372] (they asked members to keep using it, so that it would have regular activity). In r/rotmg a stray pixel became a wish for next year: "Green dot oryx for april fools 2018 hype" [rotmg/c0276].

In some rooms the subreddit's own April Fools play ran beside the work. Members checked claims before they believed them. A r/romania member wrote, "E 1 aprilie. Verificati din doua surse stirile azi" [romania/c0036] (it is the first of April; check the news in two sources today). A r/magictcg member judged a card preview: "no foil stamp, fake" [magictcg/c0091]. In r/gameofthrones a pretend sellout ran a real giveaway: "To enter, just leave a comment below with a sentence about which character you would like to see as a funko and why." [gameofthrones/c0041]. The winner was told, "Congrats - you are the winner or the random roll :)" [gameofthrones/c0042].

2. What the form does

These elements are instantiated in 80 per cent of the defining members or more (_analysis/d5f_model.py, current ledger, particular lines included). The model's prose says them so.

• P01 (96 of 96; 100 per cent of the 558): "The room calls its own members, and kindred subs, to come and place for a work: to start it, build it, finish it or hold it."
• P05 (95 of 96; 93 per cent of the 558): "The room keeps its placed work against erosion: members watch it and repair changed pixels, and the room rallies to defend it under attack, covers the night, hardens its shape and puts upkeep before growth. Repair restores the form the keepers know. A change the room has planned or agreed (P02) is therefore repaired away as damage until its keepers are told of it, and it is lost or given up where the telling does not reach them."
• P02 (94 of 96; 100 per cent of the 558): "The room settles what its mark will show of it: a member proposes a picture, the room argues its design, makes its land's flag or emblems the mark, signs it or leaves it unsigned, claims a mark others made, adds to it or enlarges it, or adds a personal piece to a shared mark."
• P12 (94 of 96; 97 per cent of the 558): "The room records what happened to its work and to the canvas around it: screenshots and timelapses, reports of its fate, mourning, imagined art, atlas entries, the end marked."
• P11 (93 of 96; 96 per cent of the 558): "When a work is up, the room marks it: announces it, celebrates it, credits makers and helpers, reports members' own parts and says what working with strangers meant."
• P03 (92 of 96; 97 per cent of the 558): "The room builds its mark, and members report its state to the thread: what is placed, done or missing, and where."
• P04 (92 of 96; 97 per cent of the 558): "Members circulate a template that lays out the mark pixel by pixel, or coordinates that locate it, ask for them, and ask strays to keep to them."
• R01 (92 of 96; 96 per cent of the 558): "The starter: a member who proposes the mark, maps it or begins placing it. Others joining is not part of the role: it is the answer to the room's call (P15), in the order A02 and A01 state."
• P24 (90 of 96; 89 per cent of the 558): "Members ask what the canvas is, how to place, what a call or a name means and what a picture shows, and others explain the rule, the timer, the controls, whose mark a picture is and what happened. They ask before, during and after the close, and some questions get no answer."
• P15 (89 of 96; 91 per cent of the 558): "A member answers a call or proposal in one line that joins, assents, reports a part done or thanks, and the line asks for nothing back."
• P16 (89 of 96; 91 per cent of the 558): "Rooms help one another's works and trade help: they give pixels to a neighbour's mark, ask other rooms for help, barter help for space or repair, thank their allies, greet them, and turn requests away."
• P07 (84 of 96; 89 per cent of the 558): "Rooms spare their neighbours' work, rein in their own attackers, apologise for damage and appeal to attackers to stop."
• P06 (82 of 96; 87 per cent of the 558): "Members work out who changed their work and why: they trace placers and rooms, find friendly fire or their own mistake, blame officers, or disown placers acting in their name."
• K05 (81 of 96; 79 per cent of the 558): "Members place on their own time and with their own devices. They fit placing around sleep, study, exams, work and travel. They cannot place from a phone or while away, they leave when the wait is too long, they save pixels under the timer, they find the work addictive, and they report what it cost them."
• P08 (79 of 96; 86 per cent of the 558): "Rooms propose, settle and contest borders, truces and deals with neighbours by talk, through envoys, and hold each other to them."
• P26 (77 of 96; 78 per cent of the 558): "Members make new jokes out of the canvas work, its mistakes, its damage and its neighbours: puns on the mark, mock names and titles for a figure, and jokes about attackers and bots. The room takes the jokes up, and some members want a joke kept in the work."

The model has the room call its members (P01), build (P03), keep the work (P05), help other rooms' works (P16), mark the work when it is up (P11) and record it (P12). These rooms do all of it. P05 is instantiated in 95 of 96 defining members, against 93.4 per cent of the 558, and P16 in 89, against 91.4 per cent. The difference is not in which elements they hold. It is in what they change.

3. What it does differently, element by element and arrow by arrow

The change signature. The form's defining members change three fourth-order themes more than the defining population does (at 1.5 times its share or more, in a third of the members or more). Repair work, the theme of keeping, is changed by 74.0 per cent of them, against 48.9 per cent of the 558 (share ratio 1.82). Transition, the theme of carrying on, by 40.6 per cent, against 20.6 (ratio 2.22). Reciprocity, the theme of traded help, by 38.5 per cent, against 20.3 (ratio 2.49). Repair work is held by three quarters of the members; the other two by under half.

Element by element and arrow by arrow. The table gives every element or arrow and op that 14 defining members or more change, at 1.2 times the defining population's share or more (_analysis/d5f_facts.py). A selected line specifies the model (add-condition, add-step), restricts it (restrict), connects two of its parts (link) or contradicts it. The kind of a line is not relied on (J: kappa 0.08).

No defining member holds a contradict line, so these rooms replace nothing in the model. I read the lines behind the table whole (_analysis/d5f_dump.py: 184 lines on carrying on, keeping, help, the April Fools frame, the host's line, the marking, the call and machine hands).

• P13, carrying on: specified (add-step 24 members, 25 per cent against 11). The added steps say when and how the room carries the work on. It begins before the close. r/italy: "Alternative-canvas discussion begins while original placement remains live, extending continuation beyond the model's near-closure timing." On a later canvas it restarts the work. r/bindingofisaac: "Continuation on another canvas restarts recruitment, representation and defense beyond the decision to preserve the earlier effort." It keeps the event's venues and gives them roles. r/denmark: "Retaining event infrastructure entails assigning administrator and channel-moderator roles and promoting the venue for ordinary community contact." And it is argued. r/sabres: "Praise for successor work coexists with disagreement about starting another version so soon."
• P05, keeping: specified (add-step 21 members, 22 per cent against 14). The added steps are how the room shares and checks its keeping. Watches are volunteered and handed on. r/metalcore: "Volunteered night and daytime watches create explicit complementary coverage without an observed imposed rota." r/warriors: "Defenders schedule small placements during game timeouts and explicitly hand protection over before sleeping." Keepers check the current canvas and the intended form before they repair. r/radiohead: "Maintenance includes checking whether unfamiliar pixels are intended changes before undoing them." r/OnePiece: "Helpers check the intended form of allied images before repairing them to avoid making them worse."
• P16, help between rooms: conditioned (add-condition 19 members, 20 per cent against 14). The conditions say when a room helps. Its own work must be safe and it must have pixels to spare. r/OnePiece: "Offered aid depends on keeping one's own work secure and having placements to spare." Kin and earlier debts come first. r/babymetal: "Prioritizing the sister community over a neighbor explains withdrawal of help that upkeep-over-expansion alone does not capture." A request that brings a quarrel is refused. r/mylittlepony: "Aid can be refused when a request imports an unresolved controversy within the requesting community." And help to one room can harm a third. r/gamindustri: "Proposed reciprocal help may remove a third party's mark, so assistance within one relationship can threaten another work."
• A13, from keeping under strain to help: restricted (33 members, 34 per cent against 26). Section 8 reads these lines.
• A09, from the record to carrying on: restricted (16 members, 17 per cent against 9). In 11 of the 16 lines the arrow fails here: carrying on came before the record or from another source (section 7).
• K01, the April Fools frame: specified (add-step 24 members, 25 per cent against 19). Members test claims instead of playing along, run real contests inside the joke, and end the play. r/magictcg: "Participants authenticate purported previews through stamps, typography, artist attribution and collector numbers rather than simply playing along." r/gameofthrones: "The pretend sellout contains a real allocation procedure with character pitches, a random winner, an additional popularity prize, and a closing notice." r/NieR: "Ending the theme swap includes a later reminder to remove its leftover page title and a moderator acknowledgment." 21 of the 24 rooms with these lines sit in D.2 (section 14).
• P20, the host's line: specified (add-step 15 members, 16 per cent against 9). Moderators remove, flair and reverse, and members contest removals. r/canada: "Participants explicitly cite removals as their reason for seeking another coordination venue." r/mylittlepony: "A removal decision could be reversed after checking discussion within moderator chat."
• P11, marking the work: specified (add-step 15 members, 16 per cent against 11). The celebration is judged and contested. r/kirby: "Celebration includes judging recognizability and longevity sufficient for victory despite remaining defects." r/gameofthrones: "Replies question whether an hour of guarding merits admiration, adding evaluation of labour to the completion exchange."
• P01, the call: connected (link 16 members, 17 per cent against 10). The call returns. In 5 members it returns from a later canvas. r/rotmg: "Successor activity restarts calls for hands and completion rather than remaining solely a record of the original effort." In 5 it returns from damage or a loss. r/rojava: "Faster encroachment explicitly prompts a renewed appeal for hands, returning upkeep to recruitment."
• P14, A01 and A06: restricted (15, 19 and 21 members). Machine hands are argued more than shown placing, the call does not always come before building, and scripts do not always follow upkeep (section 7).

What the model would not predict. The model has a room short of hands turn to other rooms, and other rooms send help (A13). In these rooms help is mostly described from the giver's side: a room helps when its own work is safe, to repay earlier help or to earn goodwill, and refuses when a request brings a quarrel. Where a room under strain asks, 14 of the 33 lines on A13 say the record cannot show that help arrived, or that the shortage caused it. The model has the room carry its work on near the close and after it (P13), after a record of the work (A09). In these rooms carrying on often began while placing went on, and on a later canvas it returned to the call, the build and the keeping. The model has no arrow from carrying on back to the call.

The rooms that show the form best, by the rule in section 11, are r/gorillaz and r/gamindustri; the one that shows it least well is r/polyamory.

What the claim rests on. The form is a cut of the allocation (changes two thirds, codes one third, Ward's method, six forms by J's ruling). Its stability on matched subsamples is about 0.21, and 32 of its 96 defining rooms lie nearer another form's centre. The table's counts are the ledger's. That members shared their watches, helped when their own work was safe and carried the work on before the close is a claim on their words, through cite.py, in sections 1, 4 and 11. One kind of evidence does not stand in for the other.

The name, read against the members. The name is "keeping, with traded help and carrying on". The strongest argument that it names the cut rather than what the rooms did: it lists the form's three signature themes, and two of them are held by under half the members. A reader who suspected the name would look for members that hold all three. There are 10 of 96, against 11.1 if the three were independent; traded help and carrying on meet in 15 members, against 15.0 (section 14). Keeping is borne out: 71 of the 96 change it. Traded help and carrying on are each borne out in about two fifths of the members, but not together. The name says and where the members show or. I propose in notes-D5.md that stage D6 read the name as keeping, with traded help or carrying on. The tree's first split divides the form by something the name does not say: the call against the host's April Fools play (section 14).

4. The concepts it employs

First-order concepts for each change the form leans to, through cite.py:

• The watch shared and handed on. "I'll work the night shift" [metalcore/c0124]. "I'm away now, so my watch has ended. Keep up the good work!" [glasgow/c0014].
• The canvas and the intended form checked before repair. "I just try to refresh right before placing something, if I've had it sitting for a while" [chicubs/c0114]. "Could you give us a picture of what its supposed to look like so we know what to do?" [OnePiece/c0220].
• Help when the room's own work is safe. "As long as Dash is fairly clean, I'll help you out." [mylittlepony/c0082].
• Help to earn goodwill. "If they don't, then at least cleaning that area up will maybe earn us some good will with them, allowing us to place something there in the future." [gamindustri/c0088].
• Help refused. "You guys need to resolve this before asking us for help." [mylittlepony/c0187].
• Help asked under strain. "Har vi ikke nogen allierede et sted vi kan bringe ind i kampen?" [denmark/c0066] (do we not have allies somewhere that we can bring into the fight?).
• Carrying on, on another canvas. "I wasn't ready for another battle. That said, lets make Lowee and Leanbox this time!" [gamindustri/c0173].
• Carrying on, as a joke for next year. "Green dot oryx for april fools 2018 hype" [rotmg/c0276].
• The April Fools claim checked. "no foil stamp, fake" [magictcg/c0091].
• The host's line. A moderator explained a removal: "We will sometimes remove multiple posts along the same theme" [canada/c0398]. Earlier a member had complained, "All the other country's subs are embracing it. We're being left in the dust!" [canada/c0170].
• The marking judged. "I spent over an hour of my life guarding the House Stark sigil while we built the Lannister Sigil and I have no regrets because they're amazing" [gameofthrones/c0140]. A reply: "I'm proud of you OP." [gameofthrones/c0142]. A later reply: "Only an hour?" [gameofthrones/c0147].
• Machine hands argued. "But as of this morning, apparently people are just running scripts now, which ruined the fun of the human interaction." [patriots/c0282].

5. Composition here

Three judgments are kept apart.

The original global model (historical). verdicts-D.jsonl, by the last analyst ruling or else the readers' agreement. All 119 members: composes 57, composes with residue 61, does not compose 0, cannot tell 1. The 96 defining members: composes 45, composes with residue 51, does not compose 0, cannot tell 0. The one that cannot tell is a thin room, r/azerbaijan (3 selected changes, 8 coded concepts). These verdicts describe the unadapted model at the first return.

The adapted local accounts. By adaptation-returns.jsonl and the current model hash (46384686), as vlib.local_return_states reads them, all 119 members are unresolved; none is validated and none has insufficient evidence. The limit D3 named is the same for each: the labelers marked every local account unresolved, and prior.md section 3's measure of local validation was not computed (J after the D3c interview). The unresolved members are:

r/anarcho_capitalism, r/anarchocapitalism, r/androidgaming, r/asktransgender, r/azerbaijan, r/babymetal, r/bangtan, r/bannedfromanime_irl, r/bih, r/bindingofisaac, r/bobross, r/borderlands, r/bostonceltics, r/buffalo, r/buffalowizards, r/calgaryflames, r/canada, r/catholicism, r/cgpgrey, r/chelseafc, r/chicubs, r/churchofhelix, r/columbia, r/completeanarchy, r/costa_rica, r/CryptoFR, r/danganronpa, r/denmark, r/denverbroncos, r/DiamondClub, r/dmt, r/donaldglover, r/eagles, r/edmontonoilers, r/ElderScrolls, r/ElSalvador, r/enterthegungeon, r/europe, r/Fez, r/FinalFantasy, r/flyers, r/frankocean, r/frc, r/furry_irl, r/futurama, r/gameattack, r/gameofthrones, r/gamindustri, r/genderfluid, r/giivasunner, r/glasgow, r/gorillaz, r/greece, r/greyblob, r/hawks, r/heroesofthestorm, r/homestuck, r/iastate, r/ibo, r/ice_poseidon, r/italy, r/kirby, r/kpop, r/lost, r/lovelive, r/magictcg, r/Mario, r/math, r/mcgillrobotics, r/metalcore, r/mizzou, r/mylittlepony, r/naruto, r/natsume, r/NieR, r/nightinthewoods, r/nlsscirclejerk, r/nuclearthrone, r/nyjets, r/oltp, r/oman, r/OnePiece, r/OneTrueEmilia, r/parrots, r/partyparrot, r/patriots, r/pepe, r/physical_removal, r/polyamory, r/porterrobinson, r/portugal, r/purdue, r/radiohead, r/rojava, r/romania, r/rotmg, r/rutgers, r/sabres, r/sadboys, r/shishamo, r/shrooms, r/southpark, r/SquareSpiral, r/Temple, r/terraria, r/texans, r/the_pack, r/THE_R, r/thesimpsons, r/thetreesnetwork, r/tokyo, r/traaaaaaannnnnnnnnns, r/uruguay, r/vim, r/warriors, r/wholesomememes, r/yogscast, r/yumenikki, r/yuyuyu

The shared form explanation: supported for keeping, unresolved for the rest. One change binds three quarters of the defining members: 74.0 per cent change repair work, and their lines say how the keeping was shared and checked. The other two signatures, traded help and carrying on, are each held by about two fifths and are not held together. The changes say what the model does not: help flows from a room whose own work is safe, and carrying on begins before the close and returns to the call. But the same changes are frequent in the population (repair work 48.9 per cent), 32 of the 96 defining members lie nearer another form's centre, and every member's own adapted account is unresolved. A verdict of composes with residue on the original model is not a current local or shared failure.

6. How the model runs here

Counts are of defining members with a current-ledger line, particular lines included (_analysis/d5f_model.py); they count any line of an op.

The elements that do the work. The elements of section 2. Of the elements instantiated in half the defining members or more, three are instantiated here ten points or more above the population. P13, carrying on, in 59 of 96 (61 per cent), against 47. K06, the site's faults reported and worked around, in 64 (67 per cent), against 50. K01, the April Fools frame, in 64 (67 per cent), against 57.

The elements that sit idle. P34 is absent in 96 of 96 defining members, A21 in 85, P33 in 83, P28 and P30 in 81, P29 in 71, K07 in 67, and C01 and P32 in 66. They are idle in the population too, and their idleness does not mark the form.

The elements that fit less here. P27, choosing the spot before any loss, is instantiated in 56 of 96 (58 per cent), against 72 per cent of the 558. A05, sparing others' work by the room's own norm, in 19 (20 per cent), against 27. Fewer of these rooms record choosing a spot before any loss, or sparing others' work by their own norm.

What these rooms do that the model has no place for. 43 of 96 defining members carry 66 propose lines, against 210 of the 558 defining rooms; that is slightly more (45 per cent against 38). The propose lines are not part of the form's lean. The return from carrying on to the call (section 3) has no arrow in the model.

Where the room models and my reading disagree. They agree. r/gamindustri's model says that its A13 line "supports reported aid and repayment, but leaves the proposed manpower-shortage-to-request-to-dispatch mechanism unresolved", and asks to "Preserve the demonstrated return from carrying the mark onward to building and exposure to loss, which the model's arrow set does not state". r/bindingofisaac's model says, "Place2 continuation reopens active work after the original closes: recruitment is followed by a defense call and a proposal to sign the new figure". My reading of the members' lines is the same.

The held proposals (QD4-001; never served to any room, not re-checked). The model above is the frozen version. J ruled that both held proposals are stated in full wherever the model is reported. They are, as the tree file states them:

• P05, move 198 (contrasting), history lines 173 to 176, reverted by line 181 (move 203). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." The status would be bounded. The bound would read: "It does not hold where the keepers read a planned change from its shape and stop repairing it with no telling: completeanarchy, polska, satania, halo, bangtan, thesilphroad (R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018), a candidate branch, 'the shape read' (F-024). It does not hold where informed members hold the change against keepers who do not know: armok, maryland, oneshot (R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013), a limit below the trigger, at three nodes. Amended at D4a-01, after the D3 freeze (46384686...); not re-checked: no room was served these words." Rooms: completeanarchy, polska, satania, halo, bangtan, thesilphroad, armok, maryland, oneshot. Lines: R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018, R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013.
• A11, move 199 (dropping working hypotheses), history lines 177 to 180, reverted by line 182 (move 203). The arrow from P02 to P04 would be withdrawn (status withdrawn, in_model false). Its reason, as written: "Rule 16 and rule 14: preserve what remains supported, and replace or withdraw what does not. No defensible formulation of A11 as an arrow survives the return. (1) The order between rooms never beat its null (111 of 185 rooms, 0.600; null p95 0.670; base_rate_beaten false), and C2 withdrew it, keeping a transition inside threads. (2) Inside threads, the return's census (D3a-38, re-run as _analysis/d4a01_a11_classes.json) shows the transition in 111 rooms and template first in 98 of the 228 rooms whose lines show both ends; across threads 19 more. The reverse order is nearly as common, so the arrow carries no direction. (3) The failure clause is present and stands alone in 117 rooms: talk only in 31 (berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia) and layout only in 86. (4) The mechanism's word 'settled' is contradicted by 261 accepted restrict lines whose 'how' says a template does not settle the design for good (rival templates, polls, later redesigns, placers who deviate). A reworded arrow (a layout answers design talk in its thread) would be a new claim, never served to any room, with its reverse nearly as common: a co-occurrence, not an arrow. What remains supported, that design talk and layouts meet in threads, is held by P02's and P04's statements and ranges ('a design argued over days and redone'; 'an official template the room asks everyone to follow against other versions'), which stand. The arrow's record keeps its evidence and reasoning." Rooms (the talk-only rooms of the failure clause): berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia. Lines (the first-return lines of the census classes talk only, layout only and template first, 216): 2007scape-012, 4chan-011, AMD-012, AmericanFlaginPlace-009, AvoArmy-011, AyyMD-041, CKCrusaders-041, CSUFoCo-015, DestinyTheGame-014, DevonUK-010, FinalFantasy-014, GuardiansOfDatBoi-009, HomestarRunner-015, MonkeyIsland-011, NewMexico-015, ScottPilgrim-015, Temple-041, TsundereSharks-048, adventuretime-041, aggies-050, albania-046, alberta-016, anaheimducks-015, animalcrossing-053, anime-012, argentina-051, armenia-030, bardmains-055, berkeley-038, berserk-012, bih-036, bisexual-012, bitcoin-012, blackmirror-046, borderlands-020, bostonbruins-052, brasil-011, canada-012, catalonia-009, catholicism-011, cfb-048, chibears-010, chicubs-010, cirkeltrek-013, clashroyale-045, completeanarchy-011, criticalrole-043, crusaderkings-039, cubers-014, cuboulder-008, czech-014, dankmemes-045, darksouls-042, detroitlions-049, edboxes-046, edmontonoilers-041, empiredidnothingwrong-013, england-045, ethereum-056, europe-050, eve-049, fivenightsatfreddys-012, flashtv-055, floridagators-035, flyers-035, formula1-048, forsen-010, ftlgame-044, fxKorea-010, gameattack-015, gamindustri-053, gatech-041, ghibli-010, globaloffensive-012, greenbaypackers-011, guatemala-010, habs-011, heyyea-010, hongkong-047, hsv-012, hyperlightdrifter-046, indieheads-056, indonesia-035, ireland-045, italy-035, katawashoujo-041, lakers-009, latvia-029, leagueoflegends-042, lifeisstrange-013, linux-015, littlewitchacademia-012, loliconsunite-010, lost-044, lovelive-041, lsu-049, luxembourg-012, madokamagica-041, magictcg-010, mechanicalkeyboards-042, metalgearsolid-013, mexico-041, miamidolphins-041, minecraft-017, mit-041, mizzou-018, mls-053, monalisaclan-013, morrowind-011, msu-011, muse-048, mylittlepony-011, nVade-013, naruto-010, nbaspurs-056, necrodancer-011, neopets-047, newzealand-046, nightinthewoods-012, nin-012, ockytop-042, opticgaming-012, overwatch-017, parahumans-013, parrots-013, pathofexile-012, pcmasterrace-013, pebble-007, penguins-055, philippines-052, pitt-041, placeDE-041, placecanada-013, placesnek-031, planetside-056, polska-054, portal-012, portugal-082, predators-010, purdue-051, puzzleanddragons-013, quebec-013, radiohead-010, rainbowgrid-006, rangers-045, re_zero-042, redpandas-018, rickandmorty-042, rit-011, rocketbeans-008, rocketleague-011, romania-015, roosterteeth-013, rpi-049, russia-052, rust-010, rutgers-012, samuraijack-047, scp-014, seahawks-014, serbia-051, singapore-016, slovenia-041, smite-010, southpark-012, spacexmasterrace-052, spain-035, ss13-016, ssbpm-012, stardewvalley-058, starryknights-041, stevenuniverse-012, straya-047, suomi-041, survivor-035, sweden-045, tampabaylightning-045, terraria-048, teslamotors-012, tf2-041, thebluecorner-016, theexpanse-012, theitalyplace-054, thepointing-043, thesimpsons-011, tinytardis-009, titanfall-013, torontoraptors-016, totallynotrobots-013, transformers-046, trees-013, turkey-055, twentyonepilots-012, ubc-046, ucf-050, uiuc-011, ultrahardcore-005, undertale-011, unitedkingdom-035, unturned-013, uofm-008, uofmn-035, uruguay-012, utahjazz-009, utaustin-013, uva-042, uwaterloo-011, vegan-043, virginiatech-043, weezer-053, wine-011, witcher-017, worldoftanks-015, xenoblade_chronicles-012, zelda-061, zootopia-012.

2 of form D's rooms are among the rooms of the P05 proposal (r/bangtan, r/completeanarchy). 4 are among the talk-only rooms of the A11 proposal's failure clause: r/bih, r/FinalFantasy, r/parrots, r/portugal.

Neither held proposal bears on this form's lean. A11 is restricted by 38 defining members (40 per cent, against 48 of the 558) and P05 by 30 (31 per cent, against 37); both are below the population's share.

7. The restrict lines: the arrow fails here, or the record cannot show it

The rule, logged at D5a-36 before reading, unchanged. I read every restrict line on an arrow held by a defining member, 316 lines, and sorted each how sentence (_analysis/d5f_restricts.py; my sort in d5a39_sort_1.json to d5a39_sort_4.json, joined in d5a39_restrict_sorted.json). The arrow fails here: the line says the consequent came without the antecedent, from another source or in another order, or that the antecedent did not lead to it. The record cannot show it: the line says the order, the link or the step is not visible, not dated or not established in the record. Both, where it says both. Neither, where it states a condition or a scope, or says that the two acts coincide or overlap. This is one reader's sort, mine; no second coder read it (J: no readers for the rest of the run).

The form's own arrows: A13 and A09. A13 runs between two of the form's signatures, keeping and traded help; section 8 reads it. Of the seven arrows with 20 restrict lines or more here, it is the only one where the record cannot show it outnumbers the arrow failing: 14 lines against 12. A09 runs from the record to carrying on. In 11 of its 16 restrict lines here the arrow fails: carrying on came before the record, or from another source. r/lovelive: "Design reuse can precede collective closure, so final recording cannot be made a necessary precursor to carrying the work onward." r/texans: "Preservation can begin from an interim image during ongoing defense rather than waiting for the final record near closure". r/radiohead: "Cooperative defense itself justifies social continuation without a preserved image demonstrably causing that wish." In 4 more the record cannot show it. r/bindingofisaac: "The successor-canvas invitation does not say that a saved image or earlier timelapse caused the move."

The arrows every form restricts. A11 (the design, then the template) fails here in 26 of 38 lines; A10 (judging too few hands, then the move) in 22 of 32; A04 (keeping, then border talk) in 20 of 25; A12 (a call, then a one-line pledge) in 14 of 26; A06 (upkeep, then scripts) in 12 of 21.

Where the record cannot show it. The record cannot show that a call turned members against a rival (A15, 6 of 6 lines), or that a flood of calls led the host to draw its line (A20, 6 of 10). On A08 (the marking, then the record) the two readings are near even: the arrow fails in 8 lines and the record cannot show it in 7.

So the two readings divide by kind, as in forms A to C. Where the line concerns the order of two acts the rooms report (keeping and talk, a shortage and a move, a design and its template, a record and carrying on), it mostly says the arrow fails as stated. Where it concerns cause (help sent because of a shortage, a rival named because of a call), it mostly says the record cannot show it. Across all 316 lines: the arrow fails here in 171, the record cannot show it in 83, both in 12, neither in 50.

8. The one relationship that runs differently here

A13 runs from P05 (keeping) to P16 (help between rooms). Its connection: "in a room carrying both, the first act of upkeep or defence comes before the first help given, asked for or traded with another room". Its mechanism: "A room keeping its work under strain runs short of hands and turns to other rooms for help, and other rooms send it."

The arrow's side. In r/denmark a member reported, "Norge angriber nu!" [denmark/c0047] (Norway is attacking now). Forty minutes later, in another thread, a member asked, "Har vi ikke nogen allierede et sted vi kan bringe ind i kampen?" [denmark/c0066]: did the room have allies it could bring into the fight. The coders' line on r/denmark says that the request is in the record and the help is not: "Defensive strain prompts an explicit allied-help request, but receipt of help cannot be inferred from the appeal alone."

The other side. In r/radiohead help was asked of a room whose work was up. A member reported, "We're in a really good position right now, we got the whole thing down now we're just filling in the background and fixing the occasional vandalism." [radiohead/c0034]. A neighbour asked, "Are you guys looking to expand? If not, could we get some help over in tagpro?" [radiohead/c0057]. To a second request from the same neighbouring room a member answered, "I'm down to help out when I can! I think there's a ton of benefit to helping protect each other when all is said and done." [radiohead/c0067]. In r/OnePiece a member put the room's own flag first before giving help (section 1). The help went out from rooms that were not short of hands. r/OnePiece's line: "Giving aid can repay prior protection after one's own image is finished, so own-room shortage is not a necessary local motive."

In 33 of 96 defining members a current-ledger line restricts A13, against 26.0 per cent of the 558. What runs differently here is the direction of the help. The model has help drawn by a room's shortage. In these rooms it is mostly sent from a room's surplus, or owed, and where a room in need asks, the record often cannot show the help arriving or its cause. The sort says so in two ways at once: the arrow fails in 12 lines (help came from spare hands, debt or affection), and the record cannot show it in 14 (a request or an offer without delivery or cause).

This is description, not a test. A13's expectation in form D is 0.675 (4 within-case datings over 705 rooms, times 119), so A13 is not-testable-here (section 10). One of its four datings, r/naruto, is a member of this form.

9. Fourth-order themes over- and under-represented

The rule was logged at D5a-01 before it ran (_analysis/d5_themes.py), and it is applied here to the defining members' codes (_analysis/d5f_facts.py). A member's coded concepts are counted by the fourth-order themes of their second-order theme's placements, and the form's pooled share on a theme is set against the pooled share over all 705 rooms. Over-represented: a ratio of 1.5 or more, with the theme present in 5 members or more. Under-represented: a ratio of 0.67 or less, with a population share of 1 per cent or more. These are shares of what the coders coded in these rooms, never a property of the rooms (contract section 5).

Over-represented (4).

• Flagging the nation: 1.9 per cent of the defining members' coded concepts against 0.8 per cent (ratio 2.32), in 9 members.
• Reciprocity: 6.2 per cent of the defining members' coded concepts against 3.0 per cent (ratio 2.05), in 57 members.
• Transition: 2.4 per cent of the defining members' coded concepts against 1.3 per cent (ratio 1.83), in 52 members.
• Attribution: 2.4 per cent of the defining members' coded concepts against 1.4 per cent (ratio 1.78), in 33 members.

In the rooms' words, from members holding the largest share on each theme (_analysis/d5f_theme_quotes.py): Reciprocity, "Omg I didn't think I'd actually recruit people. Message me and I'll help you out with a yellow heart." [ElSalvador/c0007]. Flagging the nation, "Europe America needs your help. We were there for you during WWI, WWII, and the Cold War. Please help keep our flag strong on r/place" [europe/c0514]. Transition, "Oh yeah, maybe! Not as fun without the timer but we'd be able to build more." [greyblob/c0100]. For Attribution, the theme of saying who did a thing, the top member's concept is a translation header, "Traducción chapucera:" [costa_rica/c0067], and shows little.

Under-represented (2): Neo-tribes (ratio 0.23), Visibility returns (ratio 0.57).

Reciprocity and Transition are signature changes of the form, so their excess in the codes partly restates the cut. The coders coded more naming of nations and of who did what here, and fewer tribes.

10. Arrows present, absent or not-testable-here

Section 1's arithmetic, declared at D5a-01: an arrow's expectation in a form is its within-case datings (its subs, counted over the 705 analysed rooms) over 705, times the form's n, here 119. Below one the arrow is not-testable-here, and no absence, boundary condition or failed proposition may be written from it. In form D the expectations run from 0.000 to 0.675:

• A01 (P01 to P03): 2 datings, expected 0.338; not-testable-here
• A02 (R01 to P01): 2 datings, expected 0.338; not-testable-here
• A03 (P03 to P05): 2 datings, expected 0.338; not-testable-here
• A04 (P05 to P08): 2 datings, expected 0.338; not-testable-here
• A05 (P08 to P07): 3 datings, expected 0.506; not-testable-here
• A06 (P05 to P14): 3 datings, expected 0.506; not-testable-here
• A07 (P03 to P11): 2 datings, expected 0.338; not-testable-here
• A08 (P11 to P12): 2 datings, expected 0.338; not-testable-here
• A09 (P12 to P13): 2 datings, expected 0.338; not-testable-here
• A10 (K02 to P10): 2 datings, expected 0.338; not-testable-here
• A11 (P02 to P04): 2 datings, expected 0.338; not-testable-here
• A12 (P01 to P15): 3 datings, expected 0.506; not-testable-here
• A13 (P05 to P16): 4 datings, expected 0.675; not-testable-here
• A14 (P08 to P16): 4 datings, expected 0.675; not-testable-here
• A15 (P01 to P09): 4 datings, expected 0.675; not-testable-here
• A16 (P09 to P07): 4 datings, expected 0.675; not-testable-here
• A17 (P09 to P08): 4 datings, expected 0.675; not-testable-here
• A18 (P09 to P18): 4 datings, expected 0.675; not-testable-here
• A19 (P05 to P17): 4 datings, expected 0.675; not-testable-here
• A20 (P01 to P20): 3 datings, expected 0.506; not-testable-here
• A21 (P08 to P21): 0 datings, expected 0.000; not-testable-here

Present: none. Absent: none. Not-testable-here: all 21. Members' current-ledger lines on an arrow (sections 7 and 8) are description only. Members among an arrow's within-case datings: r/anarcho_capitalism (A18); r/asktransgender (A05); r/completeanarchy (A15); r/ElSalvador (A14); r/naruto (A13, A19); r/nyjets (A16); r/Temple (A15, A16). That is arithmetic about the model's own evidence, and it tests nothing in the form.

Propositions. N01, N02, N03, N04, N05, N06, N07, N08, N09; the highest expectation among the arrows they rest on is 0.675. Every proposition is not testable here; none holds and none fails against a real expectation. No findings.jsonl line is bounded from this form.

11. How representative members do the work

The rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_facts.py). Fit is a defining member's distance to the form's centre in the allocation's 892 columns. The best two are the nearest members whose selected changes and coded concepts are at or above the form's defining medians (11 changes, 142 concepts). The least well is the farthest defining member. The member read at length is, among the ten nearest, the one with the most selected changes not read at length earlier in stage D5. All three near members fall in D.2.1, one part of the form's split (section 14); the least well falls in D.1.

Best fit: r/gorillaz (distance 0.776; 17 selected changes; 183 coded concepts; first-return verdict composes, re-check grade composes with residue; in F25; its point lies almost as near form C's centre, by a margin of 0.012). Its members, fans of a band, built the band's figures one at a time. It began with a question, "Contribution to /r/place?" [gorillaz/c0001], and an answer, "I am down" [gorillaz/c0002]. Calls went out for each figure: "We Need More Help on /r/place making 2-D and Noodle" [gorillaz/c0046]; "Noodle is being made!" [gorillaz/c0047]. Keeping took hours, and a member thought the damage came from placers who meant well: "I have spent the last 18 ours deleting random pupils from Russell's eyes. Don't be so sure" [gorillaz/c0123]; "The sad thing is that people adding in pupils probably think they're helping :(" [gorillaz/c0127]. Members complained of too few keepers: "Just a sub full of 26k people not going to defend lol" [gorillaz/c0139]. Neighbours held the borders for their own reasons: "New zealand and prequel memes wouldn't allow their borders to be in danger." [gorillaz/c0144]. A neighbour thanked the room for not taking its spot, and a member answered, "We've been trying to help maintain yall when we can" [gorillaz/c0086]. After the close a member posted another canvas, "New Place Area Created - http://pxls.space/" [gorillaz/c0160], and reported, "Update - We have started at (23,666) in true Gorillaz fashion" [gorillaz/c0161]. Another refused: "Just let it die man, place had its time and it's over." [gorillaz/c0162]. Earlier the room had played April Fools with fake releases: "New Track from Humanz on the Gorillaz YouTube channel!!" [gorillaz/c0015].

Second best fit: r/gamindustri (distance 0.794; 20 selected changes; 181 coded concepts; first-return verdict composes with residue, re-check grade composes with residue; in F11, F12 and F22). Its members, fans of a game series, built the game's logos beside a large neighbour. The room opened with the day's joke: "HAPPY APRIL'S FOOL!" [gamindustri/c0001]. Members kept their work and their neighbours' work together: "We actually need to defend Zoro from our own Nep one at this point! If we damage it our logo will go bye bye" [gamindustri/c0079]; "We're really at the mercy of GreenLattice here, we should avoid anything that could annoy them" [gamindustri/c0082]. A member proposed helping the neighbour remove a logo it did not want, and gave the reason: "If they don't, then at least cleaning that area up will maybe earn us some good will with them, allowing us to place something there in the future." [gamindustri/c0088]. After the close a member on a phone asked where the logo was: "I'm on mobile, gonna need someone to point me in the direction of the logo." [gamindustri/c0166]. The room started again on another canvas (section 1). The member who started Lastation there reported a loss in an edited reply: "Lastation is lost. The lattice is going through, and I need to get some sleep." [gamindustri/c0172]. Another answered, "I wasn't ready for another battle. That said, lets make Lowee and Leanbox this time!" [gamindustri/c0173]. Carrying on returned the room to building and to loss.

Least well: r/polyamory (distance 1.685; 5 selected changes; 7 coded concepts; first-return verdict composes with residue; in F35; its point lies as near form F's centre, by a margin of 0.0005). Its record is a call and a few answers. A member wrote, "We need to find a spot and work together to place a polyamory flag!" [polyamory/c0001]. Another declined: "I've seen too much /r/place spam today already. So...no thanks." [polyamory/c0002]. A member offered a channel: "There is a public discord channel I'm in and I'm sure I can convince the admins there to create a /r/place channel. LMK if anyone is interested." [polyamory/c0004]. One answered, "I'm interested! What would you wanna do?" [polyamory/c0007], and another did not know what the event was: "I have no idea - I got some weird notification on my phone about it. I can't even tell what it's about! XD" [polyamory/c0006]. Its lines hold no keeping, no help and no carrying on. It is in form D because Ward's method put it there.

Read at length: r/bindingofisaac (distance 0.804; 23 selected changes; 332 coded concepts; first-return verdict composes with residue, re-check grade composes with residue; in F01, F02, F04, F11, F12 and F23). The rule chose it: among the ten nearest it has the most selected changes and was not read at length earlier. Its members, players of one game, built the game's hero. A member started the figure: "I already started a little a bit at around 580,936. Its the top right of his face." [bindingofisaac/c0005]. Calls followed: "Who's with me?!" [bindingofisaac/c0018]; "sure, where are you drawing?" [bindingofisaac/c0019]. The keepers learned what the room had planned, and then held it. One wrote, "I'd been undoing your work when I was just seeing dots, not that I get it I'll help the cause!" [bindingofisaac/c0197]. Another asked, "Some of us are trying to go for 20/20 so avoid cleaning that please" [bindingofisaac/c0230], and was answered, "Ok thanks for telling me" [bindingofisaac/c0231]. The room made truces with neighbours, and the truces did not reach every placer: "It seems that some hots players are unaware of the truce, I'm trying to get hots to help rebuild" [bindingofisaac/c0141]; "we have told our ppl don't ruin yours. But some seems not seeing memo." [bindingofisaac/c0143]. A neighbour apologised, "Sorry about the people hijacking our logo to attack yours." [bindingofisaac/c0127], and was answered, "Can't control everyone...it's nice to know you're generally peaceful though :D" [bindingofisaac/c0128]. The room's April Fools play was argued over: "It was just for a day man." [bindingofisaac/c0193]; "really? iu still see the posts coming" [bindingofisaac/c0194]. The work was recorded, "Timelapse video of Isaac on /r/place" [bindingofisaac/c0204], and claimed: "Guys this means we won that run." [bindingofisaac/c0290]. After the close a member asked for a flair, and the answer was "Maybe." [bindingofisaac/c0309]. On another canvas the room started again: "Come help on Place2! Near the bottom right, near Qbert" [bindingofisaac/c0319]; "He's getting attacked! Help!" [bindingofisaac/c0321]; "Should we also write r/bindingofisaac above/under him?" [bindingofisaac/c0322]. What is unrepresentative about it: its record is large, 332 coded concepts against the form's defining median of 142, and it is in six branches. And its keepers were told of a planned change and then held it, which P05's telling clause predicts.

12. The branches its rooms come from

J asked that stage D6 build on the forms with the 35 branches as the level below. The branches do not nest in the forms: a branch was cut on one shared key, a form gathers rooms by the whole mix of their changes and codes. The table gives, for every branch, how many of its rooms are in form D, and the branch's share in D against D's share of the 705 rooms (119 of 705, 0.169). A ratio of 1 is what a branch would show if its rooms fell in the forms at random.

What the table shows. Ten branches lean to form D at 1.5 times its share or more. Five are of the family of carrying on (its sixth, F25, carrying on in talk, is at 1.32):

• F13, the work remade in other media, often before the close: 5 of 9.
• F12, the spine restarted on another canvas: 10 of 22.
• F11, carrying on as renewed work, begun before the close: 19 of 43.
• F23, the close scoped to the original canvas: continuation renewed, uncertain and contested: 10 of 30.
• F14, the mark adopted as the room's emblem while it is still placed, damage included: 2 of 7.

The others:

• F27, the telling clause not shown in keeping: interference seen, its cause and loss not: 13 of 27.
• F22, help conditional on the helper's own work and spare hands: 12 of 30.
• F18, success judged while upkeep continues: 5 of 15.
• F04, the licence policed: objections to the play, its limits and its end: 4 of 13.
• F24, machine hands debated, not shown placing: 7 of 27.

So the branch level says what the form's changes say: carrying on (F11 and four of its kin), help on conditions (F22), and keeping (F27, F18). Four of the five lean here more than to any form read so far; F14 leans more to form C (3 of 7). No room of F06 (the joke kept), F10 (a deal carried out as work) or F26 (informed members contest the terms at the border) is in form D. 23 of the 103 rooms of F01, the April Fools play, are in form D, and 21 of them in its part D.2 (section 14).

Rooms in no branch. 39 rooms (23 defining): r/anarcho_capitalism, r/anarchocapitalism (thin), r/androidgaming, r/asktransgender (thin), r/bannedfromanime_irl (core), r/bih, r/bobross (thin), r/chicubs, r/churchofhelix (core), r/completeanarchy, r/costa_rica, r/CryptoFR (thin), r/DiamondClub (thin), r/dmt (thin), r/eagles, r/edmontonoilers, r/ElSalvador, r/europe, r/FinalFantasy, r/genderfluid (thin), r/glasgow, r/iastate, r/ibo (thin), r/lost, r/math, r/mcgillrobotics (core), r/mizzou, r/natsume (thin), r/oltp (thin), r/oman (thin), r/partyparrot, r/rojava, r/shrooms (thin), r/the_pack, r/thetreesnetwork (thin), r/traaaaaaannnnnnnnnns, r/uruguay, r/yumenikki, r/yuyuyu.

13. The nearest form and what separates them

The nearest form is B, the work behind the thread. The distances between form D's centre and the others are B 0.391, A 0.407, C 0.430, F 0.541, E 0.686. In the tree D joins F, the spot, at four forms, and the two join A, B and C at two. So the nearest by centres and the nearest in the tree differ. D and B are separated by what the rooms changed: D's members change keeping, help and carrying on, B's the chat, the scripts and attack calls.

The rooms between forms. A 11, B 7, E 5, C 5, F 4: these are the forms whose centres lie nearer than D's to its defining members, 32 rooms in all, a third. The room that could have gone either way, the defining member with the smallest margin to another centre, is r/magictcg (16 selected changes, 353 coded concepts, in F01, F03 and F04). Its point lies nearer form E's centre, the April Fools play, by 0.248. Its record is the play of a card game sub: members judged card previews, "no foil stamp, fake" [magictcg/c0091], and "Nekerti is fake, life shouldn't be capitalized." [magictcg/c0211], and judged jokes: "Quality, this took some effort." [magictcg/c0116].

14. The split below the form

The split rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_split.py, on room-forms-tree-rooms.tsv). A split reads as a split when both parts hold 10 defining rooms or more and each part has a fourth-order change column (a node or a link) at 1.5 times the parent's defining share or more, held by a third of the part or more and by fewer in the other part. The walk descends only while splits read.

Form D's first split, at nine forms, reads as a split. It is the first form read so far whose split reads. The share of defining rooms holding each signature theme in each part: D.1: Repair work 0.741, Transition 0.389, Reciprocity 0.463; D.2: Repair work 0.738, Transition 0.429, Reciprocity 0.286. Keeping is the same in both parts. What divides them is something else (d5a39_parts.json).

• D.1, keeping with the call (54 defining rooms, 69 in all). 55.6 per cent of its defining rooms change mobilization, the theme of calls, against 4.8 per cent of D.2. Traded help leans here too: 46.3 per cent against 28.6, and the link from keeping to traded help 48.1 against 23.8. Its rooms nearest its own centre are r/Temple, r/purdue and r/rotmg. 2 of its 69 rooms are in F01.
• D.2, keeping inside the host's April Fools play (42 defining rooms, 50 in all). 66.7 per cent of its defining rooms change keying, the theme of the April Fools frame, against 13.0 per cent of D.1; collective representation 57.1 against 22.2; boundary work 47.6 against 18.5. Its rooms nearest its own centre are r/gorillaz, r/gamindustri and r/romania. 21 of its 50 rooms are in F01.

D.1's split, at fourteen forms, does not read: D.1.2 holds 4 defining rooms. D.2's split, at seventeen forms, reads.

• D.2.1, the play, carried on (27 defining rooms, 28 in all). The link from keeping to traded help is held by 37.0 per cent, and standardization of output by 33.3, against none of D.2.2. Transition, carrying on, is held by 59.3 per cent, against 13.3 of D.2.2. Its nearest rooms are r/gorillaz, r/nyjets and r/bindingofisaac.
• D.2.2, the play, kept (15 defining rooms, 22 in all). Every defining room changes repair work, against 59.3 per cent of D.2.1, and collective representation 66.7 against 51.9. Its nearest rooms are r/nlsscirclejerk, r/romania and r/heroesofthestorm.

D.2.1's split at forty-six forms and D.2.2's at thirty-six do not read: D.2.1.2 holds 8 defining rooms and D.2.2.2 holds 5. The walk stops there.

Whether traded help and carrying on stand apart. The mixture rule of D5a-37, logged at this leg's opening, applies to the signatures held by under half the members: Transition (carrying on) and Reciprocity (traded help). Repair work, at 74.0 per cent, is the form's base and not part of the mixture (_analysis/d5f_mixture.py, d5a39_mixture.json).

• They are held by different rooms, at chance. Transition is held by 39 defining members, Reciprocity by 37. They meet in 15, against 15.0 if the two were independent. Repair work meets Transition in 27 (against 28.8) and Reciprocity in 26 (against 27.4). All three meet in 10, against 11.1. 7 members hold none of the three.
• The tree does not sort them at the first split. Reciprocity falls 25 of 37 in D.1, which is two thirds. Transition falls 21 of 39 in D.1 and 18 in D.2, which is no lean. At the second level Transition gathers in D.2.1 (16 of its 27 defining rooms) and D.1.1 (20 of 50), and Reciprocity in D.1.1 (24) and D.2.1 (10).
• The rule's outcome. They stand apart if their holders overlap no more than independence gives and the first split sorts them into different parts, each with two thirds of a set's holders; they are mixed if the holders overlap more than independence or neither condition holds. The overlap is at independence. The first split sorts traded help to D.1 but does not sort carrying on. So the rule gives neither outcome, as at form B, and I report the counts: two patterns held by different rooms at chance; traded help leans to the part with the call, and carrying on is spread across both parts.

So form D divides, by the tree, along a line its name does not draw: rooms that kept their work with calls and traded help (D.1), against rooms that kept their work inside their subreddit's April Fools play (D.2). D.2 divides again into rooms that carried the work on (D.2.1) and rooms that kept it (D.2.2). D.1 and D.2 are candidate subforms for stage D6, and D.2.1 and D.2.2 candidates below D.2 (notes-D5.md); none is cut here.

15. The thin and core rooms placed here

Thin rooms (20), placed by the whole mix of their changes and codes at the nearest form centre: r/anarchocapitalism (1 change, 12 concepts), r/asktransgender (4 changes, 177 concepts), r/azerbaijan (3 changes, 8 concepts), r/bobross (4 changes, 12 concepts), r/CryptoFR (3 changes, 10 concepts), r/DiamondClub (1 change, 8 concepts), r/dmt (2 changes, 25 concepts), r/genderfluid (4 changes, 15 concepts), r/ibo (4 changes, 28 concepts), r/Mario (2 changes, 20 concepts), r/natsume (3 changes, 21 concepts), r/oltp (1 change, 1 concepts), r/oman (2 changes, 24 concepts), r/physical_removal (3 changes, 92 concepts), r/shishamo (1 change, 22 concepts), r/shrooms (1 change, 29 concepts), r/THE_R (1 change, 7 concepts), r/thetreesnetwork (4 changes, 12 concepts), r/tokyo (3 changes, 14 concepts), r/vim (4 changes, 15 concepts).

Their selected lines weigh less and enter no share above. The most frequent are A10 restrict 4 (r/genderfluid, r/oman, r/physical_removal, r/shrooms); P05 link 4 (r/ibo, r/natsume, r/oltp, r/vim); P12 link 3 (r/azerbaijan, r/DiamondClub, r/ibo); P05 restrict 3 (r/dmt, r/THE_R, r/vim); P25 add-step 2 (r/CryptoFR); P12 add-step 2 (r/azerbaijan, r/tokyo); P24 link 2 (r/bobross, r/vim); P23 link 2 (r/ibo, r/physical_removal). The most frequent touch keeping (P05) and the record (P12), as the defining members' lines touch keeping.

Core rooms (3), with no selected change, placed by their codes alone at the nearest centre in the code columns: r/bannedfromanime_irl (6 concepts; verdict composes), r/churchofhelix (2 concepts; verdict composes), r/mcgillrobotics (6 concepts; verdict composes). Their placement rests on 2 to 6 coded concepts and is weak.

16. The form test

The constructs. P05 (keeping), P16 (help between rooms) and P13 (carrying on), at the fourth-order themes T4-013 (Repair work), T4-017 (Reciprocity) and T4-028 (Transition), with the arrows A13 and A09, and the call's return (P01 link).

The relations. Keeping is shared by the hour and handed on, and keepers check the canvas and the intended form before they repair. Help between rooms flows from a room whose own work is safe, or repays earlier help, and is refused where a request brings a quarrel; where a room in need asks, the record often cannot show the help arriving or its cause. Carrying on begins before the close, and on a later canvas it returns to the call, the build and the keeping. Keeping relates to each of the other two. Traded help and carrying on are not related to each other: their holders meet at chance (section 14).

Is it falsifiable? For keeping and help, yes. A room that sent help while its own work was under strain and short of hands, with no earlier debt, would fall outside the relations; such rooms are what A13 predicts. For carrying on, yes: a room that carried its work on only after the close and only from a record would fall outside. I have not looked for these rooms outside the form.

The four organizing problems. Keeping binds the allocation of members to tasks: members take watches by their own choice and hand them on. It binds information provision too: keepers ask what the work should look like before they repair. Traded help touches reward: help is repaid with help or goodwill. Carrying on binds none of the four. It is a remainder the four problems do not name: the organizing outlives its first task, on another canvas or in a kept venue. Task division is left free.

What varies among members. Whether the room kept its work with calls and traded help, or inside its subreddit's April Fools play; and within the play, whether it carried the work on or kept it. The tree sorts this variation, and the split rule reads it at two levels. A subform is warranted for stage D6 to consider: D.1 and D.2, and below D.2, D.2.1 and D.2.2.

Result: a form in a weak sense, held together by keeping, with two candidate subforms. Keeping binds three quarters of the defining members, and their lines state relations the model does not: shared watches, checks before repair, help from surplus. The other two signatures do not bind together, and the form divides along a line its name does not draw. Two limits stay. The changes are frequent in the population, and a third of the defining rooms (32 of 96) lie nearer another centre. And the claim rests on my reading of the lines and the members' words, with every local account unresolved.

17. What would make you doubt this is a form at all

Three things.

First, the base rate and the split. Repair work is changed by 48.9 per cent of the 558 defining rooms. Form D may be the rooms where keeping was most of the record, not rooms that kept differently. And the split that reads divides the form by the April Fools play, which form E gathers; D.2 may be E's edge more than a part of D.

Second, my sort of the restrict lines. One reader sorted 316 lines. On A13, the line between the help came from surplus and the record cannot show that the shortage caused the help is a judgement in many lines, and the two counts are close (12 and 14).

Third, the survival figures, from the record, never from the canvas. The median organizing end is hour 72.05 for the 119 members with one, and the mean aftermath share is 0.0179. The coded work_remained field says kept in 60 members, lost in 39 and silent in 20. These figures are not compared here, and nothing in this account rests on them.

What would undo the form: rooms outside it with as much keeping whose help was drawn by shortage; or a cut in which D.1 and D.2 fall to different forms, which the tree already does at nine forms.

Room form E, the sub's April Fools play: the form account

Written at D5a-40, 27 October 2026. The model is the version frozen at D3 (46384686d6173fdeb4c749667478c1363e675bc6b52bb6f4fdc211d387e68525). Form E is one of the six room forms of the cut J ruled at D4a-08 (room-forms-D4a08c.*); how every room reaches its form is in room-forms-allocation.md. It holds 98 of the 705 analysed rooms. 84 are defining rooms: rooms with 5 or more selected changes, which shaped the form. 12 are thin rooms (1 to 4 selected changes) and 2 are core rooms (no selected change), placed afterwards. Thin and core rooms weigh less: every share, signature, theme count, representative choice and split below is read on the 84 defining rooms, and the thin and core rooms are named in section 15.

A room form is not a branch: it gathers rooms by the whole mix of their changes (two thirds) and their codes (one third), and the 35 branches are the level below it (section 12). The form is a pole of a continuum, but form E is the most separate pole read so far: 8 of its 84 defining rooms lie nearer another form's centre (section 13). This file sits beside the room-forms files, not in forms/, because the stage's close-check reads every account in forms/ as a branch account (departures.jsonl line 18). Hours are counted from the start of the event (h+).

1. How these rooms organized, as a narrative

In these 98 subreddits the host sub played April Fools with its own members, and the play took work. Moderators changed the sub's look, its rules or its subject for a day. Members played along, tested what was real, complained when the joke broke the site, argued about when it ended, and kept parts of it. The canvas work ran beside the play, and the record holds less of it than in other rooms.

The play had rules, and real tools enforced them. In r/battlecats the moderators' bot removed posts under a joke law: "Your post was removed because it contained the [Gacha] Tag, which violates the first commandment of the No Gacha bible" [battlecats/c0148]. In r/monstercat a member told others to follow the day's rule or delete: "no mcatDab pls delete" [monstercat/c0015]. In r/ontario a member answered the fake rules: "Happy April Fool's, I hope. If this is not a prank, you won't need to ban me, I'll leave very willingly." [ontario/c0027]. In r/totallynotrobots members wrote as robots and changed the game as they went: "WHAT IF WE PRETENDED TO BE ROBOTS PRETENDING TO BE HUMANS?" [totallynotrobots/c0011].

Members tested claims. A r/monstercat member checked a release: "Can't find this on his twitter. Either he deleted it or this is fake." [monstercat/c0008]. In r/GuildWars2 a fake guide was played along with, "Finally got my chak egg sac. Thanks for this guide" [GuildWars2/c0051], then exposed and praised: "That is honestly some really good editing. Good job!" [GuildWars2/c0057]. In r/fivenightsatfreddys the moderators had to tell members that a real fault was not the joke: "We know there's a problem with automod. We're fixing it." [fivenightsatfreddys/c0036], and added, "this isn't the fucking April fools joke" [fivenightsatfreddys/c0036].

The joke could break the site for members, and they worked around it. In r/wow members wrote, "STOP DIMMING MY SCREEN MY EYES HURT ALREADY!" [wow/c0112] and "Hey uh whatever you did for April fools crashed my computer. Currently phone posting. So uh" [wow/c0117]. Another left for the day: "Well that's okay I'll just not visit this subreddit until Monday." [wow/c0118]. A member gave a fix: "Thats DBM's april fools, you can disable it in DBM-core.lua" [wow/c0121].

The play ended, and the ending was argued. A r/warframe member wrote, "April Fools is over. Back to Warframe." [warframe/c0197]. Another answered with a time zone: "In Honolulu it's 7 pm" [warframe/c0198]. In r/MMA a member promised, "It's all good - we'll be able to get it back to normal. No worries." [MMA/c0124]. The same member kept screenshots as "A glorious reminder." [MMA/c0338] and closed with "Until next year, bby." [MMA/c0342]. A r/survivor member kept the play for those who missed it: "For anyone who didn't witness the horror on this sub yesterday, I archived it." [survivor/c0237].

The canvas came into these rooms as part of the day. A r/fivenightsatfreddys member explained it so: "It's an april fools thing. Every 10 minutes you get to place 1 pixel on the map. Subreddits are collaborating to get their icons on the map, so why not here?" [fivenightsatfreddys/c0066]. Some members wanted the play kept apart from the sub's ordinary use. A r/mls member asked, "Yeah, is the sub going to go crazy like it usually does tomorrow? With there being 7 games, I'd hate for the match threads to not happen because of April fools day" [mls/c0024]. Another was glad it did not: "I'm honestly relieved. This sub was fucking unusable the last few years." [mls/c0037].

2. What the form does

These elements are instantiated in 80 per cent of the defining members or more (_analysis/d5f_model.py, current ledger, particular lines included). The model's prose says them so.

• P01 (84 of 84; 100 per cent of the 558): "The room calls its own members, and kindred subs, to come and place for a work: to start it, build it, finish it or hold it."
• P02 (84 of 84; 100 per cent of the 558): "The room settles what its mark will show of it: a member proposes a picture, the room argues its design, makes its land's flag or emblems the mark, signs it or leaves it unsigned, claims a mark others made, adds to it or enlarges it, or adds a personal piece to a shared mark."
• K01 (83 of 84; 57 per cent of the 558): "The host sub is keyed as play for April Fools: members post fakes and takeovers under the one-day licence, and a claim in it, a call to the canvas included, may be a joke."
• R01 (83 of 84; 96 per cent of the 558): "The starter: a member who proposes the mark, maps it or begins placing it. Others joining is not part of the role: it is the answer to the room's call (P15), in the order A02 and A01 state."
• P04 (82 of 84; 97 per cent of the 558): "Members circulate a template that lays out the mark pixel by pixel, or coordinates that locate it, ask for them, and ask strays to keep to them."
• P12 (81 of 84; 97 per cent of the 558): "The room records what happened to its work and to the canvas around it: screenshots and timelapses, reports of its fate, mourning, imagined art, atlas entries, the end marked."
• P03 (80 of 84; 97 per cent of the 558): "The room builds its mark, and members report its state to the thread: what is placed, done or missing, and where."
• P11 (80 of 84; 96 per cent of the 558): "When a work is up, the room marks it: announces it, celebrates it, credits makers and helpers, reports members' own parts and says what working with strangers meant."
• P24 (80 of 84; 89 per cent of the 558): "Members ask what the canvas is, how to place, what a call or a name means and what a picture shows, and others explain the rule, the timer, the controls, whose mark a picture is and what happened. They ask before, during and after the close, and some questions get no answer."
• P16 (73 of 84; 91 per cent of the 558): "Rooms help one another's works and trade help: they give pixels to a neighbour's mark, ask other rooms for help, barter help for space or repair, thank their allies, greet them, and turn requests away."
• K02 (71 of 84; 82 per cent of the 558): "The room judges that it has too few hands or too little room for the work it wants: doubt, a canvas judged too full, a work judged absent or outclassed."
• P05 (71 of 84; 93 per cent of the 558): "The room keeps its placed work against erosion: members watch it and repair changed pixels, and the room rallies to defend it under attack, covers the night, hardens its shape and puts upkeep before growth. Repair restores the form the keepers know. A change the room has planned or agreed (P02) is therefore repaired away as damage until its keepers are told of it, and it is lost or given up where the telling does not reach them."
• K05 (69 of 84; 79 per cent of the 558): "Members place on their own time and with their own devices. They fit placing around sleep, study, exams, work and travel. They cannot place from a phone or while away, they leave when the wait is too long, they save pixels under the timer, they find the work addictive, and they report what it cost them."
• P08 (69 of 84; 86 per cent of the 558): "Rooms propose, settle and contest borders, truces and deals with neighbours by talk, through envoys, and hold each other to them."
• P15 (69 of 84; 91 per cent of the 558): "A member answers a call or proposal in one line that joins, assents, reports a part done or thanks, and the line asks for nothing back."
• R02 (69 of 84; 81 per cent of the 558): "The envoy: a member who acts for a room toward another room, carrying a proposal between threads or chats."
• P06 (68 of 84; 87 per cent of the 558): "Members work out who changed their work and why: they trace placers and rooms, find friendly fire or their own mistake, blame officers, or disown placers acting in their name."
• P07 (68 of 84; 89 per cent of the 558): "Rooms spare their neighbours' work, rein in their own attackers, apologise for damage and appeal to attackers to stop."

The model has the room call its members (P01), settle its design (P02), build (P03), circulate a template (P04), mark the work (P11) and record it (P12), and it holds the April Fools frame as a key (K01). These rooms do all of it. K01 is instantiated in 83 of 84 defining members (98.8 per cent), against 56.6 per cent of the 558; the one without it is r/baylor. Keeping (P05) is instantiated in 71 (84.5 per cent), against 93.4. The difference is in what they change, and the change is almost all in one element.

3. What it does differently, element by element and arrow by arrow

The change signature. The form's defining members change three fourth-order themes more than the defining population does (at 1.5 times its share or more, in a third of the members or more). Keying, the theme of the April Fools frame, is changed by 71.4 per cent of them, against 25.1 per cent of the 558 (share ratio 3.84). Collective memory, the theme of recording and remembering, by 40.5 per cent, against 28.1 (ratio 1.66). Direct information sharing, the theme of reporting the mark's state, by 36.9 per cent, against 15.9 (ratio 2.82). Keying is held by seven in ten members; the other two by under half.

Element by element and arrow by arrow. The table gives every element or arrow and op that 14 defining members or more change, at 1.2 times the defining population's share or more (_analysis/d5f_facts.py). A selected line specifies the model (add-condition, add-step), restricts it (restrict), connects two of its parts (link) or contradicts it. The kind of a line is not relied on (J: kappa 0.08).

No defining member holds a contradict line, so these rooms replace nothing in the model. I read the lines behind the table whole (_analysis/d5f_dump.py: K01's 114 added steps and 13 conditions; the restrict lines in section 7).

• K01, the April Fools frame: specified (add-step 56 members, 67 per cent against 19). This is the form's lean, and no other element comes near it. The added steps say that the play is administered. Fake rules are enforced by real removals. r/zelda: "Moderators enforce the prank premise through real removals and redirects, making ordinary posting and help contingent on the temporary fiction." r/monstercat: "A temporary joke becomes a case-sensitive participation rule enforced by automated messages and demands for deletion." Members test what is real. r/GuildWars2: "Members check supposedly official developments against hosting URLs and correct them as separately hosted spoofs." Members repair what the joke breaks. r/wow: "Identifying an intrusive joke leads to code edits, toggles, updates and removal that restore ordinary use." The play is ended. r/warframe: "Moderators settle the prank's cutoff by timezone while later proposals receive calendar corrections." Parts of it are kept. r/mls: "Members turn appreciation of temporary styling into a request for permanent optional flair rather than a canvas-derived legacy." And it is recorded. r/survivor: "Participants preserve and explain the host prank through an archive and wiki after its styling ends." The conditions (K01 add-condition, 12 members, under the table's floor) say that the licence is contested where the joke harms. r/wow: "Host-prank participation becomes conditional when members report eye strain, crashes or an intention to avoid the room."
• A01, from the call to building: restricted (23 members, 27 per cent against 15). Section 8 reads these lines.
• A08, from marking the work to recording it: restricted (24 members, 29 per cent against 20). The record came before the marking, or the record cannot show that the marking caused it (section 7).
• A15, from the call to a turn against a rival: restricted (16 members, 19 per cent against 12). In 14 of the 16 lines the record cannot show it (section 7).
• A07, from building to marking: restricted (14 members, 17 per cent against 11). Celebration came before the work was finished, or beside disappointment. r/chess: "Appreciation does not require a finished mark when participants recognize and credit an explicitly incomplete attempt."
• A10, from too few hands to the move: restricted (34 members, 40 per cent against 34). As in every form, the shortage led to a smaller plan, a pause or giving up, more than to a move (section 7).

What the model would not predict. The model holds the April Fools frame as a key: the room is keyed as play beside the work, and a claim in it may be a joke. In these rooms the play is work of its own, with the steps the model gives the canvas work. Someone starts it (the moderators), rules govern it, members enforce and test it, they repair what it breaks, they end it and they record it. The model has these steps for the canvas and none for the play. And the canvas work in these rooms is a smaller part of the record. Repair work is changed by 32.1 per cent of the defining members, against 48.9 of the 558, and the restrict lines say more often than in any form read so far that the record cannot show an arrow (section 7).

The rooms that show the form best, by the rule in section 11, are r/warframe and r/fivenightsatfreddys; the one that shows it least well is r/polandball.

What the claim rests on. The form is a cut of the allocation (changes two thirds, codes one third, Ward's method, six forms by J's ruling). Its stability on matched subsamples is about 0.21, and 8 of its 84 defining rooms lie nearer another form's centre. The table's counts are the ledger's. That the sub's play was administered, tested, repaired, ended and recorded is a claim on the members' words, through cite.py, in sections 1, 4 and 11. One kind of evidence does not stand in for the other.

The name, read against the members. The name is "the sub's April Fools play". The strongest argument that it names the cut rather than what the rooms did: the form's lean is one element and op (K01 add-step), F01 was cut on the same key, and 59 of F01's 103 rooms are here (section 12). A reader who suspected the name would look for members whose record is not about the play. 24 of the 84 defining members do not change keying, and r/baylor does not instantiate K01 at all. But 83 of 84 instantiate K01, and the members' own words in sections 1 and 11 are about the play. The name holds. I make no renaming proposal. One sharpening goes to notes-D5.md: the play administered beside the canvas, with its own rules, tests, repairs, ending and record.

4. The concepts it employs

First-order concepts for each change the form leans to, through cite.py:

• The fake rule enforced. "Your post was removed because it contained the [Gacha] Tag, which violates the first commandment of the No Gacha bible" [battlecats/c0148].
• The play extended by its players. "HAHA CAN WE REQUEST AN EXTENSION OF APRIL FOOLS DAY BY 364 DAYS" [totallynotrobots/c0009].
• The claim tested. "I thought it was an April Fool's joke too, but I just tried this with my party and 2 of the 5 of us got one." [GuildWars2/c0054].
• The joke judged. "You won April Fools as far as I am concerned. /shakes hand" [GuildWars2/c0131].
• What the joke broke, repaired. "Thats DBM's april fools, you can disable it in DBM-core.lua" [wow/c0121].
• The end of the play argued. "April Fools is over. Back to Warframe." [warframe/c0197]. "In Honolulu it's 7 pm" [warframe/c0198].
• The play recorded. "For anyone who didn't witness the horror on this sub yesterday, I archived it." [survivor/c0237]. "To be honest, I had to use the Survivor Wiki because I had forgotten some of the names" [survivor/c0116].
• The canvas read as part of the day. "It's an april fools thing. Every 10 minutes you get to place 1 pixel on the map." [fivenightsatfreddys/c0066].
• The call, with its builder already at work. "but my 1 man effort is futile." [warframe/c0077].
• The mark's state reported. "alrighty! btw someone put a blue spot on fredbear's face" [fivenightsatfreddys/c0076].

5. Composition here

Three judgments are kept apart.

The original global model (historical). verdicts-D.jsonl, by the last analyst ruling or else the readers' agreement. All 98 members: composes 53, composes with residue 44, does not compose 1, cannot tell 0. The 84 defining members: composes 46, composes with residue 38, does not compose 0, cannot tell 0. The one that does not compose is a thin room, r/picturegame (4 selected changes, 13 coded concepts). It is the only room of the 705 that did not compose at the first return. I read it at D3 (uncomposed-D.md) and ruled its kind out of scope: its record is the sub's own guessing game played on the joke day, with no act of its own on canvas work. That it falls in this form fits the form: here the sub's own play is most of the record. These verdicts describe the unadapted model at the first return.

The adapted local accounts. By adaptation-returns.jsonl and the current model hash (46384686), as vlib.local_return_states reads them, all 98 members are unresolved; none is validated and none has insufficient evidence. The limit D3 named is the same for each: the labelers marked every local account unresolved, and prior.md section 3's measure of local validation was not computed (J after the D3c interview). The unresolved members are:

r/4chan, r/acecombat, r/AceOfAngels8, r/anime_irl, r/apocalypserising, r/bahrain, r/battlecats, r/baylor, r/borussiadortmund, r/btc, r/cfb, r/chess, r/clashroyale, r/dankmemes, r/DestinyTheGame, r/detroitlions, r/dota2, r/drumcorps, r/elitedangerous, r/ethereum, r/feedthebeast, r/fivenightsatfreddys, r/flashtv, r/formula1, r/geometrydash, r/globaloffensive, r/greenbaypackers, r/GuildWars2, r/habs, r/hearthstone, r/homelab, r/hunterxhunter, r/kerbalspaceprogram, r/kingdomhearts, r/leagueoflegends, r/lego, r/liverpoolfc, r/Madeon, r/mariokart, r/marvel, r/mcgill, r/mechanicalkeyboards, r/minecraft, r/mls, r/MMA, r/monstercat, r/n64, r/nascar, r/nintendo, r/oneplus, r/ontario, r/osu, r/paladins, r/paragon, r/paydaytheheist, r/pcmasterrace, r/picturegame, r/pokemon, r/polandball, r/popheads, r/python, r/Rainbow6, r/rit, r/rocketleague, r/runescape, r/rush, r/rust, r/rwby, r/samuraijack, r/schoolidolfestival, r/scp, r/seahawks, r/smashbros, r/smite, r/spacex, r/spelunky, r/starcitizen, r/stardustcrusaders, r/starlightstage, r/startrek, r/stevenuniverse, r/survivor, r/swordartonline, r/teslamotors, r/thenetherlands, r/thesilphroad, r/titanfall, r/totallynotrobots, r/twitchplayspokemon, r/ultrahardcore, r/uoft, r/uwaterloo, r/warframe, r/wine, r/worldoftanks, r/wow, r/yugioh, r/zelda

The shared form explanation: supported as a lean, unresolved as an explanation of canvas organizing. One change binds two thirds of the defining members: K01's added steps, held by 56 of 84, against 18.5 per cent of the 558. The members' words show the play administered as work. But the lean is of the sub's play beside the canvas, not of the canvas work; the same key was cut as F01; and every member's own adapted account is unresolved. A verdict of composes with residue on the original model is not a current local or shared failure.

6. How the model runs here

Counts are of defining members with a current-ledger line, particular lines included (_analysis/d5f_model.py); they count any line of an op.

The elements that do the work. The elements of section 2. Of the elements instantiated in half the defining members or more, one is instantiated here ten points or more above the population: K01, in 83 of 84 (98.8 per cent), against 56.6.

The elements that sit idle. P34 is absent in 83 of 84 defining members, P33 in 76, P28 in 74, A21 in 73, P30 in 71, C02 and K07 in 66, A19 in 65, K03 in 64 and P21 in 62. They are idle in the population too, and their idleness does not mark the form.

The elements that fit less here. P17, rooms joining in coalitions, is instantiated in 29 of 84 (34.5 per cent), against 51.6 per cent of the 558. P18, the contest with a rival carried in talk, in 41 (48.8 per cent), against 60.8. P25, the work bringing people into the room, in 10 (11.9 per cent), against 23.8. These rooms record less of the canvas's politics.

What these rooms do that the model has no place for. 58 of 84 defining members carry 135 propose lines, against 210 of the 558 defining rooms (69 per cent against 38). These 84 rooms hold 135 of the 373 propose lines of all 558. I read them whole (_analysis/d5a40_propose.py). By a word search, 66 do not name the canvas, and 63 name it only to set the act apart from canvas work. They are the sub's own business on the canvas days: ordinary help and game talk inside joke threads, tournaments and contests, upvote campaigns, complaints about a substituted broadcast, a member who left because the styling risked a seizure. r/pokemon: "A participant explicitly leaves for the day because flashing styling poses an epilepsy risk." r/wine: "Participants explicitly set the trick aside and return to evaluating the real wine." At D3a-55 I ruled propose lines of this kind outside the model's scope, and the ruling stands. The model is about canvas organizing; form E is where its scope ends.

Where the room models and my reading disagree. They agree. r/warframe's model keeps the play's steps as "repairing practical costs and enforcing a theme bargain", under K01 and not as canvas repair. On the call, it reads a member's lone start as the starter's role: "The attempted start supplies the call's concrete object, supporting A02 locally even where proposing and calling occupy one post". r/fivenightsatfreddys's model says that its retrospective "explicitly credits members and friends with making three figures, supporting call-to-building as a participant's explanation rather than independently tracked placements". My reading of the members' lines is the same.

The held proposals (QD4-001; never served to any room, not re-checked). The model above is the frozen version. J ruled that both held proposals are stated in full wherever the model is reported. They are, as the tree file states them:

• P05, move 198 (contrasting), history lines 173 to 176, reverted by line 181 (move 203). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." The status would be bounded. The bound would read: "It does not hold where the keepers read a planned change from its shape and stop repairing it with no telling: completeanarchy, polska, satania, halo, bangtan, thesilphroad (R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018), a candidate branch, 'the shape read' (F-024). It does not hold where informed members hold the change against keepers who do not know: armok, maryland, oneshot (R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013), a limit below the trigger, at three nodes. Amended at D4a-01, after the D3 freeze (46384686...); not re-checked: no room was served these words." Rooms: completeanarchy, polska, satania, halo, bangtan, thesilphroad, armok, maryland, oneshot. Lines: R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018, R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013.
• A11, move 199 (dropping working hypotheses), history lines 177 to 180, reverted by line 182 (move 203). The arrow from P02 to P04 would be withdrawn (status withdrawn, in_model false). Its reason, as written: "Rule 16 and rule 14: preserve what remains supported, and replace or withdraw what does not. No defensible formulation of A11 as an arrow survives the return. (1) The order between rooms never beat its null (111 of 185 rooms, 0.600; null p95 0.670; base_rate_beaten false), and C2 withdrew it, keeping a transition inside threads. (2) Inside threads, the return's census (D3a-38, re-run as _analysis/d4a01_a11_classes.json) shows the transition in 111 rooms and template first in 98 of the 228 rooms whose lines show both ends; across threads 19 more. The reverse order is nearly as common, so the arrow carries no direction. (3) The failure clause is present and stands alone in 117 rooms: talk only in 31 (berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia) and layout only in 86. (4) The mechanism's word 'settled' is contradicted by 261 accepted restrict lines whose 'how' says a template does not settle the design for good (rival templates, polls, later redesigns, placers who deviate). A reworded arrow (a layout answers design talk in its thread) would be a new claim, never served to any room, with its reverse nearly as common: a co-occurrence, not an arrow. What remains supported, that design talk and layouts meet in threads, is held by P02's and P04's statements and ranges ('a design argued over days and redone'; 'an official template the room asks everyone to follow against other versions'), which stand. The arrow's record keeps its evidence and reasoning." Rooms (the talk-only rooms of the failure clause): berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia. Lines (the first-return lines of the census classes talk only, layout only and template first, 216): 2007scape-012, 4chan-011, AMD-012, AmericanFlaginPlace-009, AvoArmy-011, AyyMD-041, CKCrusaders-041, CSUFoCo-015, DestinyTheGame-014, DevonUK-010, FinalFantasy-014, GuardiansOfDatBoi-009, HomestarRunner-015, MonkeyIsland-011, NewMexico-015, ScottPilgrim-015, Temple-041, TsundereSharks-048, adventuretime-041, aggies-050, albania-046, alberta-016, anaheimducks-015, animalcrossing-053, anime-012, argentina-051, armenia-030, bardmains-055, berkeley-038, berserk-012, bih-036, bisexual-012, bitcoin-012, blackmirror-046, borderlands-020, bostonbruins-052, brasil-011, canada-012, catalonia-009, catholicism-011, cfb-048, chibears-010, chicubs-010, cirkeltrek-013, clashroyale-045, completeanarchy-011, criticalrole-043, crusaderkings-039, cubers-014, cuboulder-008, czech-014, dankmemes-045, darksouls-042, detroitlions-049, edboxes-046, edmontonoilers-041, empiredidnothingwrong-013, england-045, ethereum-056, europe-050, eve-049, fivenightsatfreddys-012, flashtv-055, floridagators-035, flyers-035, formula1-048, forsen-010, ftlgame-044, fxKorea-010, gameattack-015, gamindustri-053, gatech-041, ghibli-010, globaloffensive-012, greenbaypackers-011, guatemala-010, habs-011, heyyea-010, hongkong-047, hsv-012, hyperlightdrifter-046, indieheads-056, indonesia-035, ireland-045, italy-035, katawashoujo-041, lakers-009, latvia-029, leagueoflegends-042, lifeisstrange-013, linux-015, littlewitchacademia-012, loliconsunite-010, lost-044, lovelive-041, lsu-049, luxembourg-012, madokamagica-041, magictcg-010, mechanicalkeyboards-042, metalgearsolid-013, mexico-041, miamidolphins-041, minecraft-017, mit-041, mizzou-018, mls-053, monalisaclan-013, morrowind-011, msu-011, muse-048, mylittlepony-011, nVade-013, naruto-010, nbaspurs-056, necrodancer-011, neopets-047, newzealand-046, nightinthewoods-012, nin-012, ockytop-042, opticgaming-012, overwatch-017, parahumans-013, parrots-013, pathofexile-012, pcmasterrace-013, pebble-007, penguins-055, philippines-052, pitt-041, placeDE-041, placecanada-013, placesnek-031, planetside-056, polska-054, portal-012, portugal-082, predators-010, purdue-051, puzzleanddragons-013, quebec-013, radiohead-010, rainbowgrid-006, rangers-045, re_zero-042, redpandas-018, rickandmorty-042, rit-011, rocketbeans-008, rocketleague-011, romania-015, roosterteeth-013, rpi-049, russia-052, rust-010, rutgers-012, samuraijack-047, scp-014, seahawks-014, serbia-051, singapore-016, slovenia-041, smite-010, southpark-012, spacexmasterrace-052, spain-035, ss13-016, ssbpm-012, stardewvalley-058, starryknights-041, stevenuniverse-012, straya-047, suomi-041, survivor-035, sweden-045, tampabaylightning-045, terraria-048, teslamotors-012, tf2-041, thebluecorner-016, theexpanse-012, theitalyplace-054, thepointing-043, thesimpsons-011, tinytardis-009, titanfall-013, torontoraptors-016, totallynotrobots-013, transformers-046, trees-013, turkey-055, twentyonepilots-012, ubc-046, ucf-050, uiuc-011, ultrahardcore-005, undertale-011, unitedkingdom-035, unturned-013, uofm-008, uofmn-035, uruguay-012, utahjazz-009, utaustin-013, uva-042, uwaterloo-011, vegan-043, virginiatech-043, weezer-053, wine-011, witcher-017, worldoftanks-015, xenoblade_chronicles-012, zelda-061, zootopia-012.

1 of form E's rooms is among the rooms of the P05 proposal (r/thesilphroad). 5 are among the talk-only rooms of the A11 proposal's failure clause: r/habs, r/leagueoflegends, r/samuraijack, r/titanfall, r/wine.

Neither held proposal bears on this form's lean, which is the April Fools frame.

7. The restrict lines: the arrow fails here, or the record cannot show it

The rule, logged at D5a-36 before reading, unchanged. I read every restrict line on an arrow held by a defining member, 304 lines, and sorted each how sentence (_analysis/d5f_restricts.py; my sort in d5a40_sort_1.json to d5a40_sort_4.json, joined in d5a40_restrict_sorted.json). The arrow fails here: the line says the consequent came without the antecedent, from another source or in another order, or that the antecedent did not lead to it. The record cannot show it: the line says the order, the link or the step is not visible, not dated or not established in the record. Both, where it says both. Neither, where it states a condition or a scope, or says that the two acts coincide or overlap. This is one reader's sort, mine; no second coder read it (J: no readers for the rest of the run).

The record cannot show it, more often than in any form read so far. Across the 304 lines the record cannot show it in 113 (37 per cent), against 31 per cent in form A, 28 in B, 23 in C and 26 in D. The arrow fails here in 130 (43 per cent), the smallest share of the five. These rooms' records hold the calls and the reports of the canvas work, and less of the work between them.

The form's own arrows: A01, A08 and A15. A01 is read in section 8. A08 runs from marking the work to recording it. In 11 of its 24 lines the record cannot show that the marking caused the record. r/habs: "Celebration precedes screenshot preservation, but the record supplies a sequence rather than testimony that celebration caused recording." In 10 the arrow fails: the record came first. r/minecraft: "Recording already runs before the closing celebration and must not be modeled as accessible only after marking completed work". A15 runs from the call to a turn against a rival. In 14 of its 16 lines the record cannot show that the call turned the builders. r/nintendo: "Recruitment precedes attack proposals within the operation without establishing that recruitment caused attack."

The arrows every form restricts. A10 (judging too few hands, then the move) fails here in 24 of 34 lines; A11 (the design, then the template) in 21 of 41, with 13 more stating a condition; A04 (keeping, then border talk) in 13 of 19; A13 (keeping under strain, then help) in 10 of 18; A05 (a settled border, then restraint) in 8 of 12.

Where the record cannot show it. Besides A15: help traded across a border (A14, 7 of 7 lines), the one-line pledge as every reader's answer (A12, 11 of 24), and a record that led to carrying on (A09, 8 of 10).

So the two readings divide by kind, as in forms A to D. Where the line concerns the order of two acts the rooms report (a shortage and a move, keeping and talk, a design and its template), it mostly says the arrow fails as stated. Where it concerns cause (a call that brought builders or turned them on a rival, help traded, a record that led to carrying on), it mostly says the record cannot show it. Across all 304 lines: the arrow fails here in 130, the record cannot show it in 113, both in 15, neither in 46.

8. The one relationship that runs differently here

A01 runs from P01 (the call) to P03 (building). Its connection: "in a room carrying both, the first call for hands comes before the first build report". Its mechanism: "The room's call brings members to the canvas, who then build the mark and say how far it has come."

The arrow's side. In r/fivenightsatfreddys a member called the room to the canvas at h+4.5: "We'd need to work together, as it is a constant stream of pixels being added and replaced." [fivenightsatfreddys/c0027]. Another proposed a figure, "Fredbear is pretty iconic to us, so I thought we should do that." [fivenightsatfreddys/c0066], and at h+7.2 a member reported its state: "alrighty! btw someone put a blue spot on fredbear's face" [fivenightsatfreddys/c0076]. The call came first and the report followed. The room's model takes the room's own later account as the evidence: it "explicitly credits members and friends with making three figures, supporting call-to-building as a participant's explanation rather than independently tracked placements".

The other side. In r/warframe a member called the room after building alone: "Its been more than 12 hours, It's time for us to leave a mark on /r/place" [warframe/c0077], "but my 1 man effort is futile." [warframe/c0077]. A day later, when a thread called members to the finished logo, one answered that the work was older than the call: "We already have one; some guys and I helped make it last night." [warframe/c0211]. The building came before the call in the thread.

In 23 of 84 defining members a current-ledger line restricts A01, against 15.2 per cent of the 558. In 12 of the 23 the record cannot show it: a report follows a call, and the record does not show that the call brought the builder. r/greenbaypackers: "A progress report replies to a concerted call, but recruitment of that worker by the call is not independently established." In 8 the arrow fails: the work was under way before the call, or calls recur during the building. r/globaloffensive: "Calls can receive building commitments, but an already drawing member also calls for help, so calls do not invariably precede building." What runs differently here is that the call and the building appear in the record apart. These rooms' threads were about the play; the canvas work came into them as calls and reports, and the hands between them are not in the record.

This is description, not a test. A01's expectation in form E is 0.278 (2 within-case datings over 705 rooms, times 98), so A01 is not-testable-here (section 10).

9. Fourth-order themes over- and under-represented

The rule was logged at D5a-01 before it ran (_analysis/d5_themes.py), and it is applied here to the defining members' codes (_analysis/d5f_facts.py). A member's coded concepts are counted by the fourth-order themes of their second-order theme's placements, and the form's pooled share on a theme is set against the pooled share over all 705 rooms. Over-represented: a ratio of 1.5 or more, with the theme present in 5 members or more. Under-represented: a ratio of 0.67 or less, with a population share of 1 per cent or more. These are shares of what the coders coded in these rooms, never a property of the rooms (contract section 5).

Over-represented (3).

• Keying: 50.5 per cent of the defining members' coded concepts against 18.3 per cent (ratio 2.76), in 84 members.
• Visibility returns: 2.2 per cent of the defining members' coded concepts against 1.1 per cent (ratio 1.94), in 19 members.
• Direct information sharing: 5.8 per cent of the defining members' coded concepts against 3.6 per cent (ratio 1.62), in 46 members.

In the rooms' words, from members holding the largest share on each theme (_analysis/d5f_theme_quotes.py): Direct information sharing, "Coexist or we waste both our efforts on defense." [ethereum/c0092]. Visibility returns, "The down-dibz button is broken!" [ultrahardcore/c0107]. For Keying, the members with the largest share hold story and post titles, which show little: "Not Funny" [polandball/c0077], "JIZO TRUEFORM" [battlecats/c0087].

Under-represented (17): Neo-tribes (ratio 0.08), Attribution (ratio 0.22), Reciprocity (ratio 0.28), Live and let live (ratio 0.32), Territoriality (ratio 0.34), Rivalry (ratio 0.36), Repertoire of contention (ratio 0.42), Transition (ratio 0.47), Standardization of output (ratio 0.48), Completion ritual (ratio 0.49), Repair work (ratio 0.49), Backstage decision-making (ratio 0.53), Meta-organization (ratio 0.53), Negotiated order (ratio 0.59), Collective representation (ratio 0.61), Boundary work (ratio 0.62), Frame bridging (ratio 0.62).

Keying is the form's change signature, so its excess in the codes restates the cut: half the defining members' coded concepts (50.5 per cent) fall under it. The coders coded less keeping, design, territory, rivalry and help here than in the population. In these rooms' records the play takes the place of the canvas's work and politics.

10. Arrows present, absent or not-testable-here

Section 1's arithmetic, declared at D5a-01: an arrow's expectation in a form is its within-case datings (its subs, counted over the 705 analysed rooms) over 705, times the form's n, here 98. Below one the arrow is not-testable-here, and no absence, boundary condition or failed proposition may be written from it. In form E the expectations run from 0.000 to 0.556:

• A01 (P01 to P03): 2 datings, expected 0.278; not-testable-here
• A02 (R01 to P01): 2 datings, expected 0.278; not-testable-here
• A03 (P03 to P05): 2 datings, expected 0.278; not-testable-here
• A04 (P05 to P08): 2 datings, expected 0.278; not-testable-here
• A05 (P08 to P07): 3 datings, expected 0.417; not-testable-here
• A06 (P05 to P14): 3 datings, expected 0.417; not-testable-here
• A07 (P03 to P11): 2 datings, expected 0.278; not-testable-here
• A08 (P11 to P12): 2 datings, expected 0.278; not-testable-here
• A09 (P12 to P13): 2 datings, expected 0.278; not-testable-here
• A10 (K02 to P10): 2 datings, expected 0.278; not-testable-here
• A11 (P02 to P04): 2 datings, expected 0.278; not-testable-here
• A12 (P01 to P15): 3 datings, expected 0.417; not-testable-here
• A13 (P05 to P16): 4 datings, expected 0.556; not-testable-here
• A14 (P08 to P16): 4 datings, expected 0.556; not-testable-here
• A15 (P01 to P09): 4 datings, expected 0.556; not-testable-here
• A16 (P09 to P07): 4 datings, expected 0.556; not-testable-here
• A17 (P09 to P08): 4 datings, expected 0.556; not-testable-here
• A18 (P09 to P18): 4 datings, expected 0.556; not-testable-here
• A19 (P05 to P17): 4 datings, expected 0.556; not-testable-here
• A20 (P01 to P20): 3 datings, expected 0.417; not-testable-here
• A21 (P08 to P21): 0 datings, expected 0.000; not-testable-here

Present: none. Absent: none. Not-testable-here: all 21. Members' current-ledger lines on an arrow (sections 7 and 8) are description only. Members among an arrow's within-case datings: r/DestinyTheGame (A04, A12); r/habs (A02); r/nintendo (A20); r/pcmasterrace (A12); r/rocketleague (A20); r/titanfall (A08); r/yugioh (A19). That is arithmetic about the model's own evidence, and it tests nothing in the form.

Propositions. N01, N02, N03, N04, N05, N06, N07, N08, N09; the highest expectation among the arrows they rest on is 0.556. Every proposition is not testable here; none holds and none fails against a real expectation. No findings.jsonl line is bounded from this form.

11. How representative members do the work

The rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_facts.py). Fit is a defining member's distance to the form's centre in the allocation's 892 columns. The best two are the nearest members whose selected changes and coded concepts are at or above the form's defining medians (11 changes, 222 concepts). The least well is the farthest defining member. The member read at length is, among the ten nearest, the one with the most selected changes not read at length earlier in stage D5. Here the rule picks r/warframe twice: it is the nearest member above both medians, and the room with the most changes among the ten nearest, r/fivenightsatfreddys, was read at length earlier in the stage. So three rooms are told, and r/warframe is told once, at length.

Best fit, and read at length: r/warframe (distance 0.704; 21 selected changes; 294 coded concepts; first-return verdict composes, re-check grade composes with residue; in F01, F02, F03, F21 and F25). Its members play a science-fiction game, and for the day the moderators gave their sub another game's look. A member saw the joke: "Well played, mods. Preying on someone who got away from Destiny" [warframe/c0011]. Another, who had followed a bookmark to the sub, asked: "IS THIS APRIL'S FOOL???!" [warframe/c0061]. Members asked to play along, "Can we have Destiny related flairs during this April Fools joke?" [warframe/c0020], and a post set a price for another theme: "If this post gets 5000 upvotes, this will become a Club Penguin themed subreddit." [warframe/c0038]. Members met the price and asked for payment: "Over 5k upvotes, this is obviously a club penquin sub" [warframe/c0045]; "Where's the fucking Club Penguin theme." [warframe/c0046]. One summed it up: "this subreddit is now a warframe/destiny/club penguin abomination and i couldn't ask for more" [warframe/c0074]. A member showed how to repair the game's wiki, whose moderators were playing too: "If you don't enjoy the spasming pictures on every page and the Comic Sans font, and you actually want to use the Wikia today, there is an easy way to fix it." [warframe/c0066]. The canvas work ran beside the play. A call went out early, "Tenno, let's leave a mark on /r/place!" [warframe/c0008], and a member who had started alone called again (section 8). Later another call went out, "Help build the Warframe symbol at /r/place!" [warframe/c0122], with an order of work: "It's more important to put in the blue color before the white just so observers can see a design taking place." [warframe/c0123]. A member answered, "Doing my part too." [warframe/c0124]. Another judged the room's effort against a smaller sub's: "I love how this place simply gave up, while Parahumans (1/30th of this subreddit) even allied with Straya to make their own place come to life." [warframe/c0205]. Then a logo was up: "WE DID IT, TENNO!" [warframe/c0207]; "Now, to protect it and the green lattice that protects us!" [warframe/c0208]. The play ended by the clock, and the clock was argued (section 1). The rule chose it for its fit and its changes. What is unrepresentative about it: it holds all three of the form's signature themes, keying, collective memory and direct information sharing, as 7 of the 84 defining members do (section 14).

Second best fit: r/fivenightsatfreddys (distance 0.705; 22 selected changes; 625 coded concepts; first-return verdict composes with residue, re-check grade composes with residue; in F01, F02, F07, F09, F10, F23, F29 and F31). Its members are fans of a horror game series. Their play began within two hours of the event: "In honor of April Fools day, I will provide you with breadbear edits." [fivenightsatfreddys/c0006]; "Teaser Breadbear (Post breadbear edit requests in the comments, and i'll make it!)" [fivenightsatfreddys/c0008]. A bot's odd reply was taken for the joke: "Excuse me? Oh, I get it! APRIL FOOLS!" [fivenightsatfreddys/c0003]. The moderators had to say that a real fault was not part of the play (section 1). The canvas came in as a call and as part of the day (sections 1 and 8). A member proposed a spot away from the fights: "I personally vote we stake a claim away from a lot of contested areas." [fivenightsatfreddys/c0027]. When a stray pixel landed on the figure, another wrote, "God dammit greifers." [fivenightsatfreddys/c0077]. And letters found on the canvas became a request to the sub: "Scott face flair when?" [fivenightsatfreddys/c0055].

Least well: r/polandball (distance 1.255; 7 selected changes; 149 coded concepts; first-return verdict composes with residue; in F01 and F02; its point lies far from every centre, 0.490 nearer form E's than form D's). Its play was a rule: as the day's joke, the moderators banned the sub's own comics. Members waited for it, "Are you doing an April Fool's event?" [polandball/c0001], and joked while it was late: "The joke is that there is no joke. Ah !" [polandball/c0005]. Then it came: "Polandball comics are now permanently banned." [polandball/c0008]; "This change is permanent." [polandball/c0058]. Members wrote stories in place of comics, and one turned the canvas into such a story. Another wanted the canvas for later comics: "As long as once this madness stops, we see Polandball comics of the flag wars in Place. Too much good material in there." [polandball/c0055]. A drawing of the sub's figure on the canvas surprised the room: "Lol who planned to create that? I don't see any /r/place collab thread here" [polandball/c0143]. Its K01 line says what is unusual: "The temporary literary genre absorbs live canvas activity as an invented country story and reactions rather than only running beside it." Here the play did not run beside the canvas; it took the canvas in.

12. The branches its rooms come from

J asked that stage D6 build on the forms with the 35 branches as the level below. The branches do not nest in the forms: a branch was cut on one shared key, a form gathers rooms by the whole mix of their changes and codes. The table gives, for every branch, how many of its rooms are in form E, and the branch's share in E against E's share of the 705 rooms (98 of 705, 0.139). A ratio of 1 is what a branch would show if its rooms fell in the forms at random.

What the table shows. Twelve branches lean to form E at 1.5 times its share or more. Six are F01 and all five of its subforms, the April Fools play administered:

• F02, the takeover run as a temporary regime: 26 of 33.
• F06, the joke kept: a request that its change last: 6 of 8.
• F05, the styling ended: ordinary use restored: 7 of 12.
• F01, the play administered: steps that test, police, end and convert the April Fools frame: 59 of 103.
• F03, the joke tested: members check a claim's truth: 9 of 18.
• F04, the licence policed: objections to the play, its limits and its end: 5 of 13.

The others:

• F25, carrying on in talk: proposals and single attempts, not shown taken up: 8 of 27.
• F35, the call made workable: answers ask for a task, and callers supply it: 5 of 18.
• F33, the plan kept current while the design settles: 6 of 23.
• F21, the canvas call not a joke: the April Fools frame kept apart from the canvas work: 8 of 32.
• F34, the design sized to the hands: 5 of 22.
• F13, the work remade in other media, often before the close: 2 of 9.

F02's share, 0.788, is the largest any branch has in a form read so far (form A's F19 0.571, B's F08 0.540, C's F07 0.576, D's F13 0.556). More than half of F01 is here. So the branch level says what the form's change says: the play administered. No room of F12 (the spine restarted on another canvas) is in form E.

Rooms in no branch. 11 rooms (7 defining): r/AceOfAngels8 (thin), r/apocalypserising, r/greenbaypackers, r/homelab, r/leagueoflegends, r/Madeon, r/n64 (core), r/rit, r/rocketleague, r/startrek (core), r/thesilphroad (thin).

13. The nearest form and what separates them

The nearest form is D, keeping, with traded help and carrying on. The distances between form E's centre and the others are D 0.686, C 0.777, B 0.809, F 0.816, A 0.852. Every other form lies 0.68 or more from E's centre. In the tree E joins the other five only at two forms: it is the last form to join. E and D are separated by what the rooms changed: E's members change the April Fools frame, D's keeping, help and carrying on.

Form D's part D.2, read beside this form, as form D's notes ask. D.2 is the part of form D that leans to the April Fools frame. Its 42 defining rooms change keying nearly as often as E's (66.7 per cent against 71.4), but they change repair work far more (73.8 per cent against 32.1) (_analysis/d5a40_parts.py). D.2's centroid lies 0.270 from form D's centre and 0.611 from form E's. 30 of its 42 defining rooms are nearest form D's centre and 5 nearest E's (r/ElderScrolls, r/gameofthrones, r/glasgow, r/magictcg, r/NieR). So D.2 is a part of D: rooms that kept their canvas work inside their sub's play. Form E is rooms whose record is the play.

The rooms between forms. D 4, F 3, B 1: these are the forms whose centres lie nearer than E's to its defining members, 8 rooms in all. The room that could have gone either way, the defining member with the smallest margin to another centre, is r/apocalypserising (6 selected changes, 51 coded concepts, in no branch). Its point lies nearer form D's centre by 0.082. Its record has both. Members waited for the sub's joke, "WELL? I'M WAITING" [apocalypserising/c0001], and decoded it: "Guys binary code says Happy April Fools!" [apocalypserising/c0003]. And they kept a logo on the canvas: "holy crap you guys all got the AR logo on /r/place" [apocalypserising/c0008]; "you placed a grey brick in the orange section" [apocalypserising/c0013]; "dude all i did was try and make the black border of the AR logo bigger so someone else with more authority can make the text itself bigger" [apocalypserising/c0014]; "our AR logo on /r/place is under attack by minecraft lmao" [apocalypserising/c0029].

14. The split below the form

The split rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_split.py, on room-forms-tree-rooms.tsv). A split reads as a split when both parts hold 10 defining rooms or more and each part has a fourth-order change column (a node or a link) at 1.5 times the parent's defining share or more, held by a third of the part or more and by fewer in the other part. The walk descends only while splits read.

Form E's first split, at ten forms, does not read as a split. E.2 (13 defining rooms, 17 in all) leans to keying, held by 92.3 per cent of its defining rooms against 67.6 of E.1, and to mobilization, the theme of calls, 53.8 against 29.6. 14 of its 17 rooms are in F01, and its nearest rooms are r/paragon, r/dankmemes and r/kerbalspaceprogram. E.1 (71 defining rooms, 81 in all) has no column of its own. The share of defining rooms holding each signature theme in each part: E.1: Keying 0.676, Collective memory 0.437, Direct information sharing 0.380; E.2: Keying 0.923, Collective memory 0.231, Direct information sharing 0.308. The walk stops at the form, and I write no subform candidate.

E.1's split, a description beyond the walk (d5f_split.py --start E.1, d5a40_split_E1.json), at fifteen forms, does not read either. E.1.2 (19 defining rooms, 22 in all) leans to collective memory (73.7 per cent against 32.7 of E.1.1), mobilization (57.9 against 19.2) and the completion ritual. E.1.1 (52 defining rooms, 59 in all) has no lean of its own.

Whether collective memory and direct information sharing stand apart. The mixture rule of D5a-37, logged at this leg's opening, applies to the signatures held by under half the members: Collective memory (recording and remembering) and Direct information sharing (reporting the mark's state). Keying, at 71.4 per cent, is the form's base and not part of the mixture (_analysis/d5f_mixture.py, d5a40_mixture.json).

• They are held by different rooms, at a little under chance. Collective memory is held by 34 defining members, Direct information sharing by 31. They meet in 11, against 12.5 if the two were independent. Keying meets Collective memory in 26 (against 24.3) and Direct information sharing in 24 (against 22.1). All three meet in 7, against 9.0. 13 members hold none of the three.
• The tree does not sort them at the first split. Both fall in E.1: Collective memory 31 of 34, Direct information sharing 27 of 31. At the second level they part: Direct information sharing sits in E.1.1 (26 of 31), and Collective memory divides between E.1.1 (17) and E.1.2 (14).
• The rule's outcome. They stand apart if their holders overlap no more than independence gives and the first split sorts them into different parts, each with two thirds of a set's holders; they are mixed if the holders overlap more than independence or neither condition holds. The overlap is below independence. The first split does not sort them. So the rule gives neither outcome, as at forms B and D, and I report the counts: two patterns held by different rooms, both in E.1, which the tree parts only at its second level, and neither a subform by the split rule.

So form E is one pattern, the sub's play, with variation in how much of the canvas work its rooms recorded and how. E.2, where the play is nearly all the record, and E.1.2, where the rooms recorded and remembered their work, are descriptions for stage D6 (notes-D5.md), not candidates.

15. The thin and core rooms placed here

Thin rooms (12), placed by the whole mix of their changes and codes at the nearest form centre: r/AceOfAngels8 (1 change, 32 concepts), r/bahrain (1 change, 46 concepts), r/btc (4 changes, 221 concepts), r/elitedangerous (4 changes, 371 concepts), r/mariokart (4 changes, 16 concepts), r/mcgill (1 change, 77 concepts), r/paydaytheheist (4 changes, 175 concepts), r/picturegame (4 changes, 13 concepts), r/smite (2 changes, 435 concepts), r/spacex (4 changes, 31 concepts), r/spelunky (4 changes, 21 concepts), r/thesilphroad (4 changes, 776 concepts).

Their selected lines weigh less and enter no share above. The most frequent are K01 add-step 7 (r/bahrain, r/elitedangerous, r/mariokart, r/spacex, r/spelunky); A11 restrict 3 (r/paydaytheheist, r/smite, r/thesilphroad); A12 restrict 2 (r/AceOfAngels8, r/paydaytheheist); P16 add-condition 2 (r/btc, r/smite); P02 link 2 (r/elitedangerous); K01 add-condition 2 (r/picturegame, r/spacex); P13 restrict 2 (r/picturegame); P22 restrict 1 (r/btc). They lean as the defining members do, to the April Fools frame (K01). r/picturegame, the one room that does not compose, is among them (section 5).

Core rooms (2), with no selected change, placed by their codes alone at the nearest centre in the code columns: r/n64 (22 concepts; verdict composes), r/startrek (137 concepts; verdict composes-with-residue). Their placement rests on 22 and 137 coded concepts and is weak.

16. The form test

The constructs. K01 (the April Fools frame), at the fourth-order theme T4-001 (Keying), with P12 (the record) at T4-027 (Collective memory), P03 (the mark's state reported) at T4-007 (Direct information sharing), and the arrows A01 and A08.

The relations. The sub's play is organized work. The moderators start it and set its rules. Real removals and bots enforce the rules, and members enforce them in replies. Members test what is real, by the date, the source and the link. They repair what the joke breaks, or switch it off for themselves. They argue its end, by the clock and the time zone, and the moderators end it. They keep parts of it and record it. The canvas work runs beside the play. It enters the threads as calls and reports, and the record often cannot show the hands between a call and the building (A01) or between the marking and the record (A08).

Is it falsifiable? Yes. A sub whose April Fools play was only fakes and jokes, with no rule enforced, no test, no repair, no ending and no record, would fall outside the relations. Such subs could be looked for among the rooms where K01 is instantiated and keying is not changed (23 of the 84 defining members here); I have not read them for this.

The four organizing problems. The play binds information provision: members must learn which claims are jokes, and they test and announce it. It touches the division of authority: the moderators start and end the play, and members contest when it ends and whether its rules bind. It touches reward: a vote threshold buys a theme, and members demand the payment. Task allocation is left free. A remainder is supported: the play is the host sub's own organizing on the canvas days, beside the canvas, and the model holds it only as a key.

What varies among members. How much of the canvas work a room recorded beside its play, and whether it recorded and remembered the work (E.1.2) or reported its state (E.1.1). The tree finds no split that reads. The variation is accommodated by the form.

Result: a form in a narrow sense, of the sub's play rather than of canvas organizing. One lean binds two thirds of the defining members, and the members' words show the play's relations: rules, enforcement, tests, repair, an end and a record. Its rooms are the most separate of the forms read, and F02 has nearly four fifths of its rooms here. Two limits stay. The lean is on one key, and F01 was cut on the same key, so the form and the branch restate each other in part. And the form tells most about what the model leaves outside its scope: the sub's own business on the canvas days. The claim rests on my reading of the lines and the members' words, with every local account unresolved.

17. What would make you doubt this is a form at all

Three things.

First, the cut and the branch. The form's lean is K01's added steps, and F01 was cut on K01 at D4. Form E may be F01 drawn again with the codes added, not a form of its own. What speaks against it: 44 of F01's 103 rooms are in other forms, and 21 of them are in D.2, the part of form D where 73.8 per cent of the defining rooms change repair work (section 13).

Second, my sort of the restrict lines. One reader sorted 304 lines. In this form more lines than anywhere fell to the record cannot show it, and the line between that and the arrow fails here is a judgement in many A01 and A08 lines.

Third, the survival figures, from the record, never from the canvas. The median organizing end is hour 72.045 for the 98 members with one, and the mean aftermath share is 0.0145. The coded work_remained field says kept in 45 members, lost in 41 and silent in 12. These figures are not compared here, and nothing in this account rests on them.

What would undo the form: a cut without K01's add-step lines in which its rooms scatter across the other forms; or a reading of these rooms' threads in which the play was only a key, run by no one.

Room form F, the spot: lost, chosen or yielded, and building again: the form account

Written at D5a-41, 27 October 2026. The model is the version frozen at D3 (46384686d6173fdeb4c749667478c1363e675bc6b52bb6f4fdc211d387e68525). Form F is one of the six room forms of the cut J ruled at D4a-08 (room-forms-D4a08c.*); how every room reaches its form is in room-forms-allocation.md. It holds 56 of the 705 analysed rooms. 34 are defining rooms: rooms with 5 or more selected changes, which shaped the form. 16 are thin rooms (1 to 4 selected changes) and 6 are core rooms (no selected change), placed afterwards. Thin and core rooms weigh less: every share, signature, theme count, representative choice and split below is read on the 34 defining rooms, and the thin and core rooms are named in section 15. Form F is the smallest of the six forms, and its rooms have the shortest records: the median defining member has 64.5 coded concepts. Shares here rest on few rooms.

A room form is not a branch: it gathers rooms by the whole mix of their changes (two thirds) and their codes (one third), and the 35 branches are the level below it (section 12). The form is a pole of a continuum: 2 of its 34 defining rooms lie nearer another form's centre (section 13). This file sits beside the room-forms files, not in forms/, because the stage's close-check reads every account in forms/ as a branch account (departures.jsonl line 18). Hours are counted from the start of the event (h+).

1. How these rooms organized, as a narrative

In these 56 subreddits most of the talk was about where the mark could go. Members looked for a free spot, asked neighbours for space, gave up a spot when its owner claimed it, moved after a loss, and began again at the new spot. One room, r/dallasstars, started at six spots or more.

The search began with the canvas already full. A r/sips member wrote, "we need to find a good free spot though" [sips/c0029], and another, "it's just 15x5 pixels surely we can squeeze it somewhere!" [sips/c0063]. A r/phish member said what had gone wrong the night before: "A bunch of us tried to get fluffhead on the r/place mural last night, but due to lack of coordination and a ton of other "factions" it was too difficult." [phish/c0019].

Rooms asked before they built. A r/sips member held the room back: "right we need to ask for permission from green lattice before starting, the admin just went offline in their discord, I'll apply when I get the chance." [sips/c0042]. When an early builder started, the same member wrote, "great, but I think we should wait for permission!" [sips/c0045]. Later the room gave up on that host: "turns out alot of people are applying for the green lattice. Should we find another spot?" [sips/c0048].

Rooms gave up a spot when a neighbour claimed it. In r/dallasstars a neighbour wrote, "Hey guys, we've been working our logo on that spot" [dallasstars/c0064]. A member answered, "Sorry, looked unoccupied. We'll relocate." [dallasstars/c0065], and the neighbour replied, "No worries, good luck!" [dallasstars/c0066]. Rooms also moved after a loss. A r/UPenn member wrote, "Someone took the spot, moving to (212, 892)" [UPenn/c0002]. In r/portal members asked, "Do we move our thing a little bit to the left or do we fight back when the time comes?" [portal/c0028], then "I think we lost..." [portal/c0029], and then "Ok i create a new plan. But we already wasted so much time.." [portal/c0034].

After a move the room built again. A r/dallasstars member called the room to a new spot after several had failed: "I KNOW WE'VE TRIED THIS IN A BUNCH OF SPOTS BUT (957, 605) IS LARGELY UNOCCUPIED. COME HELP!" [dallasstars/c0067]. Later a member reported, "Furthest we've gotten I think." [dallasstars/c0076]. Rooms that built beside others made terms at the border. A r/phish builder was asked, "Can you move it over a few pixels to the right to avoid the Koi?" [phish/c0028], and answered, "can we just agree to let your koi tail be on top a little bit of our logo?" [phish/c0029]. At the close a r/UPenn member wrote, "Place is over - we made the final canvas!" [UPenn/c0019].

2. What the form does

These elements are instantiated in 80 per cent of the defining members or more (_analysis/d5f_model.py, current ledger, particular lines included). The model's prose says them so.

• P01 (34 of 34; 100 per cent of the 558): "The room calls its own members, and kindred subs, to come and place for a work: to start it, build it, finish it or hold it."
• P02 (34 of 34; 100 per cent of the 558): "The room settles what its mark will show of it: a member proposes a picture, the room argues its design, makes its land's flag or emblems the mark, signs it or leaves it unsigned, claims a mark others made, adds to it or enlarges it, or adds a personal piece to a shared mark."
• P04 (34 of 34; 97 per cent of the 558): "Members circulate a template that lays out the mark pixel by pixel, or coordinates that locate it, ask for them, and ask strays to keep to them."
• R01 (34 of 34; 96 per cent of the 558): "The starter: a member who proposes the mark, maps it or begins placing it. Others joining is not part of the role: it is the answer to the room's call (P15), in the order A02 and A01 state."
• P03 (33 of 34; 97 per cent of the 558): "The room builds its mark, and members report its state to the thread: what is placed, done or missing, and where."
• K02 (32 of 34; 82 per cent of the 558): "The room judges that it has too few hands or too little room for the work it wants: doubt, a canvas judged too full, a work judged absent or outclassed."
• P12 (32 of 34; 97 per cent of the 558): "The room records what happened to its work and to the canvas around it: screenshots and timelapses, reports of its fate, mourning, imagined art, atlas entries, the end marked."
• P24 (30 of 34; 89 per cent of the 558): "Members ask what the canvas is, how to place, what a call or a name means and what a picture shows, and others explain the rule, the timer, the controls, whose mark a picture is and what happened. They ask before, during and after the close, and some questions get no answer."
• P15 (29 of 34; 91 per cent of the 558): "A member answers a call or proposal in one line that joins, assents, reports a part done or thanks, and the line asks for nothing back."
• P11 (28 of 34; 96 per cent of the 558): "When a work is up, the room marks it: announces it, celebrates it, credits makers and helpers, reports members' own parts and says what working with strangers meant."

The model has the room call its members (P01), settle its design (P02), build (P03) and circulate a template (P04), and it has the room judge that it has too few hands or too little room (K02). These rooms do all of it. K02 is instantiated in 32 of 34 defining members (94.1 per cent), against 82.4 per cent of the 558. Keeping (P05), which 93.4 per cent of the 558 instantiate, is instantiated here in 22 (64.7 per cent). The difference is in what these rooms change, and in what their short records hold.

3. What it does differently, element by element and arrow by arrow

The change signature. The form's defining members change three fourth-order columns more than the defining population does (at 1.5 times its share or more, in a third of the members or more). Territoriality, the theme of space and claims to it, is changed by 94.1 per cent of them, against 28.0 per cent of the 558 (share ratio 5.36), the highest ratio of any form's signature. Mobilization, the theme of calls, by 44.1 per cent, against 27.6 (ratio 1.67). The link from repair work to the negotiated order, lines that join keeping the mark to terms with neighbours, by 41.2 per cent, against 28.3 (ratio 1.55).

Element by element and arrow by arrow. The table gives every element or arrow and op that 14 defining members or more change, at 1.2 times the defining population's share or more (_analysis/d5f_facts.py). A selected line specifies the model (add-condition, add-step), restricts it (restrict), connects two of its parts (link) or contradicts it. The kind of a line is not relied on (J: kappa 0.08).

The rule's floor of 14 members is 41 per cent of this form's 34 defining members, so one row passes. Below the floor, and flagged as such, three more rows reach 1.5 times the population's share with 8 to 13 members: A04 restrict (13 members, 38 per cent against 23), P03 link (12, 35 per cent against 23) and A06 restrict (9, 26 per cent against 17).

No defining member holds a contradict line, so these rooms replace nothing in the model. I read the lines behind the signature whole: the 140 Territoriality-change lines of 32 defining members (_analysis/d5a41_dump_t4014.txt), and the restrict lines in section 7.

• A10, from judging too few hands to the move: restricted (16 members, 47 per cent against 34). Section 8 reads these lines. The room moved after a loss, a taken spot or a neighbour's claim more than for too few hands.
• A04, from keeping to border talk: restricted (13 members, below the floor). Every one of its 13 lines here says the arrow fails: the room talked with its neighbours before it had a mark to keep. r/sips: "Neighbour permission was discussed as a prerequisite to building, so border talk cannot locally be confined to an outcome of maintaining an existing mark." r/wildhockey: "Border and permission talk can arise during insecure construction rather than require upkeep of an established mark."
• P03, building: connected (link 12 members, below the floor). The links run from a move back to building. r/stargate: "Repeated losses and relocation are followed by renewed construction and a completed smaller gate." r/UPenn: "The move returns directly to construction through use and correction of the new anchor." The call returns as well. r/gratefuldead: "A replacement thread carrying the new spot and design renewed the call for helpers."
• P19, a room's work under a host's rule: conditioned and restricted (5 and 6 members). Rooms asked a host for space, and the record holds the request more than the answer. r/UPenn: "Instantiate only the request stage, leaving a grant, protection promise and actual host-governed residence unresolved." r/warthunder: "A prospective host's own exposure to attack can cause refusal of a guest's request for space."
• P27, choosing the spot before any loss: linked and restricted (4 and 5 members). The choice of a spot recurs after earlier losses. r/penguins: "Prospective site selection also occurs after earlier losses, so the temporal bound must concern the particular site decision rather than the room's entire history."
• A06, from upkeep to scripts: restricted (9 members, below the floor). Scripts came with the building, not only after upkeep strained. r/sbu: "Treat upkeep-driven automation as one route rather than the explanation for a script offered from the outset to create the mark."

What the model would not predict. The model has a room that judges its hands too few move its work (A10), and the account grounds no loop from the move back to building. In these rooms the move came after a loss, a spot taken or a neighbour's claim, and the room built again at the new spot, in some rooms more than once. The model has border talk follow keeping (A04). In these rooms talk with neighbours came first: the room asked for space before it built. And the model has a host rule on a guest's request (P19); in the P19 lines here the record holds the request and leaves the ruling unresolved.

The rooms that show the form best, by the rule in section 11, are r/dallasstars and r/sips; the one that shows it least well is r/ducks.

What the claim rests on. The form is a cut of the allocation (changes two thirds, codes one third, Ward's method, six forms by J's ruling). Its stability on matched subsamples is about 0.21, and 2 of its 34 defining rooms lie nearer another form's centre. The table's counts are the ledger's, on few rooms. That members asked for space, yielded and moved for reasons other than too few hands, and built again is a claim on their words, through cite.py, in sections 1, 4 and 11. One kind of evidence does not stand in for the other.

The name, read against the members. The name is "the spot: lost, chosen or yielded, and building again". The strongest argument that it names the cut rather than what the rooms did: it lists four acts, and the form's lean is one theme, territoriality, held by 32 of 34. A reader who suspected the name would look for members that hold the theme without moving or building again. The members' lines and words show all four acts: the spot lost (r/UPenn, r/portal), chosen (r/sips), yielded (r/dallasstars), and building again (in 8 members territoriality lines run from a move back to building; P03 is linked in 12 of 34). Building again is the least held of the four by these counts. The name holds as a description of the form's lean. I make no renaming proposal.

4. The concepts it employs

First-order concepts for each change the form leans to, through cite.py:

• A free spot sought. "we need to find a good free spot though" [sips/c0029].
• Permission asked before building. "great, but I think we should wait for permission!" [sips/c0045].
• A spot yielded to its owner. "Sorry, looked unoccupied. We'll relocate." [dallasstars/c0065].
• The move after a spot was taken. "Someone took the spot, moving to (212, 892)" [UPenn/c0002].
• Fight or move, weighed. "Do we move our thing a little bit to the left or do we fight back when the time comes?" [portal/c0028].
• Too few hands named. "The real problem is there isn't a big enough Hawkeye presence on Reddit, sadly." [uiowa/c0004].
• The call again, at a new spot. "I KNOW WE'VE TRIED THIS IN A BUNCH OF SPOTS BUT (957, 605) IS LARGELY UNOCCUPIED. COME HELP!" [dallasstars/c0067].
• Terms at the border. "can we just agree to let your koi tail be on top a little bit of our logo?" [phish/c0029].
• A host's own reason to protect the space. "I'm working with the Brazillians and i approve of your placement - helps us defend against vandalism in the surroundings." [phish/c0034].

5. Composition here

Three judgments are kept apart.

The original global model (historical). verdicts-D.jsonl, by the last analyst ruling or else the readers' agreement. All 56 members: composes 33, composes with residue 20, does not compose 0, cannot tell 3. The 34 defining members: composes 18, composes with residue 16, does not compose 0, cannot tell 0. The three that cannot tell are placed rooms: r/FlipnoteStudio3D, a thin room (1 selected change, 2 coded concepts), and r/nonbinary and r/PokemonSage, core rooms (1 and 2 coded concepts). Their records hold 1 or 2 coded concepts each. These verdicts describe the unadapted model at the first return.

The adapted local accounts. By adaptation-returns.jsonl and the current model hash (46384686), as vlib.local_return_states reads them, all 56 members are unresolved; none is validated and none has insufficient evidence. The limit D3 named is the same for each: the labelers marked every local account unresolved, and prior.md section 3's measure of local validation was not computed (J after the D3c interview). The unresolved members are:

r/achievement_hunter, r/berkeley, r/clubpenguin, r/cmu, r/corridor, r/COSI, r/dallasstars, r/day9, r/dbz, r/diablo, r/ducks, r/eesti, r/ethoslab, r/FlipnoteStudio3D, r/foxstevenson, r/gameboy, r/gratefuldead, r/GreenEmpire, r/haskell, r/hoodr, r/httyd, r/KState, r/latin, r/lexington, r/miraculousladybug, r/nbaspurs, r/nonbinary, r/Northwestern, r/nyu, r/pebble, r/penguins, r/phish, r/planetside, r/PokemonSage, r/portal, r/predators, r/Produce101, r/qotsa, r/Redox, r/sbu, r/sips, r/snsd, r/stargate, r/streetfighter, r/tenma, r/TheID, r/transgender, r/TreePlace, r/twentyonepilots, r/twitch, r/ufl, r/uiowa, r/UNLincoln, r/UPenn, r/warthunder, r/wildhockey

The shared form explanation: supported as a lean, unresolved as an explanation. One change binds nearly every defining member: 94.1 per cent change territoriality, against 28.0 per cent of the 558. The changes say what the model does not: the room asks before it builds, moves for reasons other than too few hands, and builds again. But the form is small, its records are short, the rows behind the account fall below the table's floor, and every member's own adapted account is unresolved. A verdict of composes with residue on the original model is not a current local or shared failure.

6. How the model runs here

Counts are of defining members with a current-ledger line, particular lines included (_analysis/d5f_model.py); they count any line of an op.

The elements that do the work. The elements of section 2. Of the elements instantiated in half the defining members or more, two are instantiated here ten points or more above the population: P10, the move after a loss, in 18 of 34 (52.9 per cent), against 40.7; and K02, judging that the room has too few hands or too little room, in 32 (94.1 per cent), against 82.4. P27, choosing the spot before any loss, is instantiated in 27 (79.4 per cent), against 71.5.

The elements that sit idle. P34 is absent in 34 of 34 defining members, K07 and P30 in 33, A21, P28 and P33 in 32, A19, C02 and P29 in 30, and P21 in 29. They are idle in the population too, and their idleness does not mark the form.

The elements that fit less here. Nineteen elements are instantiated here ten points or more below the population. The largest gaps: P18, the contest with a rival carried in talk, in 10 of 34 (29.4 per cent), against 60.8; P17, coalitions, in 7 (20.6 per cent), against 51.6; P05, keeping, in 22 (64.7 per cent), against 93.4; P23, the chat, in 14 (41.2 per cent), against 69.0. These rooms' records are short, and they hold the search for a spot more than keeping a mark, contests or chats.

What these rooms do that the model has no place for. 11 of 34 defining members carry 26 propose lines, against 210 of the 558 defining rooms (32 per cent against 38). The propose lines are not part of the form's lean. The return from the move to building (section 3) has no arrow in the model.

Where the room models and my reading disagree. They agree. r/dallasstars's model says, on its last move, that "The later move still requires a broader local condition than too few helpers: the organizer named bodily fatigue alongside competing bot art", and that "The adapted ordering allows this entry negotiation before a stable mark, rather than treating all neighbour talk as a consequence of upkeep". r/sips's model says, "The local account therefore needs neighbour permission as a possible prerequisite to building, not only an effect of maintaining an existing mark". My reading of the members' lines is the same.

The held proposals (QD4-001; never served to any room, not re-checked). The model above is the frozen version. J ruled that both held proposals are stated in full wherever the model is reported. They are, as the tree file states them:

• P05, move 198 (contrasting), history lines 173 to 176, reverted by line 181 (move 203). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." The status would be bounded. The bound would read: "It does not hold where the keepers read a planned change from its shape and stop repairing it with no telling: completeanarchy, polska, satania, halo, bangtan, thesilphroad (R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018), a candidate branch, 'the shape read' (F-024). It does not hold where informed members hold the change against keepers who do not know: armok, maryland, oneshot (R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013), a limit below the trigger, at three nodes. Amended at D4a-01, after the D3 freeze (46384686...); not re-checked: no room was served these words." Rooms: completeanarchy, polska, satania, halo, bangtan, thesilphroad, armok, maryland, oneshot. Lines: R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018, R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013.
• A11, move 199 (dropping working hypotheses), history lines 177 to 180, reverted by line 182 (move 203). The arrow from P02 to P04 would be withdrawn (status withdrawn, in_model false). Its reason, as written: "Rule 16 and rule 14: preserve what remains supported, and replace or withdraw what does not. No defensible formulation of A11 as an arrow survives the return. (1) The order between rooms never beat its null (111 of 185 rooms, 0.600; null p95 0.670; base_rate_beaten false), and C2 withdrew it, keeping a transition inside threads. (2) Inside threads, the return's census (D3a-38, re-run as _analysis/d4a01_a11_classes.json) shows the transition in 111 rooms and template first in 98 of the 228 rooms whose lines show both ends; across threads 19 more. The reverse order is nearly as common, so the arrow carries no direction. (3) The failure clause is present and stands alone in 117 rooms: talk only in 31 (berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia) and layout only in 86. (4) The mechanism's word 'settled' is contradicted by 261 accepted restrict lines whose 'how' says a template does not settle the design for good (rival templates, polls, later redesigns, placers who deviate). A reworded arrow (a layout answers design talk in its thread) would be a new claim, never served to any room, with its reverse nearly as common: a co-occurrence, not an arrow. What remains supported, that design talk and layouts meet in threads, is held by P02's and P04's statements and ranges ('a design argued over days and redone'; 'an official template the room asks everyone to follow against other versions'), which stand. The arrow's record keeps its evidence and reasoning." Rooms (the talk-only rooms of the failure clause): berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia. Lines (the first-return lines of the census classes talk only, layout only and template first, 216): 2007scape-012, 4chan-011, AMD-012, AmericanFlaginPlace-009, AvoArmy-011, AyyMD-041, CKCrusaders-041, CSUFoCo-015, DestinyTheGame-014, DevonUK-010, FinalFantasy-014, GuardiansOfDatBoi-009, HomestarRunner-015, MonkeyIsland-011, NewMexico-015, ScottPilgrim-015, Temple-041, TsundereSharks-048, adventuretime-041, aggies-050, albania-046, alberta-016, anaheimducks-015, animalcrossing-053, anime-012, argentina-051, armenia-030, bardmains-055, berkeley-038, berserk-012, bih-036, bisexual-012, bitcoin-012, blackmirror-046, borderlands-020, bostonbruins-052, brasil-011, canada-012, catalonia-009, catholicism-011, cfb-048, chibears-010, chicubs-010, cirkeltrek-013, clashroyale-045, completeanarchy-011, criticalrole-043, crusaderkings-039, cubers-014, cuboulder-008, czech-014, dankmemes-045, darksouls-042, detroitlions-049, edboxes-046, edmontonoilers-041, empiredidnothingwrong-013, england-045, ethereum-056, europe-050, eve-049, fivenightsatfreddys-012, flashtv-055, floridagators-035, flyers-035, formula1-048, forsen-010, ftlgame-044, fxKorea-010, gameattack-015, gamindustri-053, gatech-041, ghibli-010, globaloffensive-012, greenbaypackers-011, guatemala-010, habs-011, heyyea-010, hongkong-047, hsv-012, hyperlightdrifter-046, indieheads-056, indonesia-035, ireland-045, italy-035, katawashoujo-041, lakers-009, latvia-029, leagueoflegends-042, lifeisstrange-013, linux-015, littlewitchacademia-012, loliconsunite-010, lost-044, lovelive-041, lsu-049, luxembourg-012, madokamagica-041, magictcg-010, mechanicalkeyboards-042, metalgearsolid-013, mexico-041, miamidolphins-041, minecraft-017, mit-041, mizzou-018, mls-053, monalisaclan-013, morrowind-011, msu-011, muse-048, mylittlepony-011, nVade-013, naruto-010, nbaspurs-056, necrodancer-011, neopets-047, newzealand-046, nightinthewoods-012, nin-012, ockytop-042, opticgaming-012, overwatch-017, parahumans-013, parrots-013, pathofexile-012, pcmasterrace-013, pebble-007, penguins-055, philippines-052, pitt-041, placeDE-041, placecanada-013, placesnek-031, planetside-056, polska-054, portal-012, portugal-082, predators-010, purdue-051, puzzleanddragons-013, quebec-013, radiohead-010, rainbowgrid-006, rangers-045, re_zero-042, redpandas-018, rickandmorty-042, rit-011, rocketbeans-008, rocketleague-011, romania-015, roosterteeth-013, rpi-049, russia-052, rust-010, rutgers-012, samuraijack-047, scp-014, seahawks-014, serbia-051, singapore-016, slovenia-041, smite-010, southpark-012, spacexmasterrace-052, spain-035, ss13-016, ssbpm-012, stardewvalley-058, starryknights-041, stevenuniverse-012, straya-047, suomi-041, survivor-035, sweden-045, tampabaylightning-045, terraria-048, teslamotors-012, tf2-041, thebluecorner-016, theexpanse-012, theitalyplace-054, thepointing-043, thesimpsons-011, tinytardis-009, titanfall-013, torontoraptors-016, totallynotrobots-013, transformers-046, trees-013, turkey-055, twentyonepilots-012, ubc-046, ucf-050, uiuc-011, ultrahardcore-005, undertale-011, unitedkingdom-035, unturned-013, uofm-008, uofmn-035, uruguay-012, utahjazz-009, utaustin-013, uva-042, uwaterloo-011, vegan-043, virginiatech-043, weezer-053, wine-011, witcher-017, worldoftanks-015, xenoblade_chronicles-012, zelda-061, zootopia-012.

No room of form F is among the rooms of the P05 proposal. 1 is among the talk-only rooms of the A11 proposal's failure clause: r/berkeley.

Neither held proposal bears on this form's lean, which is the spot.

7. The restrict lines: the arrow fails here, or the record cannot show it

The rule, logged at D5a-36 before reading, unchanged. I read every restrict line on an arrow held by a defining member, 114 lines, and sorted each how sentence (_analysis/d5f_restricts.py; my sort in d5a41_sort_1.json and d5a41_sort_2.json, joined in d5a41_restrict_sorted.json). The arrow fails here: the line says the consequent came without the antecedent, from another source or in another order, or that the antecedent did not lead to it. The record cannot show it: the line says the order, the link or the step is not visible, not dated or not established in the record. Both, where it says both. Neither, where it states a condition or a scope, or says that the two acts coincide or overlap. This is one reader's sort, mine; no second coder read it (J: no readers for the rest of the run).

The arrow fails here, more often than in any other form. Across the 114 lines the arrow fails here in 72 (63 per cent), against 47 per cent in form A, 46 in B, 57 in C, 54 in D and 43 in E. The record cannot show it in 28 (25 per cent). These rooms' short records still date their acts: the request for space, the loss, the move and the new start appear in order, and the order is often not the model's.

The form's own arrows: A10 and A04. A10 is read in section 8. A04 runs from keeping to border talk, and here it fails in all 13 of its lines: border talk came before there was a mark to keep (section 3).

The arrows every form restricts. A11 (the design, then the template) fails here in 10 of 12 lines; A13 (keeping under strain, then help) in 6 of 10; A06 (upkeep, then scripts) in 6 of 9; A05 (a settled border, then restraint) in 5 of 7; A08 (marking, then the record) in 5 of 6.

Where the record cannot show it. A12, the one-line pledge as every reader's answer, divides evenly: it fails in 5 of 10 lines (acceptances that ask for instructions) and the record cannot show it in 5. Help traded across a border (A14) cannot be shown in 2 of 2.

So the two readings divide by kind, as in forms A to E. Where the line concerns the order of two acts the rooms report (talk and keeping, a loss and a move, a design and its template), it mostly says the arrow fails as stated. Where it concerns cause or delivery (a pledge that obliges every reader, help delivered), it mostly says the record cannot show it. Across all 114 lines: the arrow fails here in 72, the record cannot show it in 28, both in 6, neither in 8.

8. The one relationship that runs differently here

A10 runs from K02 (judging that the room has too few hands or too little room) to P10 (the move after a loss). Its connection: "in a room carrying both, the first doubt about the room's numbers or room comes before the first move after a loss". Its mechanism: "A room that judges it has too few hands to hold its spot stops fighting for it and moves."

The arrow's side. In r/uiowa a member reported a lost spot and named too few hands in one turn: "Yeah, the 72, 826 spot got overtaken by Michigan." [uiowa/c0004], and "The real problem is there isn't a big enough Hawkeye presence on Reddit, sadly." [uiowa/c0004]. The same member then chose a new spot: "Above Minnesota might work." [uiowa/c0007]; "Ok, I'm going for it. Help me out, guys!!" [uiowa/c0007]. The coders' line on r/uiowa says that the record holds the judgement and the proposal, not the completed move: "The weakness diagnosis accompanies a proposed replacement spot but does not demonstrate that the diagnosis produced a completed move."

The other side. In r/UPenn the move followed a taken spot, and no one spoke of hands: "Someone took the spot, moving to (212, 892)" [UPenn/c0002]. In r/dallasstars the room moved when a neighbour claimed the spot (section 1), and later because its builder was tired and bots crowded the place: "Yeah, the old location isn't gonna work out and I don't think I can do another handmade one again" [dallasstars/c0097]. "I moved our image northwest underneath the Hawks on the other side of the rainbow." [dallasstars/c0097]. In r/portal the room weighed fighting against moving, lost, and made a new plan (section 1). r/portal's line: "Loss prompts relocation here without an explicit diagnosis of too few hands, leaving that narrower manpower mechanism unsupported."

In 16 of 34 defining members a current-ledger line restricts A10, against 33.7 per cent of the 558. In 10 of the 16 the arrow fails: the move came from a loss, a taken spot, a neighbour's claim or a lack of space, or the shortage led the room to stay, shrink or give up. r/nbaspurs: "Shortage can supply a reason to oppose moving, so the arrow must allow contested relocation rather than treating too few hands as a uniform reason to leave." In 3 the record cannot show that a judgement produced a completed move. What runs differently here is the cause of the move. The model has the room's own judgement of its hands move it. In these rooms the spot moved them: a neighbour's claim, a loss or a lack of room.

This is description, not a test. A10's expectation in form F is 0.159 (2 within-case datings over 705 rooms, times 56), so A10 is not-testable-here (section 10). One of its two datings, r/day9, is a thin room of this form; the account names it as the room that best supports the account, and there it lost its border at hour 48 and moved within two hours.

9. Fourth-order themes over- and under-represented

The rule was logged at D5a-01 before it ran (_analysis/d5_themes.py), and it is applied here to the defining members' codes (_analysis/d5f_facts.py). A member's coded concepts are counted by the fourth-order themes of their second-order theme's placements, and the form's pooled share on a theme is set against the pooled share over all 705 rooms. Over-represented: a ratio of 1.5 or more, with the theme present in 5 members or more. Under-represented: a ratio of 0.67 or less, with a population share of 1 per cent or more. These are shares of what the coders coded in these rooms, never a property of the rooms (contract section 5).

Over-represented (5).

• Territoriality: 20.7 per cent of the defining members' coded concepts against 3.8 per cent (ratio 5.49), in 32 members.
• Collective efficacy: 1.3 per cent of the defining members' coded concepts against 0.4 per cent (ratio 3.65), in 9 members.
• Sensemaking: 4.1 per cent of the defining members' coded concepts against 1.9 per cent (ratio 2.13), in 17 members.
• Mobilization: 8.2 per cent of the defining members' coded concepts against 4.1 per cent (ratio 2.00), in 23 members.
• Standardization of output: 3.7 per cent of the defining members' coded concepts against 2.1 per cent (ratio 1.75), in 11 members.

In the rooms' words, from members holding the largest share on each theme (_analysis/d5f_theme_quotes.py): Territoriality, "Doesn't it make more sense to have SNSD near all the other kpop related things? We can help them make a new one somewhere else." [snsd/c0052]. Collective efficacy, "Out of all the spots to choose, we pick a spot right underneath Penn State...no wonder people get us confused...." [UPenn/c0013]. Sensemaking, "10 people is a pixel a minute tho, so it adds up fast if you spread it out." [gratefuldead/c0029]. Mobilization, "We should think about a design and help The Void clear some space for it." [diablo/c0029]. Standardization of output, "I didn't realize how big 80x80 would have been." [penguins/c0057].

Under-represented (10): Neo-tribes (ratio 0.04), Attribution (ratio 0.07), Visibility returns (ratio 0.33), Rivalry (ratio 0.37), Repertoire of contention (ratio 0.39), Repair work (ratio 0.45), Live and let live (ratio 0.47), Negotiated order (ratio 0.49), Frame bridging (ratio 0.57), Transition (ratio 0.59).

Territoriality is the form's change signature, so its excess in the codes restates the cut: a fifth of the defining members' coded concepts (20.7 per cent) fall under it. The coders coded less repair work, negotiated order and contention here than in the population. In these rooms' short records, the search for space takes the place of keeping and fighting.

10. Arrows present, absent or not-testable-here

Section 1's arithmetic, declared at D5a-01: an arrow's expectation in a form is its within-case datings (its subs, counted over the 705 analysed rooms) over 705, times the form's n, here 56. Below one the arrow is not-testable-here, and no absence, boundary condition or failed proposition may be written from it. In form F the expectations run from 0.000 to 0.318, the lowest of the six forms:

• A01 (P01 to P03): 2 datings, expected 0.159; not-testable-here
• A02 (R01 to P01): 2 datings, expected 0.159; not-testable-here
• A03 (P03 to P05): 2 datings, expected 0.159; not-testable-here
• A04 (P05 to P08): 2 datings, expected 0.159; not-testable-here
• A05 (P08 to P07): 3 datings, expected 0.238; not-testable-here
• A06 (P05 to P14): 3 datings, expected 0.238; not-testable-here
• A07 (P03 to P11): 2 datings, expected 0.159; not-testable-here
• A08 (P11 to P12): 2 datings, expected 0.159; not-testable-here
• A09 (P12 to P13): 2 datings, expected 0.159; not-testable-here
• A10 (K02 to P10): 2 datings, expected 0.159; not-testable-here
• A11 (P02 to P04): 2 datings, expected 0.159; not-testable-here
• A12 (P01 to P15): 3 datings, expected 0.238; not-testable-here
• A13 (P05 to P16): 4 datings, expected 0.318; not-testable-here
• A14 (P08 to P16): 4 datings, expected 0.318; not-testable-here
• A15 (P01 to P09): 4 datings, expected 0.318; not-testable-here
• A16 (P09 to P07): 4 datings, expected 0.318; not-testable-here
• A17 (P09 to P08): 4 datings, expected 0.318; not-testable-here
• A18 (P09 to P18): 4 datings, expected 0.318; not-testable-here
• A19 (P05 to P17): 4 datings, expected 0.318; not-testable-here
• A20 (P01 to P20): 3 datings, expected 0.238; not-testable-here
• A21 (P08 to P21): 0 datings, expected 0.000; not-testable-here

Present: none. Absent: none. Not-testable-here: all 21. Members' current-ledger lines on an arrow (sections 7 and 8) are description only. Members among an arrow's within-case datings: r/corridor (A19); r/day9 (A10); r/latin (A01); r/sips (A02). That is arithmetic about the model's own evidence, and it tests nothing in the form.

Propositions. N01, N02, N03, N04, N05, N06, N07, N08, N09; the highest expectation among the arrows they rest on is 0.318. Every proposition is not testable here; none holds and none fails against a real expectation. No findings.jsonl line is bounded from this form.

11. How representative members do the work

The rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_facts.py). Fit is a defining member's distance to the form's centre in the allocation's 892 columns. The best two are the nearest members whose selected changes and coded concepts are at or above the form's defining medians (11 changes, 64.5 concepts). The least well is the farthest defining member. The member read at length is, among the ten nearest, the one with the most selected changes not read at length earlier in stage D5. As at form E, the rule picks one room twice: r/sips is the second best fit and has the most changes among the ten nearest. So three rooms are told, and r/sips is told once, at length.

Best fit: r/dallasstars (distance 0.757; 11 selected changes; 109 coded concepts; first-return verdict composes, re-check grade composes with residue; in F01 and F24). Its members follow an ice hockey team, and they tried at least six spots. Their first start was in a rival's space: "Started it at (579, 802) D: Edit: The Blues do not like that we took that spot" [dallasstars/c0025]. A member proposed a host's area, "we should build this one in green lattice. maybe in the 940, 245 area" [dallasstars/c0026], and another doubted that a host's agreement would bind its placers: "Even if everyone in that sub agrees, I doubt everyone who's defending green lattice is in that sub." [dallasstars/c0034]. Asked to recolour a rival's logo, a member refused: "there's no need to attack other people's art. better to focus on adding our logo somewhere." [dallasstars/c0059]. The room yielded a spot to its owner (section 1), dropped it, "we're dropping it." [dallasstars/c0046], and looked again: "Okay so, there's looks to be room on the Finland flag, Chicago Bears have moved on the far right side." [dallasstars/c0047]. It left that spot too: "Excellent! Finland was far too hostile." [dallasstars/c0057]. At a new spot it made terms with a neighbour writing beside it. The neighbour asked, "Hey could you please not do this? or at least let us write over it?" [dallasstars/c0079], and a member proposed a fix, "If you could move your writing 3 or 4 pixels down I don't think we'd mind the bottom star being cut off? Would that work?" [dallasstars/c0081], then agreed: "Sure, we'll try that out." [dallasstars/c0082]. The logo was made and kept by hand: "We made and maintain our logo by hand." [dallasstars/c0095]. In the end the builder moved again, tired and crowded by bots (section 8).

Second best fit, and read at length: r/sips (distance 0.758; 21 selected changes; 109 coded concepts; first-return verdict composes with residue, re-check grade composes with residue; in F20, F21 and F24). The rule chose it: among the ten nearest it has the most selected changes, and it was not read at length earlier. Its members are viewers of a video game streamer. They looked for a spot (section 1), and one member found a host's space: "There's a space at the top of the green lattice, below the purple writing. They're usually pretty tolerant of art" [sips/c0031]. The room waited for that host's permission (section 1). Meanwhile a member started beside another work: "I have started just to the right of the Rolling Stones lips, tucked in a small space that wont be missed, just added the blue so far" [sips/c0038]. In another thread members squeezed a small sign in (section 1) and finished it: "we did it guys. well done." [sips/c0066]. A neighbour then asked the room not to build over its work: "Can you guys not do the spaceman over /r/kingdomhearts keyblade? we've been working on it for a while and are almost done aside from the portion youre trying to build over." [sips/c0068], and offered a strip: "Would you consider trading to the tiny 8 wide strip? We were trying to get a couple of other spots before we were pushed out, this is the original design." [sips/c0069]. The sign was lost, "Its gone rip" [sips/c0070], and one who erased it said why: "I destroyed it last night lol. Thought it was vandalism" [sips/c0078]. Near the close the room was still choosing a spot, around another room's sign: "Actually, that would go over /r/tf2's sign, so I suggest 300, 359" [sips/c0055]. A member saw almost no free space and proposed a host: "i've been looking all over and there's almost no blank spaces that aren't being built upon, we could maybe try to co-operate with another subreddit to built upon theirs which would also offer some protection from vandalism hopefully." [sips/c0058]. A script was offered for the last spot, "I was going to write a quick script after I finish work that we could use" [sips/c0049], and helpers came from the streamer's audience: "I've been enlisted from the stream donation!" [sips/c0050]. What is unrepresentative about it: its sign was erased by a keeper who took it for vandalism, which is P05's telling clause seen from the eraser's side, and its record runs to the close with the spot still unsettled.

Least well: r/ducks (distance 1.314; 5 selected changes; 14 coded concepts; first-return verdict composes with residue; in no branch; its point lies only 0.011 nearer form F's centre than form B's). Its record is a few calls and answers. A member called for a letter, "Lets make a sick O to support our boys" [ducks/c0001], and another reported a start: "Got a green line started" [ducks/c0002]. A member proposed a spot: "We could cut it out of a pre-green area" [ducks/c0005]. Late, others proposed taking another room's letter, "I say we hijack the OSU 'O' (bottom left corner, below Michigan) CHARGE!" [ducks/c0006], or adding to a neighbour's logo: "I have already begun adding green below the Trail Blazers logo (802,551). Lets turn it into a full fledged Ducks logo! Go Ducks!" [ducks/c0012]. A member answered an invitation from another room, "Not very many people on our sub. But we'll see what we can do!" [ducks/c0010], and the last asked, "It's officially over already isn't it?" [ducks/c0013]. Its lines are about where to put a letter, and they are few. It is in form F because Ward's method put it there.

12. The branches its rooms come from

J asked that stage D6 build on the forms with the 35 branches as the level below. The branches do not nest in the forms: a branch was cut on one shared key, a form gathers rooms by the whole mix of their changes and codes. The table gives, for every branch, how many of its rooms are in form F, and the branch's share in F against F's share of the 705 rooms (56 of 705, 0.079). A ratio of 1 is what a branch would show if its rooms fell in the forms at random.

What the table shows. Four branches lean to form F at 1.5 times its share or more:

• F09, the move returns to building: relocation followed by renewed construction: 10 of 54.
• F05, the styling ended: ordinary use restored: 2 of 12.
• F04, the licence policed: objections to the play, its limits and its end: 2 of 13.
• F08, machine hands kept on one target: installing, teaching and updating every runner: 6 of 50.

F09 is one of the two narrow forms of the branch accounts: rooms that rebuild after moving. Its lean here (2.33 times F's share) is what the form's name says. But 44 of F09's 54 rooms are in other forms, so the branch and the form are not the same set. The two April Fools branches lean on 2 rooms each. Twelve branches have no room in form F, among them F02 (the takeover), F17 and its subforms (the marking provisional), the telling clause not shown in keeping or at the border (F27, F26), and help at the border conditional (F28). 28 of form F's 56 rooms are in no branch, half the form: 18 of them are thin or core rooms, and 10 are defining.

Rooms in no branch. 28 rooms (10 defining): r/achievement_hunter (thin), r/cmu, r/COSI (thin), r/diablo, r/ducks, r/FlipnoteStudio3D (thin), r/foxstevenson (thin), r/gameboy (thin), r/gratefuldead, r/GreenEmpire (core), r/haskell (thin), r/hoodr (thin), r/latin, r/lexington (thin), r/nonbinary (core), r/Northwestern, r/nyu, r/PokemonSage (core), r/Produce101 (thin), r/qotsa, r/Redox (core), r/snsd, r/TheID (core), r/transgender (thin), r/TreePlace (thin), r/ufl (thin), r/uiowa, r/UNLincoln (core).

13. The nearest form and what separates them

The nearest form is D, keeping, with traded help and carrying on. The distances between form F's centre and the others are D 0.541, B 0.547, C 0.563, A 0.567, E 0.816. Four forms lie within 0.57 of F's centre; only E lies far. In the tree F joins D at four forms, and the two join A, B and C at two. F and D are separated by what the rooms changed: F's members change territoriality, the spot, D's keeping, help and carrying on.

The rooms between forms. B 1, E 1: these are the forms whose centres lie nearer than F's to its defining members, 2 rooms in all, the fewest share of the six forms. The room that could have gone either way, the defining member with the smallest margin to another centre, is r/phish (11 selected changes, 97 coded concepts, in F01, F08, F10 and F23). Its point lies nearer form B's centre, the work behind the thread, by 0.038. Its record has both. Members asked how to coordinate, "Any ideas on how we can all coordinate? I guess we should just pick a spot and start writing it?" [phish/c0002], and used a script and an overlay to place: "Using the Tamper monkey plugin and the r/place script, I set an overlay at an area that doesn't seem to busy, and doesn't overwrite too much other stuff." [phish/c0021]. The scripts are form B's; the spot chosen where it overwrites little, and the terms at the border (section 1), are form F's.

14. The split below the form

The split rule, logged at D5a-36 before it ran, unchanged (_analysis/d5f_split.py, on room-forms-tree-rooms.tsv). A split reads as a split when both parts hold 10 defining rooms or more and each part has a fourth-order change column (a node or a link) at 1.5 times the parent's defining share or more, held by a third of the part or more and by fewer in the other part. The walk descends only while splits read.

Form F's first split, at twenty forms, does not read as a split. F.2 holds 9 defining rooms, under the rule's 10. It leans to keying, the April Fools frame (88.9 per cent of its defining rooms against 16.0 of F.1), and 7 of its 15 rooms are in F01; its nearest rooms are r/nbaspurs, r/ethoslab and r/stargate. F.1 (25 defining rooms, 41 in all) has no column of its own. The share of defining rooms holding each signature column in each part: F.1: Territoriality 0.920, Mobilization 0.440, Repair work > Negotiated order 0.480; F.2: Territoriality 1.000, Mobilization 0.444, Repair work > Negotiated order 0.222. The walk stops at the form, and I write no subform candidate.

Whether calls and terms stand apart. The mixture rule of D5a-37, logged at this leg's opening, applies to the signatures held by under half the members: Mobilization (calls) and the link Repair work > Negotiated order (keeping joined to terms). Territoriality, at 94.1 per cent, is the form's base and not part of the mixture (_analysis/d5f_mixture.py, d5a41_mixture.json).

• They are held by the same rooms, more than chance. Mobilization is held by 15 defining members, the link by 14. They meet in 8, against 6.2 if the two were independent. Territoriality meets Mobilization in 15 (against 14.1) and the link in 14 (against 13.2): every holder of either holds territoriality. All three meet in 8, against 5.8. 2 members hold none of the three, and 11 hold territoriality alone.
• The tree does not part them. At the first split Mobilization falls 11 of 15 in F.1 and the link 12 of 14.
• The rule's outcome. They stand apart if their holders overlap no more than independence gives and the first split sorts them into different parts; they are mixed if the holders overlap more than independence or neither condition holds. The overlap is above independence. So the rule gives its first definite outcome of the six forms: mixed. In these rooms the call and the terms at the border go together, and both sit on the spot. The counts are small (8 against 6.2), and I read them as a lean.

So form F is one pattern, the spot, with calls and terms held together on it by about a quarter of its defining members. The tree finds no part, and I write no subform candidate.

15. The thin and core rooms placed here

Thin rooms (16), placed by the whole mix of their changes and codes at the nearest form centre: r/achievement_hunter (3 changes, 36 concepts), r/berkeley (4 changes, 98 concepts), r/COSI (1 change, 7 concepts), r/day9 (3 changes, 38 concepts), r/FlipnoteStudio3D (1 change, 2 concepts), r/foxstevenson (3 changes, 29 concepts), r/gameboy (3 changes, 14 concepts), r/haskell (3 changes, 88 concepts), r/hoodr (3 changes, 50 concepts), r/lexington (2 changes, 15 concepts), r/miraculousladybug (4 changes, 28 concepts), r/Produce101 (2 changes, 6 concepts), r/tenma (1 change, 2 concepts), r/transgender (3 changes, 12 concepts), r/TreePlace (4 changes, 35 concepts), r/ufl (4 changes, 33 concepts).

Their selected lines weigh less and enter no share above. The most frequent are P01 add-step 3 (r/lexington, r/miraculousladybug, r/tenma); C01 restrict 2 (r/TreePlace, r/ufl); A10 restrict 2 (r/day9, r/TreePlace); P27 link 2 (r/achievement_hunter, r/foxstevenson); P03 link 2 (r/berkeley, r/day9); P17 add-step 2 (r/foxstevenson); P07 link 1 (r/COSI); P24 link 1 (r/FlipnoteStudio3D). Among them are the spot and the move (P27 link, A10 restrict, P03 link), as in the defining members. r/day9 is among them (section 8).

Core rooms (6), with no selected change, placed by their codes alone at the nearest centre in the code columns: r/GreenEmpire (7 concepts; verdict composes), r/nonbinary (1 concept; verdict cannot-tell), r/PokemonSage (2 concepts; verdict cannot-tell), r/Redox (4 concepts; verdict composes-with-residue), r/TheID (2 concepts; verdict composes), r/UNLincoln (2 concepts; verdict composes). Their placement rests on 1 to 7 coded concepts and is weak. Form F holds more placed rooms, 22 of 56, than any other form's share.

16. The form test

The constructs. P27 (choosing the spot), P10 (the move after a loss), P19 (a room's work under a host's rule) and P08 (border terms), at the fourth-order theme T4-014 (Territoriality), with K02, the arrows A10 and A04, and the return from the move to building (P03 link).

The relations. The room looks for a spot before it builds, and it asks the neighbour or host for space, so border talk comes before keeping. When a spot is claimed, taken or lost, the room yields or moves, and the cause it names is the spot more than its own hands. At the new spot it calls again and builds again, and the cycle may repeat. Where it builds beside others it makes terms at the border, and the rooms that call are more often the rooms that make terms than chance gives (8 against 6.2).

Is it falsifiable? Yes. A room that moved only when it judged its hands too few, or that built first and talked with its neighbours only to keep what it had, would fall outside the relations. A10's within-case dating, r/day9, fits the relations: the account says it offered a neighbour terms before any damage, the agreement broke at hour 48, and the room judged the spot lost and moved. I have not looked for such rooms outside the form.

The four organizing problems. The form binds information provision: a room must learn where it can build, from the canvas and from its neighbours, before it can call anyone. It touches task division between rooms: the canvas is divided by request, claim and terms. Reward and the allocation of members to tasks are left free. A remainder is supported: the search for space, and the return from the move to building.

What varies among members. How many spots a room tried, and whether it asked a host or found free space. The tree finds no split that reads, and its one small part leans to the April Fools frame. The variation is accommodated by the form.

Result: a form in a narrow sense, on few rooms. One theme binds nearly every defining member (32 of 34), and the members' words show its relations: asking before building, yielding and moving for the spot's reasons, and building again. A smaller share of its defining rooms lies nearer another centre than in any other form (2 of 34). Two limits stay. The form is small and its records are short, so the rows behind the account fall below the table's floor. And the claim rests on my reading of the lines and the members' words, with every local account unresolved.

17. What would make you doubt this is a form at all

Three things.

First, the size and the short records. 34 defining rooms with a median of 64.5 coded concepts. Form F may be the rooms whose records were short and mostly about where to build, not rooms that organized differently. Its 19 elements instantiated ten points or more below the population say the same: much of what other rooms recorded is not in these records.

Second, my sort of the restrict lines. One reader sorted 114 lines, fewer than in any other form. The share where the arrow fails, 63 per cent, rests on that sort.

Third, the survival figures, from the record, never from the canvas. The median organizing end is hour 70.86 for the 53 members with one, and the mean aftermath share is 0.0056, the lowest of the six forms. The coded work_remained field says kept in 20 members, lost in 13 and silent in 23. These figures are not compared here, and nothing in this account rests on them.

What would undo the form: rooms outside it with as much talk about the spot whose moves followed their own judgement of too few hands; or a cut on longer records in which these rooms fall into the forms of keeping and design.

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

Written at D5a-41, 2026-10-27 UTC: room form F's account, the last of six. The model stands frozen at D3c, 46384686…, re-checked in all 705 rooms. The return was served at pass 15 (e15f9647…b3fecd).

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: 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?

J's rulings for stage D (17:40 Amsterdam, through the PI; carry them)

• "No second coder on your solo reads: Codex did not read all rooms, so its evidence is thin; your reads stand, with their limits stated as you stated them." Stage D and every later stage run at xhigh effort. "Keep the room, or groups of rooms, as the unit, and keep the contract's two questions in view." QD1-001, QD2-001, QD3-001 (J): an element may sit in more than one dimension; a dimension may stand as the element of restrict, add-condition and add-step; packets are read whole. Absent lines are counted by observation (J, 16 October). QD3-002 (J; carry it): "the analyst is doing induction." I place codes where the population's evidence leads, say why, and ask for the changes I need: "Not the rules bound their understanding." J, 16 October, 19:08 Berlin, on drift (carry it): re-orient at every leg start and after every compaction; a ruling rule changes only by a dated amendment that says whether it applies backwards. QD3-003 to QD3-008: G4a applies forward and backwards; A07's bound keeps its words; wording questions without a correction are mine, logged. QD3-011 (J): option (b): freeze 46384686; keep R01 as it is; hold the paladins and portugal proposal beside P34.
• J after the D3c interview (24 October, 13:39 Berlin; carry it): no further re-check, no labelers and no readers for the rest of the run. Do not rely on the kind of add-condition, add-step and restrict lines (kappa 0.08); run the distance once with kind collapsed for them (done). Report local validation as not established unless prior.md section 3's measure is computed (not computed). QD4-001 (J, 24 October, 15:05 Berlin): option (b): the P05 and A11 amendments are reverted, so the model is 46384686 again, and both are held proposals, stated in full wherever the model is reported; keep F-024's and F-017's re-examination lines. QD4-002 (J, 25 October, 19:48 and 19:54 Berlin): option (a): the engine is patched to chunk-comparison-v1.1 (residue-only placements counted apart); run it, report each room's residue share, and declare the version as a departure (done: departures.jsonl line 10).

The return and the tree (D1a to D4a-01)

• D1a to D3c. 705 rooms returned 42,243 lines, then 53,493 at the re-check; all ruled. Moves 172 to 197 revised R01, P05, P21, P22 and A21, stood five candidates, entered fifteen, and decided P05's scope (F-024). Verdicts, first return then re-check: composes 201 and 630, with residue 489 and 56, cannot tell 14 and 19, does not compose 1 and 0.
• D4a-01 to D4a-04. Delta 0.4227; the dendrogram is a chain; shared corrections reach 5 rooms only at the bare target. F01 (103 rooms) and five subforms came first (moves 200 to 207); the other 31 element keys of 20 rooms or more gave 29 cuts (24 branches, 5 subforms), 8 keys set aside and 759 cross-links. The branches are facets: 200 rooms are in one branch, the rest in two or more. Accounting: 476 in a branch, 229 in none; 705. The comparison (v1.1) does not survive a change of distance; its clusters sort rooms by size (eta squared 0.255). Top-level branches cannot be joined (J asked): they meet only at a dimension or the bare target.
• D5a-01 to D5a-35, F01 to F35. Families state one change at several nodes: the April Fools frame (F01 and five subforms, F21), P05's telling clause (F07, F26, F27; F-025 to F-027), the instruction kept current (F08, F15, F33), carrying on (F11 to F14, F23, F25), the chat (F16, F29, F30), help on conditions (F22, F28). All groupings. Narrow forms: F09 (54), rooms rebuild after moving; F32 (21), rooms keep after marking. No arrow is testable; 12 names kept.
• D5b. work_remained, re-read for the 476 rooms, agrees with the field in 248; after the close the rooms' words say stood in 149, gone in 43.
• D4a-05 to D4a-08 (J, 26 October; added after the accounts, not a recut). Room forms by changes (two thirds, arrows as links) and codes. J ruled six forms, core placed (room-forms-D4a08c.*); allocation in room-forms-allocation.md; tree to the leaves in room-forms-tree.*. The six forms stand (J, 22:51); all six have accounts (room-form-*-account.md), and a handback supplement reads them together.

The held proposals (QD4-001; never served, not re-checked)

• P05 (move 198, history lines 173 to 176; reverted by move 203, line 181). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." Status bounded. The bound names completeanarchy, polska, satania, halo, bangtan and thesilphroad (the keepers read the change from its shape) and armok, maryland and oneshot (informed members hold it), with their nine re-check lines. The full text is in the tree file ("The held proposals").
• A11 (move 199, history lines 177 to 180; reverted by move 203, line 182). The arrow from P02 to P04 would be withdrawn under rule 14. It never beat its null; template first (98 rooms) is nearly as common as the transition (111); the failure clause stands alone in 117 rooms, 31 of them talk only; 261 accepted restrict lines say that a template does not settle the design for good.

The current account, and the contrary rooms

The account is account.md, pass 15, with the readers' disagreements in account-readers-C5.md. A room, or a group of rooms, is the actor where its members spoke or acted for it.

• The spine. A member starts a mark [R01]. The room's calls follow the start in 64 of 89 rooms [A02], building follows calls in 81 of 126 [A01], and keeping follows building in 148 of 190 [A03]. Keeping holds the known form [P05]. Repair restores the form the keepers know, so a change the room planned [P02] is repaired away until they are told of it. In six rooms the keepers read the change from its shape, and in three informed members hold it (F-024; the bound is a held proposal).
• The bare answer. Most calls get no written reply. Written acceptances come bare (25 of 31, F-023), and refusals give a reason (attack calls 23 of 38, F-014). The host's line. It follows the calls in 132 of 155 rooms [A20].
• Alignment without decision (theorised, thin). 233 of 370 rooms with calls report a work up after the first call (F-021). A template settles a design inside a thread [A11, its withdrawal held]. Decided order is coded in 46 rooms [C01, F-006], and the return shows it in about 119. Direct information sharing (T4-007). Members post the mark's state [P03; F-018], largely apart from sharing templates (F-022).
• Other rooms. Keeping brings neighbour talk in 235 of 401 rooms [A04], mostly offering terms first. Help names a deal in 63 of 127 such rooms, against 23 of 67 [A14; F-020]. Sparing rests on the room's own norm (A05 theorised). Coalitions [A19] cannot bind every placer, and members say so [P21], after an agreement or at the making of terms [A21].
• The contest. A call can turn members against a rival [A15]. Rooms meet attack calls with restraint [A16] or terms [A17]. Loss (thin). A room that judges its hands too few moves [A10]; after doubt and a loss, 10 moved and 11 gave up (F-019). No loop is grounded. The close. The room celebrates, records and carries the work on [A07, A08, A09]. Placement stops at hour 73. After it, rooms record the work [P12] and contest which version is kept [P22]. Carrying on stays apart [P13]. The frame [K01]. The room is keyed as April Fools play beside the work, and in 103 rooms its members administer that play (F01). Machine hands. Scripts follow upkeep under strain [A06]. C02 (untested for order): a tie the room had before the canvas names the rival in the attack turn. Fifteen candidates (P23 to P34, K05 to K07), from chats and explaining the canvas to members of both rooms.

The room that best supports the account: day9. It offers a neighbour terms before any damage, loses its border at hour 48, moves within two hours, and finishes the new work at hour 53. For the return's claim: monsterhunter, where a member tells the keepers to stop repairing [monsterhunter/c0138].

The room that most threatens it: thebluecorner. It is a colour faction whose faith names its rivals and rules on guests. For the return's claim: halo, whose keepers saw what the work was and protected it, with no telling [halo/c0402].

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 faith or a host's rule decides, it does not. For the return: how the keepers can learn that a change is planned.

The reasons for the last revisions

• Moves 198, 199 and 203 reverted the refused amendments (QD4-001); 200 to 237 cut the branches and cross-links; 238 to 313 named the room forms of D4a-05 to D4a-08 and withdrew 32 sub-forms (J).

Where the run stands

• The tree's files: branches.jsonl (35), forms/ (35), crosslinks.jsonl (759), and the stage's other files. Ledgers (lines): adjudications 96,568; verdicts 1,029; tier history 1,020; model history 182; findings 45 (27 findings); elements 45 (30 standing, 15 candidates); arrows 21. Still open: the account's survival paragraph rests on the work_remained field (defects line 100); four timings the canvas contradicts (line 101); the fields the prose rule did not read; structure-C4.md's stale prose; Critical mass flagged; the border coders' kappa, 0.19. Questions: none open.

J on language (C4, 18:20 Berlin; restated 15 October; 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. Follow ASD-STE100 about 80% of the time: one idea per sentence, active voice, common words, the actor and the act named. Describe what members did, in what order, in how many rooms, and write no figures of speech. Gloss each construct name in plain words where it first appears.

Stage C2

• J's ruling on QC2-002: "from here the criterion is a guide, not the judge, and a rise in residue is not a failure. 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. Close by saying what you are sure of, what you are not, and why." Pass 1 (C2a-01). J at 23:24 Berlin: "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."

Stage C1 (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 of its own (J's floor). QC1-003 (the handler, for J). Five revision-rate errors stay in out/_analysis/c1_unapplied.jsonl; all 34 count. Reading rules (scheme_v2.md). A theme names an act in the record of the room whose threads hold the words (the visitor rule). "The work" is the room's own unless a field names another's. A bare mention of the event holds no act. Help between rooms is read from either room's record.

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 and the bag test are in stage B's notes.

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, slow scripts. Never end a turn while a job runs in the background; run every write and check in the foreground.

Open, carried

• The tree. The families of changes as the next stage's material; the size confound (branches lean to large rooms); the element change keys at level 4 held by 5 to 19 rooms, unread; prior.md section 3's local measure; the two held proposals.
• Held from D3c and earlier (listed in the handbacks with their rooms): R01's added sentence; the paladins and portugal proposal; A11's 'settled'; the spine's links; the arrows' wording items; the rewrite of the account, the figure and the data structure; the colour-faction doubt [PurplePixels/c0165].

Rules kept

• Checking. Never type an id, an order, a name or a count from memory; check with a script. Never log a write before the tool answers. Count a ledger's lines after appending. Check a claim against its source before writing. Logging. There is no --kind close; log closes as notes. Log every move with --kind move, naming one of Grodal, Anteby and Holm's eight ("stabilizing" is not one), and snap it. Writing and checks. Never put a placeholder or a no-op in a command. Never put an Edit or Write and its check in one turn. Never run two writes or Edits to one file in parallel, nor in one turn. Count the head's words before the closing line. Ledger formats. A superseding finding's supersedes is the bare id. The head never names a proposition id. A re-ruling, or a history correction, is an appended line; the earlier line stays. The permission check refuses deleting any file or link; shell variables, loops, functions, brace groups, heredocs and words beginning "for_"; find -exec with braces; awk with system() or $ fields; env-var prefixes; cat or jq on out/diary/; cut after a read or a helper; head -n -N. Write a script in out/_analysis/ instead. Output. Bash output above 30 KB is cut; measure first. Files. Read the field only from out/field.

The next comparison

Next: the next stage reads the notes: renamings, subform candidates, the two missing returns, the survival paragraph.

Notes, stage D5: the branch accounts

Target length: about 300 words per branch leg, and a closing section at the last leg. Each leg adds a section; earlier sections are not edited.

D5a-01: F01, the play administered (103 members)

Section 1, declared before any comparison. The arrows stand on 0 to 4 within-case datings (their subs over the 705 analysed rooms): 2 for A01 to A04 and A07 to A11, 3 for A05, A06, A12 and A20, 4 for A13 to A19, and 0 for A21. The expectation is the datings over 705 times the branch's n. In the largest branch, F01 (103), it is at most 0.584; in the smallest, F14 (7), at most 0.040. So every arrow is not-testable-here in every branch, and every proposition (N01 to N09 rest only on arrows) is not testable. No arrow absence, boundary condition or failed proposition can be written in this stage.

Rules logged before they ran, the same for every branch. Themes over and under (section 2.8): out/_analysis/d5_themes.py. Representative members (section 2.10): out/_analysis/d5_reps.py. The other helpers: d5_line_fields.py, d5_arrows.py, d5_near.py, d5_elements.py, d5_assemble.py, d5_line.py.

Renaming proposal, for D6. D4's name, "the play administered: steps that test, police, end and convert the April Fools frame", names the keys. "Administered" holds in the takeover subform (F02), where moderators set and enforced rules. In many other members no one ran the play: members tested a claim (r/AMD), switched the styling off (r/minecraft), or complained and apologised to each other (r/phish). Proposed name: "the April Fools play handled: members and moderators test, police, end and keep the joke". Also in defects.jsonl.

A gap in the model, for D6. 64 of 103 members carry propose lines (240 of 705 rooms overall). 22 of them, in 18 members, name the sub's ordinary life going on beside the event: ordinary talk, rules and work. The model has no element for it. Also in defects.jsonl.

Subform candidates. None. D4 cut five subforms (F02 to F06); the rest of the variation is particular to one history.

Form test. A grouping, not a form. The constructs can be named, but the members do not show the relations among the five steps: 14 of 103 hold two or more steps.

Doubts carried. The size confound (median 201 coded concepts against 101); the coders' threshold for an add-step on K01 (354 rooms instantiate K01, 115 add to it); Keying's share drives most of the under-represented list.

D5a-02: F02, the takeover run as a temporary regime (33 members, subform of F01)

Arithmetic. Expectations 0 to 0.187; every arrow not-testable-here, every proposition not testable.

A reading added for this branch. F02 has one key at one third-order theme, so I sorted its 43 how sentences into the parts of the regime they show (out/_analysis/d5a02_F02_facets.py): real enforcement 6 members, the regime performed 10, styling made usable 7, the end set 7, limits contested 5, the takeover turned to another activity 8. 9 members show two or more parts. This is my reading of the coders' sentences, not a key, and it grounds no cut.

A tie rule added. For the room that could have gone either way: the most even balance of key lines, then more lines, then the fewest other branches, then alphabetical. Logged before it was applied; kept for later legs.

The name. Kept. "The takeover" names what every member's line concerns; "temporary regime" holds for the members with rules and enforcement and in part for the rest. No renaming proposal.

On the F01 account. Its last sentence, "In the lines read here, the room models keep the play and the canvas apart", held for the lines read there. Two F01 members read here show the play reaching the canvas work: r/battlecats (a canvas call in the takeover's required format) and r/bindingofisaac (the joke in the canvas figure). The F01 account is not wrong and is not superseded; its condition for reading F01 as a form ("many members") is not met by two rooms.

Subform candidates. None on keys.

Form test. A grouping, not a form.

D5a-03: F03, the joke tested (18 members, subform of F01)

Arithmetic. Expectations 0 to 0.102; every arrow not-testable-here, every proposition not testable.

An amendment to the representative-member rule, dated D5a-03, forward only. Every F03 member holds one key line, so the best-fit condition (two or more key lines) selected no one. Where no member holds two lines, the condition drops: the best fit is the highest share on the key's fourth-order theme among members whose verdict is composes. Logged before it was applied. By it, r/ontario.

A general reading script. out/_analysis/d5_facets.py counts a reading file (room:theme to facet letters) against the branch's key lines and refuses nothing silently: it lists lines unread and readings with no line. F03's reading is d5a03_F03_reading.json.

The name. Kept. 14 of 18 members' lines ask whether a claim is true or a joke; the other four turned the test into performance, sincere exchange, repair of styling or troubleshooting.

What the members showed. No canvas call tested as a joke: a search of the members' coded concepts for prank words beside canvas words found 13 concepts, all explanations of the canvas or a call. So K01's clause "a call to the canvas included, may be a joke" has no instance in this branch. The canvas works of these members are small (9th percentile), against F01 and F02.

A slip, twice. At D5a-02 and here a bold lead-in held the word the close-check reads for section 13 ("doubt"), and the check refused the order. Rule for later legs: no bold lead-in or heading line before section 13 uses that word, and none before sections 10 to 12 uses their heading words.

Subform candidates. None on keys.

Form test. A grouping, not a form; the closest of F01's subforms so far.

D5a-04: F04, the licence policed (13 members, subform of F01)

Arithmetic. Expectations 0 to 0.074; no member is among any arrow's within-case datings; every arrow not-testable-here, every proposition not testable.

Two amendments to the representative-member rule, dated D5a-04, forward only. (1) The D5a-03 fallback applies whenever no member meets both best-fit conditions (composes and two or more key lines). (2) The member read at length passes over a member already read at length in an earlier account of this stage. Logged before they were applied. By them: best fit r/monstercat, read at length r/nbaspurs (r/dankmemes was read at length for F01 and F03).

The reading. d5a04_F04_reading.json: quality 6 members, the end 4, the play or its compulsory rules 4, taste 3, labels or deletion 2, moderators enforcing 1. The host's answer to an objection is in the ledger for 2 members and in my quotes for 4.

Renaming proposal, for D6. "The licence policed" says someone enforced the limits; in 12 of 13 members the lines show members objecting and no one enforcing. Proposed: "the licence contested: objections to the play, its limits and its end". Also in defects.jsonl.

The four-problem mapping is empty. Information is touched in 2 members only. The remainder, the licence's limits set from below and addressed to the host, is supported in 4 members' quotes.

What the members showed. On the canvas, restraint that follows an objection rather than an attack call (A16 restricted in r/bindingofisaac, r/chelseafc and r/nbaspurs). It is the move the members made on their pages; I note the likeness and claim no link.

Subform candidates. None on keys.

Form test. A grouping, not a form.

D5a-05: F05, the styling ended (12 members, subform of F01)

Arithmetic. Expectations 0 to 0.068; every arrow not-testable-here, every proposition not testable.

The reading. d5a05_F05_reading.json: the host ended the styling or restored the sub 6 members, members complained or refused its rules 4, members switched it off for themselves 3, asked what changed 2, leftovers cleared or kept 2, waited it out 1. 5 of 12 show two or more.

Renaming proposal, for D6. "The styling ended: ordinary use restored" claims an outcome shown in 6 of 12 members. Proposed: "the styling escaped or ended: members switch it off, the host restores ordinary use". Also in defects.jsonl.

A weakness of the representative rule, noted, not amended. Fit is the share of a member's concepts on the fourth-order theme above the key. For every subform of F01 that theme is Keying, so the same small room whose record is mostly play comes first in each (r/ontario for F03 and F05). The rule stays as logged for the remaining subform (F06); the account says so where it bites. D6 may want fit measured on the key's own third-order theme.

What the members showed. P20 is restricted or conditioned in 7 of 12 members: the coders kept the host's play rules and ordinary rules apart from a line around canvas talk. The mean aftermath share, 0.0023, is the lowest of F01's subforms so far. In r/anime_irl the licence let one canvas post through.

Subform candidates. None on keys.

Form test. A grouping, not a form.

D5a-06: F06, the joke kept (8 members, subform of F01)

Arithmetic. Expectations 0 to 0.045; no member is among any arrow's within-case datings; every arrow not-testable-here, every proposition not testable.

An amendment to the representative rule, dated D5a-06, forward only. The three representatives are three different rooms: where the member read at length is already the best or the worst fit, the next by the length rule is read. Logged before it was applied. Here the length rule gave r/runescape, the best fit, then r/kanye, the worst fit, so r/mls was read at length.

The reading. d5a06_F06_reading.json: an outside maker (a game company or another site) asked to keep a joke or make it real 4 members, the sub's own change asked to stay 2, members made it real themselves 2. Each member shows one route; an outcome appears in the quotes of 3.

The name. Kept, read as the members' aim; the subtitle "a request that its change last" holds for every member.

What the members showed. Scripts served building as well as keeping: A06 is restricted in 4 of 8 members and conditioned in one. Workarounds (T4-009) is over-represented, its themes at T3-028 in 4 members. F06 has the largest records (median 308 coded concepts) and the lowest aftermath share (0.0019) of F01's subforms.

F01's subforms, all accounted. F02 to F06 are all groupings. Each is one third-order step of K01, read in members that mostly hold one line on it. Two of five names hold as written (F03, F06), one holds in part (F02), and two have renaming proposals (F04, F05). The steps meet the canvas work in a few members only: r/battlecats and r/bindingofisaac (F02), r/anime_irl (F05). The representative rule's weakness for subforms (fit on Keying) is noted at D5a-05.

Subform candidates. None on keys.

Form test. A grouping, not a form.

D5a-07: F07, the telling clause not shown at the design (59 members, top-level)

Arithmetic. Expectations 0 to 0.335; r/notredame, r/czech and r/unitedkingdom are within-case datings of A14, A17 and A18; every arrow not-testable-here, every proposition not testable.

The reading. d5a07_F07_reading.json: informed members reject the change, so repair enforces a competing design and telling does not settle it, 31 members (20 with no evidence limit in the same line); the record does not show the agreed change, the untold keepers, the failed telling or the loss, 36 (11 of them among the 31); mistaken repair seen in part 7; a welcomed change defended 2; new work before upkeep 1; uncertain keepers hold back 1. The third-order themes do not separate the readings.

A claim the branch bounds: F-025 (findings.jsonl line 43). P05's clause presumes that the keepers would accept a planned change once told. Where informed members reject it, repair is a contest over the design and telling does not end it. It rests on the 20 lines without an evidence limit and on cited words (r/AyyMD, r/katawashoujo, r/megaman, r/fivenightsatfreddys). It changes no word of P05 and does not touch F-024's two routes or the held proposal. r/AyyMD's room model had already asked for "an acceptance condition". For D6: if P05 is amended, this is a third limit beside the two the held proposal names.

A check that removed a relation. A11 (design to template) is restricted in 37 of F07's 59 members against 261 of 646 other rooms, but in 142 of the 230 other rooms of F07's median size or more. The association is the size of the record. The form test stays a grouping.

Renaming proposal, for D6. "Informed members reject the planned change" holds for 31 of 59. Proposed: "the telling clause limited: informed members reject the change, or the record cannot show the clause". Also in defects.jsonl.

A slip. construct_bindings first held A11; the check accepts only construct ids (elements, themes, dimensions). The line was corrected in place before the close.

Subform candidates. None on keys.

Form test. A grouping, not a form, carrying one bound claim.

D5a-08: F08, machine hands kept on one target (50 members, top-level)

Arithmetic. Expectations 0 to 0.284; seven members are within-case datings of arrows (r/mexico, r/wallstreetbets, r/sooners, r/Temple, r/PlaceNL, r/czech, r/rpi); every arrow not-testable-here, every proposition not testable.

The reading. d5a08_F08_reading.json: keeping every runner's target current 24 members, installing and teaching 17, a stale target undoing a planned or friendly change 10, control of the target 6, operators switching off 5, recruiting runners 3, a script that built then kept 2. Installing or keeping the target current: 39 of 50.

For D6, beside F-025 and the held P05 proposal: a machine form of P05's telling clause. In 10 of F08's members a script kept the old form and undid the room's own planned or friendly change until someone updated its target; telling the people did not reach the machine. r/zootopia: "You will need to get him to edit his pattern before you can add this" [zootopia/c0122]; r/AmericanFlaginPlace: "an older version that sleeping people had on and it's conflicting with a newer version" [AmericanFlaginPlace/c0407]. r/zootopia's room model says it in so many words. It is not a finding: it bounds nothing, it adds a route by which the telling must travel. If D6 amends P05, the clause has now four limits or routes: the change read from its shape and informed members holding it (the held proposal), informed members rejecting it (F-025), and the scripts' target (here).

A check that removed a relation. A06 (upkeep before scripts) is restricted in 18 of 50 members; among the other 201 rooms that instantiate P14, 68 restrict it. The restriction follows having scripts, which is the cut.

The name. Kept, as what members tried; "every runner" names an aim the lines never show met.

Subform candidates. None on keys.

Form test. A grouping, not a form.

D5a-09: F09, the move returns to building (54 members, top-level)

Arithmetic. Expectations 0 to 0.306; r/uiuc, r/day9, r/Temple and r/nyjets are within-case datings of arrows; every arrow not-testable-here, every proposition not testable. The branch's own link is not an arrow of the model and has no expectation.

The first form of the stage, in a narrow sense, and why it differs. F01 to F08 each added a step inside one element or restricted one clause, and their parts were shown in subsets of members, so I reported groupings. F09's key is a link between two constructs of canvas organizing, P10 (the move) and P03 (building), and every member's line states that relation; the members' words show it. Constructs, a relation, conditions (a loss or taken spot in 11, a site offered by others in 6) and means (new coordinates in 14) can be written, and the relation is falsifiable by rooms that moved and gave up (F-019). Shared status: supported as a sequence; no cause is claimed, and every local account stays unresolved. The doubts are in the account's section 13: the relation selected the members, the readers wrote similar sentences, and the kept rate may follow from selection.

For D6: the arrow the model lacks. From P10 to P03: after the move, the room builds again at a new site, and members report the new work. It stands on 55 re-check lines in 54 rooms and has no within-case dating, so its order has not been tested against a null. D4 named it at D4a-02. If D6 adds it, the loop the head says is not grounded (loss, move, building) would have its return.

For D5b: survival with a caveat. Work is kept in 35 of 54 members against 53 of 106 rooms of similar size outside the branch that also moved. A room that built again had something to keep, so the difference may be the cut.

A slip, a third time. A bold lead-in in section 12 held the word the close-check reads for section 13 ("after doubt and a loss", from F-019's wording). Found by the heading check before assembly and reworded.

Subform candidates. None on keys.

Form test. A form, narrow: the move-and-rebuild sequence.

D5a-10: F10, a deal carried out as work (38 members, top-level)

Arithmetic. Expectations 0 to 0.216; r/switzerland, r/littlewitchacademia and r/notredame are within-case datings of A04 and A14; every arrow not-testable-here, every proposition not testable.

The reading. d5a10_F10_reading.json: carried out by moving work or changing templates or bot targets 8 members, prepared inside the room 7, terms relayed or the relay failing 7, uneven, conditional or refused bargains 7, a channel or person to deal through 6, terms sought before any loss 4, an appeal or apology turned into accommodation 3. Four members show two parts; one (r/earthbound) shows two of the three steps the name gives.

Renaming proposal, for D6. "A deal carried out as work: prepared in the room, then implemented and relayed" names three steps never shown together. Proposed: "the deal's work: preparing, carrying out and relaying the terms, or bargaining from weakness". Also in defects.jsonl.

The telling problem between rooms. Relaying a deal's terms to the room's own placers is the P05 clause carried across rooms. P21 (no one binds every placer) is absent in 24 of 38 members; these rooms worked at reaching placers instead of only saying they could not. For D6 beside F-025 and F08's machine form, with one limit: r/buffalobills' room model says the record does not show whether the placers who pushed past its deal had heard of it.

A correction made before the close. I first wrote that the night crew had not heard of r/buffalobills' deal; the room model is right that the record does not say so, and the account now says no more.

Size does not drive this branch. The median member has 93 coded concepts, below the population's 101, the first branch so far below it.

Subform candidates. None on keys.

Form test. A grouping, not a form (a step inside P08, its parts in subsets).

D5a-11: F11, carrying on as renewed work, begun before the close (43 members, top-level, subforms F12 to F14)

Arithmetic. Expectations 0 to 0.244; r/touhou (A07) and r/naruto (A13, A19) are within-case datings; every arrow not-testable-here, every proposition not testable.

The reading. d5a11_F11_reading.json: another canvas 20 members, other media or personal use 10, questioned, objected to or declined 10, adopted into the room or its source 7, attack, loss or defence again on the new canvas 7, damage kept in the emblem 3, keepsakes sold and contested 3, venue or ties kept or proposed 2, the shared act sought in another form 2. 21 members show two. Dated by the earliest hour each key line cites, 11 of 43 begin before placement stopped at hour 73.

Renaming proposal, for D6. "Begun before the close" holds for 11 of 43 members; it names the coders' contrast with P13's wording ("near the close and after it"). Proposed: "carrying on as new work: on another canvas, in other media or in the room's emblems; begun before the close in a quarter of the members". Also in defects.jsonl.

For D6: A09's wording. 15 of 43 members restrict A09 (recording before carrying on), against 37 of 240 rooms of 144 coded concepts or more. Of the 12 shared restrict lines, 6 say carrying on came first or needed no record, and 6 deny that the record caused it, which A09 does not claim. The account's prose ("carries the record on into banners, later canvases ...") may invite the causal reading. A wording item, beside the arrows' wording items held from D3c.

F11 and F23 may be one set of events read with two ops. Both change P13 at T4-028; F11 adds a step, F23 a condition (the close scoped to the original canvas). r/greenlattice's F11 line states F23's condition, and r/greenlattice is not in F23. For D6, beside D4a-04's finding that branches meeting at one node are groupings.

The theme check mattered here. r/theblackvoid holds 17 per cent of the branch's coded concepts and carries both non-key theme excesses (Neo-tribes, Repertoire of contention) alone. The rule as logged reports them; the account says whose they are. For D5b and D6: pooled shares let one large room speak for a branch.

Corrections made to fit the room models. r/miraculousladybug's ties were proposed, not shown to last; r/warriors', r/naruto's and r/cgpgrey's invitations to other canvases are not shown followed. The reading's label now says "kept, or proposed", and the account counts carrying on proposed or begun.

Size. Median 144 coded concepts against 101; rates compared within size (A09, P05, P22, propose lines). The first branch whose median organizing end (73.48) is past the close.

Subform candidates. None on keys; D4 already cut the three kinds of carrying on with 7 members or more.

Form test. A grouping, not a form (a step inside P13, its kinds in subsets).

D5a-12: F12, the spine restarted on another canvas (22 members, subform of F11)

Arithmetic. Expectations 0 to 0.125; r/naruto is a within-case dating of A13 and A19; every arrow not-testable-here, every proposition not testable. The spine's own arrows (A01 to A03) expect 0.062 each.

A rule for section 7, dated D5a-12, forward only. The one relationship is the arrow whose restrict rate among the members most exceeds its rate among rooms outside the branch with at least the branch's median coded concepts, particular lines included. For F12 it is A09 (9 of 22 against 48 of 306), as in F11, where my reading had chosen it.

The reading. d5a12_F12_reading.json: built again 11 members, called 9, venue named or weighed 7, attack, loss or defence again 7, questioned or declined 5, another shared act instead of a canvas 2. Of the four parts of the restart, 3 members show three and none shows four. 3 of 22 lines begin before the close.

Renaming proposal, for D6. "The spine restarted on another canvas" names a restart no member's line shows whole. Proposed: "the work taken to another canvas: weighing the copies, calling, building and defending again, rarely all in one room". Also in defects.jsonl.

A placement question, for D6 and E1. T3-054 (another canvas) holds r/forsen's song and r/polska's day of memes, which seek a new shared act, not a canvas. The third-order theme lumps two things; the subform inherits the lump. Also in defects.jsonl.

For D6: the choice of a copy. The model has no element for choosing among several copies of the canvas by where others will go, or for judging them by the first canvas's rules. P27 (choosing a spot before any loss) is instantiated in 13 of 22, against 240 of 306 rooms of this size; P10 (moving after a loss) is absent in 11, against 115. The place-finding work moved off the canvas.

The theme check, again. r/theblackvoid and r/greenlattice hold 53 per cent of the branch's coded concepts. The rule's excesses on Repertoire of contention and Backstage decision-making are r/theblackvoid's; three under-represented themes are the two rooms' effect. Territoriality and Transition stand without them. For D5b and D6: in a small branch, one or two large records can set its theme profile.

Corrections made to fit the room models. r/Mario's and r/naruto's calls to a copy are not shown followed; the account counts calls made and work begun.

Subform candidates. None on keys.

Form test. A grouping, not a form (a step inside P13 at one third-order theme, its parts in subsets).

D5a-13: F13, the work remade in other media, often before the close (9 members, subform of F11)

Arithmetic. Expectations 0 to 0.051; r/touhou is a within-case dating of A07; every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A09 again (4 of 9 against 23 of 131). Two restrict lines say the remake came before the record, two that no record caused it. The order turns on when the remaking began: r/lego's wish and the three early copies of a room's mark came before the record; r/globaloffensive's skin of the finished canvas came after it.

The reading. d5a13_F13_reading.json, corrected before use to fit r/romania's room model (its vampire copied in beads and a vector file beside a new app): new work 4 members, the room's mark remade 4, the whole canvas 2, others join in or ask 5, one member's act 4, cost, copyright or credit 3. The 3 lines dated before the close are each one member's copy of the room's mark.

Renaming proposal, for D6. "Often before the close" holds for 3 of 9, and "the work remade" for 6 of 9. Proposed: "the event carried into other media: a member's copy of the mark, new work made from it, or the whole canvas proposed as a keepsake". Also in defects.jsonl.

For D6: whose work a copy copies. P13 says nothing of authorship once the work leaves the canvas. A copy of the whole canvas held other rooms' work and companies' logos; a claim of inspiration was challenged; a member asked leave to post new work. This is the four-problem remainder of the branch; the mapping is empty.

The theme check, again. r/globaloffensive holds a third of the branch's coded concepts and 601 of its 792 on Keying (the sub's own April Fools change). Without it, Direct information sharing and Transition stay over, Keying falls to 0.49, and four themes leave the under list. With Keying left out, Completion ritual and Boundary work join the over list. Territoriality is under here and over in F12, the clearest contrast between the two subforms.

Size. With 9 members, one room moves a rate by 11 points; the account reports only large differences. The canvas median area is at the 100th percentile.

Subform candidates. None on keys; each medium is a particular of one history.

Form test. A grouping, not a form (a change inside P13 at one third-order theme; members split by what was remade and who acted).

D5a-14: F14, the mark adopted as the room's emblem while it is still placed, damage included (7 members, subform of F11)

Arithmetic. Expectations 0 to 0.040; no member is a within-case dating; every arrow not-testable-here, every proposition not testable.

An amendment to the section 7 rule, dated D5a-14, forward only. Where no arrow's restrict excess reaches one member's share of the branch (1/n), the account says that by the rule's measure no relation runs differently, and describes the arrow with the largest excess as description only. In F14 (one member 0.143) the largest excess is A16's (0.125), so the account says so and describes A16.

A09 where the record is the emblem. A09 is instantiated in 4 of F14's 7 members (restricted in 2), against 5 of F11's 43, 1 of F12's 22 and none of F13's 9. Where the thing carried on is a screenshot made into the sub's picture or flair, the record comes first. For D6, beside D5a-11's wording item: A09 holds when what is carried on is the record itself.

The reading. d5a14_F14_reading.json: the sub's face 4 members, flair 2, damage kept 3, the image corrected first 2, beyond the sub 2, a member's own use 1, carried out in the record 3. The three early adoptions (r/texans, r/anaheimducks, r/pitt) are not the three that kept damage (r/cgpgrey, r/gatech, r/feedthebeast).

Renaming proposal, for D6. The name joins two clauses no member's line shows together. Proposed: "the mark taken into the room's emblems: early, from a picture taken while the work was still placed, in 3 of 7; with its final damage kept in 3". Also in defects.jsonl.

For D6: kept damage, beside P26 and P05. In three rooms the final damage became part of the emblem once the canvas was locked: the red dot made "official", a typo made the room's joke, a white pixel judged mild and a plan to change the game's own icon to match. P26 covers the jokes; P05 says repair restores the form the keepers know. Here the keepers chose the damaged form as the one to know. A particular of three histories, not a subform.

Size. With 7 members, one room is 14 per cent of the branch; no room holds more than a fifth of its coded concepts, so no check beside the theme rule was needed. The first branch whose median organizing end (70.59) comes before the close; aftermath share 0.009.

Subform candidates. None on keys.

Form test. A grouping, not a form (a change inside P13 at one third-order theme; early adoption and kept damage in different members).

F11's subforms, all accounted. F12 (another canvas, 22), F13 (other media, 9) and F14 (the room's emblems, 7) are all groupings. F11's, F13's and F14's names fail on their timing clauses (before the close in 11 of 43, 3 of 9 and 3 of 7 key lines); F12's fails on the spine, which no member's line shows whole. A09 runs differently in all three, and in opposite directions: restricted where the work went to a copy or a new medium, instantiated where the record itself became the emblem.

D5a-15: F15, the plan kept current: correcting, updating and re-circulating the template (42 members, top-level)

Arithmetic. Expectations 0 to 0.238; r/udub (A11), r/littlewitchacademia (A14), r/nyjets (A16) and r/criticalrole (A19) are within-case datings; every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A11 (29 of 42 against 211 of 386; one member 0.024). The restrict lines say a posted template settles the design only as far as placers receive and follow the current version. r/udub, the account's quoted example for A11 and one of its two within-case datings, restricts it in its own line. For D6, beside the held A11 proposal: F15 is where the proposal's reason is plainest.

The reading. d5a15_F15_reading.json: a revision put before placers 14 members, findable and usable 11, the plan follows the work 6, the reference kept 5, a revision undone by uninformed keepers 5, placers messaged by hand 4, tools 4, errors in the reference 3, kept open 2. 33 members show one kind; 22 keep the plan current in some sense.

Renaming proposal, for D6. "Kept current" holds for 22 of 42; in 11 the work was making the plan usable and in 5 keeping a plan at all. Proposed: "the plan kept current and usable: correcting it, relaying revisions to placers, and making it findable". Also in defects.jsonl.

For D6: the telling clause carried through the plan. Five members report keepers who restored an old form because they had not seen the revision; four message placers by hand. This is P05's clause (F-024's scope) at work through P04. r/philippines' room model proposes the local link "a plan decided elsewhere must reach the people maintaining the visible version", across P23, P04 and P05. Beside F-025 (informed rejection), F08's machine form and F10's telling between rooms, this is the fourth form of the telling problem the stage has met: inside one room, carried by the template.

For D6: the plan follows the work. In 6 members the reference was corrected against placements, recovered from work under way, or ratified after building. P04 runs from template to placements; here it ran the other way. A reading, not a key; D6 may look for it in the keys.

Rooms with little beside the work. K01, P20, P31 and P13 are absent far more often than in rooms of this size (25, 24, 22 and 26 of 42 against 99, 98, 70 and 156 of 386), and propose lines are in 7 of 42 against 177 of 386. The median member has 86 coded concepts, below the population's.

The theme check. r/placestart carries the excess on Live and let live alone (0.81 without it).

A slip caught before assembly. A quote named the canvas's sub with a capital P, which the room-name check refuses; replaced by a paraphrase.

Subform candidates. None on keys.

Form test. A grouping, not a form (a step inside P04; the revision, relay and repair together in 3 members).

D5a-16: F16, the chat kept open: invitations renewed, entrants screened, outcomes relayed to the thread (35 members, top-level)

Arithmetic. Expectations 0 to 0.199; r/lakers (A08) and r/pcmasterrace (A12) are within-case datings; every arrow not-testable-here, every proposition not testable. No arrow touches P23.

Section 7 by the amended rule (D5a-14). The largest restrict excess is A07's (0.014), under one member's share (0.029): by the rule's measure no relationship runs differently. A07 described as description only (a celebration before the work was done, then a correction).

The reading. d5a16_F16_reading.json: an expired or broken invitation replaced 15 members, decisions carried between chat and thread 11, entry controlled 5, the chat named as where the plan lives 4, a way kept open for those outside 4. 31 members show one kind; none shows renewal, screening and relaying together.

Renaming proposal, for D6. The name lists three kinds of upkeep that no member shows together, and "kept open" sits badly beside screening. Proposed: "the chat's access kept up: invitations renewed, entry controlled, decisions carried back, each in different rooms". Also in defects.jsonl.

For D6: three ops on one node. F16 (add-step), F29 (add-condition) and F30 (restrict) all change P23 at T3-014. F16 shares 6 rooms with F30 and 3 with F29. As with F11 and F23, the branches may be one set of records read with three ops.

For D6: host containment and the move to a chat. P20 is absent in 18 of 35 members against 40 of 272 rooms this size, and K01 in 18 against 42. r/de's room model names the local dependence the model lacks: the host sub contained canvas talk ("we just want to avoid being drowned") and the detail moved to other venues. Untested for order; a candidate link between P20 and P23.

For D6: what the record cannot see. No member's record shows a decision made inside a chat; the room models say so (r/pcmasterrace, r/ik_ihe). The branch is cut on what a thread shows of a chat. r/pcmasterrace's model also warns that the coders' chat theme holds phone-placing instructions that fit P24.

For D6: entry control. Five members screened applicants, kept links private, divided channels by role, or banned a member; P33 (secrecy against rivals) is not coded for it. A reading, not a key.

The theme checks. r/de carries the excess on Sensemaking alone (0.96 without it); the template theme falls under the rule without r/lakers (1.38).

Tie rule, read as the scripts read it. Alphabetical order in the tie rule ignores case, as the scripts sort (r/de before r/OrderOfTheKoi).

Subform candidates. None on keys.

Form test. A grouping, not a form (a step inside P23, a candidate; its kinds of upkeep in different members).

D5a-17: F17, the marking provisional and contested: success judged and credit disputed while the work goes on (36 members, top-level, subforms F18 and F19)

Arithmetic. Expectations 0 to 0.204; r/weezer is a within-case dating of A13; every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A20 (11 of 36 against 73 of 329; excess 0.084). Every restrict line denies that a flood of calls caused the host's line; in these rooms the line was the sub's standing rules (a spoiler-tag removal, full sticky slots, a low-effort rule). P20 is instantiated in 14 of 36 against 220 of 329.

For D6: the coders read causes into arrows of order. A09 (F11 to F13) and A20 (F17) state orders. Their restrict lines in these branches mostly deny causes the arrows do not state: a record causing the carrying on, a flood causing the host's line. A20's own list names "an objection to the flood" among the host's lines, which may invite the reading. A wording item beside the arrows' wording items held from D3c.

The reading. d5a17_F17_reading.json: credit claimed, contested or corrected 14 members, success judged 9, the marking provisional 9, helpers recognised 7, machine hands in the credit 3, the post kept in order 1. 29 members show one kind. By date 23 of 36 lines begin before the close; 10 of the 14 on credit.

The name, kept. Its main clause holds for 31 of 36 members and its timing clause for 23. No renaming proposal.

For D6: credit as reward, with F-016's limit. The branch binds reward in the sense of credit's distribution: who was involved, which sub may claim the work, people or scripts. Whether credit moved anyone to place is not tested (F-016). The remainder: success had no given test and was argued after the fact.

For D6: F17 beside F32. The nine provisional markings (celebration followed by more work or defence) are F32's link from the marking back to keeping, read from P11's side; r/ripcity is in both.

A refused command. A piped pair of python calls was refused; out/_analysis/d5_branch_misc.py now prints a branch's propose lines, one arrow's member lines and the account's sentence on it.

Subform candidates. None on keys beyond F18 and F19.

Form test. A grouping, not a form (a step inside P11; its kinds in different members, two of them cut as subforms).

D5a-18: F18, success judged while upkeep continues (15 members, subform of F17)

Arithmetic. Expectations 0 to 0.085; r/weezer is a within-case dating of A13; every arrow not-testable-here, every proposition not testable.

Section 7 by the amended rule. A03 (3 of 15 against 24 of 292; excess 0.118, above one member's 0.067; A10 next at 0.112). The restrict lines say keeping began before the work was done; in F18 keeping runs on both sides of the finish. A03 is instantiated in 6 of 15 against 149 of 292.

The reading. d5a18_F18_reading.json: success judged 7 members, upkeep or more work after "done" 5, labour weighed 2, machine hands weighed 2, the name or post corrected 2. Both of the name's clauses in one member (r/bostonceltics). Of the 7 judging success, 4 begin after the close.

Renaming proposal, for D6. "While upkeep continues" does not date the judging, and the two clauses fall in different members. Proposed: "success judged and the finish reopened: judged by what survived, often at the close, or a 'done' followed by more work". Also in defects.jsonl.

For D6: who decides that a work is up. P11 marks a work "when a work is up". The members show no given test: survival, recognizability, a place on the final canvas, damage as style, effort without a result; one judgment revised within four minutes. The same remainder as F17's.

For D6: the return from celebration to upkeep, again. r/ripcity's room model proposes "returning from celebration to upkeep", F32's link read from P11's side, in five F18 members.

The theme checks. Direct information sharing is r/flyers' record; Completion ritual falls to 1.48 without r/weezer. Repair work is under-represented in a branch named for upkeep, and stays under without its largest contributor.

Representatives. r/ripcity is both the member read at length and the either-way room; the tie rule has no pass-over.

Subform candidates. None on keys.

Form test. A grouping, not a form (a step inside P11 at one third-order theme; its two clauses in different members).

D5a-19: F19, credit contested during the work (14 members, subform of F17)

Arithmetic. Expectations 0 to 0.079; no member is a within-case dating; every arrow not-testable-here, every proposition not testable.

Section 7 by the amended rule (D5a-14). The largest restrict excess is A20's (0.065), under one member's share (0.071): by the rule's measure no relationship runs differently. A20 described as description only (the host's line was the sub's standing rules, here inside a credit dispute in r/anime).

The reading. d5a19_F19_reading.json: who made the work disputed 8 members, a claimant's standing checked 3, a list of helpers corrected 3, an attempt credited 2, a reward or proof with the credit 2. 9 contest credit, 7 of them before the close; 5 credit without a dispute.

Renaming proposal, for D6. The contest falls during the work in half the members, and five members credit without contest. Proposed: "credit claimed, checked and corrected: makers disputed, claimants checked, lists of helpers mended, mostly while the work stood". Also in defects.jsonl.

For D6: links the room models name. r/Okami's: credit "explicitly justifies protecting the helper's separate logo, a dependence the standing arrows do not state" (P11 to P07). r/anime's: "checking the collective entitled to claim a picture" as a local step. r/wine's: keeping a mark must be separated from claiming it.

For D6: credit draws the collective's edge. The four-problem remainder: with no roll of members, claims to credit decided who belonged to the "we" that made the work (an hour-old account, a nationality, a political sub, specialists beside a host).

Within size. P31 (whether covering others' work is fair) absent in 9 of 14 against 72 of 389; K01 in 9 against 99; P20 in 7 against 99. Rivalry and Repertoire of contention nearly vanish from these records.

F17's subforms, both accounted. F18 (success judged, 15) and F19 (credit, 14) are groupings. F18's name fails on its timing clause; F19's on its timing and on the five members who credit without dispute. F17's own name was kept.

Subform candidates. None on keys.

Form test. A grouping, not a form (a step inside P11 at one third-order theme; claim, contest and settlement together only in r/Okami).

D5a-20: F20, the close as news: late arrivals told that placement has ended (10 members, top-level)

Arithmetic. Expectations 0 to 0.057. Two members are within-case datings, one room each: r/sips of A02 and r/stlouis of A15. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A08 (6 of 10 against 127 of 391; excess 0.275, above one member's 0.1; A20 next at 0.18). Four restrict lines say the marking and the record came together in one post at the close, or the record came first. Two (r/canucks, r/hatsune) restrict a cause the connection does not state, as at A09 and A20. Part of the excess may restate the cut: A08's restrict lines fall on P12, the element the key changes.

The reading. d5a20_F20_reading.json, revised once before use (r/eder carries L only): news answering a stale call, offer or promise 5 members, learned late or sorry to have missed the event 3, relief, fatigue and pride 2, advice or a request closed by the end 2, a version shown without its damage 1. The end reached a member as news in 7; in 3 no one learns of it. 7 of 11 lines begin within an hour of the close.

Renaming proposal, for D6. "Late arrivals" holds in 3 members; most stale acts came in the first hour from members still at work. Proposed: "the close as news: calls, offers and requests made after placement stopped, and members telling each other it was over". Also in defects.jsonl.

For D6: the telling clause at the close. Members learned of the close by being told or by reading it, and until then they called, offered and kept. P05's telling clause says the same of a planned change. r/hatsune's room model: "correcting a stale build plan remains a finer step inside ending"; r/stlouis's: "willingness to help can persist after the capability disappears". A candidate for P12's statement, beside the held P05 proposal; no change here.

For D6: the end of a clock the rooms did not set. The four-problem remainder: the site stopped placement for everyone at once, and members told each other, some within minutes and some after a working day.

The theme check. r/Rainbow6 holds 43 per cent of the branch's coded concepts and 70 per cent of its Keying. Without it, Frame bridging and Mobilization leave the over list and Keying joins the under list. r/Rainbow6 is in the branch by the theme (a cleaned picture), not by the news; its room model agrees.

Within size. The members are of two sizes (five below 90 coded concepts, three below 20), so absences compare weakly. P31 absent in 6 against 73 of 391; K06 in 7 against 122; P21 in 9 against 206; P10 in 7 against 151; P13 in 7 against 154 (instantiated in 2 against 225). Transition is in no member.

Representatives. Best fit r/Rainbow6 by the D5a-03 fallback (two members compose; r/hatsune holds two key lines but composes with residue); worst fit r/stlouis, whose one key line is the plainest case of the step; at length r/hatsune, where the stale plan came from the room's own contact. Either way: r/sips (a script posted in the last hour; a member's regret at missing the event).

Subform candidates. None on keys.

Form test. A grouping, not a form (a step inside P12 at one third-order theme; stale act, news and acceptance together in 5 members; 3 show no news).

D5a-21: F21, the canvas call not a joke: the April Fools frame kept apart from the canvas work (32 members, top-level)

A helper, written this leg. out/_analysis/d5_within.py computes the within-size pool, the section 7 rule, absences and the nearest-branch tie as the earlier inline scripts did; run on F20 it reproduces F20's figures. No rule changes.

Arithmetic. Expectations 0 to 0.182. Three members are within-case datings, one room each: r/sips of A02, r/titanfall of A08, r/pcmasterrace of A12. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A08 again (17 of 32 against 93 of 297; excess 0.218, above one member's 0.031; A02 next at 0.15). By my reading 7 restrict lines are on the order and 10 on a cause the connection does not state. r/titanfall, one of A08's two within-case datings, restricts A08 in its own line, and the arrow's audit already marks that dating as failing (the record came first). For D6, beside A08's bound: the late-side record-first scope may reach its datings.

The reading. d5a21_F21_reading.json: the canvas calls not shown to be jokes 14 members; less of the joke than K01 names 14; a claim's truth or authorship open 6; styling narrowed 5; the joke made outside the room 5; the joke's day bounded 3; the joke reaching the work 1 (r/osu). 18 of 32 lines do not speak of the canvas.

Renaming proposal, for D6. Proposed: "the April Fools frame narrowed: less of the joke than the model names, and the canvas calls not shown to be jokes". Also in defects.jsonl.

For D6: K01's one-day licence has its own clock. Members set where April Fools ended: by a time zone (r/warframe), by noon (r/southafrica), by 2 April (r/twitch), or by a free weekend that ran before the day (r/titanfall). K01 says "the one-day licence" and leaves its edge unstated.

For D6: r/osu's qualification. Its room model: "The model's isolation of host play needs a local qualification". The sub's own April Fools swap sent helpers to the wrong sub and moved coordination to a chat. A link from K01 to P01 and P23 the model does not state.

For D6 and E1: branches cut on restrict keys may sort coders. F21's members carry 10.9 restrict lines a room (14.6 per cent of their lines) against 8.1 (11.0) in rooms of their size; F30, the nearest branch and also a restrict key, 13.4 (17.2) against 7.9 (10.8); F20 and F07 sit at their pools' rates. F21's members restrict K01 (32 against 9), P05 (27 against 182; 25 of them on the telling clause not shown) and A08 (17 against 93) together. Four of F21's five nearest branches are cut on restrict keys. A check for D6: the restrict-line rate of each restrict-keyed branch against its pool, before any is read as a form of organizing.

The theme check. r/pcmasterrace holds 20 per cent of the branch's coded concepts; without it Rivalry and Visibility returns leave the under list and Keying falls to 0.98. No theme is over-represented; Keying, the key's theme, is at 1.21.

Within size. These rooms attack and deal less often than rooms of their size: P09 instantiated in 18 of 32 against 277 of 297; P08 in 24 against 278; P18 absent in 11 against 31.

Representatives. Best fit r/warframe by the D5a-03 fallback (r/picturegame's share is higher, but it does not compose); worst fit r/Fez, the one member whose joke and call share a thread; at length r/patriots (r/pcmasterrace passed over, read at length at D5a-16). Either way: r/chile (no other branch; before r/scp by the alphabet).

The uncomposed room. r/picturegame, the only room the first return judged not to compose, sits in F21 (and F25). Its room model finds no canvas construction in its coded record; its key line narrows prank styling.

Subform candidates. None on keys.

Form test. A grouping, not a form (a restriction of K01 at one fourth-order theme; the name's relations in fewer than half the lines; r/osu shows the opposite).

D5a-22: F22, help conditional on the helper's own work and spare hands (30 members, top-level)

The helper. d5_within.py now also prints the restrict-rate check logged at D5a-21; it reproduces F21's figures.

Arithmetic. Expectations 0 to 0.170. Two members are within-case datings, each of two arrows: r/ubc of A05 and A06, r/PlaceNL of A16 and A17. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A03 (4 of 30 against 25 of 318; excess 0.055, above one member's 0.033; A09 next at 0.033). The restrict lines say keeping began before building was done; 11 members instantiate the order. Beside the key: the helper's first task, its own work, had no clear end.

The reading. d5a22_F22_reading.json: the helper's own work first 13 members; terms between rooms 7; spare capacity 6; delivery or decision left open, or refused 6; a tie as the reason 3; a recognisable form 3; the clock 2. The name's two clauses in 15 of 30.

Renaming proposal, for D6. Proposed: "help on conditions: the helper's own work first, spare hands, and the terms between rooms". Also in defects.jsonl.

For D6: P16's conditions, named by the room models. r/smite's: "P16 still needs a local condition" (help withdrawn over a border, with a promise to return). r/OnePiece's: "Retain own-image priority and learning the allied design as explicit aid conditions". An order of tasks the model lacks: the room's own mark first, a neighbour's work second (P05 or P03 to P16, in 13 members by my reading; not a key).

For D6: recognising the form, in help and in keeping. r/simonfraser's help was undone because it looked like vandalism; r/OnePiece's keepers fought their own jaw fix for the same reason (its F27 line). P05's "form the keepers know" and a helper's need for the allied picture may be one condition: the placer must know the form.

The restrict-rate check. F22's members restrict less than rooms of their size (6.3 lines a room, 8.5 per cent, against 8.2 and 11.2). The D5a-21 worry does not reach this branch, cut on an add-condition key.

The theme checks. No record carries the branch, but Attribution is r/smite's (0.83 without it) and Transition largely r/maryland's (1.16 without it; 1.47 with Keying left out). Reciprocity holds without either.

Within size. Members' records range from 20 to 435 coded concepts, so absences compare weakly. P23 instantiated in 19 of 30 against 260 of 318, P26 in 22 against 295, P18 in 16 against 243; P17 at the pool's rate. Backstage decision-making and Meta-organization under-represented: help arranged room to room in the threads.

Representatives. Best fit r/egypt by the D5a-03 fallback, a room that turned the requests away (the condition was the askers' argument); worst fit r/smite; at length r/OnePiece, also the either-way room (the most lines on both keys; no pass-over in the tie rule).

Held. r/maryland is among the P05 proposal's rooms (informed members hold it); r/wine among the A11 proposal's talk-only rooms.

Subform candidates. None on keys.

Form test. A grouping, not a form (a condition in every line, but not the same condition; the own-work relation in 13 of 30).

D5a-23: F23, the close scoped to the original canvas: continuation renewed, uncertain and contested (30 members, top-level)

Arithmetic. Expectations 0 to 0.170. Four members are within-case datings: r/DestinyTheGame of A04 and A12, r/TheFarLeftSide of A06, r/touhou of A07, r/naruto of A13 and A19. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A09 (12 of 30 against 38 of 239; excess 0.241, above one member's 0.033; A19 next at 0.099), the fourth branch on P13 where A09 runs differently (F11, F12, F13, F23). By my reading 3 restrict lines on order, 8 on a cause, 1 on deployment. For D6, beside A09's bound ("Where a room planned its next canvas or its emblem while still building"): r/enterthegungeon adds a case the bound does not name, a wish to reuse that fetched the record after the close.

The reading. d5a23_F23_reading.json: one member's attempt, a call or an invitation, uptake open 12 members; a proposal to keep the mark at home or beyond, not shown done 7; the stop bound only the original canvas 6; contested 4; conditioned on upkeep, access or the site 4; the room kept with rules or goals 2. By the cited passages, starts on another canvas in 14 members, calls only in 5; r/greyblob and r/thebluecorner began on another canvas at hour 39.

The name kept. "Uncertain" echoes the coders' "remains unresolved", but members said it too ("I am alone in making it", "Should we do it again?"). Its limit: 7 members continue at home, not on a new canvas.

Subform candidate on keys, for D4 or D6. add-condition on P13 at T3-054 holds 23 lines in 23 rooms, all F23 members, mirroring F12 inside F11. Also in defects.jsonl.

For D6: the carrying-on family and the op. F11 (add-step), F23 (add-condition) and F25 (restrict) are keyed on P13 at T4-028; F11 and F23 share 7 rooms. Which branch a room joined may turn on the op a coder chose for the same kind of passage. A check for D6: read the shared rooms' lines on both keys side by side.

For D6: a group outliving its task. The four-problem remainder: rooms formed for the canvas asked whether to last (r/greyblob), set goals and deadlines (r/TheFarLeftSide), set content rules and a moderation team (r/loliconsunite), or closed and reopened on a new canvas (r/purplecorner). P28 instantiated in 11 of 30 against 31 of 239.

For D6: the close as a scope. The model places the close at hour 73 for every room. Members placed again on copies of the canvas from hour 39 on; the stop ended one site, not the work. With F20 (the close as news), the close is learned and it is local.

The theme checks. r/thebluecorner holds 15 per cent of the branch's coded concepts; five of six excesses rest on one room each (Neo-tribes, Meta-organization, Backstage decision-making on r/thebluecorner; Symbolic boundaries on r/india; Decided order on r/touhou). Only Transition, the key's theme, survives.

Survival. Median organizing end 80.7, aftermath 0.0702 (the highest so far), kept 17, lost 12, silent 1; with F12 (80.76), one of two branches whose organizing ran well past the close. It restates the cut. A claim that F23 was the first such branch was caught by script before assembly.

Representatives. Best fit r/greyblob by the D5a-03 fallback; worst fit r/india (a large record; the continuation three posts by one member); at length r/enterthegungeon (two key lines). Either way: r/cgpgrey (F11 and F23; one other branch, F14).

Held. No member among the P05 proposal's rooms; r/placeDE among the A11 proposal's talk-only rooms.

Form test. A grouping, not a form (the condition holds where members went on elsewhere; a start, uptake and an outcome together in few).

D5a-24: F24, machine hands debated, not shown placing (27 members, top-level)

A helper, written this leg. out/_analysis/d5_heading_check.py checks the parts' section order reading the whole of each bold-led line, as validate.py does for the word that broke F23. It is stricter than validate.py (it flags a 'one relationship' inside a closed F22 paragraph that validated clean), so its flags are read, not obeyed.

Arithmetic. Expectations 0 to 0.153. One member is a within-case dating: r/sips of A02. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A04 (13 of 27 against 67 of 248; excess 0.211; A06, the arrow into P14, next at 0.145). The restrict lines say border talk came before keeping, during building or before it, the path A04's bound and C5's reading of 40 rooms already name.

The reading. d5a24_F24_reading.json: a script offered, prepared or explained, not shown run 14 members; argued over 8; attributed to others 7; extra accounts or a timer bypass 4; refused or set aside 4. Members of about five rooms claim placing beyond one pixel; three scripts were published in the last hour (r/sips, r/rutgers, r/OKState).

Renaming proposal, for D6. Proposed: "machine hands offered, refused and argued over: handmade work claimed as merit, placing by script claimed but unverified". Also in defects.jsonl.

For D6: P14's two evidence states. The key lines restrict P14 in all 27 members; the same members' other lines instantiate it in 11. r/uoft's room model keeps the two apart: a member's report of extra accounts counts as reported use, a posted script does not count as placing. P14's statement could say which it claims.

For D6: a norm of means without enforcement. The four-problem remainder: placing by hand held as the event's point ("against the spirit of /r/place", "raw manpower", "made it by hand, as a community"), used to judge other rooms and to lose interest, with no rule and no way to compel anyone. A06's mechanism names strain as the cause of scripts; r/dallasstars adds bodily pain, and several rooms refused scripts under strain.

For D6 and E1: restrict-keyed branches, again. F24's members carry 10.5 restrict lines a room (14.2 per cent) against 8.2 (11.1) in rooms of their size, and restrict P05 in 23 of 27 against 152 of 248. F24 is the third restrict-keyed branch to show the excess (F21, F30, F24); F22 (add-condition) and F23 (add-condition) sit at or below their pools. The three nearest branches (F31, F30, F27) are restrict-keyed too.

The theme checks. r/prequelmemes holds 17 per cent of the branch's coded concepts; Completion ritual and Transition rest on it, and both fall under the bar with Keying left out. Only Workarounds, the key's theme, holds under every check.

Within size. P10 instantiated in 6 of 27 against 119 of 248; P20 in 12 against 180; K01 in 15 against 199; P31 in 17 against 209.

Representatives. Best fit r/OKState by the D5a-03 fallback (a bot prepared, tested and published, the close first); worst fit r/prequelmemes; at length r/belgium (the length rule gave r/prequelmemes, already the worst fit; by the D5a-06 amendment the next). Either way: r/uoft (F24 and F31; no other branch).

The slips of this leg. A quote check ran in the same turn as its Write; a log line said 0 errors before the validate output was read (it was 1, the expected missing branches-D5 line). Both logged with corrections.

Subform candidates. None on keys.

Form test. A grouping, not a form (adoption and its effect shown in no member by the key's own standard).

D5a-25: F25, carrying on in talk: proposals and single attempts, not shown taken up (27 members, top-level)

Arithmetic. Expectations 0 to 0.153. Five members are within-case datings: r/pcmasterrace of A12, r/Temple of A15 and A16, r/PlaceNL of A16 and A17, r/czech of A17, r/corridor of A19. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A09 (13 of 27 against 25 of 175; excess 0.339, the largest since the rule was logged; A19 and A08 next at 0.256). A09 now runs differently in five of the six branches keyed on P13 (F11, F12, F13, F23, F25; not F14). By my reading 3 order lines, 9 on a cause, 1 another route. For D6: A09's connection is an order, its mechanism a cause; across the five branches the restrict lines keep the order and drop the cause, and the order exceptions fall inside its bound.

The reading. d5a25_F25_reading.json: one member's start or a call, uptake not shown 17 members; begun during live placement 8; an emblem, flair or emoji proposed 4; contested 2; ties beyond the canvas 2; one each for a record not a remaking, the stop scoped to the original canvas, plans for next time. Six rooms' members report placing elsewhere, mostly alone; none shows a room moving together.

The name kept, with two limits: "in talk" understates six rooms that placed elsewhere, and the name drops D4's own clause on reuse during live placement.

Subform candidate on keys, for D4 or D6. restrict on P13 at T3-054 holds 17 lines in 17 rooms, all F25 members. With F23's add-condition at the same node (23 rooms) and F12's add-step inside F11 (22), the family "Carrying on" has three keys at T3-054 under three ops. Also in defects.jsonl.

For D6: the family's ops. F23 and F25 hold the same commonest reading (one member's start or a call, uptake open) under add-condition and restrict. F25's members restrict 12.9 lines a room against 7.9 (16.7 per cent against 10.8); F23's sit at their pool. Read the shared kind of passage in both branches side by side before any cut. What the ops do not explain: F23's members organized far past the close (median end 80.7, aftermath 0.0702), F25's did not (72.91, 0.0271).

For D6: P13's timing. Four room models (r/gorillaz, r/kirby, r/picturegame, r/starcitizen) and eight members' lines put carrying on during the work; P13 says "Near the close and after it". F11's name already says "begun before the close".

The theme checks. r/thebluecorner holds 17 per cent of the branch's coded concepts and carries three of the four excesses (Mobilization, Backstage decision-making, Meta-organization), as in F23; only Transition, the key's theme, survives.

The restrict-rate check. F25 is the fourth restrict-keyed branch above its pool and the highest among those accounted; F30 (computed at D5a-21, not yet accounted) is higher still (13.4 against 7.9). Two over-claims ("the highest so far"; "five P13 branches") were caught by script before assembly.

Representatives. Best fit r/gorillaz (composes and two key lines; with r/pcmasterrace the only members meeting both conditions); worst fit r/starcitizen; at length r/picturegame, the population's one uncomposed room, whose record holds no canvas work and whose one canvas link is a proposal for an emoji. Either way: r/kirby (F01 and F25; by the alphabet among three tied rooms).

Subform candidates. One on keys (above).

Form test. A grouping, not a form (uptake and an outcome shown in no member's cited passages).

D5a-26: F26, the telling clause not shown at the border: informed members contest the terms (23 members, top-level)

Arithmetic. Expectations 0 to 0.130. Three members are within-case datings: r/metroid of A01, r/uiuc of A09, r/thailand of A17. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A05 (12 of 23 against 57 of 266; excess 0.307; A18 next at 0.158). By my reading of the 16 restrict and add-condition lines, 12 say that a settled border spares a neighbour only where its terms reach the placers and they accept them, and 4 say that sparing came before any border, inside the arrow's bound. For D6: the first group is P05's telling clause stated on P07, so A05's excess here partly restates the cut from the neighbour's side.

The reading. d5a26_F26_reading.json: the record does not show the clause's parts 17 members; informed members contest the terms 10; mistaken repair shown 7; the change undone not the room's agreed change 3. 9 members show one of these, 14 two.

A renaming proposal. The D4 name holds in its second clause, but "not shown" is the coders' standard of evidence: members' cited words show told keepers stopping in at least five rooms and the change fought or lost where telling did not reach in two. Proposed: "the telling clause at the border: told keepers stop, untold ones undo the change, informed ones contest the terms". Also in defects.jsonl.

Finding F-026 (findings.jsonl). At the border the telling clause needs the news to cross between two rooms, and it settles the change only where those told on both sides accept the terms. It carries F-025's limit (F07, the design) to the border. For D6: F07, F26 and F27 restrict the same clause at three themes; read F-024, F-025 and F-026 together before any amendment of P05, beside the held P05 proposal (r/maryland is one of its rooms and an F26 member).

The family and the nearest branch. F07 and F27 share no room with F26. The nearest is F10, on the same third-order theme through P08 (7 shared rooms).

The theme checks. No record carries the branch (r/stevenuniverse holds 13 per cent of its coded concepts). Reciprocity rests on r/maryland (34 per cent; 1.10 without it). Negotiated order, the key's theme, holds.

The restrict-rate check. F26's members' lines restrict at about their pool's rate (8.9 lines a room, 12.7 per cent, against 8.3 and 11.2), unlike F21, F24 and F25, the other restrict-keyed branches accounted.

Survival. Median end 72.22 (all rooms 72.02; F10 71.93). Mean aftermath share 0.0373, carried by r/NewMexico (0.333) and r/placeportalpattern (0.25); 0.0226 without r/NewMexico. Lost in 10 of 23 (43 per cent, against 31), silent in 2 (9 per cent, against 20).

Representatives. Best fit r/buffalobills (the fallback: each member holds one key line); worst fit r/python; at length r/stevenuniverse (the most coded concepts; not read at length before). Either way: r/buffalobills (with r/earthbound and r/nascar one line on each key and no other branch; first by the alphabet; the tie rule has no pass-over).

Corrections before assembly. r/python's operator said they would disable the script (my draft said the script was disabled, and that scripts kept placing the grey, which the record does not show). The member who wrote "DOWN WITH THE BORDER" had stated the compromise (my draft said another member). The aftermath mean rests on two members.

Subform candidates. None on keys (all 23 key lines lift through T3-010).

Form test. A grouping, not a form (the relations shown in parts, the key a restriction, no relation in every member's line); it bounds F-026.

D5a-27: F27, the telling clause not shown in keeping: interference seen, its cause and loss not (27 members, top-level)

Arithmetic. Expectations 0 to 0.153. Two members are within-case datings: r/lakers of A08, r/pcmasterrace of A12. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A07 (7 of 27 against 20 of 175; excess 0.145; A08 next at 0.122). By my reading of the 9 restrict and add-condition lines, with r/greece's room model, 8 say the marking did not close the work: a finish declared and then corrected (r/OnePiece, r/pcmasterrace, r/lakers, r/greece) or celebrated while repair went on (r/babymetal, r/empiredidnothingwrong, r/gravityfalls, r/metalcore); 1 marks a work stopped short to spare a neighbour (r/frankocean). For D6: a declared finish draws a correction toward the design, and that correction is the change keepers repair away; the room models of r/OnePiece and r/greece each propose this return as a new step.

The reading. d5a27_F27_reading.json (28 lines, 27 lifts): loss not shown 12; interference shown, cause not 10; mistaken repair or untold keepers shown 7; another point 5; informed members refused or acceptance not shown 3; change kept 2; nothing of the clause 2; a helpful change recognised 1; adoption not shown 1. 12 members show one, 14 two, 1 three.

A renaming proposal. "Its cause not" is the coders' standard of evidence: in at least eight rooms members say keepers took a change for damage or had not been told. Proposed: "the telling clause in keeping: corrections and changes taken for damage, made late or kept, not shown lost". Also in defects.jsonl.

Finding F-027 (findings.jsonl). In keeping, repair takes a member's correction toward the room's design for damage, as it takes a planned change (six rooms); telling reaches a script only through its operator (four rooms); the ends shown are delay, survival and informed abandonment, and no cited passage shows a planned change lost for want of telling. For D6: P05's clause names "a change the room has planned or agreed"; its first sentence, "Repair restores the form the keepers know", already covers corrections. With F-024, F-025 and F-026, the family "P05's added clause holds only in part" has now bounded the clause at the design, the border and in keeping; read the four findings together, beside the held P05 proposal (r/armok, an F27 member, is one of its rooms, and its F27 key line is one of the nine lines the proposal cites), before any amendment.

A step the room models propose. r/OnePiece, r/cowchop and r/armok's models, and add-step lines in r/radiohead and r/OnePiece, add a step inside P05: checking whether a change is intended before undoing it. For D6, beside F-027.

The family and the nearest branch. F07 shares one room with F27 (r/OnePiece), F26 none. The nearest is F24 (machine hands, 4 shared rooms); the two meet at scripts, though none of F27's four rooms with scripts as keepers is in F24.

The theme checks. The largest record, r/pcmasterrace (17 per cent), carries no excess. Reciprocity rests on r/radiohead (31 per cent; 1.27 without it). Visibility returns rests on r/pokemon (42 per cent; 1.49 without it), whose coded concepts for it are upvote stunts in the sub's own April Fools takeover, not the canvas. Repair work, the key's theme, holds.

The restrict-rate check. F27's members' lines restrict above their pool's rate (10.1 lines a room, 13.4 per cent, against 8.2 and 11.1), like F21, F24 and F25 and unlike F26, though by less than F25.