r/place A fruit fly for organization science

out/figure-C5.md

Saved at r/norway: 6.1 local model, R6. This reading copy substitutes participant identifiers in saved text; it is not a new interview response. Reading Markdown.

Participant handles in these reading copies use the pixel stream's identifiers: base64(SHA1(username)), case preserved, without a salt. These are linkable pseudonyms. Profile links are removed; missing-author markers remain. Original research files are unchanged. Quote offsets refer to original text. Source and reading-copy hashes are listed separately.

Source commit: c070d990be88, 2026-10-23T12:38:38+02:00. Saved-state date: not recorded. Not recorded in the catalogue; source commit date is not a close date. Commit date and saved-state date are distinct.

Declared saved-state supplement. Member: workspace/out/figure-C5.md. Original SHA-256: 9894a729920d894c783d822012efaccf864c469c676b6d6d9822e000822416c9. Reading-copy SHA-256: 9894a729920d894c783d822012efaccf864c469c676b6d6d9822e000822416c9.

Dynamic model figure specification

Use the same retained model in both views, once with theorised arrows enabled and once without. There are no theorised arrows, so the views should be identical. Do not add links among isolated processes. Every arrow has a proposition tag and a source instance. Read labels as activities, not institutional actors.

Boxes and arrangement

Use a left-to-right request-answer-acknowledgment layout. In the left column put P02, Seeking room or restraint from people addressed as canvas claimants. In the middle put P03, Answering spatial claims with asserted terms of occupancy or support, and P04, Locating an operating audience and delimiting this room's responsibility. In the right column put P05, Acknowledging substantive replies and stating how to proceed.

Below that connected portion, show the retained unlinked activities: P01, Specifying and contesting contributions to the flag; P07, Accounting for effort already contributed or limited; and P06, Remembering affiliation after the game. These boxes have no causal connectors. They preserve instruction, effort report and remembrance rather than conceal them in one execution box.

There is no independently grounded condition node. Requests occasion answers, and the answer activities mediate the limited observed movement toward acknowledgment; no arrow promises compliance. D01 is a contribution-and-entitlement aggregate, not a causal connector. T4-003 remains dimensionless.

Place an explicit marker: imposed placement stop at hour 73. It is a contextual clock boundary, not a new model element or evidence that a group dissolved. Live requests and replies precede it; retrospective P06 follows it. Some activities span different observed times, so the column layout is not a universal timeline.

Arrows and instances

Arrow Source and target Proposition tag Instance and mechanism Scope annotation
A01 P02 to P04 N01 In E-32, Texas's request c0066 (6340w3) receives c0067 (dfrbw8a): "Go to r/norge". Assigning an operating audience changes the offered address for the request, not its spatial permission. Episode instances retained in the arrow register: E-32, E-35, E-29. This is instance coverage, not a community or behavior prevalence estimate.
A03 P02 to P03 N02 In E-47, the FFXIV request at 637igs receives c0105 (dfrvohp): "No, we have plans for some artwork ourself." The answer makes asserted occupancy terms explicit. Other recorded instances include Madeon exclusion, Factorio reassurance, Texas exclusion and a pact report. No mandate or implemented policy is inferred.
A02 P03 to P05 N03 In E-47, c0106 (dfrx3ig) explicitly responds: "Duly noted, thanks for the responses everyone, we'll try to look elsewhere." The requester treats replies as consequential and states an intention. E-20 supplies contrasting thanks after a reported pact. This proposition is thin beyond explicit acknowledgment; the direct-negative test is incomplete.

All displayed instances are exact quotations resolved through cite; full attribution is in account.md and data_structure.md. Arrows rest on retained code-linked answer relations, not on a new measurement of intervals or mere adjacent timestamps. The arrow register's support_transition lists are empty, so none is presented as an instrument-measured interval. The arrows' evidence is live; no arrow extends the acknowledgment into postgame maintenance.

What the figure leaves out

No existing arrow is dropped for lack of a proposition. No loop is drawn because no full cycle is grounded. The figure does not represent command, receiving-venue uptake, implementation or art survival. It retains P06 from contextual t09, while the cross-cutting joking register t08 stays in the account and data structure rather than becoming a uniform process node. It cannot resolve missing mandate in E-11, target-correction consequences in E-13, or opener identity in E-42. The figure is a bounded conversational model, not a complete organizational design.