Form pass, stage C1 (leg C1a-09)

This file is the form pass of stage C1, section 7. It holds the form-pass findings FP-01 to FP-08, and they exist here and nowhere else: no schema, no line in any JSONL. Stage C2 reads them from this file, by id. Their unit is the turn, not the topic.

These findings were never counted and never clustered. None has a line in assignments_final.jsonl. None has the three counts, a share in the chunk-share tree at stage D4, or a branch contrast at stage D5. They travel on exemplars under rule 5's carve-out. The figures below say how many communities and concept lines each finding covers. They describe the search; no placement arithmetic uses them. No gate was written or amended to make any of them look promotable.

What I searched, and at what limits

• The material. Every first-order concept in the store: 115,388 in 705 rooms. I read the participants' quoted words directly, not through second-order themes.
• The count. Every pattern went through mem.py codes --grep <re> --json, with no limit on the count and one logged read per pattern (out/_mem_reads-C1.jsonl). The helper is out/_analysis/c1_form_pass.py. The patterns, with the reason for each, are in out/_analysis/c1_form_patterns.json. mem.py matches the coder's label and note as well as the words, and ignores case. The helper keeps only the concepts whose quoted words match and reports both counts; every figure below is the quoted-words count. Where anchors or shape mattered (a reply that is only "On it."), a stricter pattern ran on the words alone: the text field of the pattern.
• Position. The forest coordinate is Dewey: 0 is the submission and the segment count is the depth. Depth 1 is a top-level comment; depth 2 or more is a reply.
• A coded reply. A coded concept by another author, in the same thread, whose coordinate lies below the concept's item. For a submission, any coded comment by another author in its thread.
• The line theme. The first theme on the concept's placement line in assignments_final.jsonl. A concept is cited when a placed theme's support_by_theme lists it.
• Baselines. 41.7% of all concepts are cited. 73.7% of all comments sit under a coded parent item. 33.5% of concepts are in submissions, 36.6% in top-level comments, 29.8% in replies.
• Grounding. Every quote below was found again with cite.py --grep in its room. Its concept id follows it.
• Language. The patterns are English.

Sweep 1: form

I swept for turn shape, position in a sequence, length and timing. The stage file asks: what is the cheapest act in this corpus, and how would I know?

The next table gives every concept in the store by its length in words.

Concepts of three words or fewer number 11,164 (9.7%), in 659 rooms. 4,045 of them are submissions, mostly titles such as "r/place", "April Fools" and "We did it!". A concept of three words or fewer draws a coded reply by another author in 20.9% of cases. The share is 28.8% for 4 to 10 words and 35.0% for 11 words or more.

The next table lists each form pattern. It gives the concepts and rooms whose quoted words match, the number of line themes those concepts sit on, and the largest line theme's share.

The cheapest act is the one-line reply that joins, assents, reports a part done or thanks. I know it by three signs in the record.

• Its length: the median is two words.
• Its position: 90.3% of these replies sit under a coded parent item, against 73.7% for all comments. The parents are border posts, calls to place, defence posts and proposals.
• What follows it: a concept of three words or fewer draws a coded reply in 20.9% of cases. The one-line reply closes its sequence and asks for nothing back.

A fourth sign is in the placements. 33.9% of these replies are cited as a placed theme's support, against 41.7% for all concepts. The scheme places them by the call they answer, and no theme names the act of joining. This is FP-01.

The record undercounts this act. The coders dropped items that carried no code and had no coded descendant. NieR's forest, for one, has 282 items: 121 coded, 12 bridges and 149 dropped. The pass cannot tell how many one-word replies are among the dropped items, so 590 is a floor.

Two more turn forms sit on many themes and are owned by none: the edited post (FP-02) and the talk of sleep and time zones (FP-03). The other patterns are owned or near it. "We did it" is T3-009's: it holds 64.1%. The canvas clock leans on T3-016 (28.1%). A marked loss spreads over the end and loss themes T3-009, T3-029 and T3-117.

Sweep 2: register

I swept for vocabulary that cuts across subjects. The stage file's rule is that a register that appears widely and is owned by no theme is a tier, not a residue.

The next table lists each register pattern with its concepts, rooms, line themes and largest line theme.

Two first counts were polluted, and I recounted them. "gg" matched discord.gg links, which made T3-014 hold 36.9% of the game words; with links dropped the pattern falls from 919 concepts to 291. "Ranks" and "squads" are game words in rocketleague and Rainbow6, so the military row was recounted on its core words (troops, soldiers, army, reinforcements, front line, battalion, brigade, regiment, siege, retreat, commander, recruits, deploy, platoon, legion, warriors, veterans, fallen). The state-and-war pattern is the core military words, territory and empire, attackers named as wrongdoers, and war, wars, battle, enemy, enemies, ally and allies.

What each register became:

• Owned. Diplomacy belongs to T3-010 and T3-149 (58.5% together). Pride belongs to T3-009. Trade leans on T3-010 (26.7%).
• Wide but not this event's. The craft words are the medium's own words, spread because every theme is about the canvas. Profanity and internet slang are the site's register. The pass did not compare either with the rooms' pre-event week.
• Wide, spread, and not read far enough. Kinship (253 rooms, largest line theme 9.8%) and faith and ritual (225 rooms; the count holds exclamations such as "holy shit"). Both are leads for stage C2, not findings.
• A tier. The vocabulary of state and war (FP-04), and the split of "we" and "I" by turn position (FP-05).

Sweep 3: what is not said

I swept for terms used without gloss, roles invoked without introduction and questions nobody answered.

The next table lists each pattern of this sweep with its concepts, rooms, line themes and largest line theme.

A first pattern for a gloss on the void matched 43 concepts. All were statements such as "The void is approaching", not glosses, so the row above uses questions only. The leaders row first held "chief" and "commander": in halo "Chief" is Master Chief, and "cmdr" is a title in the space games. The recount dropped both, with "officers" and "generals".

The next table gives every concept whose quoted words hold a question mark, by position and by asking word, with the share that drew a coded reply by another author.

What each pattern became:

• The rules are explained to whoever asks. The event is named in 684 rooms and explained in 115; the cooldown is glossed in 227 rooms, and 342 of those 454 glosses are replies, most often under a T3-016 parent. This is T3-016's ground, so it is no finding here.
• Other platforms lean on T3-014 (43.7%).
• Findings. The canvas-wide collectives, named and never glossed (FP-06). The room's question to itself, answered least (FP-07). Who leads, neither asked nor named (FP-08).

The findings

Each block below can be quoted whole. "Lines" are concept lines in the store, counted on quoted words; "communities" are rooms.

FP-01. The one-line reply is the cheapest act

• Statement. A member joins, assents, reports a part done or thanks in one to three words, under a coded call, proposal or border post, and the reply draws nothing back.
• Covers. 590 lines in 337 communities (the four one-line patterns and a bare salute, as one pattern). Median two words. 88 line themes, the largest T3-010 at 11.2%.
• Signs. 90.3% sit under a coded parent item (all comments: 73.7%). Concepts of three words or fewer draw a coded reply in 20.9% of cases (11 words or more: 35.0%). 33.9% are cited as a placed theme's support (all concepts: 41.7%).
• Exemplars. "On it." [fivenightsatfreddys/c0483]. "Did my part." [TeamDignitas/c0017]. "Agreed" [tf2/c0359]. "will do" [sips/c0047]. "I'll help." [southafrica/c0151]. "im in" [teamcube/c0002].
• Limit. The coders' dropped items are not seen, so the count is a floor.

FP-02. The edited post carries a running record

• Statement. A member amends a posted turn with "EDIT:" or "UPDATE:" lines as the canvas changes, so one turn holds the call, the new coordinates and the state of the fight, in order.
• Covers. 1,124 lines in 418 communities: 276 in submissions, 542 in top-level comments, 305 in replies. 101 line themes, the largest T3-010 at 10.7%.
• Exemplars. "Stay vigilant people. Vandals have been trying to destroy our beautiful creation all day. Help out with a dot when you can. Edit: We're losing this battle at the bottom. They're fucking with the spelling hard." [prequelmemes/c0462]. "In media arma ruamus! I suggest just north of the Greek flag, and below Deus Vult in the area around 426, 146. Should we do Red, Purple? edit: Head to 978, 440, all!" [latin/c0005].
• Limit. The pattern sees the marker only. The record gives the item's posting hour, not the time of the edit.

FP-03. Rooms time the work by who is awake

• Statement. Members time the work by the world's clock: they plan to take or hold space while another country sleeps, hand the watch over at bedtime and report what changed overnight.
• Covers. 362 lines in 219 communities. 64 line themes, the largest T3-005 at 13.5%.
• Exemplars. "We are working together now on making a second flag to the left side. We should cooperate before the yanks all wake up and take over." [newzealand/c0143]. "everyone in england will be asleep in a few hours tho so we can take over" [starcraft/c0087]. "I woke up this morning and tried to keep the BLM in as best shape as I could. Was tough though." [fullcommunism/c0222].
• Limit. The hour field counts hours since the canvas opened. The pass did not convert it to each room's local time.

FP-04. The vocabulary of state and war is the common speech of canvas work

• Statement. Members speak of pixels as a state speaks of land and army: troops, reinforcements, territory, empire, invasion, war, enemies, allies, griefers and traitors. They do so under any act, not only defence and borders.
• Covers. 4,759 lines in 571 communities. 145 line themes: T3-010 holds 14.9% and T3-005 13.0%. 42.4% are cited, the corpus rate. Its parts: the core military words 670 lines in 260 communities; territory and empire 1,345 in 378; attackers named as wrongdoers 1,637 in 442.
• Exemplars. "WE NEED EVERYONE TO RETREAT TO THE BASE AND HELP MAINTAIN IT RIGHT NOW" [thebluecorner/c0189]. "We need to claim our territory and put a black frame around the entire pineapple, and put r/trees under it" [trees/c0175]. "Canadian reinforcements, reporting in sir!" [ripcity/c0192]. "Our labour as core-soldiers has ended. Good job guys." [metalcore/c0003]. "I'm pissed because a lot of us put a lot of work into that logo and they came in with a brigade and scripts to destroy it." [rangers/c0192].
• A caution for scheme_v2.md and stage C2. The named words of T3-010 | T3-149 read attack, war, fight, battle, invasion, raid and conquest as naming an attack. This finding says such words are the common register, used even for builders ("core-soldiers"). The rule decides only between those two themes, and no gate is amended here. The doubt goes to the handback.

FP-05. The post speaks as "we"; the reply speaks as "I"

• Statement. In submissions, "we" words outnumber "I" words by 1.8 to 1. In top-level comments the two are level, and in replies "I" leads.
• Covers. "We" words: 33,472 lines in 694 communities. "I" words: 30,890 lines in 684 communities.
• Figures. Submissions: "we" in 28.8% of concepts, "I" in 16.2%. Top-level comments: 29.2% and 30.4%. Replies: 29.0% and 34.2%. The "we" share is flat across positions; the "I" share rises with depth.
• Exemplars. Submissions: "We got a spot in /r/place, thanks to Green Lattice! Start building!" [titanfall/c0102]; "WE NEED EVERYONE TO RETREAT TO THE BASE AND HELP MAINTAIN IT RIGHT NOW" [thebluecorner/c0189]. Replies: "I'll help." [southafrica/c0151]; "I woke up this morning and tried to keep the BLM in as best shape as I could. Was tough though." [fullcommunism/c0222].
• Limit. Submissions are shorter (median 9 words, against 11 to 13 in comments), which lowers any pronoun's share. Length does not explain why the "we" share stays flat.

FP-06. The canvas's large collectives are named as known actors

• Statement. Rooms name the void, the blue corner, the green lattice, the rainbow road and the purple as forces everyone knows. They ask for help against them or offer to join them, and nobody asks what they are.
• Covers. 3,605 lines in 453 communities, four of them the collectives' own subs. 118 line themes, the largest T3-005 at 17.4%. The void alone: 2,057 lines in 302 communities.
• What is not said. 128 lines in 57 communities put the void in a question. None asks what or who it is. The one gloss found answers a question that already assumed the name: "have you seen the void and erase? they are actively destroying art. they are the black and white blobs" [globaloffensive/c0732].
• Exemplars. "The void is approaching." [cubers/c0152]. "/r/homestuck here. Any chance you'd join us and /r/India in the fight against the void?" [undertale/c0161]. "We're suffering from imperial overstretch and fading like the blue corner." [ainbowroad/c1537].

FP-07. A room's question to itself, posted as a submission, is answered least

• Statement. A question posted as a submission draws a coded reply in 37.7% of cases, against 52.8% for a question in a reply. A submission that asks the room what to do ("should we", "can we") draws one in 36.2%.
• Covers. 13,354 question lines in 674 communities. In submissions: 5,072 lines in 559 communities, 3,158 of them unanswered, in 352 communities. "Should we" and "can we" in submissions: 943 lines in 290 communities, 602 unanswered, in 169 communities.
• Exemplars, each without a coded reply. "Dear r/funhaus, r/SC seems uninterested in r/place. So should we make the Undertaker?" [funhaus/c0245]. "Should we eat it or find a pact?" [ainbowroad/c0107]. "do we have a discord? i dont know which one is the right thread and its tedious refreshing both" [jerma985/c0036].
• Limit. An answer in a dropped item is not seen. The unanswered share is an upper bound. Rooms whose coders coded many titles and few comments raise it.

FP-08. Who leads is neither asked nor named

• Statement. Rooms seldom name a leader or an office and almost never ask who is in charge. When they ask, it is to find someone to bargain with or to dispute a decision already made.
• Covers. "Who is in charge", "who decides" and "who decided" are asked in 15 lines in 14 communities. Leaders, leadership, "in charge", a council or the organisers are named in 86 lines in 61 communities. Beside them, mods and admins are named in 1,307 lines in 349 communities, the largest line theme T3-023 (26.2%).
• Exemplars. "We don't have a structure, no one is in charge, you should open a post thus more Italians can read you." [italy/c0145]. "A4mGcpLJVXylPhwXPK6GuPkhcIw=, to/a5MmYJCHgPqLCuM6ClobMtPo=, 20Rw797WBr1bc/O7TuCXCPd95ig= , who's in charge of the Superman logo ?" [harrypotter/c0239]. "who decided on this? rainbows have enough of the map, they don't need inside our letters too." [rocketleague/c0695]. "Its not being vandalised at all. Who decides what is and what is not art? Its a personal thing. That space is an expression of this community." [halo/c0260]. "For the people who think black void lacks leadership, I have created /r/PerfectEntropy. I swear to be a loyal leader that will listen to our followers." [theblackvoid/c0814].
• My reading. The rooms take for granted that whoever posts a call may call. This reading is mine; the count shows only the absence of the question.

What the pass could not reach

The same list is in notes-C1.md, for stage E1 and the write-up's account of what the study cannot say.

1. Stance. A register or a stance is a property of a whole utterance. String matching finds the words, and it cannot tell play from earnest. "Canadian reinforcements, reporting in sir!" [ripcity/c0192] may be a joke or a pledge. FP-04 counts the vocabulary of war, not the stance of war.
2. Acts named by topic. No route through second-order themes reaches an act whose themes name what it was about rather than what it was. The one-line reply sits on the theme of the call it answers: FP-01's 88 line themes are topics, not the act of joining. The same holds for the edited post and the talk of sleep.
3. Dropped items. The coders dropped items with no code and no coded descendant. Short replies and many answers are among them. FP-01 is a floor, and FP-07's unanswered share is an upper bound.
4. Timing. The hour is the item's posting time, in hours since the canvas opened. The pass did not measure reply latency, the time of an edit, or each room's local time.
5. Case. mem.py's grep ignores case, so shouting in capitals, itself a register, was not counted.
6. Language. The patterns are English. Rooms that wrote in Portuguese, German, French, Czech and other languages are undercounted in every sweep, for example the barter in "Após negociações cedemos um espaço na esquerda da bandeira pra eles em troca de suporte para futuros projetos e paz com os raids" [brasil/c0333].
7. Links and images. A turn that is a template link or a screenshot has a URL for its words, and its register is invisible.
8. Who answers whom. The pass read the line theme of a coded parent item. It did not follow authors across turns, so it cannot say whether the caller answers the joiner.
9. The week before. Profanity and internet slang are wide. The pass did not compare them with the rooms' pre-event week, so it cannot say whether the event changed the register.