r/place A fruit fly for organization science

out/structure.md

Saved at r/cirkeltrek: 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/structure.md. Original SHA-256: 8c20be8a82507365b6463ee52d5b6a6bd6fcfb3a55a79496db203bbcbbc32a92. Reading-copy SHA-256: e1f23a2e7f8306bd6cea8b4007abc5145b97f082b2d15c8283572f848a24d9e0.

R3 data structure

Reading and status

The structure starts from immutable coder themes and the full first-order census. See form_pass.md for the separate turn-level sweeps; those findings are not topic members. The preparatory optional names are unchanged aliases, not the grouping rule. These are provisional pre-model constructs (pass 0); no element, arrow, loop, proposition or critic candidate is built.

Each coder theme below is defined by the coding's own practice note, quoted intact, followed by the lead's separating test. The source supplies no coder-theme gate blocks or independent coder-conflict register; I do not invent either or claim to repair an unobserved disagreement. The higher-theme gates are declared here and in fourth/fourth.jsonl. All travel on exemplars under rule 5, not prevalence gates.

Coder-theme practices and boundaries

t01 — turning the subreddit itself into the April joke

Coding's unchanged practice note:

These passages act on the room and its language rather than the canvas: people join, reject, explain, or replace Spanish/German themes and pranks, police English wording, and complain when Place posts take over the feed. What varies is whether they play along, demand restoration, or propose another subreddit theme.

What it is and is not: Subreddit styling/feed conduct is not a pixel-group objective.

Nearest-neighbour test: Nearest is T4-004's result-display work: the test is whether the action concerns the canvas result or the room's April styling. Royal language is not enough.

Placement: contextual; no higher-theme gate is imposed. Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t02 — calling people into pixel work and its planning rooms

Coding's unchanged practice note:

These passages recruit placers or tell them how and where to join coordinated work. They vary between basic canvas instruction, cooldown news, direct help calls, external upvoting, and routing work to Discord or PlaceNL.

What it is and is not: Entering/routing shared work is not accepting a plan or proof of active participation.

Nearest-neighbour test: Nearest t04: an invitation supplies access; a guide supplies the representation. Both are aspects of T4-001, not duplicate placements.

Placement: T4-001. Higher-theme gate, quoted: “The coder theme's practice offers or troubles an entry route, concrete content/layout, or usable plan by which otherwise separate people could join a common pixel project.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t03 — laying out Dutch words, pictures, and borders

Coding's unchanged practice note:

These passages decide what to draw and how it should fit: anthem text, names, windmills, portraits, flags, houses, logos, mottos, and borders. They vary from proposing an object or location to reporting that a component now stands.

What it is and is not: Specifying or trying a content/layout contribution is not settling another project's right to remain.

Nearest-neighbour test: Nearest t08: an internal windmill location is design; a border negotiated to protect Pusheen concerns coexistence. Theme-level placement preserves the main problem rather than recoding mixed examples.

Placement: T4-001. Higher-theme gate, quoted: “The coder theme's practice offers or troubles an entry route, concrete content/layout, or usable plan by which otherwise separate people could join a common pixel project.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t04 — publishing and changing the plan

Coding's unchanged practice note:

These passages make a plan public or replace it with a newer one. They vary between exact and inexact pixel guides, Discord-returned images, current or definitive plans, and requests for judgment on a proposal.

What it is and is not: Publishing or seeking a usable plan is not binding its users.

Nearest-neighbour test: Nearest t05: a guide offers an arrangement; correction identifies a breach of one. Definitive wording is not observed acceptance.

Placement: T4-001. Higher-theme gate, quoted: “The coder theme's practice offers or troubles an entry route, concrete content/layout, or usable plan by which otherwise separate people could join a common pixel project.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t05 — correcting pixels and holding builders to the plan

Coding's unchanged practice note:

These passages identify wrong pixels or spellings and try to bring contributors back into line. They vary from synchronized repair and practical script warnings to naming, shaming, proof, apology, and release.

What it is and is not: Repair and accountability address deviations, including disputed allegations; they do not verify sabotage.

Nearest-neighbour test: Nearest t06: internal miscorrection and attributed external damage differ, but both address continuity. The false attribution in E-04 is retained.

Placement: T4-002. Higher-theme gate, quoted: “The coder theme addresses divergence, damage or vulnerability of an already recognizable project through correction, repair, guarding or accountability.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t06 — defending Dutch pixels from damage

Coding's unchanged practice note:

These passages treat existing Dutch words, flags, or royal pictures as under damage and call for protection or restoration. They vary in the named threat and in whether defence means cleaning, guarding overnight, stopping scripts, or fighting back.

What it is and is not: Defending a recognizable arrangement is not a right to replace all adjacent work.

Nearest-neighbour test: Nearest t07: c0247's attack-by-finishing-the-flag is a boundary case. Keep its coded attack theme in the territorial contest; do not infer a trustworthy defender/aggressor distinction from military language.

Placement: T4-002. Higher-theme gate, quoted: “The coder theme addresses divergence, damage or vulnerability of an already recognizable project through correction, repair, guarding or accountability.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t07 — calling for orange attacks and annexations

Coding's unchanged practice note:

These passages urge taking over, recolouring, replacing, or sabotaging other work. They vary from bare attack calls and border expansion to named targets, polls, jokes about conquest, and plans to overwrite pictures or flags.

What it is and is not: Pressing expansion or takeover is not evidence it occurred.

Nearest-neighbour test: Nearest t08: both concern the reach of claims, but unilateral replacement differs from seeking another project's accommodation. Their opposition is held within T4-003, not erased.

Placement: T4-003. Higher-theme gate, quoted: “The coder theme presses, negotiates, restrains or disputes claims about occupying, replacing, sharing or protecting space claimed by another identifiable project.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t08 — negotiating room and looking after neighbours' work

Coding's unchanged practice note:

These passages seek coexistence, peace, alliances, permission, repair, or protection for neighbouring work. They vary between visitors' petitions, Dutch restraint, reciprocal border promises, apologies, help rebuilding, and shared designs.

What it is and is not: Negotiating, restraining and protecting neighbours can produce a promise without the ability to bind placers.

Nearest-neighbour test: Nearest t06: protecting another project's continued room contests project reach; protecting one's recognized pixels maintains continuity. c0306 is a limit report, not a successful negotiation exemplar.

Placement: T4-003. Higher-theme gate, quoted: “The coder theme presses, negotiates, restrains or disputes claims about occupying, replacing, sharing or protecting space claimed by another identifiable project.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t09 — commenting on what the canvas has become

Coding's unchanged practice note:

These passages stand back from immediate instruction to describe or judge a visible or reported outcome. They vary between progress reports, jokes, complaints, lament, mockery, gratitude from visitors, and celebration of gains.

What it is and is not: Describing or judging a reported result is not immediate work instruction or independent image verification.

Nearest-neighbour test: Nearest t10: the former evaluates live outcomes, the latter answers closure; the shared practice is making results tellable, not a claim that all judgments are retrospective.

Placement: T4-004. Higher-theme gate, quoted: “The coder theme describes, evaluates, attributes or preserves a reported pixel result rather than primarily specifying or restoring its construction.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t10 — marking Place's ending and keeping its result in view

Coding's unchanged practice note:

These passages respond to the stopped canvas by mourning, thanking, claiming, contesting, recounting, or preserving the result. They vary between final toasts and criticism, subreddit display, wallpapers, timelapses, compilations, and retrospective accounts.

What it is and is not: Interpreting/preserving a stopped result is not proof that the shared placing practice continued.

Nearest-neighbour test: Nearest t11: a wallpaper holds a result available, whereas a pxls.space invitation offers work again. A header request is actionable display work without restarting pixel production.

Placement: T4-004. Higher-theme gate, quoted: “The coder theme describes, evaluates, attributes or preserves a reported pixel result rather than primarily specifying or restoring its construction.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

t11 — moving pixel work to pxls.space

Coding's unchanged practice note:

These two passages explicitly redirect the placing practice to pxls.space after r/place ended: one calls it r/plaats returned 'sort of' and the other calls people to keep fighting there.

What it is and is not: Reopening the possibility of placing in a named substitute venue is not a migration outcome.

Nearest-neighbour test: Nearest t02: substitute-venue entry repeats recruitment's problem under a stopped original venue; both sit in T4-001. Short coded spans omit the venue, so neither is promoted as a standalone T4 exemplar.

Placement: T4-001. Higher-theme gate, quoted: “The coder theme's practice offers or troubles an entry route, concrete content/layout, or usable plan by which otherwise separate people could join a common pixel project.” Within-practice variation is preserved in the quoted source note. These examples travel on exemplars; no prevalence figure is inferred.

Only the two coded passages are available for this theme; a third exemplar is unavailable. Their full threads, already read at R2, establish replacement-venue invitations; the quoted fragments alone do not. They are side evidence, not the core T4 exemplars. The later invitation's visible reply refuses; sustained re-entry remains unobserved.

Higher themes: abstraction, scope and evidence

The complete gates, declarations, variation and disconfirmation conditions are in fourth/fourth.md and fourth/fourth.jsonl. The following is the material register. Each quote is copied from the instrument; item/thread/hour and offsets are kept together. The gateway does not return created_utc in the cite record, so no Unix timestamp is invented; hour_since_open is the supplied clock. Position denotes conceptual centrality, not frequency.

T4-001 — Offering a common project

Coined. Showing people where to join, what to build and which plan to use, including an attempted restart.

Scattered willingness is made available for combination by offering an entry route, an identifiable object and a usable representation of the work. These offers can be partial, revised or difficult to find. An invitation to a replacement venue repeats the entry problem without showing a new group has formed. The shared practice is making participation addressable, not commanding compliance.

Question: How can scattered willingness be directed toward an identifiable shared undertaking?

Near case outside: c0027 offers exact timing but addresses a breach in the existing spelling, so its coded repair theme sits in T4-002. Least certain: t11. For inclusion, it offers an entry route to the same placing practice after closure, as t02 offers entry during it. Against, no jointly chosen new target or implementation follows and the coded quotes omit pxls.space; the full R2 context supplies that venue. Retain it as a thin entry variant, not a standalone core exemplar or evidence of integration.

Material: higher theme T4-001; coder theme t02, calling people into pixel work and its planning rooms; first-order c0070; community cirkeltrek; position core; nearest neighbour T4-002. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-001; coder theme t03, laying out Dutch words, pictures, and borders; first-order c0019; community cirkeltrek; position core; nearest neighbour T4-002. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-001; coder theme t03, laying out Dutch words, pictures, and borders; first-order c0060; community cirkeltrek; position core; nearest neighbour T4-002. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-001; coder theme t04, publishing and changing the plan; first-order c0043; community cirkeltrek; position core; nearest neighbour T4-002. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

T4-002 — Recovering workable alignment

Coined. Repairing, correcting or guarding work that contributors treat as already worth maintaining.

A project remains workable only as contributors revisit departures from what they treat as its current arrangement. They can synchronize repairs, demand correction, identify suspected interference, or ask for protection through vulnerable periods. The shared work is recovering continuity across independent placements; whether the breach comes from misunderstanding, a script or an adversary varies. The construct names attempts and disputes, not their success or a verified enemy.

Question: How is a recognizable project kept workable when independent contributions undo it?

Near case outside: c0247 proposes attacking the void by completing a flag; its attack theme places the territorial claim in T4-003 rather than assuming defence. Least certain: t06. Its defence talk can claim territory, not merely keep work recognizable. For inclusion, the cleaning and restoration passages explicitly protect existing work; against, military language can disguise expansion. The separating test is whether the practice takes an existing arrangement or another project's continued room as its object.

Material: higher theme T4-002; coder theme t05, correcting pixels and holding builders to the plan; first-order c0027; community cirkeltrek; position core; nearest neighbour T4-003. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-002; coder theme t05, correcting pixels and holding builders to the plan; first-order c0032; community cirkeltrek; position core; nearest neighbour T4-003. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-002; coder theme t05, correcting pixels and holding builders to the plan; first-order c0049; community cirkeltrek; position side; nearest neighbour T4-003. Why this one: it asks to clean an identified flag, but the full thread disputes whether that flag is theirs; it is a boundary example, not verified defence of the same project.

Material: higher theme T4-002; coder theme t06, defending Dutch pixels from damage; first-order c0074; community cirkeltrek; position between; nearest neighbour T4-003. Why this one: it explicitly prioritizes restoring claimed ground while also asserting a border; this is a real limit on separating maintenance from entitlement.

T4-003 — Contesting what orange may claim

Coined. Pressing for takeover or seeking room, restraint and promises where projects compete.

People make rival claims about the legitimate reach of a Dutch project: one proposal treats another flag as available for recolouring, another seeks a border that protects a neighbouring picture. These are not shared commitments or a peaceful consensus. They are competing ways of settling whose work may remain and on what terms. Holding unilateral appropriation beside bargaining explains why an agreement in one exchange cannot stand for authority over all placers.

Question: Who may remain in shared space, and how far can a speaker commit the project?

Near case outside: c0066 reallocates text and a windmill within the plan without negotiating another project's right to remain, so it belongs to T4-001. Least certain: t08. A bargain differs sharply from a unilateral attack. For inclusion, both make competing claims about the same finite shared space; against, bundling them could falsely imply a single boundary policy. The theme's question is contested entitlement, not agreement; peaceful proposals, broken promises and inability to bind others remain opposed cases.

Material: higher theme T4-003; coder theme t07, calling for orange attacks and annexations; first-order c0096; community cirkeltrek; position core; nearest neighbour T4-002. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-003; coder theme t07, calling for orange attacks and annexations; first-order c0246; community cirkeltrek; position core; nearest neighbour T4-002. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-003; coder theme t08, negotiating room and looking after neighbours' work; first-order c0080; community cirkeltrek; position core; nearest neighbour T4-002. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-003; coder theme t08, negotiating room and looking after neighbours' work; first-order c0308; community cirkeltrek; position core; nearest neighbour T4-002. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

T4-004 — Making a collective result tellable

Coined. Describing, judging, claiming and preserving what participants say their pixel work became.

The work becomes an account as participants mark progress, celebrate or condemn the result and give it a durable form in a header request, wallpaper or compilation. Live evaluation and post-stop remembrance both select what is worth describing as an achievement or a harm. They need not agree. This accounts for a result's public afterlife without treating praise as a placement instruction or preservation as continued production.

Question: What is made publicly recognizable and preservable as the result of the work?

Near case outside: c0297 reopens placing in a replacement venue in full context; it is an entry offer in T4-001, not merely keeping a result in view. Least certain: t09. A fragmentary progress title can merely announce a picture rather than organize a collective account. For inclusion, it renders reported work available for appraisal; against, appraisal is not preservation. The bundle holds a shared public-result problem while retaining that variation and leaving its contribution to active coordination unproved.

Material: higher theme T4-004; coder theme t09, commenting on what the canvas has become; first-order c0136; community cirkeltrek; position core; nearest neighbour T4-001. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-004; coder theme t09, commenting on what the canvas has become; first-order c0262; community cirkeltrek; position core; nearest neighbour T4-001. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-004; coder theme t10, marking Place's ending and keeping its result in view; first-order c0296; community cirkeltrek; position core; nearest neighbour T4-001. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Material: higher theme T4-004; coder theme t10, marking Place's ending and keeping its result in view; first-order c0300; community cirkeltrek; position core; nearest neighbour T4-001. Why this one: it displays the member practice at a different substantive or temporal edge of the bundle; the quote itself shows the work specified in the gate.

Aggregate dimension

D01 — Provisional coordination of a porous project

Coined, source empty. Gloss: making separate placements potentially work together while the project's content and reach remain revisable. Members: T4-001, T4-002, T4-003.

Question: how can a project be made actionable and kept recognizable while neither participation nor territorial commitments are fully bounded? Offering a project alone cannot explain the need to correct it; correction alone cannot explain disputes over whose work deserves protection. Considering those distinct problems together separates making a contribution possible from securing others' compliance. This is an explanatory distinction, not an asserted causal relation between them.

Membership predicate: include a higher theme whose organizing problem concerns availability, continuity or legitimate reach of ongoing shared pixel work. Exclude a construct whose main question is representing or preserving its reported result. Gate: offers, restoration and competing spatial claims each arrange independent contributions; they are aspects, not necessary stages.

Explicit evidence: E-02 shows an offer to synchronize a repair and acknowledgments; E-03 follows accountability proposals; E-05 and E-11 bound promises by reported loss; E-09 contains the explicit inability explanation. The material quotations above include c0019, c0043, c0027, c0032, c0049, c0096 and c0308; c0306 below is the relevant limit, not universal proof.

Least certain member: T4-003. Its inter-project contest can be treated as context outside internal coordination. Against excluding it, its replies directly make and limit commitments about what “we” will do, so the reach of those commitments is part of the same organizing problem. It remains an arguable dimension rather than a claim of unified organization. No borrowed concept is verified here.

Disconfirmation elsewhere: the three problems concern unrelated undertakings, or binding membership/decision arrangements make this distinction between project offers and their reach explanatorily idle. Nearest mistaken reading is centralized command. The dimension cannot identify all placers or attribute external Discord decisions.

T4-004 has dimension=[]: result narration and preservation do not by themselves arrange current placement or territorial claims. The header request is a near case—it coordinates display, but not the live project's alignment. A separate “afterlife” dimension was considered and rejected: one result-focused higher theme does not warrant a new level. A single encompassing national-solidarity dimension was also rejected because vocabulary would replace the practice distinction. There is no second retained dimension, hence no meaningful pairwise dimension separation to fabricate.

What no higher theme picked up

t01 remains contextual. The instrument computes its code mass as 29/308 of this room's live codes, receipt 2534, not an estimate of how much organizing occurred. Metadata: {"id":"unpicked","mode":"coverage","unit":"codes","n":29,"denominator":{"unit":"codes","n":308,"of":"this room's live codes, hours 0 through 97 inclusive"},"receipt":2534,"boundaries":{"end":{"hour":97,"ids":[],"items":[]},"start":{"hour":0,"ids":[],"items":[]}}}.

The April joke shows real conduct, but its target is the room's identity/styling/feed, not necessarily the pixel project. A royal-register bundle would pick it up only by confusing shared language with shared work. The following evidence spans styling protest and a request for fewer Place images:

I considered a standalone higher theme of maintaining room identity, but it would rename the existing coder practice without answering an additional case-organizing question. It remains available as context for participation and competing uses of the venue, not deleted or treated as proof of no organizing.

Assignment and coverage audit

Every coder theme is represented once in assignments.jsonl, either in one defined higher-theme member list or contextual. No theme is split and no extra placement is made. The empty multiplacement_log.jsonl records that no primary/additional pair exists at this level; no joint/lump rate or cross-dimension pair is invented. The code-level ambiguity of c0074 is retained as material, not used to multiply-place its whole theme.

The table reports only coverage of code mass carried by the written assignments, measured by the instrument after the files were written. It does not count how often organizing succeeded or gate these constructs.

Assignment Codes represented / all live codes Receipt
T4-001 70/308 2519
T4-002 54/308 2523
T4-003 104/308 2526
T4-004 51/308 2530
Contextual 29/308 2534
D01 228/308 2538

All windows are hours 0 through 97 inclusive; no code sits exactly at either boundary. Full metadata are in structure-counts.jsonl. The higher-theme blocks plus contextual block exhaust the source code IDs without overlap. The dimension count is a subset and must not be added to that partition. There are no three prevalence/opportunity classes to sum: no prevalence claim is made, and each construct travels on exemplars.

There is no independent onset contrast within a one-onset room. The live/aftermath distinction keeps t11's attempted re-entry separate from t10's result work without treating either as proven continued production. No coder-conflict packet is delivered, so there are no independently conflicting coder words to report under read another way. The substantive alternatives and weakest memberships are stated above.

Consequence for the next stage

This structure distinguishes project availability, recovery and contested reach from result narration. It is not a dynamic model. R4 must test the episodes rather than infer arrows from bundles, reconsider the opposed-practice boundary in T4-003, and preserve the failed promise, corrected accusation and refused invitation as limits. The turn-level form findings remain available only as prose in form_pass.md, never clustered or counted as topic practices.

R4 critic reconciliation

The initial R3 discussion above remains the structure's construction record, not a claim that no model currently exists. The candidate now uses these unchanged memberships and gates. The critic correctly found inconsistent attribution of c0049; canonical code delivery 4234 and source search 4131 establish its immutable placement as t05. The material register was right on membership; the earlier t06 example list was wrong and now uses the actual defence code c0057. No source code or coder theme was altered. In full thread 62tfcu, dfp1rbz disputes whether the flag is theirs, so the cleaning appeal is side material, not independent proof of defending shared work.

The rival partition clarifies that access, intelligibility, territorial entitlement and public representation are alternative questions. I retain the current grouping because it distinguishes offering an arrangement from restoring its recognizable continuity, and distinguishes contested reach from guarding an existing arrangement. t01 remains contextual: shared public presentation does not by itself connect April styling/feed disputes to interpreting or preserving a pixel result. The alternative is plausible but more inclusive at those boundaries, not a refutation by membership count. T4-003 remains the weakest retained construct; no number or majority settles it.