The model read against the field, stage C4

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

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

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

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

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

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

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

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

What the field holds

The field model has two phases and nine processes.

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

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

What happened to the three claims

None of the three was overturned.

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

List 1: where the two agree

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

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

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

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

List 2: what only the field sees

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

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

List 3: where they disagree

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

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

The field's three limits of the room record

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

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

Findings bounded or changed by the field

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