# Literature, stage C3: the model read against the explanation shelf

This file holds what the literature did to the model, leg by leg. The model is stage C2's resting state, pass 5 (`model-p5.md`). The notes and the record of each step are in `notes-C3.md` and the diary.

**How claims about the literature are marked.** `verified`: I opened the work on the shelf in this session and quote it, with the page the extraction names. `recalled`: I am working from memory, with author, year and the claim I attribute, so a reader can check it. The read tier was served whole this leg: Puranam, Alexy and Reitzig (2014); Felin and Zenger (2016, the SSRN manuscript, pages the manuscript's); Felin and Zenger (2017); O'Mahony and Ferraro (2007); Bechky (2006); March (1991). Nothing on the on-request tier was served.

**What the read log can and cannot show.** `_mem_reads-C3.jsonl` and `_cite_reads-C3.jsonl` record what was served, not why. They cannot tell a check of a quote or a count from an abductive read I failed to log. Each abductive read of this stage is listed below with the diary line logged before it ran. The other room reads of this leg were checks of instances the model already cites.

## Leg 1 (C3a): work that contradicts the model

Four works contradict the model, or explain its phenomenon with something it did not use. For each: the two claims, what in the record decides between them, which of three things is true (the accounts disagree about the world, about the setting, or are about different things), and whose claim the disagreement bounds.

### O'Mahony and Ferraro (2007): a shared basis of authority (verified)

- **Their claim.** "Before an organization can develop a form of governance, it must establish a shared basis of authority" (p. 1081). In Debian, de facto founder rule gave way to a recalled leader, then a constitution, then elected leaders valued for organization building. They conclude that "coordinating their efforts and managing interdependence grew problematic without the help of people managing the organizational structure" (p. 1100).
- **The model's claim.** Rooms aligned their placers mostly without decided order (C01; F-006: Decided order is placed in 46 of 705 rooms).
- **What in the record decides.** Most rooms built and kept their work within hours with no shared basis of authority: "Help us draw Metroid over at /r/place!" [metroid/c0001, h4.27] was answered two minutes later with the location and a report of the placed piece [metroid/c0002, h4.29]. The paper made me look for where a basis of authority does form (abductive read 1, below). Decided order gathers in rooms placed on a colour-faction theme or on vetting guests' requests to build.
  - 7 of those 39 rooms carry it (0.179), against 39 of the 666 other rooms (0.059).
  - Held to room size by `items_in_window` quartile, the 7 stand against a null mean of 2.7 (95th percentile 5, p 0.014).
  - The gap lies in the two smaller quartiles (5 of 14 against 13 of 339). In the two larger it vanishes (2 of 25 against 26 of 327).
  - None of the 56 rooms whose members asked a host for space carries it.
  - The factions appoint officers and lay down rules: "Looking for positions to fill!" [PurplePixels/c0057, h8.58]; "Good idea! Would you like to be Recruitment Overseer?" [PurplePixels/c0137, h8.81]; "I am the new temp leader in the discord chat please don't give up we will not lose our corner" [TheGreatGreenBox/c0051, h14.64]; "Mods, BAN HIM" [orderofthebluecorner/c0009, h3.87].
- **Which of the three.** The accounts disagree about the setting. Debian integrates many contributions into one code base over 13 years. Most rooms made one picture in 73 hours, and the half-built picture showed the next placer what was missing. Where the canvas comes closest to their setting, a small body governing a territory for others, their pattern appears.
- **Whose claim it bounds.** Both. It bounds mine as a condition (rule 16), written into F-006's superseding line: decided order is rare in rooms whose work is their own picture, and gathers in the small canvas-born factions that govern a territory. It bounds theirs: organizing a single work in hours needs no shared basis of authority, so their "must" holds for governing a lasting body, not for organizing as such.

### Bechky (2006): role-based coordination in temporary organizations (verified)

- **Her claim.** Common portrayals of temporary organizations "as ephemeral and unstable are inaccurate: Temporary organizations are in fact organized around structured role systems whose nuances are negotiated in situ" (p. 3). The generalized role structure travels between projects by careers, and crews enact it by enthusiastic thanking, polite admonishing and role-oriented joking (pp. 8-13).
- **The model's claim.** Strangers coordinated by a start, calls and a visible half-built work. The model's two roles, the starter (R01) and the envoy (R02), are taken up on the canvas.
- **What in the record decides.** The roles the rooms name are coined there: "Hi, I'll be the ambassador for WIT on /r/place, we arent trying to write over you guys." [littlewitchacademia/c0049, h62.87]; "Good idea! Would you like to be Recruitment Overseer?" [PurplePixels/c0137, h8.81]. Her enactment practices appear without a role structure, and they enact a norm about the work, not a role. "Wipe out the Dolphins. They're building." [nyjets/c0086, h47.85] is answered one minute later by "Nah, keep /r/place neutral." [nyjets/c0087, h47.87]. The one role a room brings in is the host sub's moderator, whose acts are the host's line around canvas talk (P20), not the canvas work.
- **Which of the three.** The accounts disagree about the setting. She names it herself: "This prompts consideration of how temporary organizing can be successful in settings without a generalized role structure" (p. 17).
- **Whose claim it bounds.** Hers. The canvas lies outside her scope: no careers carry roles between rooms, and nothing makes the room a total institution. The model is one answer to her open question for this setting, and nothing in it changes.

### Felin and Zenger (2016; 2017): the theory-based view (verified)

- **Their claim.** Organizing starts from an actor's theory, "a set of contrarian beliefs" that frames which problems to solve (2017, p. 258). "Valuable theories require a contrarian belief" (2017, p. 262). The theory reveals "an architecture of problems to solve" (2016, p. 9). Organizations with a clear theory attract those who share it by self-selection (2017, p. 266), and "a key outcome of hierarchy is systematically advantaging one actor's theory of value over another" (2017, p. 265).
- **The model's claim.** A member's start gives calls something to gather around (A02). What the room makes is mostly given by its topic: its characters, its logo, its land's flag (P02). A design argued in a thread is settled by a template posted in it, not by authority (A11), and decided order is rare (C01).
- **What in the record decides.** On the order of events the record agrees with them: a start comes before calls in 64 of 89 rooms carrying both (A02). On what the start is, it mostly disagrees. Rooms build the emblem their members already share. The nearest instance of their theory reframes an existing mark: "On /r/place , the bottom left corner is green and labeled GREENCORNER . I say we make an OG logo and change it to GREENWALL. Anyone down?" [opticgaming/c0191, h6.43]. It is answered "We're all gonna have to come together to get it done." [opticgaming/c0192, h6.45]. An argued design is settled by a template, not a ruling: "Maybe make it 20x20? Or just a purple W?" [udub/c0008, h55.02], then "20x20 is possibly a better idea... Will update template image and upload here." [udub/c0009, h55.09].
- **Which of the three.** They are about different things. Their theory is a contrarian belief about economic value held against a market. A room's start is mostly a proposal of a picture its members already share. The model's names, a start and a proposal, are the right ones for the rooms.
- **Whose claim it bounds.** Neither is bounded by the record. The open part is whether each room inherited, negotiated, contested or changed what it made. That is stage C3c's question on the goal, and it is left there.

### Olson (1965): collective action without selective incentives (recalled)

- **The claim I recall.** I believe Olson (1965), *The Logic of Collective Action*, holds that a large group whose members share an interest will not act to secure it without coercion or selective incentives, because each member gains whether or not they contribute. Puranam, Alexy and Reitzig (2014, p. 171, verified) cite Olson (1971) for "privileged groups that value the public good highly enough to contribute regardless of the (non) contributions of others".
- **The model's claim.** Large rooms built and kept marks with no coercion and no selective incentive beyond credit and thanks.
- **What in the record decides.** Nothing here. The record holds who spoke, not who placed, so members who never contributed are invisible, and a claim about them is an absence claim, marked weak. It would be decided by placement counts per account against each room's readership. The study does not use those, since the canvas is not a declared ground (rule 7).
- **Which of the three.** Most likely the setting. A contribution costs one pixel per interval, and the cheapest answer to a call is one line. The contradiction is reported as open.

### Works read and not taken as contradictions

- **Puranam, Alexy and Reitzig (2014), verified.** The standing claim of the contract's section 1: a form of organizing is "a specific set of solutions to the four universal problems that any organization must address in order to exist" (p. 166). It also rules out "goalless networks, and crowds (but not mobs)" (p. 164). It is put to the structure at stage C3c, by design, and not decided twice. Read for this leg it resembles the model more than it contradicts it. The final product as "its own representation" simplifies coordination (p. 172). Authority in open source lies in the right to accept or reject contributions and membership (p. 173).
- **March (1991), verified.** No contradiction. Its organizational code, which newcomers learn and which learns from them, and its point that "the development of knowledge may depend on maintaining an influx of the naive and ignorant" (p. 86), bear on the residue of six pass 5 rooms (what a mark brings back into its room). That is stage C3b's material.

### The abductive reads of this leg

1. **Prompted by O'Mahony and Ferraro (2007).** Logged before it ran (`mem.py log --kind abductive`, C3a). It looked for whether decided order gathers in rooms that rule on other rooms' works, held to room size (`out/_analysis/c3a_decided_order_split.py`, output `c3a_decided_order_split.txt`). It bounded F-006 (a superseding line with `literature`, `abductive: true` and `prompted_by`) and wrote a C01 line in `model/history.jsonl` with the same flags. No element statement, arrow or tier changed. Move: relating or contrasting, snapped as C3-move-relating-48.

The read also surfaced one turn I did not act on: "jiAPggk+x8m5bwxd/l61z1oUQxA= was a fellow comrade during the button. He is a very good choice for this role!" [PurplePixels/c0165, h23.72]. It names a tie from an event before the canvas. The model states colour factions as bodies the canvas gathered, whose faith is not a tie from before the canvas. One turn does not change that, but it is a doubt carried to the next legs.

### Switch records

None. F-006 rested on a count across rooms and still does; the bound is another count across rooms. No name moved from the participants' words to the literature's, and no claim moved between the rooms' words and a pattern across rooms.

## Leg 2 (C3b): work that resembles the model

### Distant fields, and the mechanisms (section 4a)

The arrows whose mechanisms were hardest to write are the ones resting least on a count. Two are theorised: the template settling a design (A11) and the one-line answer to a call (A12). Four are thin: the settled border (A05), the move after doubt (A10), help along a border (A14) and coalitions (A19). One is partly constitutive: the refusal of an attack call (A16). For each, I asked what literature outside organization studies describes the same move. All six distant works below are `recalled`: none is on the shelf.

**Conversation analysis: the one distant field that supplied a mechanism.** I believe Schegloff and Sacks (1973) set out the adjacency pair: a first part, such as an invitation or a request, makes a fitting second part the next thing due. I believe Pomerantz (1984) and Levinson (1983) set out preference organization: acceptance is the preferred second and comes bare, refusal the dispreferred one and comes marked, often with an account.
- **Fit.** It describes the move of two arrows. The one-line answer (A12) is the preferred second to a call. The refusal of an attack call (A16) is the dispreferred second, and its account is where the room's norm gets said.
- **The prediction tested** (abductive read 2, below; F-014). Refusals of a call carry a reason, and acceptances do not. Of 80 seeded pairs, 57 had a first part that calls for or proposes an attack. Refusals gave a reason in 23 of 38 and acceptances in 2 of 14 (one-sided Fisher p 0.003). The other half of the prediction failed: refusals were not longer (median 9.5 words against 11.5).
- **What changed.** Both mechanisms are rewritten in `model/arrows.jsonl` and `model-C3.md`, with the stage C2 sentences kept as `mechanism_C2` and the work named. Each failure clause gains the mechanism's own observation: joins as reasoned as refusals, or refusals as bare as joins. A12 stays theorised. Its order is never counted, and calls to place were not tested; one bare refusal of a call to build is on record ("No." [formula1/c0015]).
- **What it explains that the model did not:** why a call is cheap to answer (acceptance needs no reason), and why restraint arrives carrying the room's norms ("our task is to create, not destroy" [placestart/c0117]; "Why? That'll just cause them to want to attack us" [uoft/c0115]).
- **What the model has that it does not:** that the acceptance is followed by labour on a shared surface, by strangers who never meet.

**Threshold models of collective behaviour.** I believe Granovetter (1978) holds that each person acts once enough others have, so that a crowd's outcome turns on the spread of thresholds and on people seeing how many have acted. `structure.md` already names this as what Critical mass may be mistaken for.
- **Fit.** It would supply the mechanism of the concept's claimed function: the replies under a call as the room's head count.
- **The prediction tested** (abductive read 3; F-015, weak). It failed. Of 40 sampled first turns on the doubt-about-numbers theme, 11 judge the room's own hands. None of them rests on who answered: 3 rest on the readership's size, 2 on the canvas, 1 on both, 5 on nothing.
- **What changed.** No arrow. The concept's head-count claim is dropped (`concept-C3.md`).

**Behavioural ecology: the "dear enemy" effect.** I believe Fisher (1954) named it and Temeles (1994) reviewed it: a territory holder that has settled a boundary is less aggressive toward its established neighbour than toward strangers, because the neighbour no longer threatens the territory and contesting again costs more than it gains.
- **Fit, in part, with the settled border (A05).** It says why a settled border keeps the peace.
- **Its distinctive prediction,** that aggression is kept for strangers, was not tested. The read was declined: no query tells whether an attack's target is a settled neighbour or a stranger, and settling it means reading every attack call's target against the room's border partners.
- **Not rewritten.** The part that fits restates the stage C2 mechanism; the part that would add something is untested.

**Social psychology: superordinate goals.** I believe Sherif (1958), and Sherif and colleagues' Robbers Cave study (1961), hold that a goal neither of two rival groups can reach alone turns them to cooperation and lowers their hostility. Walt's (1987) balance of threat in international relations says much the same of alliances.
- **Fit with coalitions under attack (A19):** it names what the arrow's mechanism already says, that rooms whose works face the same threat join.
- **Its distinctive prediction,** that partners stop attacking each other, was not tested. The read was declined: coalition pairs cannot be recovered by query.
- **Not rewritten.** It would add a name, not a test.

**Game theory: focal points.** I believe Schelling (1960) holds that in tacit coordination people converge on the option they expect others to expect. I also believe, but cannot verify here, that he held a suggestion can make an option focal.
- **Fit with the template settling a design (A11).** A posted template settles a design because each placer expects the others to follow it, not because anyone can enforce it. That would also say why the template works whether it comes before the argument or after (A11's bound).
- **Not rewritten.** The fit rests on the part I cannot verify. The arrow's order is at chance, and its distinctive prediction, disputes where two templates are in use, would need every template thread read. Declined.

**Animal contests: the war of attrition.** I believe Maynard Smith (1974) holds that a contestant gives up when its costs pass what the resource is worth to it.
- **Fit with the move after doubt (A10):** A10's mechanism is already a judgment of the room's own hands. The war of attrition adds the worth of the spot, which the record does not measure.
- **Not tested and not rewritten.**

### The resembling works on the shelf (verified)

- **Puranam, Alexy and Reitzig (2014).**
  - *What it names that I named differently.* Self-selection into tasks (p. 171) is the model's join (P15) and the start it answers (R01). The final product as "its own representation" and transparent task division (pp. 172-173) are my Stigmergy and Standardization of output; Stigmergy's declaration is amended below. Authority as the right to accept or reject contributions and membership (p. 173) is the hosts ruling on guests, a boundary the model does not reach.
  - *What it explains that the model does not:* why self-selection, transparent task division, intrinsic reward and visible collaboration come together as complements (pp. 173-174).
  - *The reverse:* the model shows coordination through the visible work where no founder or core laid the architecture out.
- **Bechky (2006).**
  - *What it names:* enthusiastic thanking and polite admonishing (pp. 11-12). These are my completion ritual's credit to others and the room's restraint.
  - *What it explains that the model does not:* how practices carry from one project to the next through careers.
  - *The reverse:* the practices without roles, and (F-014) the admonishing's reason states the room's norm.
- **O'Mahony and Ferraro (2007).**
  - *What it names:* a shared basis of authority, and leaders valued as organization builders (pp. 1081, 1091). That is my Decided order; its declaration is amended below.
  - *What it explains that the model does not:* how a community comes to govern itself over years.
  - *The reverse:* organizing without governance in hours, with the small canvas-born factions as the canvas's nearest case (C3a).
- **March (1991).**
  - *What it names:* an organizational code that newcomers learn and that learns from them, and "the development of knowledge may depend on maintaining an influx of the naive and ignorant" (p. 86). These are the host sub's line around canvas talk (P20) and the residue of six pass 5 rooms, where a mark brings readers to the room and the room fears them (Visibility returns, unused).
  - *What it explains that the model does not:* why a code may need the newcomers a room fears.
  - *The reverse:* the rooms court and fear the newcomers their mark draws. Not tested here; what a mark brings back is not an element.
- **Felin and Zenger (2016; 2017).**
  - *What it names:* self-selection to a theory (2017, p. 266). That is my calls gathering around a start (A02).
  - *What it explains that the model does not:* why a contrarian proposal draws those who share it.
  - *The reverse:* starts that are mostly the emblem a room already shares.

### The concept (section 4b)

The one-line enrolment is a relabelling. Its form is conversation analysis's preferred acceptance (recalled), and the account asymmetry held where tested (F-014). Its claimed function, the replies as the room's head count, failed its test (F-015, weak). It is renamed as borrowed, "the preferred acceptance". What the material adds is a setting: written, public, given by a stranger to a stranger's call to labour.

The nearest three short of that name:
- self-selection into tasks (Puranam and colleagues 2014, verified), which names the choice, not the public reply;
- slacktivism (recalled), which stands in for action, where the acceptance comes before it;
- the conditional pledge (recalled), which is conditional, where the acceptance is not.

The verdict sits close to the third outcome, a relabelling that adds nothing. Stage C5's propositions should not lean on a named concept. `concept-C3.md` is written whole, and `concept.md` stands.

### Declarations amended (section 6)

- **Stigmergy (T4-007).** Its `mistaken_for` now names the transparent task architecture of open source and Wikipedia (Puranam, Alexy and Reitzig 2014, verified, pp. 172-173). There a founder or a core lays out the architecture; here no one does.
- **Decided order (T4-011).** Its `mistaken_for` now names a shared basis of authority (O'Mahony and Ferraro 2007, verified, p. 1081). A decided element here binds one work for hours; a basis of authority is a lasting consensus on who may decide.

Each is a `tier_history.jsonl` line with the old line as `was`, move relating or contrasting, snapped as C3-move-relating-49. No fourth-order theme or dimension was renamed, and the third-order themes keep their descriptive names. `structure-C3.md` carries both amendments.

### The abductive reads of this leg

Each was logged before it ran (`mem.py log --kind abductive`, C3b).
2. **Prompted by conversation analysis** (Schegloff and Sacks 1973; Pomerantz 1984; Levinson 1983; recalled).
   - *What it looked at:* reply pairs to attack moves, drawn by theme through `mem.py codes --fourth T4-020` and `T4-015`, a seeded sample of 40 rooms each, read whole under rules written first (`c3b_ca_pairs.py`, `c3b_ca_codes.json`, `c3b_ca_tally.txt`).
   - *What it changed:* F-014 written; the mechanisms of A12 and A16 rewritten (C3-move-relating-50).
   - *What it showed beyond its question:* the theme a reply sits under does not track its stance.
3. **Prompted by threshold models** (Granovetter 1978; recalled).
   - *What it looked at:* the first turn on the doubt-about-numbers theme in 40 seeded rooms, read whole under rules written first (`c3b_threshold_sample.py`, `c3b_threshold_codes.json`).
   - *What it changed:* F-015 written; the concept's head-count claim dropped.
   - *What it showed beyond its question:* a ground the rules did not foresee, the readership's size, coded apart.

Reads declined, each with its reason above: the dear enemy effect (A05), superordinate goals (A19), focal points (A11), the war of attrition (A10).

### Switch record: the concept

- **The work and the cue.** Conversation analysis (recalled). The cue: the bare "I'm in" under a call read as a preferred second pair part.
- **What moved.** The concept's name moved from my coinage, "the one-line enrolment", to the literature's, "the preferred acceptance". Its form claim moved from exemplars, the form pass's lines that are never counted, to a pattern across rooms (F-014). Its function claim was put to a pattern across rooms and failed (F-015).
- **What is redone or rechecked, and where.** The mechanisms of A12 and A16 (this leg) and the concept (`concept-C3.md`, this leg). Stage C5 reads `concept-C3.md`, not `concept.md`, through the manifest.
- **What differs in the output.** The concept is borrowed, not coined. Its head-count function is gone. Two arrows carry a mechanism from the literature.
- **Why the state after the switch serves the claim better.** The concept now carries a test that could have failed. Half of it held; the half that failed is dropped, not carried.
- **The findings line.** No earlier finding is superseded, since stage C2 wrote the concept in `concept.md` and in no finding. F-014 and F-015 are new lines with literature ids.

## Leg 3 (C3c): the four universal problems, put to the structure

**The claim.** Puranam, Alexy and Reitzig (2014, verified) hold that any organization must solve task division, task allocation, reward provision and information provision. Solutions to the four are "individually necessary and collectively sufficient" (p. 166), and a form of organizing is defined by its set of solutions to them (p. 166). Their definition of an organization assumes a multiagent system with "identifiable boundaries" and goals at the level of the system (pp. 163, 166).

**How it was put.** The claim was put to the structure and the model as they stood at the C3b close. Nothing was revised to fit it. The one written operation is `mapping-C3.jsonl`: one line per fourth-order theme, mapped to one problem or to none, with a clause of why. Each mapped line says what this material's version of the problem cannot do. Each unmapped line names the test it meets. `c3c_mapping_check.py` checks the file against the tier and counts the rooms per problem.

**The result in one line.** Nine of 28 fourth-order themes map to one of the four, and 19 do not (F-016).
- Information provision: 4 themes, 555 of 705 rooms.
- Reward provision: 2 themes, 543 rooms.
- Task allocation: 2 themes, 394 rooms.
- Task division: 1 theme, 237 rooms.
- Any mapped theme: 675 rooms.

Every count here is of rooms whose coded talk sits under a theme. It is not a count of rooms that solved a problem.

**The reads of this leg.** All room reads of this leg were counts through `mem.py rooms` and `mem.py codes`, and quotes served through `cite.py`. None added or changed a theme, an arrow or an element. The goal counts answer the stage's own question (section 5) and wrote F-017 with Felin and Zenger as its literature. I did not log them as abductive, because they are the stage's design and changed nothing in the structure or the model. A reader who counts every read a paper prompted as abductive should read F-017 as one.

### Two themes answer by construction

Two fourth-order themes already carry one of the four's names under their declarations.

- **Mobilization (T4-005), allocation.** Its declaration's `changed` clause says "no one can hold a member's minutes or allocate them". A call offers a task, and whoever answers takes it. That is allocation by self-selection (p. 171).
  - *What this material's version cannot do.* It cannot assign a member to a task or hold one to it. The call only offers, and a room with no answers has no one to allocate.
  - *Would the frame have cut it where I did?* Nearly. The frame takes allocation as one problem with several solutions, self-selection among them (p. 171). It would put Mobilization's calls and Decided order's assignments under one problem. My cut keeps them apart because the rooms keep them apart: calls in 345 rooms, a vote in 18, one member put in charge in 6. One member would leave: cheering the builders on (23 rooms) is an inducement, so the frame would move it to reward.
- **Completion ritual (T4-026), reward.** Its question is "How a room pays members no one could pay". The frame defines reward provision as "mapping a set of rewards (both monetary and nonmonetary) to the agents in the organization in order to motivate the agents to cooperate" (p. 165).
  - *What this material's version cannot do.* No one can pay, promote or withhold. Credit is given in words by peers, after the work, to anyone who claims a part, so it can induce only by expectation.
  - *Would the frame have cut it where I did?* No. The frame would cut through it. Crediting who made the work (156 rooms), reporting one's own placing labour (60) and prizes (7) map something to agents. Celebrating the finished work (442) and announcing the mark is up (54) map nothing to anyone; they mark the work. My theme joins the two because the rooms do them in the same turns, at the same moment. The frame would take reward out and leave the celebration with no problem to belong to.

### 1. What I expected

`prior.md` does not name the four problems. The substitution held (`notes-C3.md`). Its kinds and its refusals still speak to each problem.

- **Division.** It expected "Instructions for placing. Coordinates, templates, grids, pixel maps, overlays, outline-before-fill orders, colour guides." Found: Standardization of output, in 237 rooms; sharing coordinates, templates and how-to, in 207.
- **Allocation.** It expected "Who does the work. One or two members carrying it; a self-appointed leader; a vote; a chief elected; members unable to bind the crowd; a representative or diplomat for the room." Found, but thin: a vote in 18 rooms, one member in charge in 6, elections in 2. The members unable to bind the crowd are the model's claim C01. The representative is the envoy, R02. Its "Calling and gathering" kind is allocation by self-selection, and that was found richly: calling members in to place, 345 rooms.
- **Information.** It expected "Moving the talk off the thread. Discord, IRC, Telegram, Skype, a second sub, a private sub, a stream chat; plans brought back to the thread; members outside the venue missing the plan or refusing the venue." Found: moving planning into a chat in 263 rooms, announcing what the chat decided in 33, disputing the chat's authority in 9.
- **Reward.** It refused this kind: "Reward and motive. The rooms rarely say why a member placed a pixel, beyond pride, fun, a joke or loyalty to a team or nation. A kind for what the work paid its members will be thin; thanks and credit are talk about the work, not reward." Found: a reward offered before the work is thin, as expected (9 rooms). Credit after the work is rich (156 rooms), and my C1 declaration called it pay. `prior.md` and my structure disagree. Part 4 takes a side.
- **The goal.** It expected "Settling what to act on will often be settled by the canvas before the room spoke (the linked work placed from the first hours), by a host's terms, or by one member's start. Votes and polls will be rare and late." Found:
  - one member's start more often than the other two: a member proposes the room's mark in 166 rooms, median first hour 12.7;
  - the canvas before the room spoke less often: the room's mark found already placed in 43 rooms, median first hour 32.0;
  - a host's terms: asking a host for space in 52 rooms;
  - votes rare (18 rooms) and only partly late (median first vote at hour 42.4; 7 of 18 before hour 24).

**What turned up only where the material was thin.** Division among teams (5 rooms), elections (2), prizes (7) and timing a mass placement together (2). Each is a textbook solution to one of the four, and each is a rare-tier theme.

**What `prior.md` holds that the structure has no room for.** Its first refusal: "Deliberation off the record ... the material will give only 'a decision returned from a venue'." The structure holds the venue and the decision returned. It has no theme for how a venue divided or allocated the work.

### 2. What in the structure speaks to the claim

The next table lists the nine mapped fourth-order themes. For each it gives the problem, the rooms carrying any member, the largest member, rule 5's gate for its members, and who put it there. Every member's gate is `all` (every room had the opportunity), except Attribution's, whose gate is `work` (the room had a work of its own). The gates and counts are read from `structure-C3.md` by `c3c_rule5_members.py`.

| Fourth-order theme | Problem | Rooms of 705 | Largest member (rooms) | Gate | Put there by |
|---|---|---|---|---|---|
| Standardization of output (T4-008) | division | 237 | sharing coordinates, templates and how-to (207) | all | the material: a template is the frame's own kind of division artifact (p. 165) |
| Mobilization (T4-005) | allocation | 370 | calling members in to place (345) | all | its declaration, by construction |
| Decided order (T4-011) | allocation | 46 | putting decisions to a vote (18) | all | me: the theme holds the rooms' rare decided elements, and allocation is one of them beside oaths and excluding vandals |
| Completion ritual (T4-026) | reward | 522 | celebrating the finished work (442) | all | its declaration, by construction, against `prior.md` |
| Visibility returns (T4-025) | reward | 117 | recruiting canvas visitors (76) | all | me: the return goes to the room, not to a member |
| Sensemaking (T4-003) | information | 283 | explaining what the canvas is (232) | all | the material |
| Stigmergy (T4-007) | information | 348 | building and reporting the mark (237) | all | the material; the frame names the product as "its own representation" (p. 172) |
| Backstage decision-making (T4-010) | information | 276 | moving planning into a chat (263) | all | the material |
| Attribution (T4-019) | information | 155 | tracing who changed the work (119) | work | me: it tells the room about a change, after the work exists |

Three of the nine mappings are mine more than the material's: Decided order, Visibility returns and Attribution. Two rest on declarations I wrote at C1: Mobilization and Completion ritual.

### 3. What the structure carries that the claim has no place for

The remainder is 19 fourth-order themes. Each was tested as a different mechanism, a renamed instance, a change of level or an evidence gap. The test is in each line of `mapping-C3.jsonl`.

- **A change of level: between rooms (7 themes).** Territoriality, Live and let live, Negotiated order, Reciprocity, Meta-organization, Repertoire of contention, Rivalry. The frame's organization has boundaries; these are relations across them. Negotiated order alone is in 467 rooms. Reciprocity is also a renamed instance one level up: rooms ask rooms for help and thank allies, with rooms in the place of members.
  - "Sure thing, but please take it like one pixel away from the army bomb so that the whole space looks better ;-;" [bangtan/c0085, h71.72]
  - "We are trying to create a heart with both flags in it" [AmericanFlaginPlace/c0396, h62.03]
- **The frame's premises, made on the clock (8 themes).** The frame assumes the boundary and the goal. Six themes make the boundary and the membership: Keying, Boundary work, Frame bridging, Flagging the nation, Neo-tribes, Symbolic boundaries. A host sub decides during the event whether the canvas work is its own: "Aaa fue todo en el mismo post? Yo pense q iban a ser varios post, igual con el cancer de los píxeles ni abri el sub jaja" [argentina/c0525, h81.31]. My translation: "Oh, it was all in the same post? I thought there'd be several posts; anyway, with the pixel cancer I didn't even open the sub, haha." Two themes make, size or drop the goal: Collective representation and Collective efficacy (part 5).
  - "Okay, I'll send out the message! Good effort anyway." [raocow/c0027, h58.42]
  - "Let it happen" [rutgers/c0194, h55.02]
- **A different mechanism (1 theme).** Workarounds multiplies hands under the rate limit: "Modified script to fix Buzz in /r/place" [gatech/c0110, h61.56]. This was the closest call. A script is a machine given a task, which is allocation. But what holds the theme together is a change in the technology of production, which the frame holds fixed. I kept it unmapped.
- **The work itself (1 theme).** Repair work is in 526 rooms, the widest theme in the tier. It is the task done again, not a solution to organizing it. One member, covering the night shift (24 rooms), allocates by who is awake. Repair and information meet in it: "Saw someone place a green dot on one of the spiders legs, didn't know it was supposed to be going there so I immediately covered it up again." [australia/c0327, h67.83]
- **After the clock (2 themes).** Collective memory and Transition. They hold what the organization leaves and what outlives it, a change of level in time.
- **An evidence gap.** None of the 19 is unmapped for want of evidence. The gap is elsewhere: how a chat divided and allocated the work is off the record. "consensus on discord is we needed one spot and to have a mod sticky if it was going to work" [indieheads/c0144, h32.11]

**Why it extends the framework.** There are two extensions, each specific enough to be wrong.
- The first: an organization with no given goal and no given boundary must make both while it works. Eight of the 19 themes do that. The frame starts after they are made.
- The second: an organization on a shared, finite surface must handle its neighbours. Seven of the 19 themes do that. The frame describes one organization at a time.

`prior.md`'s forms already differed "in where the work was coordinated and on whose terms the room held its space". The first half is the four problems. The second half lies between rooms.

### 4. Which of the four the structure reaches richly, thinly, or not at all

- **Information provision: richly.** Four themes, 555 rooms. The half-built picture tells the next placer what is missing, and chats enrich the channel. The thin part is what was said in the chats. That limit is in the material.
- **Reward provision: richly as credit after the work, thinly as an inducement before it.** Credit is in 156 rooms and celebration in 442. A reward offered before the work is in 9: "As an insentive, for every person who joins in and comments below I will post 5 pig gifs! No limit!" [Pigifs/c0036, h48.94]. I take a side: these rooms did not provide rewards in the frame's sense. To induce, an offered reward must be announced where the call is, and calls are public. So an offered reward is the one solution the instrument should see if it was there. Credit after the work maps words to members, but nothing in the record shows that it moved anyone to place. On this point `prior.md` was right and my C1 declaration overreached. The absence claim is weak: it is about small rooms writing in public.
- **Task allocation: richly as self-selection, thinly as assignment.** Calls are in 345 rooms. Decided order is in 46: a vote in 18, one member in charge in 6, division among teams in 5. The night shift is in 24. The limit is partly in the material: an assignment made in a chat to the chat's members never reaches the thread, and chats posted their decisions back in only 33 rooms. I take a side all the same: most rooms did not assign. No one could hold a member to a task, and the cheapest answer to a call was one line and a pixel. Rooms with large chats are the likeliest exceptions. This absence claim is weak.
- **Task division: moderately, and only as an artifact.** A template or coordinates appear in 237 rooms. Division among members or teams appears in 5. The rooms divided the picture into pixels anyone could take. They did not divide the people. So division by artifact and allocation by self-selection come apart. That is the open-source pairing the frame describes (pp. 173-174), without the founder or core who lays the architecture out.
- **Not at all: none.** All four appear in public talk.

**Where each limit lies.** For allocation and information, in the material: chats are off the record. For reward, in the rooms, as I read it above. In the coders' selection, any assignment or offer made in a thread would have been coded, since both move the work. In my own pruning: prize-giving sits in Completion ritual, one member of eight, and two rare-tier themes have no rooms in the store (recruiting quietly to avoid attackers; moderators disowning the canvas work).

Stage E1 inherits this paragraph. These rooms were seen to solve information and to allocate by self-selection. They were seen rarely to assign, and rarely to offer a reward before the work. What a chat decided, they were not seen at all.

### 5. The goal

**Where the making of a goal sits.**
- In the structure, it sits in Collective representation (T4-006, 483 rooms), outside the four problems. Its contest sits in Boundary work. Its sizing and abandonment sit in Collective efficacy. Its change after a loss sits in Territoriality (relocating). A goal set after the clock sits in Transition.
- In the model, it sits in the starter (R01) and the room settling its mark (P02). A start gathers calls (A02), an argued design is settled by a template (A11, theorised), and a room that judges it has too few hands moves (A10).

No theme or dimension gathers the goal as such. That is a finding about the structure: the goal is scattered across five themes, because it was never a code's object.

**Whether the rooms inherited, negotiated, contested or changed it** (F-017; modes placed by me from the third-order themes' names, counted by `c3c_goal_counts.py`):
- **Inherited, 152 rooms.** The homeland's flag in 96, national emblems in 39, the room's mark found already placed in 43, a sign others began adopted in 6. "I saw one in the top right that said /r/anime. It was rather small, but it was there." [anime/c0177, h69.66]
- **Proposed by one member, 166 rooms.** I kept this apart from negotiation: a proposal others join is a start. 65 of these rooms also argue the design.
- **Negotiated, 289 rooms.** The design argued in 281, a vote in 18. "Stop adding periods, the template is wrong. I used a screenshot post-summoning release to make it." [2007scape/c0230, h17.72]
- **Contested, 152 rooms.** Mostly over whether the canvas belongs in the host sub at all: arguing the canvas's worth in 76, objecting to the canvas flood in 72.
- **Changed, 190 rooms.** Relocating after losing the spot in 116, upkeep chosen over expansion in 43, effort concentrated on fewer pieces in 29, quitting under strain in 20. "I have dishonored my family by joining the purples" [GreenCorner/c0107, h25.70]

The modes overlap: 49 rooms both inherit and negotiate, and 93 both negotiate and change. 515 rooms carry at least one of the four modes.

**Against Felin and Zenger.** Their chosen problem rests on an actor's contrarian theory (2017, p. 258). Here the problem was mostly inherited, and the solution negotiated. The room already had its sign. A member proposed which picture of it to make, and the room argued over the pixels. This bounds no claim of theirs (C3a: about different things). It says what the chosen problem looks like where no one can choose for others.

**What the setting did to the four problems.** The goal is a picture, and a picture can be stated exactly. So one artifact can state the goal and divide it: the template (A11, theorised). The frame says division knowledge "is more likely to exist for well-understood goals" (p. 165), and a picture is as well understood as a goal can be. The half-built picture informs, and members join a sign they already share. I tested the first claim at room level and it is weak. An argued design goes with shared coordinates in 94 of 281 rooms, against 113 of the other 424 (not held to size). So I do not claim that settling the goal divides the work in most rooms.

### 6. Whether the material supports the claim, contradicts it, or is silent

- **It supports a weak form.** Each of the four appears as public talk, and 675 of 705 rooms carry at least one mapped theme.
- **It is silent on necessity.** The claim holds "whether or not anyone says so". The 30 rooms with no mapped theme say nothing either way, and neither does any room's silence on a problem. Every such absence claim is weak.
- **On reward, the frame cannot lose here.** It asks for inducements "extrinsic or intrinsic", and only "if its constituent agents need to be motivated to contribute" (p. 165). Pride and fun count as intrinsic, and a pixel costs a click. The claim holds trivially, so the material cannot test it. Taken as rewards mapped to agents before the work, the material leans against it in all but 9 rooms (weak).
- **On sufficiency, the material leans against it, as I read it.** The 19 remainder themes cover talk in 694 rooms. Telling the canvas's forms apart needs the order between rooms and the making of boundaries and goals, as well as the four. Stage D4 can test this when forms are built from adaptation keys: do the forms differ on the four, or on the remainder? Until then it is my reading.

### 7. Whether the claim is answerable with this material

In part.
- **Answerable:** which solutions to each problem appear in public, how often, in what order, and alongside what.
- **Not answerable:** necessity. The evidence is talk, there is no denominator of groups (contract section 5), and a group that solved a problem in silence is invisible.
- **Answerable later, not here:** sufficiency for telling forms apart, at stage D4.

For the claim as stated, a claim about necessity, the structure does not speak to it.