# R3 data structure Target length: under 6,500 words. ## Basis and scope This is a provisional structure, not a dynamic model. The original coded IDs, labels and memberships remain immutable. Optional names in out/names.jsonl predate R1 and do not decide these bundles. Every construct below is coined with no source claim. The R3 cut is retained in the history. R4 pass 2 separates remembered attachment from local accomplishment after the critic; all original coder themes and code memberships remain intact. Each construct travels on exemplars, not a prevalence claim. Counts below describe how the assignment file covers codes. The frame is all closed codes in hours [0,97], with no codes on either boundary. Receipt 2043 gives 143/143 delivered codes. The three direct sweeps and their limits appear in out/form_pass.md. Their turn-level findings do not enter the topic assignment arithmetic. ## Coder themes and separating tests The closed coding provided descriptive theme notes, not a new gate scheme to amend here. I quote each note as its supplied membership description. The separating tests below guide higher placement only; none recuts its codes. There are no cross-coder conflict records supplied for this sibling, so no comparative reader words can be invented. Every theme travels on exemplars; no carries/opportunity/no-opportunity prevalence is claimed. ### `t01`: building recognizable Mindcrack pictures Supplied description: "These passages hold together as making recognizable community pictures on the canvas: proposing, starting, joining, and completing logos or faces; what varies is the picture and whether one person starts or others join." It concerns picture-making, including proposals and reported starts; it does not establish completion or a shared master plan. Nearest neighbours: t02 adds pressure on continued presence; an initial or fresh target belongs here, whereas maintenance and selective defense belong there. Variation: An individual's start through invitation to join and a staged target choice. > I have begun! (three diagonal black pixels below Guude logo) r/mindcrack, hLPwO0zXq7I/qjGSJ8xWAcvnRqM=, hour 25.767777777777777, `c0013`, item `dfp6ejt`, thread `62o1bl`, offsets 0:60. > Let's work together, guy. r/mindcrack, j8keIeM9rZn7od9eiOVkgd5zYx0=, hour 7.654444444444445, `c0008`, item `dfo864v`, thread `62o1bl`, offsets 0:25. > We will start with the Guude logo and if we finish that then we will see what we do next. r/mindcrack, 1x5iQiNWjJbpA+GMUYZIcdbBOts=, hour 51.78722222222222, `c0082`, item `dfqmepu`, thread `631n36`, offsets 198:287. ### `t02`: keeping the pictures standing by repairing, defending, or moving Supplied description: "These passages all work to keep some Mindcrack picture present under pressure; what varies is watching, repairing, defending, abandoning part of it, or moving and rebuilding elsewhere." It concerns continued picture presence under pressure; describing loss does not itself establish that rebuilding followed. Nearest neighbours: t01 starts a picture; t04 states obligations toward neighbours. The decisive concern here is what own work remains maintainable. Variation: Reported threat and repair through relocation, abandonment and narrowing defense. > It's gone now, alas, or at least partially eaten. I suggest we rebuild it below the Guude and Doc logos. Bigger! r/mindcrack, zGiQo1R1H70FFQw9eD5FepBd37Q=, hour 25.148611111111112, `c0012`, item `dfp4v0y`, thread `62o1bl`, offsets 0:112. > We need to pull back and defend the Guude symbol at least until things cool off some with the dutch. r/mindcrack, UxXfCSY3pqwtLE85e6btxoHp8zs=, hour 50.141666666666666, `c0040`, item `dfqhthh`, thread `62v848`, offsets 57:157. > We should focus our efforts on the G logo underneath Bender at the bottom right area. r/mindcrack, 6/NMVDa22cEiQfhmblyJgDI+/6g=, hour 64.36583333333333, `c0109`, item `dfrhest`, thread `635gaw`, offsets 0:85. ### `t03`: calling people in and coordinating the work Supplied description: "These passages recruit people or relay where and how to work together; what varies is a Reddit call, a Discord report, a stream request, or a shared background plan." Calls and relays make participation available; neither a request nor reporting outside help proves pixel contributions. Nearest neighbours: t01 settles a target; t10 reorganizes the discussion venue. This theme reaches toward helpers without exercising moderator control. Variation: An open invitation, an outside stream solicitation and a request whose target has been deleted. > I see the start of a new mindcrack logo to the right of doc and etho. Let's help! r/mindcrack, RVSFJsdD1q4Kyj0zcfnGMcmH2Wg=, hour 31.30527777777778, `c0027`, item `dfpjn46`, thread `62sh1v`, offsets 0:81. > I've solicited Justin's stream to help - hopefully that will turn the tide. r/mindcrack, 9FaQ1Aaul1/tO6sRUjd8S2OZKjg=, hour 36.836666666666666, `c0036`, item `dfpvs0r`, thread `62v848`, offsets 0:75. > Could I possibly get some help from my fellow Mindcrackers? (/r/place) r/mindcrack, [deleted], hour 40.22416666666667, `c0051`, item `62ykvg`, thread `62ykvg`, offsets 0:70. ### `t04`: bargaining for borders and helping neighbours Supplied description: "These passages make coexistence practical by agreeing borders, moves, non-expansion, refuge, or mutual help; what varies is the neighbour and whether the bargain protects Mindcrack, the other work, or both." Terms for coexistence include requests, warnings and incomplete performance; the theme is not a claim of universal reciprocity. Nearest neighbours: t05 evaluates conduct and responsibility. A border, move or aid obligation supplies the practical term that separates this theme. Variation: A pixel of room through bilateral defense, cession, threats and invoked promises. > Mind leaving me one pixel border between us? r/mindcrack, B8nSUnd4avjwgNoL/XV4TF4VFCo=, hour 32.158055555555556, `c0031`, item `dfplomc`, thread `62v848`, offsets 58:102. > They have agreed to not expand into us and to help defend, if we don't expand into their bird and help to defend them. r/mindcrack, UxXfCSY3pqwtLE85e6btxoHp8zs=, hour 53.5125, `c0091`, item `632e25`, thread `632e25`, offsets 159:277. > We're trying not to step on a small subreddits work, since we have just had a similar experience to that with the dutch. r/mindcrack, UxXfCSY3pqwtLE85e6btxoHp8zs=, hour 58.980555555555554, `c0094`, item `dfr6y1r`, thread `632hzb`, offsets 341:461. ### `t05`: arguing over who is ruining the work and what is fair Supplied description: "These passages identify, shame, excuse, or challenge people said to be erasing work; what varies is whether blame falls on spam, flags, a member, rogues, or people ignoring an agreement." These speakers evaluate means and attribute responsibility. Their accounts do not independently verify who placed pixels or what scripts ran. Nearest neighbours: t04 bargains over what to leave and help; evaluating whether a means or speaker is legitimate stays here without a practical term. Variation: Condemnation and apology through disputes about scripts, rogue action and official organization. > Kinda defeats the point if you have a script, it's supposed to be a community thing. r/mindcrack, gb/N8iAQKMeXxp9AlKnqQWBR0y4=, hour 51.88666666666666, `c0083`, item `dfqmo8s`, thread `631n36`, offsets 0:84. > i realized that when I woke up, forgot to edit the post saying so; sorry. I've been helping defend from the dutch and others since then. r/mindcrack, UxXfCSY3pqwtLE85e6btxoHp8zs=, hour 49.955, `c0039`, item `dfqhak1`, thread `62v848`, offsets 0:136. > I just wanted to let you guys know the organized Dutch did not want the Mindcrackers to get attacked. Thats all the fault of the randoms. Sorry! r/mindcrack, 5IwgiwRkEApKdegTNPBP5PD62kY=, hour 74.87833333333333, `c0122`, item `dfs5fc1`, thread `638be0`, offsets 0:144. ### `t06`: letting the pictures bring old fans back Supplied description: "These passages turn recognition of the canvas art into renewed connection: remembering, welcoming, watching old videos, checking an old subreddit, or returning to place pixels." Renewed connection includes viewing and memories; it does not establish that everyone returned as a builder or stayed. Nearest neighbours: t09 recognizes a local accomplishment. Here the speaker's earlier relationship to the community is reopened. Variation: Fond memory through welcome, old video viewing, flair curiosity and an offer of defense. > Not a Fan Anymore, But This Brought Back Some Fond Memories. Thanks Guys :) r/mindcrack, zOPEvZDWG3l7Vl4F8MG+gKshjI8=, hour 37.12722222222222, `c0042`, item `62xyiq`, thread `62xyiq`, offsets 0:75. > I saw this in /r/place and it bought all the nostalgia back. I should really be studying but oh well... time to watch some old mindcrack vids I guess! r/mindcrack, xXUPpdpD1d86snLQPjRhvYoB2j0=, hour 39.66888888888889, `c0044`, item `dfpzvsc`, thread `62xyiq`, offsets 72:222. > Was happy to see this, and I'm happy to help defend it (in its new location), along with a few other parts I'm defending. r/mindcrack, aWlzfgNDO7bh71iVWDf6nsWcmfo=, hour 53.485, `c0048`, item `dfqquue`, thread `62xyiq`, offsets 94:215. ### `t07`: making and mistaking April Fools jokes Supplied description: "These passages concern the room's own April Fools practice rather than canvas work: one mistakes canvas loss for the local joke, while the recap deliberately revives an older joke." Local jokes and a mistaken identification of canvas loss are contextual to organizing; common April Fools vocabulary is not a common work practice. Nearest neighbours: t12 uses recurring recaps to recount the event. The old joke here concerns the room's own practice rather than a closed-event account. Variation: A brief misidentification and a deliberate revival of an old joke. Only these two coded passages are available; a third exemplar is unavailable. > For a split moment I thought this was the official /r/Mindcrack April Fools Day event. We are now a Czech themed subreddit. r/mindcrack, vuunFut4c0tZCjF164ELynCI0GM=, hour 26.834722222222222, `c0025`, item `dfp91qf`, thread `62sh1v`, offsets 0:124. > APRIL FOOLS! Wait, what? Anyway, check out the link to the post from two years ago, I completely forgot I did that! r/mindcrack, wLY+iVmCLoRF6vlFjpiBr4pJKGc=, hour 36.63861111111111, `c0041`, item `62xual`, thread `62xual`, offsets 963:1078. ### `t08`: asking what r/place is and explaining the pixel rules Supplied description: "These passages make the event intelligible inside the room; the first explains the placement interval and later passages add a direct question and answer." Orientation makes a platform intelligible; it is not evidence of an expressed current contribution. Nearest neighbours: t03 invites or relays help. General explanation is distinguished by what is being asked and answered. Variation: An unsolicited rule explanation and an explicit question-answer pair. > Its reddit's april fools day joke. They created /r/place which is a subreddit where people get 1 pixel every 5 miniutes to draw. r/mindcrack, C34PwUEpdamriHtaqcWJxmdFzdQ=, hour 5.6575, `c0003`, item `dfo2r22`, thread `62o1bl`, offsets 0:128. > Can anyone explain what the deal with r/place is? Like what even is it? r/mindcrack, /y13QQ7eARl/GA7ooPH7X0SzOyY=, hour 58.723055555555554, `c0084`, item `dfr6544`, thread `631vjm`, offsets 0:71. > It's basically a place where each person can place a colored dot on a plane every five minutes. r/mindcrack, K/rsgAqzw6zp1AaTKJoIj0jIyRE=, hour 60.00527777777778, `c0085`, item `dfr9vq5`, thread `631vjm`, offsets 0:95. ### `t09`: celebrating a finished picture and asking what comes next Supplied description: "These passages publicly mark success, congratulate builders, greet people who found the work, or turn completion into the next proposal." Recognition and completion reports do not by themselves organize a next task; a mixed success-and-next-question passage can do both. Nearest neighbours: t06 reopens a prior community connection; t11 recounts the closed event. These turns acknowledge a visible or locally finished picture. Variation: A location pointer or greeting through congratulations, mission completion and a next proposal. > Success at 450,33! What's next? Floating block of ice? Apple Rise? r/mindcrack, j8keIeM9rZn7od9eiOVkgd5zYx0=, hour 10.442222222222222, `c0015`, item `62q0ji`, thread `62q0ji`, offsets 0:66. > I Saw This On /r/place, Good Job Guys! r/mindcrack, SpTDwu0rvW4i5/dRq7WhtbM0GMM=, hour 11.592222222222222, `c0022`, item `62qcdm`, thread `62qcdm`, offsets 0:38. > Mission complete r/mindcrack, 7927lbV4MzkMUyOJ9ahvrp/NT3M=, hour 61.08111111111111, `c0101`, item `634qx8`, thread `634qx8`, offsets 0:16. ### `t10`: gathering r/place talk into one megathread Supplied description: "These passages form one moderation practice: a member asks for consolidation, a moderator agrees, and recent posts are removed so later place talk returns to one thread." The moderator consolidates posts. This authority does not establish command over pixel placers. Nearest neighbours: t03 gathers help; the separating test is a change to the public discussion arrangement with moderator action. Variation: A member's request, moderator commitment and performed consolidation within one response sequence. > Can we get a megathread for /r/place related posts? r/mindcrack, J2sUx7jb1MylGS47SBQJT0HrHg4=, hour 64.39527777777778, `c0110`, item `635h8y`, thread `635h8y`, offsets 0:51. > Yes good idea. I'll make one. r/mindcrack, 1x5iQiNWjJbpA+GMUYZIcdbBOts=, hour 64.48805555555556, `c0111`, item `dfrhk5p`, thread `635h8y`, offsets 0:29. > I removed all the posts of the last three hours to combine them here. r/mindcrack, 1x5iQiNWjJbpA+GMUYZIcdbBOts=, hour 64.52361111111111, `c0112`, item `635i5t`, thread `635i5t`, offsets 129:198. ### `t11`: taking stock, mourning, and thanking people after placement ended Supplied description: "These passages begin the room's immediate account of finished work by thanking participants and taking pride; later passages add what survived, what was lost, who helped, and who claimed a part." Post-close accounts credit, evaluate and mourn. Reports of survival and loss are participant accounts of the canvas. Nearest neighbours: t09 marks local achievement during the event; t12 edits it into established publications. Here witnesses take stock after closure. Variation: Pride and gratitude through partial loss, missed allegiance and incomplete aid. > I'm proud of how much are community pulled together, not just for our own stuff, but to make allies and help friends as well. r/mindcrack, UxXfCSY3pqwtLE85e6btxoHp8zs=, hour 73.20722222222223, `c0115`, item `dfs02kx`, thread `635i5t`, offsets 62:187. > RIP Doc's face that was there briefly. r/mindcrack, 76BuZxx3WPb4HgMsFEOqo6a8rBU=, hour 75.1825, `c0123`, item `dfs6d15`, thread `638be0`, offsets 0:38. > near the end, the r/indonesia crew was also trying to use scripts to overtake the pinkbird, and despite our best efforts, we couldn't completely save those allies r/mindcrack, esBmWFBISxqKD6t1X8/sEEMyTEY=, hour 78.05888888888889, `c0129`, item `dfsf86o`, thread `638be0`, offsets 231:393. ### `t12`: folding r/place into the room's regular recaps Supplied description: "These passages recruit established FIU and Weekly Recap formats to place the finished event inside ordinary community life; what varies is using the ending as an opening or recounting the week's logo-building directly." Recaps place the finished event beside ordinary content. The FIU invitation is consumption of an existing recap, not a new pixel task. Nearest neighbours: t11 offers immediate participant accounts. The recurring publication format separates this theme. Variation: Using the ending to invite reading through a heading and weekly narration. The two weekly passages share one item, so they are not independent witnesses. > I hear that now as /r/place ended you don't have anything to do? Then I have something just for you because the FIU is here with the last recap! r/mindcrack, lfgzg4/6G+biHFgtSRfNYVqij+U=, hour 77.55833333333334, `c0135`, item `639sof`, thread `639sof`, offsets 51:195. > Mindcrack Invades r/Place! r/mindcrack, HmIl7LTLf6JXyN0+7zpYK+I4uqs=, hour 84.14833333333333, `c0136`, item `63bxgr`, thread `63bxgr`, offsets 438:464. > Over the past weekend, the pixel controlling craze of r/place was raging on Reddit, Mindcack fans/and some Mindcrackers contributed on this with building Mindcrackers’s logo on the subreddit r/mindcrack, HmIl7LTLf6JXyN0+7zpYK+I4uqs=, hour 84.14833333333333, `c0137`, item `63bxgr`, thread `63bxgr`, offsets 1821:2011. ## Higher themes The exemplar spread is within r/mindcrack only. Each bundle uses material from its coded members, with starts, restraint, explicit claims and contrary edges chosen for breadth. A sole coder-theme member cannot supply two distinct coder themes: for `T4-003` and `T4-004`, the requested broader spread is unavailable. Their contrasting practices warrant retention rather than merging to meet a display quota. ### `T4-001`: Keeping a recognizable presence by revising the work Declaration: coined, source empty. Gloss: Build, preserve, rebuild, or relinquish a picture or site while pursuing a recognizable presence. Question: What remains shared when the picture, site and defended extent can change? Starting a face and abandoning a vulnerable base both concern which recognizable work participants will keep making. The shared object is revisable. Proposed expansion, reports of erosion, repairs and selective retreat vary within this practice; this does not show an unchanged master plan or an accomplished rebuild whenever one is proposed. Members: `t01`, `t02`. Gate: "Material proposes, starts, reports or revises the making or preservation of recognizable Mindcrack pictures." Against `T4-002`, the object or continued condition of the picture is at issue, rather than access to people or discussion. What varies: Initial building through repair, rebuild, relocation, selective defense and acknowledged loss. Exclusion: Proof that every proposal was enacted, that all pictures shared a fixed plan, or that damage itself organized a response. Borderline decision: Place the coded theme by its shared picture-work practice; explicit recruitment is held in `T4-002` at its own coder-theme placement. This is not a two-part conjunctive gate; gate_parts is empty. Outside near case: Recruiting helpers without settling or maintaining a picture belongs in `T4-002`. Least certain membership, read both ways: `t01` includes one-off proposals with no uptake. Retain because they open the same target-selection problem; do not infer continuation from the proposal alone. Mistaken for: Persistence at a fixed site or commitment to finish every proposed picture. Disconfirmation elsewhere: Would fail where the named target remains fixed and these passages concern unrelated projects without any recognizable shared presence. Dimension: `D01`. Material: `c0013`, `c0082`, `c0012`, `c0040`. Verbatim passages and attribution appear above; the structured material below records each position and contrast. Coverage, not prevalence: 36/143 codes, receipt 2307. ```json {"fourth":"T4-001","third":"t01","second_order":"building recognizable Mindcrack pictures","code_id":"c0013","sub":"mindcrack","author":"hLPwO0zXq7I/qjGSJ8xWAcvnRqM=","hour_since_open":25.767777777777777,"quote":"I have begun! (three diagonal black pixels below Guude logo)","cite":{"author":"hLPwO0zXq7I/qjGSJ8xWAcvnRqM=","end":60,"hour":25.767777777777777,"item":"dfp6ejt","start":0,"thread":"62o1bl"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-001","third":"t01","second_order":"building recognizable Mindcrack pictures","code_id":"c0082","sub":"mindcrack","author":"1x5iQiNWjJbpA+GMUYZIcdbBOts=","hour_since_open":51.78722222222222,"quote":"We will start with the Guude logo and if we finish that then we will see what we do next.","cite":{"author":"1x5iQiNWjJbpA+GMUYZIcdbBOts=","end":287,"hour":51.78722222222222,"item":"dfqmepu","start":198,"thread":"631n36"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-001","third":"t02","second_order":"keeping the pictures standing by repairing, defending, or moving","code_id":"c0012","sub":"mindcrack","author":"zGiQo1R1H70FFQw9eD5FepBd37Q=","hour_since_open":25.148611111111112,"quote":"It's gone now, alas, or at least partially eaten. I suggest we rebuild it below the Guude and Doc logos. Bigger!","cite":{"author":"zGiQo1R1H70FFQw9eD5FepBd37Q=","end":112,"hour":25.148611111111112,"item":"dfp4v0y","start":0,"thread":"62o1bl"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-001","third":"t02","second_order":"keeping the pictures standing by repairing, defending, or moving","code_id":"c0040","sub":"mindcrack","author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","hour_since_open":50.141666666666666,"quote":"We need to pull back and defend the Guude symbol at least until things cool off some with the dutch.","cite":{"author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","end":157,"hour":50.141666666666666,"item":"dfqhthh","start":57,"thread":"62v848"},"position":"side","nearest_neighbour":null,"why_this_one":"Shows a contrasting edge of the practice without establishing every possible outcome."} ``` ### `T4-002`: Making contributions findable and intelligible Declaration: coined, source empty. Gloss: Tell readers how to participate, point them to work and helpers, or gather the discussion. Question: How can dispersed readers identify an available contribution or a place to discuss it? An explanation of the placement rule, a call to help at a location and gathering posts into a megathread make an activity accessible from different starting positions. Understanding the event, locating ongoing work and finding its discussion vary here. None alone demonstrates that a reader placed a pixel. Moderation has power over posts that a general invitation does not have over helpers. Members: `t03`, `t08`, `t10`. Gate: "Material makes the event understandable, invites or relays participation, or makes its discussion findable." Against `T4-001`, the shared concern is access to an activity or its communication rather than choosing the picture to preserve. What varies: Rule explanation, open calls, outside help relays and moderator-backed consolidation. Exclusion: An inferred assignment, counted uptake, or evidence that all planning occurred on Reddit. Borderline decision: Retain the access practice of the coder theme; a target mentioned as context does not move it into picture revision. This is not a two-part conjunctive gate; gate_parts is empty. Outside near case: A plan selecting a picture without addressing participation belongs in `T4-001`. Least certain membership, read both ways: `t08` supplies general orientation without a current commitment. Retain as intelligibility, with no inference that explanation recruited a builder. Mistaken for: A hierarchy assigning tasks or a measure of actual recruitment success. Disconfirmation elsewhere: Would fail where the messages merely describe an inaccessible activity, or where consolidating talk only archives completed work with no participating public. Dimension: `D01`. Material: `c0027`, `c0036`, `c0085`, `c0112`. Verbatim passages and attribution appear above; the structured material below records each position and contrast. Coverage, not prevalence: 14/143 codes, receipt 2310. ```json {"fourth":"T4-002","third":"t03","second_order":"calling people in and coordinating the work","code_id":"c0027","sub":"mindcrack","author":"RVSFJsdD1q4Kyj0zcfnGMcmH2Wg=","hour_since_open":31.30527777777778,"quote":"I see the start of a new mindcrack logo to the right of doc and etho. Let's help!","cite":{"author":"RVSFJsdD1q4Kyj0zcfnGMcmH2Wg=","end":81,"hour":31.30527777777778,"item":"dfpjn46","start":0,"thread":"62sh1v"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-002","third":"t03","second_order":"calling people in and coordinating the work","code_id":"c0036","sub":"mindcrack","author":"9FaQ1Aaul1/tO6sRUjd8S2OZKjg=","hour_since_open":36.836666666666666,"quote":"I've solicited Justin's stream to help - hopefully that will turn the tide.","cite":{"author":"9FaQ1Aaul1/tO6sRUjd8S2OZKjg=","end":75,"hour":36.836666666666666,"item":"dfpvs0r","start":0,"thread":"62v848"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-002","third":"t08","second_order":"asking what r/place is and explaining the pixel rules","code_id":"c0085","sub":"mindcrack","author":"K/rsgAqzw6zp1AaTKJoIj0jIyRE=","hour_since_open":60.00527777777778,"quote":"It's basically a place where each person can place a colored dot on a plane every five minutes.","cite":{"author":"K/rsgAqzw6zp1AaTKJoIj0jIyRE=","end":95,"hour":60.00527777777778,"item":"dfr9vq5","start":0,"thread":"631vjm"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-002","third":"t10","second_order":"gathering r/place talk into one megathread","code_id":"c0112","sub":"mindcrack","author":"1x5iQiNWjJbpA+GMUYZIcdbBOts=","hour_since_open":64.52361111111111,"quote":"I removed all the posts of the last three hours to combine them here.","cite":{"author":"1x5iQiNWjJbpA+GMUYZIcdbBOts=","end":198,"hour":64.52361111111111,"item":"635i5t","start":129,"thread":"635i5t"},"position":"side","nearest_neighbour":null,"why_this_one":"Shows a contrasting edge of the practice without establishing every possible outcome."} ``` ### `T4-003`: Making room through conditional restraint and help Declaration: coined, source empty. Gloss: Negotiate who may occupy which space, what to leave alone and whom to help. Question: How does keeping Mindcrack work become answerable to other work? Requests for borders and moves, offers of protection and reminders of pacts treat work as constrained by other projects. What varies is whether restraint is requested, accepted, threatened, performed or invoked later. A reported cession can be reluctant; a joke can mock the bargain. The practice is making claims on coexistence, not universal goodwill or effective control. Members: `t04`. Gate: "Material advances, answers, invokes or contests a claim about neighbouring space, restraint or reciprocal assistance." Against `T4-004`, there is a practical claim on coexistence, rather than solely an attribution of blame or legitimate participation. What varies: Requests, threats, cessions, assistance, accepted moves and promises whose fulfillment is uncertain. Exclusion: Verified treaty compliance or a community-wide ethical change. Borderline decision: Use the coexistence practice of `t04`; legitimacy-only talk stays with `t05` in `T4-004`. This is not a two-part conjunctive gate; gate_parts is empty. Outside near case: Blaming rogues without negotiating a boundary belongs in `T4-004`. Least certain membership, read both ways: `t04` is the sole coded member. Its coercive warnings and border jokes weaken a purely reciprocal reading, so the theme includes contested terms rather than defining every contact as cooperation. Mistaken for: A stable treaty among unified groups, or a general norm that Mindcrack never displaced neighbours. Disconfirmation elsewhere: Would fail if apparent agreements were only unilateral placement descriptions and no terms of coexistence were proposed or answered. Dimension: `D02`. Material: `c0031`, `c0091`, `c0094`, `c0100`. Verbatim passages and attribution appear above; the structured material below records each position and contrast. Coverage, not prevalence: 40/143 codes, receipt 2314. ```json {"fourth":"T4-003","third":"t04","second_order":"bargaining for borders and helping neighbours","code_id":"c0031","sub":"mindcrack","author":"B8nSUnd4avjwgNoL/XV4TF4VFCo=","hour_since_open":32.158055555555556,"quote":"Mind leaving me one pixel border between us?","cite":{"author":"B8nSUnd4avjwgNoL/XV4TF4VFCo=","end":102,"hour":32.158055555555556,"item":"dfplomc","start":58,"thread":"62v848"},"position":"core","nearest_neighbour":"T4-004","why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-003","third":"t04","second_order":"bargaining for borders and helping neighbours","code_id":"c0091","sub":"mindcrack","author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","hour_since_open":53.5125,"quote":"They have agreed to not expand into us and to help defend, if we don't expand into their bird and help to defend them.","cite":{"author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","end":277,"hour":53.5125,"item":"632e25","start":159,"thread":"632e25"},"position":"core","nearest_neighbour":"T4-004","why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-003","third":"t04","second_order":"bargaining for borders and helping neighbours","code_id":"c0094","sub":"mindcrack","author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","hour_since_open":58.980555555555554,"quote":"We're trying not to step on a small subreddits work, since we have just had a similar experience to that with the dutch.","cite":{"author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","end":461,"hour":58.980555555555554,"item":"dfr6y1r","start":341,"thread":"632hzb"},"position":"core","nearest_neighbour":"T4-004","why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-003","third":"t04","second_order":"bargaining for borders and helping neighbours","code_id":"c0100","sub":"mindcrack","author":"7927lbV4MzkMUyOJ9ahvrp/NT3M=","hour_since_open":59.06916666666667,"quote":"I'm on it. Moving pak 3 pixels right.","cite":{"author":"7927lbV4MzkMUyOJ9ahvrp/NT3M=","end":38,"hour":59.06916666666667,"item":"dfr77ok","start":0,"thread":"633yh1"},"position":"side","nearest_neighbour":"T4-004","why_this_one":"Shows a contrasting edge of the practice without establishing every possible outcome."} ``` ### `T4-004`: Disputing acceptable participation and responsibility Declaration: coined, source empty. Gloss: Argue about who is ruining the work, who can answer for it and what makes participation fair. Question: What kind of participation and representation can participants treat as legitimate? Condemning vandalism, challenging scripts and distinguishing organized people from rogues dispute the grounds on which damage and conduct should be judged. Apologies and contradictory voting reports vary the response. These accounts put responsibility in question; they do not reveal the actual identity or control of every placer. Members: `t05`. Gate: "Material evaluates conduct or contests who caused, authorized, represents or should answer for harmful participation." Against `T4-003`, attribution and legitimacy are the object; no practical negotiated term need be present. What varies: Shaming, apology, script objections, claims of official restraint and counterclaims about organization. Exclusion: Proof of automation, of a binding vote, or of enforceable control. Borderline decision: Keep `t05` here when accusations accompany a border dispute; the separate practical accommodation theme remains in `T4-003`. This is not a two-part conjunctive gate; gate_parts is empty. Outside near case: A conditional offer to move for protection belongs in `T4-003`. Least certain membership, read both ways: `t05` includes simple complaints about flags as boring. They judge the worth of participation without disputing a representative, so the label retains acceptable participation as well as responsibility. Mistaken for: Verified attribution of attacks, or an enforced rule system shared by all groups. Disconfirmation elsewhere: Would fail if the passages only reported neutral damage and did not evaluate conduct, attribution or legitimate representation. Dimension: `D02`. Material: `c0083`, `c0039`, `c0076`, `c0122`. Verbatim passages and attribution appear above; the structured material below records each position and contrast. Coverage, not prevalence: 22/143 codes, receipt 2318. ```json {"fourth":"T4-004","third":"t05","second_order":"arguing over who is ruining the work and what is fair","code_id":"c0083","sub":"mindcrack","author":"gb/N8iAQKMeXxp9AlKnqQWBR0y4=","hour_since_open":51.88666666666666,"quote":"Kinda defeats the point if you have a script, it's supposed to be a community thing.","cite":{"author":"gb/N8iAQKMeXxp9AlKnqQWBR0y4=","end":84,"hour":51.88666666666666,"item":"dfqmo8s","start":0,"thread":"631n36"},"position":"core","nearest_neighbour":"T4-003","why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-004","third":"t05","second_order":"arguing over who is ruining the work and what is fair","code_id":"c0039","sub":"mindcrack","author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","hour_since_open":49.955,"quote":"i realized that when I woke up, forgot to edit the post saying so; sorry. I've been helping defend from the dutch and others since then.","cite":{"author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","end":136,"hour":49.955,"item":"dfqhak1","start":0,"thread":"62v848"},"position":"core","nearest_neighbour":"T4-003","why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-004","third":"t05","second_order":"arguing over who is ruining the work and what is fair","code_id":"c0076","sub":"mindcrack","author":"8pbxW8wqZBh+6iwf5kBE5VrjZOM=","hour_since_open":47.01416666666667,"quote":"It's some guys that aren't really listening to the subreddit...","cite":{"author":"8pbxW8wqZBh+6iwf5kBE5VrjZOM=","end":63,"hour":47.01416666666667,"item":"dfq9j2r","start":0,"thread":"62zamp"},"position":"core","nearest_neighbour":"T4-003","why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-004","third":"t05","second_order":"arguing over who is ruining the work and what is fair","code_id":"c0122","sub":"mindcrack","author":"5IwgiwRkEApKdegTNPBP5PD62kY=","hour_since_open":74.87833333333333,"quote":"I just wanted to let you guys know the organized Dutch did not want the Mindcrackers to get attacked. Thats all the fault of the randoms. Sorry!","cite":{"author":"5IwgiwRkEApKdegTNPBP5PD62kY=","end":144,"hour":74.87833333333333,"item":"dfs5fc1","start":0,"thread":"638be0"},"position":"side","nearest_neighbour":"T4-003","why_this_one":"Shows a contrasting edge of the practice without establishing every possible outcome."} ``` ### `T4-005`: Reopening attachment through familiar work Declaration: coined, source empty. Gloss: Seeing familiar work recalls a previous connection and can reopen viewing or participation. Question: How can familiar work reopen a previous relationship without establishing lasting return? Remembering the community, welcoming former viewers and returning to its videos revisit a relationship to Mindcrack through familiar pictures. The connection can remain a memory or include offered defense. Those differences do not establish lasting return. This practice differs from publicly marking a local picture as an accomplishment. Members: `t06`. Gate: "Material recalls or reopens a prior connection to the community through familiar work, including welcomes and reported returns." `T4-007` marks work as an accomplishment; it need not revisit a previous relationship. Variation: Memories, welcomes, renewed viewing, old community spaces and offered defense. Exclusion: Proof of permanent return, general recruitment or a completed placement. Borderline: Place `t06` here for the relationship it reopens; `t09` belongs to `T4-007` for acknowledgment of visible work. No two-part gate is claimed. Mistaken for: Permanent membership recovery or an established recruitment effect. Disconfirmation elsewhere: Would fail where the passages neither recall a prior relationship nor welcome or revisit one. Least certain member, read both ways: `t06` is the sole member. Its flair curiosity is a side to renewed contact and remains unexplained residue rather than evidence of renewed building. Near case: a congratulation with no reopened relationship belongs in `T4-007`. Dimension: none. A dimension with accomplishment or accounting would imply a common longer-term effect the record does not establish. The member is a sole coder theme; a spread across multiple coder themes is unavailable and does not justify a forced merge. The exemplar set spans a former fan's title, an explicit viewing choice and a remembered community. Coverage is 7/143 codes, receipt 4438, hours [0,97], with no endpoint codes. This is code mass, not prevalence. > Not a Fan Anymore, But This Brought Back Some Fond Memories. Thanks Guys :) r/mindcrack, zOPEvZDWG3l7Vl4F8MG+gKshjI8=, hour 37.12722222222222, `c0042`, item `62xyiq`, thread `62xyiq`, offsets 0:75. Core material: Shows the stated practice without assuming uptake or permanent return. > I saw this in /r/place and it bought all the nostalgia back. I should really be studying but oh well... time to watch some old mindcrack vids I guess! r/mindcrack, xXUPpdpD1d86snLQPjRhvYoB2j0=, hour 39.66888888888889, `c0044`, item `dfpzvsc`, thread `62xyiq`, offsets 72:222. Core material: Shows the stated practice without assuming uptake or permanent return. > I forgot about this community until I saw this. Brought back memories :) r/mindcrack, XPYBTXCPOqJDhaVqpyO3Cig2j88=, hour 59.26444444444444, `c0050`, item `dfr7sfq`, thread `62xyiq`, offsets 0:72. Core material: Shows the stated practice without assuming uptake or permanent return. ### `T4-007`: Establishing accomplishment through acknowledgment Declaration: coined, source empty. Gloss: Locate recognizable work and mark it as an accomplishment that others can acknowledge or take further. Question: How does a local work product become something participants can publicly acknowledge or take as a next-task reference? Pointing readers to the work, congratulating builders and declaring a mission complete make a local achievement available for public acknowledgment. A next-task question can accompany this act without establishing another accepted project. This practice concerns the standing of the work, rather than a viewer's renewed relationship to the community. Members: `t09`. Gate: "Material publicly locates or acknowledges visible work as an accomplishment, possibly asking what follows it." `T4-005` reopens a prior community relationship; `T4-006` accounts for the closed event as a whole. Variation: Location pointers, greetings, congratulations, completion announcements and next-target questions. Exclusion: Independent canvas verification, lasting attachment or demonstrated uptake of a next proposal. Borderline: Place `t09` by acknowledgment of local work; `t06` by remembered attachment; `t11` and `t12` by accounting after closure. No two-part gate is claimed. Mistaken for: Verified completion, consensus over success or a guaranteed transition to another project. Disconfirmation elsewhere: Would fail where the passages only propose unstarted work and never locate or acknowledge an achievement. Least certain member, read both ways: `t09` is the sole member. A location pointer and greeting do not state completion as strongly as Mission complete; the practice includes acknowledging visible work without asserting a settled final state. Near case: memories of old viewing without a local achievement belong in `T4-005`. Dimension: none. Retain local accomplishment separately from renewed attachment and closed-event accounting; no common aggregate effect is supported. The member is a sole coder theme; a spread across multiple coder themes is unavailable and does not justify a forced merge. The exemplar set spans a next-task question, congratulations and a local completion report. Coverage is 5/143 codes, receipt 4441, hours [0,97], with no endpoint codes. This is code mass, not prevalence. > Success at 450,33! What's next? Floating block of ice? Apple Rise? r/mindcrack, j8keIeM9rZn7od9eiOVkgd5zYx0=, hour 10.442222222222222, `c0015`, item `62q0ji`, thread `62q0ji`, offsets 0:66. Core material: Shows the stated practice without assuming uptake or permanent return. > I Saw This On /r/place, Good Job Guys! r/mindcrack, SpTDwu0rvW4i5/dRq7WhtbM0GMM=, hour 11.592222222222222, `c0022`, item `62qcdm`, thread `62qcdm`, offsets 0:38. Core material: Shows the stated practice without assuming uptake or permanent return. > Mission complete r/mindcrack, 7927lbV4MzkMUyOJ9ahvrp/NT3M=, hour 61.08111111111111, `c0101`, item `634qx8`, thread `634qx8`, offsets 0:16. Core material: Shows the stated practice without assuming uptake or permanent return. ### `T4-006`: Accounting for the event in community life Declaration: coined, source empty. Gloss: Describe what the finished event left, credit and mourn contributors, and include it in regular recaps. Question: What can participants retain and contest in words once placement has ended? Inventories, loss accounts, thanks and recurring recaps make the event available as a community account after placement. The immediate witness account and the regular publication differ in format and audience. Their common practice is selecting what the event meant and left, not proving an agreed verdict or the end of further organizing. Members: `t11`, `t12`. Gate: "Material retrospectively evaluates, inventories, credits, mourns or recaps the placement event after its closure." Against `T4-005`, closed-event accounting is the shared practice rather than live recognition or local task completion. What varies: Pride, partial survival, loss, gratitude, dissatisfaction and established recap formats. Exclusion: Verified canvas survival, shared consensus, or absence of further work. Borderline decision: Use `t11`/`t12` for the completed event account. New prospective work must remain outside this gate regardless of clock. This is not a two-part conjunctive gate; gate_parts is empty. Outside near case: A new prospective call after closure is not retrospective accounting. Least certain membership, read both ways: `t12` is a recurring editorial format rather than the immediate witness exchange. Retain because it recounts or redirects attention from the finished event; no claim that all readers returned to routine follows. Mistaken for: A consensus that the event succeeded, or proof of complete closure and routine reintegration. Disconfirmation elsewhere: Would fail if the passages concerned only ongoing placement, without retrospective evaluation or incorporation into an account. Dimension: none. I considered a community-continuity aggregate with the other unaggregated theme. Recognition and accounting have distinct functions; the record does not establish their joint production of enduring community. Material: `c0115`, `c0123`, `c0129`, `c0135`, `c0137`. Verbatim passages and attribution appear above; the structured material below records each position and contrast. Coverage, not prevalence: 17/143 codes, receipt 2324. ```json {"fourth":"T4-006","third":"t11","second_order":"taking stock, mourning, and thanking people after placement ended","code_id":"c0115","sub":"mindcrack","author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","hour_since_open":73.20722222222223,"quote":"I'm proud of how much are community pulled together, not just for our own stuff, but to make allies and help friends as well.","cite":{"author":"UxXfCSY3pqwtLE85e6btxoHp8zs=","end":187,"hour":73.20722222222223,"item":"dfs02kx","start":62,"thread":"635i5t"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-006","third":"t11","second_order":"taking stock, mourning, and thanking people after placement ended","code_id":"c0123","sub":"mindcrack","author":"76BuZxx3WPb4HgMsFEOqo6a8rBU=","hour_since_open":75.1825,"quote":"RIP Doc's face that was there briefly.","cite":{"author":"76BuZxx3WPb4HgMsFEOqo6a8rBU=","end":38,"hour":75.1825,"item":"dfs6d15","start":0,"thread":"638be0"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-006","third":"t11","second_order":"taking stock, mourning, and thanking people after placement ended","code_id":"c0129","sub":"mindcrack","author":"esBmWFBISxqKD6t1X8/sEEMyTEY=","hour_since_open":78.05888888888889,"quote":"near the end, the r/indonesia crew was also trying to use scripts to overtake the pinkbird, and despite our best efforts, we couldn't completely save those allies","cite":{"author":"esBmWFBISxqKD6t1X8/sEEMyTEY=","end":393,"hour":78.05888888888889,"item":"dfsf86o","start":231,"thread":"638be0"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-006","third":"t12","second_order":"folding r/place into the room's regular recaps","code_id":"c0135","sub":"mindcrack","author":"lfgzg4/6G+biHFgtSRfNYVqij+U=","hour_since_open":77.55833333333334,"quote":"I hear that now as /r/place ended you don't have anything to do? Then I have something just for you because the FIU is here with the last recap!","cite":{"author":"lfgzg4/6G+biHFgtSRfNYVqij+U=","end":195,"hour":77.55833333333334,"item":"639sof","start":51,"thread":"639sof"},"position":"core","nearest_neighbour":null,"why_this_one":"Names or performs the practice in the declared gate."} ``` ```json {"fourth":"T4-006","third":"t12","second_order":"folding r/place into the room's regular recaps","code_id":"c0137","sub":"mindcrack","author":"HmIl7LTLf6JXyN0+7zpYK+I4uqs=","hour_since_open":84.14833333333333,"quote":"Over the past weekend, the pixel controlling craze of r/place was raging on Reddit, Mindcack fans/and some Mindcrackers contributed on this with building Mindcrackers’s logo on the subreddit","cite":{"author":"HmIl7LTLf6JXyN0+7zpYK+I4uqs=","end":2011,"hour":84.14833333333333,"item":"63bxgr","start":1821,"thread":"63bxgr"},"position":"side","nearest_neighbour":null,"why_this_one":"Shows a contrasting edge of the practice without establishing every possible outcome."} ``` ## Aggregate dimensions ### `D01`: Keeping shared work revisable and accessible Members: `T4-001`, `T4-002`. Declared coined, source empty, confidence clear. Gloss: Choose what to keep making while making ways to join and discuss it available. Question: What must remain open when recognizable work continues through changing sites and contributors? Picture revision answers what is available to do; invitations, explanations and discussion arrangements answer how a dispersed reader can find and understand it. Their distinction explains why a proposed target and an accessible contribution are different achievements. No temporal or causal relationship is asserted. Membership predicate: "A higher theme concerns the revisable object of shared picture work or access to contributions to it." D02 concerns terms and legitimacy between actors; D01 concerns the object and access to working on it. Exclusion: A claim that every reader contributes or that a fixed plan governs all projects. Mistaken for: A plan-and-command system, or a causal claim that access guarantees uptake. Disconfirmation elsewhere: Would fail if target work and contribution access were fixed independently and never required participants to reopen either. Explicit evidence: `c0012`, `c0082`, `c0027`, `c0085`, `c0112` with quoted words above. The least certain component is general explanation in `T4-002`: it opens understanding without showing a current contribution. Excluding orientation would make access mean only current recruitment; keeping it preserves that distinction. ### `D02`: Setting limits on what groups may do and promise Members: `T4-003`, `T4-004`. Declared coined, source empty, confidence arguable. Gloss: Make terms for space and help while disputing responsibility and fair means. Question: How can participants state shared obligations when who represents and controls the placers remains disputed? A pact specifies who should refrain and help. A rogue-action account disputes who can answer for damage despite assurances. Keeping the two together distinguishes stated obligations from the authority needed to make them dependable. Evidence supports the distinction; it does not show that disputes themselves generate every bargain. Membership predicate: "A higher theme concerns practical constraints on neighbouring work or contested legitimacy and responsibility for it." D01 asks what work and access are available; D02 asks what people may do or credibly undertake toward others. Exclusion: Verified control of placements, compliance or a unified community norm. Mistaken for: A shared constitution, treaty enforcement or evidence that speakers control every placer. Disconfirmation elsewhere: Would fail if binding authority settled both conduct and obligations without any negotiated or disputed limits. Explicit evidence: `c0091`, `c0094`, `c0100`, `c0083`, `c0076`, `c0122` with quoted words above. The least certain component is `T4-004`: a fairness complaint need not challenge a representative. Keeping acceptable participation in the question preserves the contrast with specific obligations. Pairwise separation: `D01` concerns what is available to make and how a reader can approach it. `D02` concerns what participants may do toward others and whether speakers can answer for it. The move `c0100` concerns a boundary obligation and stays in `T4-003`; a general new location without another party's claim stays in `T4-001`. No multiply placed coder theme crosses this boundary. ## What no higher theme picked up `t07`, making and mistaking April Fools jokes, remains contextual. Its two codes out of the full 143-code frame are the unpicked code mass, gateway receipt 2327. Both passages are quoted above as `c0025` and `c0041`; another quote is unavailable. One mistake concerns canvas loss, the other an old recap joke. Their shared vocabulary does not supply a shared organizing practice, and a catch-all community-culture construct would add no explanatory test. I considered placing it with recognition, then rejected that move: a deliberately revived joke need not recognize the canvas work. Nothing is classified out-of-scope or unresolved in this initial placement. ## Alternatives, accounting and limits I rejected a single continuing-presence bundle for `t01`, `t02`, `t03`, `t04` and `t10`: it obscures the differences among selecting work, enabling contribution, bargaining for space and controlling posts. Merging accommodation with fairness disputes also hides an enacted move's difference from an apology that denies authority. The narrower singleton themes preserve that contrast. A third dimension combining `T4-005` and `T4-006` as community reproduction would assume a supported longer-term result that this window cannot establish. They remain unaggregated, without becoming residue. The critic's alternative makes the cost of the earlier recognition bundle explicit. Pass 2 adopts the split: `T4-005` retains `t06`, while `T4-007` takes `t09`. Reopening a relationship and acknowledging a work product are different practices. Each remains unaggregated; no lasting-return or general recruitment effect follows. The old combined code mass remains historical in the pass-1 record; the current masses and receipts are given above. Assignments give one placement to each retained coder theme and contextual status to `t07`. All referenced coder themes are defined; every one is in a higher theme or the unpicked list. Each higher theme belongs to a defined dimension or explicitly has none. The assignment-derived code coverage is 141/143 placed (receipt 2391) and 2/143 contextual (2327); out-of-scope and unresolved are empty classifications, not findings of absent practices. These disjoint rows exhaust the 143-code frame. No code or theme is multiply placed, so no recurring primary/additional pair or supporting quote is available; the multiplacement log is empty. These structural counts are not prevalence, and no three-way opportunity partition is required for an exemplar claim. No onset contrast across rooms applies. R2 episodes remain the time account. The uncoded source item `dfs76hx` at hour 75.48861111111111 calls for work on another venue, as recorded in notes-R2.md. It prevents `T4-006` or the coded aftermath share from establishing an end of all coordination. It stays an uncoded contextual counterexample, never a new code. Participant accounts of rogues, scripts, survival and promises remain attributed claims. Distinct speakers' positions do not establish a collective change of mind. No relation follows from this static structure alone. R4 pass 2 records its separately warranted revision in out/model.md and its typed files.