r/placeAn organizational fruit fly

One shared research object

A fruit fly gives researchers a common object whose accumulated record can constrain a new claim. We propose r/place for that role in organization science. The question is how organizational forms emerge and stay different.

What composition adds

A detailed account can explain one community without explaining how it relates to others. Composition asks whether those case accounts can support a population model and keep the evidence that qualifies it. The contribution is a baseline that later work can inspect, challenge and extend.

Qualitative research needs that detail: an action can mean different things in different cases. It also needs categories that emerge from the record. In the instrument, each community coder keeps its own evidence, and a population model shows the shared patterns and the departures from them. Researchers judge whether those descriptions amount to a theoretical contribution.

The repository connects three things: the event record, an instrument for reading it, and the model that one use of the instrument produced. They can be inspected separately. A different instrument may find distinctions or relationships that this model missed.

A broad record and a bounded study

The record has two parts: pixel changes and public posts and comments. The collection scripts can retrieve records from thousands of subreddits where the event's pixel placers wrote. Many posts in those subreddits have nothing to do with r/place. The data guide keeps collection apart from the selection of material for analysis.

The current study covers 705 curated communities with evidence of coordination during the 2017 event. Each has a written record and a case account. It is a census of this curated population; many more subreddits mentioned r/place.

The shared canvas is the setting; communities are the cases. Their differences are what the analysis seeks to explain. Common conditions support comparison, and the event record keeps the sequence within each case.

A frozen dataset and a revisable instrument

The dataset holds the event record. The instrument specifies how agents read, code and compose it under researcher supervision. Each community coder works with its own material, keeps notes outside the conversation and retrieves evidence as needed. The aggregator compares those accounts across communities. No conversation has to hold all the material, though selection and interpretation remain.

Researchers can change the instrument, bring a different theory to the record, or extend the population, while stating which baseline they use.

A population model is returned to saved community coders for comparison with their own records. Their objections can qualify an explanation that seemed to hold across cases. The check runs against the recorded evidence. The contracts keep the outputs and reports behind each step.

r/PlaceNL's defense script erased a planned addition. Evidence like this changed the model's account of repair. The example follows the objection through the revision and the later finding that bounded it.

What accumulation would mean

The completed model is a baseline. A later account must show which observations it explains better, which distinctions it preserves, or which earlier claim it corrects. The agent codes and composes; researchers judge whether that amounts to a theoretical contribution.

Follow one community from coding to its place in the model or explore the population model and forms.

The wider aim is to learn how organizations emerge and evolve. Whether an explanation travels beyond this event needs further evidence, and a model organism makes that question easier to pose and test.

Further comparisons

The paper proposes two further population models from the same record: induction supported by an algorithm from term frequencies, with no community coder, and a separate aggregator that works from tables across cases. Both are planned. The current aggregator already draws on several qualitative traditions; its contract holds the rules.

At C4, an interim reading of the central r/place subreddit prompted tentative additions and qualifications to the community-based model. Read the checks and their limits.

Keeping the baseline usable

Checkpoint interviews depend on access to compatible models and software. The paper proposes rerunning the pipeline with an open-weight model and archiving its weights. This is future work, and the current checkpoints hold no such weights. Saved outputs and transcripts can still be read without resuming an agent.

Reruns also need time, storage and model access. The paper reports roughly three months on a US$200 monthly subscription for coding the 705 communities and one composition run. A new run may differ in cost and time, and extending the census needs a new estimate.

The Model organism page applies four features that Ankeny and Leonelli discuss in model organism research to r/place: material accessibility, integrative understanding, standardization and a research community.