r/place A fruit fly for organization science

out/figure-C5.md

Saved at r/Goodboye: 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: 7dc588a5950d3a9dab9ef6f84b2b128a973b765c92902683e6c2798085b538b8. Reading-copy SHA-256: 7dc588a5950d3a9dab9ef6f84b2b128a973b765c92902683e6c2798085b538b8.

Figure: local organizing without total project control

Rendered figure and mandatory reading key

Controller-rendered retained model

The actual controller drawing uses a stacked layout. Its three arrow labels must be read with these proposition tags: A01 = N01; A02 = N02; A03 = N03. The imposed clock marker is hour 73: placement stops there, while affiliation and prospective work can continue. This caption is part of the figure; those proposition tags and the terminus are not printed inside the controller's image. The requested three-column arrangement below is a precise layout specification, not a claim that the gateway implements it. No source statement or relation was altered to force a different renderer layout.

With-theory view: the image above plus this caption. Without-theory view: the same image and caption. There is no drawable extra conjectural link because neither A04 nor A05 has an instance. This is a source limitation, not a claim that the two hypotheses are established.

Complete source specification and instances

Use the conditions/moves/reports arrangement in sketches.md. Draw all ten retained elements once: left K01 reported or anticipated reversion limits and K02 personal acceptance without mandate; middle P01 directing a usable contribution, P02 seeking/offering/crediting help, P03 explaining/negotiating terms, P04 selecting intended features/extent, P07 explicitly revising a stated position, P05 affiliating/commemorating and P06 proposing further community work; right C01 qualified textual reports of retained principal dogs. Grouping by dimensions remains visible in the accompanying data structure, not as extra process boxes.

Draw exactly these supported arrows, each fair and bounded:

The community scope on each is Goodboye only. It is not a measured cross-community tendency. Evidence is quoted words in linked episodes; the controller's clocks appear in account.md and data_structure.md, and no interval is calculated by hand. These are the only three links carried by propositions. Neither conjectural A04 nor A05 has a supporting instance, so neither may be drawn even in the with-theory view. Render the with-theory and without-theory views from the same source: both therefore have these same supported links, with the omitted hypotheses named in this caption rather than unsupported dashed arrows. Do not invent instances to make the views differ.

Include the imposed terminus at hour 73: placement ends, but affiliation and prospective work need not. No loop is drawn because model/loops.jsonl contains no complete dated cycle. There is a middle column of named practical processes, but no earned arrows from every condition or into every reported consequence. The figure is deliberately not an all-connected causal chain.

What it leaves out: ungrounded attachment-to-renewal A04 and agreement-to-retention A05; contextual c0073; the four unresolved episode consequences; and the verbal registers of commands, uncertainty, personal disclaimers, gratitude and jokes. No whole coder theme is excluded. The topic-based defence theme is split because directing correction, excluding a friendly addition and describing an unsustainable change do different work. The table and account retain these distinctions and their uncertainty.