Forming: branch accounts | D5b

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.

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

Written at D5b, 2026-10-26 UTC, the stage's last leg. 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. Families state one change at several nodes. 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. F01 (103) and five subforms administer the April Fools frame; F07, F26 and F27 limit P05's telling clause (F-025 to F-027); F08 keeps scripts' targets current; F10 does a deal's work; F11 and three subforms carry work on; F15 and F33 keep templates current; F34 sizes designs; F16, F29 and F30 keep the chat's door; F17 and two subforms contest the marking; F20 to F25, F28, F31 and F35 tell the close, narrow the frame, help on conditions, restart, argue over scripts, propose going on, host by leave and answer calls. All groupings. Narrow forms: F09 (54), rooms rebuild after moving; F32 (21), rooms keep after marking. No arrow is testable; 12 names kept.
• D5b. The waterfall (F11, F12, r/forsen) contradicts two names, not the account or the model. 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.

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. The amendments, refused by the close-check, were reverted (QD4-001). Moves 200 to 237. The cuts and cross-links, logged and snapped.

Where the run stands

• The tree's files: branches.jsonl (35), forms/ (35), crosslinks.jsonl (759), comparison, projection and tree files, stage notes, handback, brief. Ledgers (lines): adjudications 96,568; verdicts 1,029; tier history 944; 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 (the handbacks and sections list them 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 this stage's notes for amendments: renamings, 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.

P22 restricted. 10 of 27 members against 15 of 175: the lines say members' work on copies after the close was cleaning and correction, not a contest over versions.

Survival. Median end 72.76 (all rooms 72.02; F24 72.16). Mean aftermath share 0.0359, carried by r/armok (0.5); 0.0173 without it. Lost in 10 of 27 (37 per cent, against 31), silent in 3 (11 per cent, against 20).

Representatives. Best fit r/greece (the fallback: the one member with two key lines, r/OnePiece, has residue); worst fit r/pokemon; at length r/radiohead (r/OnePiece read at length at D5a-22, r/pcmasterrace at D5a-16, r/pokemon the worst fit, all passed over). Either way: r/cowchop (with r/frc, r/futurama and r/hawks one line on each key and one other branch; first by the alphabet).

Corrections before assembly. r/lakers shows distorting repairs, not a member's fix undone (six rooms of corrections, not seven). r/greece's A07 line says only that report and celebration came in one announcement; the correction is in its room model and is cited as such. r/radiohead's complaining member also said they liked the red, so r/radiohead left the list of informed refusers. P06's rate is below its pool's. A Visibility returns quote was replaced: r/radiohead's c0291 sits under other themes.

Subform candidates. None on keys (T3-005 holds 14 lines, T3-021 12; my readings do not separate by them).

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-027.

D5a-28: F28, help at the border conditional: on the home work, the terms and harm to a third room (22 members, top-level)

Arithmetic. Expectations 0 to 0.125. One member is a within-case dating: r/touhou of A07. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A21 (3 of 22 against 7 of 295; excess 0.113; A05 next at 0.084), resting on three rooms. Two lines show a neighbour's member stating what their own room could not promise (r/cowchop, r/mindcrack), one a refusal with no dispute over who speaks for the room (r/utaustin). It meets the key: offers of help at the border came from members who could not commit their room.

The reading. d5a28_F28_reading.json (23 lines, 22 lifts): the helper's own work or capacity 9; the recipient's conduct or terms 8; offered, delivery not shown 7; a reason beyond the trade 3; aimed against a third room 2. 16 members show one, 5 two, 1 three.

The name kept, with two limits: "harm to a third room" rests on 2 members, and the name drops the offers that stayed offers (7), which D4's own sentence names. Also in defects.jsonl.

For D6: P16's order of tasks, across two branches. The helper's own work first, a neighbour's second: 9 of F28's members by this leg's reading, 13 of F22's by D5a-22's. F22 (add-condition on P16 at T4-017) and F28 (the same at T3-010) share no room; the cuts may split one change by where the coders lifted the line. A candidate amendment to P16, not a subform of either branch. Beside it: help offered on the recipient's conduct or the terms (8 members), in r/utaustin withdrawn when the recipient attacked and in r/catalunya threatened with withdrawal, and the room models of r/hungary ("beneficiary-specific terms"), r/mindcrack (losing one's own task frees help) and r/utaustin (help conditional on stopping attacks and on available labour).

The family and the nearest branch. F22 shares no room. The nearest is F18 (4 shared rooms; a subform of F17, which shares 5); in the shared rooms the room's own upkeep came first both when it marked its work and when it helped.

The theme checks. r/dota2 holds 30 per cent of the coded concepts, 73 per cent of the Keying concepts, and moves most of the theme lists: without it Direct information sharing leaves the over list for the under, and six of the nine under themes leave it. Attribution rests on r/cowchop (1.17 without it). Reciprocity is under in a branch keyed on help: the coders placed this help in border threads, under Negotiated order.

The restrict-rate check. F28's members' lines restrict below their pool's rate (6.3 lines a room, 8.8 per cent, against 8.4 and 11.4), as F22's did; the D5a-21 worry does not reach the add-condition branches.

Within size. K01 instantiated in 12 of 22 against 236 of 295, P20 in 10 against 207, P31 in 13 against 241, P18 in 13 against 226, P22 in 6 against 142: the records hold the help and the borders, less of the host's frame, the fairness argument and the talk with rivals.

Survival. Median end 71.695 (all rooms 72.02; F22 72.14). Mean aftermath share 0.0171, 0.0080 without r/cloud9 (0.2). Lost in 7 of 22 (32 per cent, against 31), silent in 4 (18 per cent, against 20). An ordinary ending.

Representatives. Best fit r/hungary (the fallback: the one member with two key lines, r/utaustin, has residue); worst fit r/btc (help as a move in the sub's own faction quarrel); at length r/utaustin (two key lines; the rival school's members as helpers, delivery shown). Either way: r/ripcity (even balance with r/gameofthrones and r/kirby; the fewest other branches; read at length in F18's account; no pass-over in the tie rule).

Corrections before assembly. r/quebec's reply came a minute later, not two; r/hungary's "go for it" was in another thread, not an answer; r/btc's anti-SegWit poster was the neighbour; the "We're all Texans" reply came eight minutes later, not fourteen; r/mindcrack's freed helper only promised to come. The heading check flagged "doubt" in a quote inside the bold-led r/utaustin paragraph; the quote was paraphrased, its citation kept.

Subform candidates. None on keys (all 23 key lines lift through T3-010).

Form test. A grouping, not a form (a condition in every line, but not the same condition; the home work before help in 9 of 22); it bounds no claim.

D5a-29: F29, the chat's reach conditional: access, and the return of decisions to the thread (25 members, top-level)

Arithmetic. Expectations 0 to 0.142. Two members are within-case datings: r/reddevils of A03, r/mexico of A09. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A02 (8 of 25 against 26 of 124; excess 0.110; A11 next at 0.098, restricted in 20 of 25 against 87 of 124). 8 of the 10 restrict and add-condition lines say the start and the call came in one post; r/AprilKnights called before choosing a picture (inside the bound); r/reddevils ran in the arrow's order, its line asking for cause. It does not meet the key: the posts are public and mostly hours before any chat.

The reading. d5a29_F29_reading.json (25 lines): the chat's deliberation not in the record 11; access 7; a decision not binding everyone 7; outsiders learn what returns 6; the move stalled 3. 16 members show one, 9 two.

The name kept, with one limit: its commonest line (11) is the coders' limit of evidence, which F30 names as its own key. Also in defects.jsonl.

For D6: the chat family, divided by op. Three keys on P23 at T3-014: F16 add-step (35 rooms), F29 add-condition (25), F30 restrict (24); F29 shares 3 rooms with F16 and 2 with F30. Read them together, beside "Carrying on" at T3-054, before any amendment of P23. The room models of r/mexico ("a venue-access-and-relay process"), r/liverpoolfc ("adding venue access") and r/thebluecorner (command in a chat apart from control of placers) name the same process.

For D6: the held A11 proposal and the chat. Five F29 members are among its 31 talk-only rooms (r/eve, r/mexico, r/portugal, r/quebec, r/samuraijack): 20 per cent of the branch, 4.4 per cent of all rooms. F16 holds 2 of 35, F30 none. A possible reading: where planning moved to a chat, a template may have lived there, and the thread shows design talk without it. Untested; noted beside the held proposal.

The family and the nearest branch. The nearest is F28 (4 shared rooms), on help; both branches add a condition on reaching another party. F16 shares 3, F30 2.

The theme checks. r/thebluecorner holds 15 per cent of the coded concepts; Meta-organization rests on it (1.06 without it), Live and let live on r/placestart (1.25 without it); Backstage decision-making, the key's theme, holds. Neo-tribes stands at 3.40 in 4 members, below the floor, 75 per cent r/thebluecorner's.

The restrict-rate check. Below the pool's rate (7.3 lines a room, 9.7 per cent, against 8.1 and 10.9), as in the other add-condition branches.

Within size. C01 instantiated in 11 of 25 against 31 of 124, P33 in 10 against 24, P25 in 12 against 44; K01 in 14 against 105, C02 in 2 against 36, K03 in 4 against 44, P22 in 11 against 76.

Survival. Median end 72.99 (all rooms 72.02; F16 72.06). Mean aftermath share 0.0389, 0.0319 without r/rangers (0.2). Lost in 7 of 25 (28 per cent, against 31), silent in 2 (8 per cent, against 20).

Representatives. Best fit r/liverpoolfc (the fallback: each member holds one key line); worst fit r/quebec (its planning, and its scripts' change time, in the open thread); at length r/thebluecorner (the most coded concepts; the account's room that most threatens it). Either way: r/quebec (in no other branch; no pass-over in the tie rule).

Corrections before assembly. P23 was served in the re-check (my draft said never). An r/neopets quote with a sub name in the wrong case was replaced. Votes in the cited passages are not all the chat's. r/samuraijack's schedule change is not shown to be an April Fools act. "nm found it" was another member's and was dropped. The r/thebluecorner vote proposer is not shown to be a moderator. The chat closed five hours after the "current focus" post, not four. An unchecked size superlative, and a claim in the computed note that F29's canvas median was the largest (F13 and F23 are larger), were corrected.

Subform candidates. None on keys (all 25 key lines lift through T3-014).

Form test. A grouping, not a form (a condition in every line, but not the same one; the commonest line a limit of the record); it bounds no claim.

D5a-30: F30, the chat seen only through its invitations and returned reports, not its choices (24 members, top-level)

Arithmetic. Expectations 0 to 0.136. Three members are within-case datings: r/reddevils of A03, r/pcmasterrace of A12, r/littlewitchacademia of A14. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A07 (7 of 24 against 30 of 259; excess 0.176; A02 next at 0.136). 4 of the 8 restrict and add-condition lines say the room marked the work before the whole was done or while repair went on; the others record one post for report and cheer, an order seen without its cause, and credit for an erased piece. It does not meet the key. A07 ran differently in F27 too; r/pcmasterrace carries the same A07 line in both.

The reading. d5a30_F30_reading.json (24 lines): a move into a chat not shown at all 11; chat work reported, its talk not in the record 10; authority over placers not shown 4; another point 3; access 2. 18 members show one, 6 two.

A renaming proposal. The name holds in the 10 where a chat worked; in the 11 where no chat is shown at work there was nothing behind the invitations. Proposed: "the chat asked for, offered, or used out of sight: its talk and choices not in the record". Also in defects.jsonl.

For D6: the key lumps two things. A chat never shown at work and a chat whose talk is out of sight. One r/spongebob passage (c0003) carries an F16 add-step line and an F30 restrict line: the family's division by op in one room. F30's second facet is F29's commonest. Read F16, F29 and F30 together (note of D5a-29).

The restrict-rate check. 13.4 lines a room, 17.2 per cent, against 7.9 and 10.8: the highest of the branches accounted (F25 was 12.9). P05 restricted in 21 of 24 against 160 of 259, C01 in 10 against 32, K06 in 9 against 20. The D5a-21 worry applies in full.

Within size. C01 instantiated in 1 of 24 against 64 of 259 and restricted in 10 against 32 (its lines: decided elements of order shown locally, the population claim untestable). P20 absent in 10 against 39. P22 instantiated in 8 against 127.

The theme checks. r/pcmasterrace holds 18 per cent of the coded concepts and carries no excess. Sensemaking rests on r/de (0.86 without it), Collective efficacy on r/planetside (0.97 without it); Backstage decision-making, the key's theme, holds. Meta-organization and Live and let live, over in F29 (each on one room), are under here.

Held. No member among either held proposal's rooms; F29 holds five of the A11 talk-only rooms, F30 none.

Survival. Median end 72.265 (all rooms 72.02; F16 72.06). Mean aftermath share 0.0161. Kept in 8 of 24, lost in 9 (38 per cent, against 31), silent in 7 (29 per cent, against 20).

Representatives. Best fit r/lofihiphop (the fallback: each member holds one key line; its share, 0.0833 against r/FloydVsVoid's 0.0829, rests on one of 12 coded concepts); worst fit r/canucks; at length r/de (r/pcmasterrace passed over, read at D5a-16; r/de and r/prequelmemes tie at 734 on the helper's count, broken by the helper's order and the tie rule's alphabet, and the within-size count also puts r/de first). Either way: r/de (with r/OrderOfTheKoi one line on each key and no other branch; first by the alphabet with case ignored; no pass-over).

Corrections before assembly. r/xcom's earlier post was two and a half hours before, not two. r/lsu's member first asked at hour 47.26. The r/stardustcrusaders notice is automatic. Who ran r/paladins' hunt is not in the record. r/porterrobinson moved to the group whose order is seen but not its cause. Two timings (r/lofihiphop, r/de) and an unchecked "only two" were corrected.

Subform candidates. None on keys (all 24 key lines lift through T3-014).

Form test. A grouping, not a form (the key restricts two different things; the chat's decisions and their effect shown in no member); the four-problem mapping empty, with a remainder: making a venue comes before it can carry information. It bounds no claim.

D5a-31: F31, hosting as one-off permission: requests and leave, no standing host rule (22 members, top-level)

Arithmetic. Expectations 0 to 0.125. Two members are within-case datings: r/metroid of A01, r/foxes of A06. Every arrow not-testable-here, every proposition not testable.

Section 7 by the D5a-12 rule. A07 (8 of 22 against 26 of 219; excess 0.245; A10 next at 0.216). 7 of the 9 restrict and add-condition lines say the room marked its work with no finished or lasting mark; r/nbaspurs's "permanent spot" was moved about five minutes after it was announced. It meets the key in part: spots held on another room's leave.

For D6: A07 across three branches. A07 ran as section 7 in F27, F30 and F31. 18 rooms across them carry an A07 restrict line, 4 in two branches (r/pcmasterrace, r/FloydVsVoid, r/prequelmemes, r/frankocean), against 87 in the population. The lines say rooms marked their work during it, before it was finished, after losing it, or on a spot held on leave. A07's bound covers a mark found already made and a work the close cut short; it does not cover these. Also in defects.jsonl (lines 91 and 92, the second correcting the first's description of the bound).

The reading. d5a31_F31_reading.json (22 lines, one facet each): a request with no grant shown 8; a grant for one arrangement 8; a disputed or provisional grant 5; another point 1.

A renaming proposal. "No standing host rule" is the guests' record's limit: members name applications ("an official spot"), requests to a host and a host's refusal. Proposed: "hosting seen from the guest's side: requests and one-off leave, the host's rule outside the record". r/thebluecorner, not a member, is the named contrast: a host whose own record holds its rule. For D6: read the hosts' records (r/greenlattice was read at length in F12's account) beside the guests'.

The restrict-rate check. 12.7 lines a room, 16.5 per cent, against 8.1 and 11.0: second to F30 among the branches accounted. P05 restricted in 19 of 22 against 133 of 219. The D5a-21 worry applies.

Within size. P19 instantiated in 15 of 22 against 125 of 219 and restricted in all 22 against 14. P13 instantiated in 9 against 149 (absent in 13 against 63), P20 in 10 against 167 (absent in 10 against 23), P21 in 4 against 85, K06 in 9 against 161, P25 in 4 against 68. K02 in all 22.

The theme checks. r/prequelmemes holds 16 per cent of the coded concepts and carries no excess; Collective efficacy holds without r/fivenightsatfreddys (1.71); Sensemaking falls to 1.50 without it. Negotiated order, the key's theme, is not over (1.31). The coders placed requests to a host under Territoriality, over at 1.54.

Held. r/torontoraptors is among the A11 proposal's talk-only rooms; its F31 line does not bear on the proposal. No P05 proposal room.

Survival. Median end 72.22 (all rooms 72.02; F24 72.16). Mean aftermath share 0.0094, against 0.0200. Kept in 13 of 22, lost in 9 (41 per cent, against 31), silent in none (against 20 per cent).

Representatives. Best fit r/FloydVsVoid (the fallback; guest in a neighbour's work and host offering a spot); worst fit r/foxes (its grant and its loss of space in its last hours); at length r/prequelmemes (the most coded concepts; a host, where most members were guests). Either way: r/uoft (in no other branch; its script and its leave in one member's work).

Corrections before assembly. Ten details against the sources, listed in the diary; among them the "permanent spot" lasted about five minutes, not four, and r/uoft's member kept the host's flag in return rather than took rent. A working-rule breach was logged: two Edits to one part file in one turn.

Subform candidates. None on keys (all 22 key lines lift through T3-010).

Form test. A grouping, not a form (requests, one-off leave and disputes in parts; the host's side outside the branch); the four-problem mapping empty, with a remainder: rights to space among rooms with no common authority. It bounds no claim.

D5a-32: F32, the marking returns to keeping: celebration followed by renewed defence (21 members, top-level)

Arithmetic. Expectations 0 to 0.119. Two members are within-case datings: r/habs of A02, r/clg of A18. 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 second form of the stage, in a narrow sense, by F09's test. The key is a link on P05 at T3-009, the ground of P11: it joins the marking to keeping in every member's line (20 recorded as sequence, 1 as dependence), and every member's cited words show it. Constructs (P11, P05), a relation (after the marking the room keeps the work), conditions and means can be written; the relation is falsifiable by rooms whose marking was their last act, which the model's own close describes (not counted). Shared status: supported as a sequence; three lines claim no cause, and every local account stays unresolved. The doubts are in the account's section 13: the cut, paired rulings with uniform words, keeping after new damage in 7 members, and selection and size in the survival and canvas figures.

For D6: the link the model lacks. From P11 to P05: after the marking, the room keeps the work, and members call for defence, repair and night cover. It stands on 21 re-check lines in 21 rooms and has no within-case dating, so its order has not been tested against a null. D4 named it at D4a-02, beside F09's link from P10 to P03. Of the 103 link lines on P05 in the population, T3-009 holds the most (21). A narrower reading stands on 10 members, where the celebrating post or its reply named keeping before any new damage (7) or the finish was corrected (3); in 7 the keeping followed new damage and may answer the attack, which P05 already states.

For D6: A07's restriction, the other side. F27, F30 and F31 restricted A07 because rooms marked work that was unfinished or did not last. F32's rooms marked the work and kept it. A07 is restricted in 3 of F32's 21 members, against 34 of 259 rooms of their size. Together: the marking is a point inside the work, not its end.

Section 7 by the D5a-12 rule. A02 (8 of 21 against 65 of 259; excess 0.13; A17 next at 0.058). 7 of the 8 restrict lines say the start and the call came in one turn; the eighth (r/undertale) recruited keepers around a figure no member started. It meets the key in part: the coders read stages joined in one turn, at the start as at the marking. A02's bound covers a call before the proposal, not a proposal that is itself the call. For D6.

The reading. d5a32_F32_reading.json (21 lines, one of five groups each, two side flags): keeping named before new damage 7; after new damage or an alarm 7; a finish corrected 3; a work found made 3; the expected close not come 1. Keeping named as members' task in 19 members' cited words; credit in 10; three lines claim no cause.

A renaming proposal. "Renewed defence" holds in the 11 members whose cited words name defence, protection, an attack or reinforcements, and "returns" follows the model's order: in the rooms keeping had often never stopped. Proposed: "the marking does not end the keeping: celebration followed by defence and repair". Also in defects.jsonl (line 93).

The room models. They agree on the sequence; four of them (r/newzealand, r/starvstheforcesofevil, r/undertale, r/OnePiece) file it under A03, reading the celebration as the end of building. I believe the key: the celebrating words and their replies turn to keeping.

The restrict-rate check. 6.5 lines a room, 9.1 per cent, against 8.4 and 11.4: below the pool, unlike F30 and F31. P05 restricted in 13 of 21 against 162 of 259.

Within size. P11 and P05 instantiated almost everywhere (21 and 20 of 21; 254 and 252 of 259). Present less often: P13 in 8 against 162 (absent in 13 against 87), P19 and P14 in 5 against 142 each, P22 in 6 against 129, P21 in 5 against 94, K06 in 10 against 179, C01 in 3 against 60, P10 in 8 against 123.

The theme checks. Without r/newzealand (12 per cent of the coded concepts) every excess holds, and Live and let live and Backstage decision-making join the under list. Frame bridging is one room's: without r/starvstheforcesofevil it falls to 0.78 (its fans' quarrel over which couple to show, and its celebration placed under its in-jokes). Standardization of output holds without r/rickandmorty (1.52). With Keying left out Mobilization falls to 1.49. Completion ritual, the key's theme, is not over (1.30).

Held. r/habs is among the A11 proposal's talk-only rooms; its F32 line does not bear on the proposal. No P05 proposal room. r/OnePiece's defender who worked against a correction taken for damage shows P05's telling clause at work.

Survival. Median end 72.3 (all rooms 72.02). Mean aftermath share 0.0076, against 0.0200. Kept in 14 of 21 (against 144 of the 259 rooms of their size), lost in 5, silent in 2. A room that went on keeping had a work to keep; the canvas median is at the 98th percentile (read only afterwards), so size may carry the sequence.

Representatives. Best fit r/luxembourg (the fallback; a celebration, a watch and two repairs, no attack); worst fit r/habs (a record about moving and rivals; its model names both D4 links, and only this one put it in a branch); at length r/newzealand (the most coded concepts; marking and keeping in turns from hour 12; its laser brought a raid, and the raiders helped repair). Either way: r/newzealand (in no other branch; its F07 line on alterations it knew and repaired, its F32 line on when it was called to keep).

Corrections before assembly. Seven details against the sources, listed in the diary; among them "renewed defence" counted from the quote text only (11 members, not 14), and r/luciomains' call came six hours after "It's done!", not four. A stray shell assignment slipped into one check command; it changed nothing.

Subform candidates. None on keys (all 21 key lines lift through T3-009).

Form test. A form, narrow: the marking-then-keeping sequence. It binds allocation (keeping named as the next task and asked of members' time); a remainder: on a canvas that stays open, a finished work is not a finished task. It bounds no claim.

D5a-33: F33, the plan kept current while the design settles (23 members, top-level, level fourth)

Arithmetic. Expectations 0 to 0.130. One member is a within-case dating: r/dragonquest of A13. Every arrow not-testable-here, every proposition not testable.

For D6: F15 and F33, one change at two nodes. Both keys are add-step on P04; F15's is at T4-008 (Standardization of output, 42 rooms), F33's at T4-006 (Collective representation, 23 rooms). The two share no room. Of the population's 115 add-step P04 lines in 114 rooms, 43 lift to T4-008 and 23 to T4-006. A room's branch follows where its coders placed the theme that carries its template talk: with the templates, or with the design. In F33, Standardization of output is not over (0.70), and Direct information sharing falls to 0.36. D6 may read the 65 rooms as one change. Also in defects.jsonl (line 94).

Section 7 by the D5a-12 rule. A07 (5 of 23 against 55 of 395; excess 0.078; A03 next at 0.039). Three restrict lines say the marking did not follow a separate report of a finished work: report and marking in one turn (r/CSUFoCo, r/mit), or marking while the design went on (r/gatech celebrated, then added its name). Two mark works never finished (r/chess, r/superman), partly inside A07's bound. A07 has now run as section 7 in F27, F30, F31 and F33: 23 rooms across them, against 87 in the population. F32 is the other side.

For D6: A11 in the room models and in the ledger. Three room models (r/tf2, r/torontoraptors, r/gatech) say in their own words that a template did not settle the design. The ledger restricts A11 in 11 of 23 members, against 221 of 395 rooms of their size (d5_arrow_restrict.py, a new helper on d5_within.py's pool). I believe the room models; the point may sit in the P04 step instead. The A11 held proposal's reason is plain here, as in F15. r/wine and r/torontoraptors are among its talk-only rooms; r/wine's line agrees with that reading, r/torontoraptors's in part.

P05's telling clause, inside the plan. Where the design kept changing, keepers repaired a planned change away or were warned against it in four members: r/feedthebeast (a member returned the new colour to the old for hours), r/tf2 ("I WAS WRONG, DO NOT FIX"), r/nuclearthrone (a template asked so allies would not repair an addition away), r/gatech (overwriters messaged). As in F15, keeping the plan current is in part telling the keepers.

The reading. d5a33_F33_reading.json (23 lines, one of five groups each, one side flag): a detail corrected against the plan 7; one current plan made to replace others 6; the reference asked for or made usable 5; the canvas or a neighbour's work as the reference 3; the location sent again 2. The design changing at the time in 16.

The name. Kept. It holds for most members; its strongest objection is that "while the design settles" restates what the node T4-006 holds.

The restrict-rate check. 5.5 lines a room, 7.7 per cent, against 8.0 and 11.0: below the pool. P05 restricted in 9 of 23 against 251 of 395.

Within size. The median member has 86 coded concepts; half the members are smaller than every room of the pool, so idle elements lean against them. Present less often: P31 in 7 against 312 (absent in 16 against 71), P09 in 14 against 357, P18 in 10 against 286, P23 in 12 against 318, P20 in 7 against 245, P14 in 6 against 193, P21 in 2 against 125, K04 in 15 against 323. P27, choosing and changing the spot before any loss, in 20 against 305.

The theme checks. Without r/india (18 per cent) both excesses hold; Live and let live leaves the under list and Repertoire of contention joins it. Transition is r/tf2's (1.03 without it; its reuse of the art as sprays, flairs and icons). Keying out: Workarounds joins the over list (1.503), Boundary work leaves the under list (0.672).

Held. No P05 proposal room. r/wine and r/torontoraptors among the A11 proposal's talk-only rooms (above).

Survival. Median end 70.59 (all rooms 72.02). Mean aftermath share 0.0268, against 0.0200. Kept in 10 of 23 (against 227 of the 395 rooms of their size), lost in 9 (against 152), silent in 4 (against 16). Three members organized after hour 94 (r/india, r/tf2, r/NewMexico). For D5b and E1: r/india's work_remained 'lost' rests on c0461, a line about the neighbour's flag; its own words say its flag stood (defects.jsonl line 95). If the field is misread, kept is 11.

Representatives. Best fit r/kuwait (the fallback; a site, a rejected site, the location sent again and one task, between two members); worst fit r/feedthebeast (a record of the day's jokes; its canvas work was the instruction); at length r/india (the most coded concepts; its plan lived in a defence script whose file had to change with the design, and which blocked later changes). Either way: r/feedthebeast (fewer other branches than r/gatech; its F14 line on the canvas as a model after the close, its F33 line on the canvas as the instruction during the work).

Corrections before assembly. Twelve details against the sources, listed in the diary; among them r/tf2's second alarm came four minutes later, not seven, and a stray unquoted phrase was removed from section 8.

Subform candidates. None on keys (six third-order nodes; the 13 T3-004 lines spread over four of the five groups).

Form test. A grouping, not a form (a step inside P04; the chain from a design change to a revision reaching the keepers in parts; the boundary with F15 the coders' placement). It binds information; no remainder needed. It bounds no claim.

D5a-34: F34, the design sized to the hands: scale and detail conditioned on crew, upkeep, space and colours (22 members, top-level, level fourth)

Arithmetic. Expectations 0 to 0.125. One member is a within-case dating: r/yugioh of A19. Every arrow not-testable-here, every proposition not testable.

For D6: a link from K02 to P02. The model gives K02 (too few hands or too little room) one consequence, A10: after a loss, the room moves. In 10 of F34's members the cited words show the judgment coming first and sizing the design: a small tag because the room is small (r/crystalclear), a compact design so the room can finish (r/evex), no second picture because the first is hard to keep (r/aoe2, r/strangerthings, r/detroitlions). r/evex's room model proposes it as a new element ("fitting ambition to available builders before losing a spot"); r/crystalclear's model reads the same act as not K02, because K02 is written as a judgment that the room cannot do what it wants. A10 is restricted in 7 of 22 members, against 149 of 364, its lines saying a shortage did not lead to a move.

Section 7 by the D5a-12 rule. A16 (5 of 22 against 60 of 364; excess 0.062; A17 next at 0.051). The restrict lines qualify the reasoned refusal: bare refusals or refusals of the caller's right to enlist (r/4chan), a call withdrawn by its own author (r/evex), a refusal given with a slur (r/PORTUGALCARALHO), one target questioned while a rival's peace request was ignored (r/detroitlions), restraint asked with no call seen (r/starlightstage). On the other side, the room's capacity is a reason for restraint: r/palestine "barely" had the hands to defend its flag, and r/aoe2 refused a second picture that would cover two neighbours and lose two allies. For D6: capacity beside A16's norm and cost.

For D6: three branches at T4-006. F07 (keepers who knew a planned change and rejected it), F33 (the plan kept current) and F34 (what the design can be, given the room) share the coders' theme for what the mark shows of the room. F07 and F34 share three rooms, F07 and F33 three, F33 and F34 one. D6 may read the node's changes together.

The reading. d5a34_F34_reading.json (22 lines, one of five groups each, one side flag): sized to the crew 5; limited by upkeep 3; conditioned on space, a site's leave or an ally 5; on colours or pixels already placed 3; on something else 6. The room's own capacity named in 10.

The name. Kept. Its list of conditions holds for 16, "sized to the hands" strictly for 10; six lines qualify the design in other ways (defects.jsonl line 96).

A reading-only subform candidate. The 10 members whose words name the room's capacity. D4 cut on keys; this is a reading, written for D6, not a cut.

The restrict-rate check. 6.5 lines a room, 8.9 per cent, against 8.1 and 11.0: below the pool. P05 restricted in 14 of 22 against 230 of 364.

Within size. The median member has 95 coded concepts; half the members are smaller than every room of the pool. Present less often: P22 in 3 against 163, P19 in 3 against 194, P21 in 2 against 116, P31 in 8 against 292, P17 in 6 against 231, P20 in 6 against 237, K06 in 6 against 218, P10 in 5 against 166, P14 in 5 against 181, R02 in 12 against 329. P27, choosing the spot before any loss, in 19 against 280.

The theme checks. Frame bridging (1.60) is r/farmcarrots' (1.25 without it). Without r/4chan (11 per cent), Collective representation, Sensemaking and Transition join the over list, and Workarounds, Repertoire of contention and Collective memory join the under list. Keying out: no change. Territoriality is under although the key often concerns space: the coders placed that talk with the design.

Held. No P05 proposal room; no A11 talk-only room.

Survival, and a field for D5b. The ledger: median end 72.31 (all rooms 72.02), mean aftermath share 0.0269 (against 0.0200), kept 14, lost 6, silent 2 (the pool 209, 142, 13 of 364). Read against its codes, the field shows the work standing at the close in 6 members and gone in 1; for the rest it rests on completion reports during the event or lines about other rooms (defects.jsonl line 97). With r/india in F33, survival-D5 should re-read the field from the codes.

Representatives. Best fit r/crystalclear (the fallback; one member sized a tag to the room in one post; 8 coded concepts); worst fit r/detroitlions (a record of a prank and rivals; one picture at a time); at length r/4chan (the most coded concepts; a clover sized to the hands and given up, a script, many calls to deface others' work, refused in part). Either way: r/AyyMD (tied with r/farmcarrots on the rule's earlier steps; the alphabet decides; its F07 and F34 lines name one poll).

Corrections before assembly. Nine details against the sources, listed in the diary; among them the pool's survival counts were F33's and were replaced with F34's.

Subform candidates. None on keys (six third-order nodes).

Form test. A grouping, not a form (a condition on P02; the room's capacity named in 10 of 22). It binds division in part; a remainder: ambition fitted to capacity before any loss. It bounds no claim.

D5a-35: F35, the call made workable: answers ask for a task, and callers supply it (18 members, top-level, level third)

Arithmetic. Expectations 0 to 0.102. Two members are within-case datings: r/lebanon of A12, r/littlewitchacademia of A14. Every arrow not-testable-here, every proposition not testable. The last branch of D5a: all 35 branches are accounted (branches-D5.jsonl, 35 lines).

For D6: P15 and A12. P15 says a member answers a call in one line that "asks for nothing back". In F35 it is instantiated in 13 of 18 members, against 336 of 354 rooms of their size, and A12 (the bare answer after the call) is restricted in 8 of 18, against 83 of 354 (section 7 by the D5a-12 rule; excess 0.21, A08 next at 0.061). The restrict lines and the key describe one exchange from its two ends: willing members asked for coordinates, a plan or a starting place, gave reasons, or doubted the call, and callers had to supply the task. r/polyamory's room model records P15 absent because no written answer asks nothing back. For D6: the bare answer as one form of acceptance; a willing answer that asks for a task as another. F-023's count stands.

The reading. d5a35_F35_reading.json (18 lines, one of four groups each): a willing answer asks for the task, the place or the means 5; a joining answer reports a part or renews the call 5; the caller widens or orients the call 5; the call redirected, divided or refused 3. The whole exchange, a question answered with a task, in 2 members' words (r/FlaggyFlag, r/clashroyale).

A renaming proposal. "Answers ask for a task" holds for 5; "callers supply it" for 5 others as visibility or a cue. Proposed: "the call answered beyond a bare yes: questions for a task, reports that renew the call, and calls made visible". Also in defects.jsonl (line 98).

The restrict-rate check. 6.4 lines a room, 8.9 per cent, against 8.2 and 11.1: below the pool. P05 restricted in 11 of 18 against 224 of 354.

Within size. The median member has 98 coded concepts; three have ten or fewer. Present less often: P25 (the work bringing new people in) in none against 97, P13 in 5 against 207, P17 in 5 against 225, P18 in 7 against 264, P23 in 9 against 289, K04 in 8 against 296, P31 in 8 against 280, P22 in 3 against 160. P10 in 10 against 158, a little more often.

The theme checks. Mobilization (2.63) restates the cut. Keying (1.73) is r/clashroyale's (1.38 without it); Keying is 31.7 per cent of the branch's coded concepts, and four members are also in F01. Live and let live (1.63) is r/lebanon's (1.09 without it; its theme on taking other rooms' flags). Without r/clashroyale or with Keying left out, Boundary work, Repair work, Completion ritual and Collective memory leave the under list.

Held. No P05 proposal room; no A11 talk-only room.

Survival, and the field for D5b. The ledger: median end 71.51 (all rooms 72.02), mean aftermath share 0.028 (against 0.0200), kept 9, lost 6, silent 3 (the pool 203, 139, 12 of 354). Read against its codes: the work stood at the close in 3 members and plausibly in 3 more; 2 'kept' are completion reports during the event and 1 a post title; of 'lost', 3 say the work was gone, 1 that the main flag stood, 1 is a loss during the event, 1 unclear; the 3 silent records are 2 to 10 coded concepts (defects.jsonl line 99). Across F33, F34 and F35 the field takes completion statements, and lines about other rooms, for survival; survival-D5 should re-read it from the codes.

Representatives. Best fit r/tenma (the fallback; one call and one landmark by the same member; 2 coded concepts); worst fit r/seahawks (a record of a moderator game and disputes over space; a volunteer who asked for a starting place); at length r/clashroyale (the most coded concepts; many parallel calls, a template that could not be drawn, a designer who asked for a reference and did not get one, a logo given up to a band's sub). Either way: r/seahawks (fewer other branches than r/stargate; its F25 line on a pointer to a new canvas, its F35 line on a volunteer who waited for a task).

Corrections before assembly. Fourteen details against the sources, listed in the diary; among them three unchecked superlatives removed, and the moderator's call to abandon a space placed under the princess call, with the refusal that followed.

Subform candidates. None on keys (all 18 lines lift through T3-002).

Form test. A grouping, not a form (a step inside P01; the exchange in parts). It binds allocation and information in part; a remainder: between a yes and a pixel lies a task the call did not carry. It bounds no claim.

D5b: the waterfall and survival

The waterfall (waterfall-D5.md). The rule, logged before the walk: the parent whose subforms cover the largest share of its members (F11, 38 of 43), its largest subform (F12, 22), and the subform's member at the lower median of coded concepts (r/forsen, 114; the upper median would be r/greyblob). The walk holds from the quotes to the room model. It contradicts F12's name at r/forsen: the room enters F12 on one add-step line about a song (R-forsen-d98406bef832-062), and its record shows a call to another site and no building there. This confirms the placement question F12's account logged; T3-054's gloss already holds turning a later canvas down, so the name describes half the theme. It contradicts the second half of F11's name (the room's carrying on began after the close), as F11's renaming proposal says. At the account, r/forsen shows A09's order (a loss announced at hour 73.20 before the song at 73.48) and no cause, which is all the account's count claims. Against prior.md: a model all the way down held on this walk; the subform's condition drops at the room; the room describes decline and continuity within about five hours. Canvas, afterwards: the atlas links a monkaS figure that the record calls gone; a question for the room's account.

Survival (survival-D5.md). From the record: median organizing end 72.20 for the 476 rooms in a branch (72.02 for 705); 53 ended before hour 64, 303 between 64 and the close, 120 at 73 or later; 117 coordinated after the close, mostly toward later canvases. Latest: F12 (80.76) and F23 (80.66); earliest: F14 and F33 (70.59); no member of F18 coordinated after the close. These restate the keys where the key is about carrying on.

work_remained, re-read. By a rule logged before the reading, for all 476 rooms: the field agrees in 248. 'Kept' rests on a post-close line saying the work stood in 146 of 253; 'lost' on a post-close line saying it was gone in 40 of 161. For D6: the account's paragraph 'Which keep the work alive' rests on the field and should either be restated from a reading of the codes or carry the field's error beside its shares (defects.jsonl line 100). The ledger is unchanged.

Dated changes and the canvas. Of 25 dated acts in the narratives, 23 checkable: the members' placements by hour corroborate the timing of 15, contradict 4, do not show 3, and 1 window is empty. The four contradicted timings are questions for their accounts at D6 (defects.jsonl line 101): r/thebluecorner at hour 39 (F23, F25), r/hawks at 61.14 (F27), r/faeria at 29.15 (F31), r/httyd at 52.45 (F32).

What the members showed that the room notes did not predict. r/forsen's organizing end, by the A1 rule, is the song proposal itself. Rooms whose own words say the work was gone placed a larger share of their placements in the last nine hours than rooms whose words say it stood (0.201 against 0.165), with nearly the same median area; a timing, not a cause.

Licences exercised at D5b. The re-reading rule and its four conventions, adopted while reading and applied to all pages; three overrides after the reading files were written (r/detroitlions, r/placetardis, r/liverpoolfc); the timing rule and one amendment after seeing its output (an empty window corroborates nothing; it moved r/ockytop); the waterfall's even-count convention, fixed after the sorted list was printed. The canvas entered only afterwards: survival-D5.md sections 5 and 6 and the waterfall's last section.

Handback, stage D5: the branch accounts, the waterfall and survival

Legs D5a-01 to D5a-35 and D5b, ending 26 October 2026. One account per branch (forms/F01-account.md to forms/F35-account.md, one line each in branches-D5.jsonl), then waterfall-D5.md and survival-D5.md. The model is the one frozen at D3 (46384686…), unchanged at this stage; the return was served at pass 15 (e15f9647…b3fecd). The P05 and A11 amendments are held proposals (QD4-001), stated in full in every account, in the tree file and at the end of the waterfall. Comparison engine v1.1 is a declared departure (QD4-002). Local validation is not established: every member's adapted account is unresolved, and prior.md section 3's measure was not computed. Following J's ruling after the D3c interview, no account relies on the kind of an add-condition, add-step or restrict line, and no further re-check, labeler or reader was used.

The claim

The 35 branches are groupings of rooms that made the same change to one element of the model. They are facets, not exclusive types: 200 of the 476 rooms are in one branch, and the rest are in two or more. Read in their members' words, 33 are groupings and not forms: no relation between two constructs is in every member's line and shown in the members' words. Two are narrow forms, and both are returns the model lacks. After a move, the room builds again at a new site (F09, 54 rooms). After the marking of a finished work, the room goes back to keeping it (F32, 21 rooms).

The branches differ in their functioning by which part of the work the shared change touches. Some add work the model does not state: the sub's April Fools play administered (F01 and five subforms), a deal carried out (F10), the shared plan kept current (F15, F33, F08), the chat's door kept (F16, F29, F30), a host's leave asked for (F31), a design sized to the hands (F34), a call made workable (F35). Some limit a clause: P05's telling clause, at the design, the border and in keeping (F07, F26, F27). Some carry the work past the close (F11 to F14, F23, F25). Families of branches state one change at several nodes of the model.

On survival the branches differ less than their names suggest. The rooms' own words after the close say the work stood in 149 of the 476 rooms in a branch and was gone in 43; no branch sorts the two by much. Branches whose key is carrying on end later, which restates the cut.

The branch that best supports the claim: F09. In 51 of its 54 members the words show a move followed by building at a new site. Its name survived the members' reading, its room models agree with the reading, and it supplies an arrow the model lacks, from the move to building and reporting the new work, for stage D6. It stands on 55 re-check lines with no within-case dating, so its order is untested.

The branch that most threatens it: F01. It is the largest branch (103 rooms), and its shared change is about the sub's April Fools play, which the members' lines say is not canvas work. The tree's widest branch is cut on an element the model provoked (the frame, K01), not on how rooms organized their canvas work. If the largest grouping tracks the coders' frame, the branches may track the model's own provocations more than the forms organizing took.

The condition between them is where the shared change lies. Where it lies on the spine of the canvas work (a return to building, a return to keeping), the members' words show a relation and the branch reads as a form. Where it lies beside the spine (the sub's play, a chat's door, a host's leave, a plan's upkeep), the members share a change but not a relation, and the branch is a grouping.

The return value

• Branches accounted: 35 of 35. They hold 476 rooms; 229 rooms are in no branch.
• Branches that failed the form test: 33, reported as groupings (shared status unresolved). Forms: F09 and F32 (shared status supported).
• Names that survived the members' reading: 12 (F02, F03, F06, F08, F09, F17, F23, F25, F28, F29, F33, F34). The other 23 carry renaming proposals for stage D6 in notes-D5.md.
• The branch whose reading disagreed most with the room models: F11. I believed the room models on two points: crossover threads proposed near hour 63 were not shown to last, and several room models say an invitation to another canvas is not shown to have been followed. The waterfall walked through F11 and met the same limit at r/forsen.
• Where the uncomposed rooms sit. By the verdict the branch lines carry (the analyst's last ruling, else the readers' one verdict): r/picturegame, the one room that did not compose at the first return, is in F21 and F25; at the re-check both readers found it composes with residue. r/azerbaijan, which both readers could not tell at both returns (eight concepts, below the floor), is in F17, F19 and F20. At the re-check both readers could not tell 19 rooms. Three of them are in a branch: r/azerbaijan, and r/polyamory (F35) and r/THE_R (F27), which I ruled composes with residue at D3a-56. The other 16 are in no branch.
• Arrow absences. Real: 0. Not testable here: 735, all 21 arrows in all 35 branches. No arrow had an expectation of one or more within-case datings in any branch (section 1's arithmetic), so no arrow is present or absent anywhere.
• Propositions. None failed against a real expectation; N01 to N09 are not testable in every branch. The branch reading bounded P05's telling clause in three findings, written from members' words and not from absence arithmetic: F-025 (F07, at the design), F-026 (F26, at the border) and F-027 (F27, in keeping), each with status bounded.
• The waterfall's contradictions (F11, F12, r/forsen, by a rule stated before the walk). Two, both on names: r/forsen enters F12, "the spine restarted on another canvas", on a line about a song, and its record shows no building on another canvas; and its carrying on began after the close, against the second half of F11's name. Neither reaches the account or the model. One question from the canvas: the atlas links a figure the room's record calls gone.
• The most consequential difference between two forms: what sends the room back. In F09 a loss of place sends the room back to building; in F32 the marking of success sends it back to keeping. prior.md expected loss of the spot to send a group back to its beginning. F32 adds success as a second way back. So the model's spine has two re-entries the model does not state, one from each outcome. Neither has a within-case dating; both wait for an order test.

Survival by branch

Reported in full in survival-D5.md, from the record first.

• The record. For the 476 rooms in a branch the median organizing end is hour 72.20 (705 rooms: 72.02). 53 rooms ended their coordinating before hour 64, 303 between 64 and the close, and 120 at 73 or later; 117 coordinated after the close, mostly toward later canvases. The latest medians are F12 (80.76) and F23 (80.66), then F13 (74.88) and F11 (73.48); the earliest are F14 and F33 (70.59). No member of F18 coordinated after the close.
• work_remained. The field as the ledger gives it: kept 253, lost 161, silent 62. I read it again for all 476 rooms from its cited codes, by a rule logged before the reading. The field agrees with the reading in 248. 'Kept' rests on a line after the close saying the work stood in 146 of 253, and 'lost' on a line after the close saying it was gone in 40 of 161. The field over-reads both outcomes, loss more. The account's paragraph 'Which keep the work alive' rests on the field; it is a question for stage D6 (defects.jsonl line 100). The ledger is unchanged.
• Each branch's ending. The last coordinating act in most branches is repair work or transition; in F35 it is a call (0.361 of last acts against 0.065), in F08 a workaround (0.22 against 0.046), and in F33 negotiated order (0.304 against 0.113). After the close, transition leads in nearly every branch.
• The canvas, afterwards. The frame is built from artworks that survived, so the canvas leans toward survival: 475 of the 476 rooms have an artwork, and rooms whose words say the work stood or was gone have nearly the same median area (770 and 758 px). The contract's section 5 sentence stands beside every figure: the atlas records what survived the last hour, is not a measure of skill, and has no measure of whether the room went on.
• Dated changes. Of 25 acts the narratives date, 23 are checkable against the members' placements by hour. The canvas corroborates the timing of 15, contradicts 4, does not show 3, and one window is empty. The four contradicted timings are questions for F23 and F25 (r/thebluecorner, hour 39), F27 (r/hawks, 61.14), F31 (r/faeria, 29.15) and F32 (r/httyd, 52.45) (defects.jsonl line 101). A timing is corroborated, never a mechanism.

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

Both are stated in full in tree-D4.md, in every account's section 6 and at the end of waterfall-D5.md. In short: P05 would gain "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it", with a bound naming nine rooms; A11, the arrow from P02 to P04, would be withdrawn under rule 14. Neither is part of the model the accounts read.

Questions, departures and defects

• Questions: none open.
• Departures: comparison engine v1.1 (QD4-002; departures.jsonl line 10), carried.
• Defects: 38 lines from stage D5 (defects.jsonl lines 64 to 101), among them the renaming proposals, the families of one change at several nodes, the work_remained misreads (lines 95, 97, 99, and the stage-wide re-reading at line 100), and the four contradicted timings (line 101).
• For stage D6 (notes-D5.md): 23 renaming proposals; the two returns the model lacks (F09, F32); P15's 'asks for nothing back' beside A12 (F35); K02 to P02 (F34); the reading-only subform candidate in F34 (the room's capacity named in 10 of 22); F12's name at r/forsen and r/polska; the account's survival paragraph.

Licences exercised (METHOD.md)

• The count set by kinds, not by a head's capacity: exercised. 35 accounts, 2 forms and 33 groupings, by the form test, with no target number.
• An in-sample return in Eisenhardt's spirit: the branches were cut on the return's ledger, so the accounts read members of groups the return made; they cannot corroborate the return.
• Langley's strategy, declared: exercised at D5b as temporal bracketing. The organizing end and 25 dated acts were read against prior.md section 4's brackets and the placements by hour.
• Gioia's explosion at the front end: not a D5 licence.
• Rules I set and logged during the stage: section 7's arrow rule (D5a-12, amended D5a-14); the representatives' rule (D5a-01, amended D5a-03, D5a-04 and D5a-06); the tie rule (D5a-02); at D5b, the re-reading rule for work_remained with four conventions and three overrides, the timing rule with one amendment after seeing its output (an empty window corroborates nothing), and the waterfall's rule, whose even-count convention I fixed after printing the sorted list.

Slips

At D5a-31 two Edits to one file went into one turn; at D5a-32 a stray shell assignment slipped into a command. Both were logged, and the rules were restated in the head. At D5b, one log line named a helper file before the file was written (the timing rule's list of 25 acts); the file was written next, with the 25 acts the line named. Also at D5b, two Edits to the head went into one turn; both applied once, checked by count, and the slip is logged.