R3 data structure

Scope and rule of placement

This structure concerns the public coded text of r/armenia. It uses no canvas observation and no unseen Discord record. Original coder IDs, labels, membership and notes remain unchanged. The initial constructs are coined here, with no borrowed source or recalled literature authority. Pass 0 denotes this pre-model structure, not an R4 model pass. R3 initially left all in_model fields false. R4 pass 1 uses every higher theme without changing membership or gates. The pass metadata records this inclusion, not a new dimension-level arrow.

The scheme distinguishes a target from effort supplied to it, permitted occupation from effective control, venue management from command, and accounting for work from doing it. These are analytical distinctions grounded in contrasting acts. They are not relations, temporal phases or a fixed division of labour.

The higher themes and dimensions travel on exemplars, not prevalence. Their gates place material, not count how common a practice is. All quotations below are source-bound citations from one room; breadth is across coder themes and episodes, not across communities. Three sweeps and their findings remain in form_pass.md. No FP finding is assigned or counted.

Closed coder themes and their higher destinations

t01: planning where and how to make Armenian flags and hearts

These passages turn a desired Armenian drawing into locations, dimensions, colours, borders, lettering, hearts, and revised plans; what varies is whether people are proposing the first flag, expanding it, relocating it, or adding a symbol.

Higher destination: T4-001. The original theme is carried whole; no code or theme was recut.

t02: expanding, defending, and maintaining Armenian pixels

These passages describe hands-on work to grow, fight for, repair, or keep the Armenian drawing; they vary between placing pixels, rallying defence, persisting under pressure, and maintenance after completion.

Higher destination: T4-002. The original theme is carried whole; no code or theme was recut.

t03: asking neighbours for pixel help and returning it

These passages make, answer, or acknowledge requests for help between Armenian participants and neighbouring groups; the direction varies between receiving aid, defending an ally, brokering mutual help, and promising or thanking help in return.

Higher destination: T4-002. The original theme is carried whole; no code or theme was recut.

t04: negotiating borders and restraining expansion

These passages work out where drawings should stop and how neighbours can coexist; they vary between ceasefires, border assurances, rules for hearts, limits on expansion, and agreements not to overwrite nearby art.

Higher destination: T4-003. The original theme is carried whole; no code or theme was recut.

t05: fighting and narrating flag takeovers

These passages participate in or narrate the canvas as invasion, fighting, takeover, and resistance; what varies is whether the speaker rallies defence or retaliation, performs the takeover, reports its progress, or comments on the attackers' coordination.

Higher destination: T4-001, T4-005. The actionable target proposals are separated from accounts and performances of conquest. The duplicate is contextual.

t06: celebrating and recounting what the flag effort achieved

These passages mark completion, victory, friendship, or the work already spent on the flag; they range from immediate cheers to explanations for late arrivals and retrospective accounts of what lasted.

Higher destination: T4-005. The original theme is carried whole; no code or theme was recut.

t07: joking through the great flag war

These passages make the pixel work into jokes and shitposting in the room's own register; the joke varies from a wrong-colour pixel and a new diaspora to Cirkeltrek banter and mock-war history.

Higher destination: T4-005. The original theme is carried whole; no code or theme was recut.

t08: using and comparing Discord coordination

These passages treat Discord as a place for coordination: judging an opponent's advantage there, asking for access, supplying invitations, welcoming participants, or reporting decisions back to Reddit; what varies is whose Discord is involved and how much returns to the thread.

Higher destination: T4-004. The original theme is carried whole; no code or theme was recut.

t09: keeping place talk in designated threads

These passages designate, replace, redirect, or contest the Reddit threads where place discussion belongs so other Armenia material can remain visible; what varies is whether the move comes from moderators, thread authors, or members objecting to clutter.

Higher destination: T4-004, T4-005. Venue acts remain together; the surviving unity account is placed as an account, and the opaque new-order title is unresolved.

t10: sharing flag designs and automatic-colouring tools

These passages give other builders an external design or a tool for carrying it out; what varies is whether the shared object is an area image, rotated lettering design, or automatic-colouring script.

Higher destination: T4-001. The original theme is carried whole; no code or theme was recut.

t11: repairing harm to neighbouring pictures

These passages identify unplanned or rogue damage, refuse retaliation, ask for it to stop, clarify what was harmed, apologize, or organize repair; the targets vary across national, character, and pride-related drawings.

Higher destination: T4-003. The original theme is carried whole; no code or theme was recut.

t12: calling out what phRQZRXYX1NI04Oyn2DTVC3MBQI= is doing

The surviving title calls out one user's conduct but gives no recoverable description that would responsibly join it to another practice.

Higher destination: unresolved, unpicked. The original theme is carried whole; no code or theme was recut.

t13: carrying the Armenian flag into Place 2.0

These late passages carry the flag practice onto a named replica by supplying new coordinates and proposing ARMENIA lettering; they vary between repeated location posts and making the new drawing recognizable.

Higher destination: T4-001. The original theme is carried whole; no code or theme was recut.

T4-001: Making and revising a flag others can build

Declaration: coined; source empty; not recalled. Gloss: Turning a desired symbol into a usable target, including replacement sites and a replica.

Participants give a collective aspiration a practical object by specifying a drawing, an address or a means of reproducing it. Keeping the national symbol does not require keeping its location, scale or means of construction. A takeover proposal belongs here when it proposes what to replace, not because it uses war words.

Question: How can people orient to the same undertaking while its specific drawing and site remain revisable?

Members: t01, t10, t13, c0015, c0092, c0165, c0167. Dimension: D01.

Gate and variation

Condition: The material proposes, specifies, revises, withdraws or supplies a reproducible target or means for making the flag or a related symbol.

Discriminator: Against T4-002, decides what or where to build rather than who will supply continuing work; against T4-005, offers a possible drawing or replacement rather than only performing or recounting victory.

Varies: From tentative dimensions and linked designs to concrete relocation, executable colouring instructions, withdrawal and replica coordinates.

Is not: A promise to defend an existing drawing, an account of past victory, or a bare hostile slogan.

Decide when both: Place a practical target proposal here even when framed as revenge; place a capacity commitment in T4-002. Split bundled coder themes by the coded act rather than duplicating them.

Gate parts: none. This is not a two-part joint requiring multiple placement.

Outside near case: c0038, in T4-002. A conditional commitment tells neighbours when help may be available, without specifying a new drawing.

Least sure member: t13. Replica coordinates enact the same specification practice, but the setting changes and no completed replica is observed. A narrower reading would leave that edge outside; a broader reading would wrongly treat every adjacent utterance as the practice.

Mistaken for: Successful implementation, stable goal agreement, or a technical blueprint guaranteed to be followed.

Disconfirmation elsewhere: In another setting, if practical specifications neither give a common target nor distinguish changed undertakings, this construct would lose its explanatory use.

Exemplar spread

c0004 from t01; c0108 from t10; c0124 from t13; c0015 from t05. These examples show different acts inside this room rather than a representative sample. Early and late examples are contrasted without positing a community-wide conversion. Their source times are the instrument's hours.

{"fourth":"T4-001","third":"t01","second_order":"planning where and how to make Armenian flags and hearts","code_id":"c0004","author":"BNw45dETeoRO6jEpMI9jf9GYr58=","hour_since_open":17.134444444444444,"quote":"I think we should plan for 4 pixel height for each color? then we can surround it with a border and add a flagpole","cite":{"author":"BNw45dETeoRO6jEpMI9jf9GYr58=","end":114,"hour":17.134444444444444,"item":"dfoqm0e","start":0,"thread":"62qqvs"},"position":"core","nearest_neighbour":"T4-002","why_this_one":"Tentative dimensions make an initial proposal reproducible."}

{"fourth":"T4-001","third":"t10","second_order":"sharing flag designs and automatic-colouring tools","code_id":"c0108","author":"8Itia8gwgDJKVfArfsluVJSPcwU=","hour_since_open":49.10055555555556,"quote":"I adapted someone else's Python2 script for automatic colouring.\n\nThe following script colours the rectangle above Turkey with the Armenian flag.\n\nPut your username and password as values of variables `username` and `password`, and leave it running.\n\nEach stripe is 6 pixels tall.","cite":{"author":"8Itia8gwgDJKVfArfsluVJSPcwU=","end":280,"hour":49.10055555555556,"item":"dfqewer","start":0,"thread":"62zu9o"},"position":"core","nearest_neighbour":"T4-002","why_this_one":"A concrete script offers a method for carrying out a specified rectangle; its sharing does not establish use."}

{"fourth":"T4-001","third":"t13","second_order":"carrying the Armenian flag into Place 2.0","code_id":"c0124","author":"[deleted]","hour_since_open":80.68888888888888,"quote":"New plan for Armenian flag in place 2.0: coordinates (500, 432)","cite":{"author":"[deleted]","end":63,"hour":80.68888888888888,"item":"63awgq","start":0,"thread":"63awgq"},"position":"core","nearest_neighbour":"T4-002","why_this_one":"Coordinates carry the practice into a new setting after original closure; outcome remains unknown."}

{"fourth":"T4-001","third":"t05","second_order":"fighting and narrating flag takeovers","code_id":"c0015","author":"mgktLaEmQHC4q55DpeCXFJ0QuhA=","hour_since_open":29.24111111111111,"quote":"I say we invade their flag. They already have the top red, so we turn the white blue and blue Orange","cite":{"author":"mgktLaEmQHC4q55DpeCXFJ0QuhA=","end":100,"hour":29.24111111111111,"item":"dfpesg7","start":0,"thread":"62t1vh"},"position":"side","nearest_neighbour":"T4-002","why_this_one":"Revenge language contains an actionable recolouring proposal, so it belongs with targets."}

Assignment coverage (not practice prevalence): {"mode":"coverage","unit":"codes","n":35,"denominator":{"unit":"codes","n":168,"of":"all delivered r/armenia code records, hours 0 through 97 inclusive"},"receipt":2312}. No code lies at either window endpoint. There is no carries/opportunity/no-opportunity partition because no quantitative prevalence claim is made.

T4-002: Keeping work going through contributions and help

Declaration: coined; source empty; not recalled. Gloss: Mobilizing one's own and neighbours' pixels under limited capacity.

Participants make available effort visible and seek more of it when keeping a drawing exceeds what they can do alone. A defender's continuing effort and a neighbour's conditional help are different sources of capacity for a shared job, rather than separate topics just because they concern different flags. Requests, commitments, reports of work, return help and acknowledgements do not guarantee enough capacity.

Question: How is limited effort sustained without a visible compulsory allocation of workers?

Members: t02, t03. Dimension: D01.

Gate and variation

Condition: The material calls for, commits, reports, redirects, bargains for or acknowledges contributions toward keeping or rebuilding drawings.

Discriminator: Against T4-001, addresses available or needed effort rather than a revised target; against T4-003, seeks support rather than primarily settling permissible occupation or responsibility for damage.

Varies: From unilateral persistence and urgent defence to conditional promises, reported aid, reciprocal maintenance and thanks for provided room or help.

Is not: A drawing specification alone, a territorial limit alone, or praise with no contribution being recognized.

Decide when both: Keep a help bargain here when contribution is its practical object. A request to stop overwriting belongs in T4-003 even when it invokes mutual safety.

Gate parts: none. This is not a two-part joint requiring multiple placement.

Outside near case: c0071, in T4-003. The expansion objection addresses what may be occupied rather than making additional effort available.

Least sure member: t03. Thanks and friendship can be retrospective rather than a live contribution; the theme is retained for its evidenced requests, conditional commitments and returned help, with acknowledgements as its edge. A narrower reading would leave that edge outside; a broader reading would wrongly treat every adjacent utterance as the practice.

Mistaken for: A pooled workforce with enforceable assignments or an unlimited alliance.

Disconfirmation elsewhere: The construct would fail elsewhere if the purported contributions were only spectators' metaphors, or if no distinction between promised and available capacity could be sustained.

Exemplar spread

c0051 from t02; c0038 from t03; c0018 from t03; c0145 from t03. These examples show different acts inside this room rather than a representative sample. Early and late examples are contrasted without positing a community-wide conversion. Their source times are the instrument's hours.

{"fourth":"T4-002","third":"t02","second_order":"expanding, defending, and maintaining Armenian pixels","code_id":"c0051","author":"cyE1IHl9gx5B7zMe8bKFb0h/v7w=","hour_since_open":34.25194444444445,"quote":"we have too many fights to fight and not enough manpower. lets just work on keeping the flag intact and going west","cite":{"author":"cyE1IHl9gx5B7zMe8bKFb0h/v7w=","end":126,"hour":34.25194444444445,"item":"dfpqkiw","start":12,"thread":"62x4ti"},"position":"core","nearest_neighbour":"T4-003","why_this_one":"A stated capacity shortage is used to narrow what work should continue."}

{"fourth":"T4-002","third":"t03","second_order":"asking neighbours for pixel help and returning it","code_id":"c0038","author":"flUcgcZ/QJJr29uZapvrRMemcGY=","hour_since_open":32.253055555555555,"quote":"We are currently fighting on our home turf but I would be happy to help you guys out once the Dutch (hopefully) stop attacking us.","cite":{"author":"flUcgcZ/QJJr29uZapvrRMemcGY=","end":130,"hour":32.253055555555555,"item":"dfplwty","start":0,"thread":"62vu0n"},"position":"core","nearest_neighbour":"T4-003","why_this_one":"Help is conditional on the home drawing no longer being attacked."}

{"fourth":"T4-002","third":"t03","second_order":"asking neighbours for pixel help and returning it","code_id":"c0018","author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","hour_since_open":28.10638888888889,"quote":"Been throwing some blocks your way for a while, brosky","cite":{"author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","end":54,"hour":28.10638888888889,"item":"dfpc39g","start":0,"thread":"62uqof"},"position":"core","nearest_neighbour":"T4-003","why_this_one":"A participant reports supplied pixels rather than merely promising them."}

{"fourth":"T4-002","third":"t03","second_order":"asking neighbours for pixel help and returning it","code_id":"c0145","author":"iV86afXsXgtiwLAp0vKJ79VHwAI=","hour_since_open":62.49333333333333,"quote":"Hey, GreyBlob here, we're trying to make a monochrome heart at 556, 761, right next your Armenia hearts <3! If possible we would like to ask for some help in maintaining it once we've fixed it as we are struggling just to make a new base at the moment. In return we'll help keep your hearts protected as much as we can!","cite":{"author":"iV86afXsXgtiwLAp0vKJ79VHwAI=","end":319,"hour":62.49333333333333,"item":"dfreufc","start":0,"thread":"632tpb"},"position":"side","nearest_neighbour":"T4-003","why_this_one":"Maintenance is requested in return for protection, with current shortage stated."}

Assignment coverage (not practice prevalence): {"mode":"coverage","unit":"codes","n":35,"denominator":{"unit":"codes","n":168,"of":"all delivered r/armenia code records, hours 0 through 97 inclusive"},"receipt":2317}. No code lies at either window endpoint. There is no carries/opportunity/no-opportunity partition because no quantitative prevalence claim is made.

T4-003: Making room for neighbours and answering for harm

Declaration: coined; source empty; not recalled. Gloss: Working out limits on pixels and responding when collective work overruns them.

Continuing beside other drawings requires more than winning space. Participants negotiate how far to go and answer complaints that their own work has become destructive. Prospective border bargains and retrospective apology differ, but both make another drawing's claim on space relevant to what builders should do. Disowning rogues can defend a group's account without controlling placements.

Question: How can people claim a collective drawing while making neighbouring claims and unwanted damage answerable?

Members: t04, t11. Dimension: D02.

Gate and variation

Condition: The material bargains for or disputes a limit on occupation, objects to encroachment, attributes responsibility for harm, apologizes or calls for restraint or repair.

Discriminator: Against T4-002, primarily concerns permission, limits or damage rather than supplying help; against T4-004, concerns drawings and neighbours rather than where public discussion belongs.

Varies: From proposed peace, ceasefires and stopping points to damage complaints, unstable borders, refusal of retaliation, apology and unsuccessful rescue.

Is not: Proof that an agreement controls every pixel, or a helper's promise alone.

Decide when both: Place a repair response here when it answers a specific harm; place ordinary mutual maintenance in T4-002. Shared safety rhetoric alone does not erase this distinction.

Gate parts: none. This is not a two-part joint requiring multiple placement.

Outside near case: c0145, in T4-002. Mutual maintenance asks for contributions; it does not answer a reported encroachment.

Least sure member: t11. Rogue attribution can evade responsibility rather than repair damage. It remains here because evasion and apology are contrasting ways to answer a concrete complaint, not evidence of restored control. A narrower reading would leave that edge outside; a broader reading would wrongly treat every adjacent utterance as the practice.

Mistaken for: Effective governance of every builder, successful restoration, or a completed transition from aggression to restraint.

Disconfirmation elsewhere: Elsewhere the construct would fail if purported limits carried no claim on action, or every response to harm were merely unrelated commentary rather than a negotiated obligation.

Exemplar spread

c0071 from t04; c0135 from t04; c0140 from t11; c0142 from t11. These examples show different acts inside this room rather than a representative sample. Early and late examples are contrasted without positing a community-wide conversion. Their source times are the instrument's hours.

{"fourth":"T4-003","third":"t04","second_order":"negotiating borders and restraining expansion","code_id":"c0071","author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","hour_since_open":39.7575,"quote":"Why? Some people have some nice art there, it's just gonna encourage them to ruin our flag. Plus, we have to stop *somewhere*.","cite":{"author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","end":126,"hour":39.7575,"item":"dfpzzko","start":0,"thread":"62y7ms"},"position":"core","nearest_neighbour":"T4-002","why_this_one":"A limit is argued through both others' art and danger to the flag."}

{"fourth":"T4-003","third":"t04","second_order":"negotiating borders and restraining expansion","code_id":"c0135","author":"z8dgF0tbU5hf9m8xs1SRh4U7yxY=","hour_since_open":55.213055555555556,"quote":"I placed a black border between our two flags on the right top of Squidward's head\n\nEdit: somebody keeps removing it","cite":{"author":"z8dgF0tbU5hf9m8xs1SRh4U7yxY=","end":116,"hour":55.213055555555556,"item":"dfqvuf3","start":0,"thread":"632tpb"},"position":"core","nearest_neighbour":"T4-002","why_this_one":"A reported placed boundary is repeatedly removed, separating stated limits from control."}

{"fourth":"T4-003","third":"t11","second_order":"repairing harm to neighbouring pictures","code_id":"c0140","author":"2psXPUPcqVd6hXhUVs4WlgFYNvk=","hour_since_open":58.91972222222222,"quote":"Don't kill Squidward. Remember what the Dutch did to us, that is what we are doing to Squidward.","cite":{"author":"2psXPUPcqVd6hXhUVs4WlgFYNvk=","end":96,"hour":58.91972222222222,"item":"dfr6ri9","start":0,"thread":"632tpb"},"position":"core","nearest_neighbour":"T4-002","why_this_one":"The speaker applies the earlier victim experience to current harm by their own side."}

{"fourth":"T4-003","third":"t11","second_order":"repairing harm to neighbouring pictures","code_id":"c0142","author":"flUcgcZ/QJJr29uZapvrRMemcGY=","hour_since_open":60.004444444444445,"quote":"We apologize. Some trolls or misinformed people did it. /r/Armenia condemns what has happened to poor Squidward.","cite":{"author":"flUcgcZ/QJJr29uZapvrRMemcGY=","end":112,"hour":60.004444444444445,"item":"dfr9vnb","start":0,"thread":"632tpb"},"position":"side","nearest_neighbour":"T4-002","why_this_one":"An apology and rogue attribution answer damage without showing restoration."}

Assignment coverage (not practice prevalence): {"mode":"coverage","unit":"codes","n":33,"denominator":{"unit":"codes","n":168,"of":"all delivered r/armenia code records, hours 0 through 97 inclusive"},"receipt":2321}. No code lies at either window endpoint. There is no carries/opportunity/no-opportunity partition because no quantitative prevalence claim is made.

T4-004: Routing coordination while containing place talk

Declaration: coined; source empty; not recalled. Gloss: Making venues usable for builders without giving place the entire subreddit.

The work needs accessible discussion, but the subreddit also has other purposes. Participants invite people into Discord, return accounts of decisions and argue over where Reddit posts belong. Concentrating discussion can aid access and protect elections or ordinary Armenia posts, while post removal can encourage another route. These acts manage attention and access, not a known chain of command over pixels.

Question: How is organizing made findable while participation competes with other uses of the forum?

Members: t08, c0017, c0069, c0094, c0114, c0116, c0117, c0131, c0090, c0123, c0129, c0130. Dimension: D02.

Gate and variation

Condition: The material establishes, supplies access to, compares, redirects, contests or explains the costs of a venue for place coordination or discussion.

Discriminator: Against T4-001, provides a place to communicate rather than the drawing target; against T4-003, bounds use of discussion space rather than occupation by drawings.

Varies: From access questions and invitations to reports from Discord, designated threads, removal threats, clutter objections and acknowledged limits to containment.

Is not: Evidence of the contents of unseen Discord deliberation, or an opaque title with no recoverable venue instruction.

Decide when both: A reported Discord agreement remains a venue-mediated coordination act here; do not infer its implementation from that report. A post-removal rationale belongs here even when it praises the project.

Gate parts: none. This is not a two-part joint requiring multiple placement.

Outside near case: c0004, in T4-001. Dimensions of the drawing make a target actionable but do not route discussion.

Least sure member: t08. The opponent's Discord advantage is an attribution, not our own access practice. It is kept as a comparison informing why coordinated communication matters, not proof about what happened on either server. A narrower reading would leave that edge outside; a broader reading would wrongly treat every adjacent utterance as the practice.

Mistaken for: A unified command channel, successful containment, or the subreddit as identical to the building group.

Disconfirmation elsewhere: Elsewhere the construct would fail if venue routing did not distinguish access to a job from protecting other discussion, or if venues had no relevant boundary of attention.

Exemplar spread

c0077 from t08; c0132 from t08; c0094 from t09; c0129 from t09; c0130 from t09. These examples show different acts inside this room rather than a representative sample. Early and late examples are contrasted without positing a community-wide conversion. Their source times are the instrument's hours.

{"fourth":"T4-004","third":"t08","second_order":"using and comparing Discord coordination","code_id":"c0077","author":"ooxjhC6/bh0BanecRvTG2R2g34E=","hour_since_open":42.964166666666664,"quote":"You guys have Discord? Then we can communicate","cite":{"author":"ooxjhC6/bh0BanecRvTG2R2g34E=","end":46,"hour":42.964166666666664,"item":"dfq38rn","start":0,"thread":"62y7ms"},"position":"core","nearest_neighbour":"T4-001","why_this_one":"Access is sought so groups can communicate."}

{"fourth":"T4-004","third":"t08","second_order":"using and comparing Discord coordination","code_id":"c0132","author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","hour_since_open":54.99805555555555,"quote":"Just as a side note, since the mods are removing any posts about it, we have a discord server that we're using to coordinate that you can join through this link.\n\nhttps://discord.gg/Gk787sZ","cite":{"author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","end":189,"hour":54.99805555555555,"item":"dfqv8kd","start":0,"thread":"632tpb"},"position":"core","nearest_neighbour":"T4-001","why_this_one":"Post removal is explicitly linked by the speaker to using another coordination venue."}

{"fourth":"T4-004","third":"t09","second_order":"keeping place talk in designated threads","code_id":"c0094","author":"mgktLaEmQHC4q55DpeCXFJ0QuhA=","hour_since_open":42.083333333333336,"quote":"Removed.   \nGreat idea, but please make the post in the stickied post. We're having an important election today and want to keep the sub clean. Thanks.","cite":{"author":"mgktLaEmQHC4q55DpeCXFJ0QuhA=","end":151,"hour":42.083333333333336,"item":"dfq2e89","start":0,"thread":"62yvdr"},"position":"core","nearest_neighbour":"T4-001","why_this_one":"The moderator names an election as the reason to redirect place content."}

{"fourth":"T4-004","third":"t09","second_order":"keeping place talk in designated threads","code_id":"c0129","author":"bK3xjinbPDXIbuTeq4MUfgOJLzo=","hour_since_open":83.10861111111112,"quote":"Mods, can we please keep all /place content on a single thread? It's great if people want to participate, but I'm here for /Armenia stuff and it's getting crowded out.","cite":{"author":"bK3xjinbPDXIbuTeq4MUfgOJLzo=","end":167,"hour":83.10861111111112,"item":"63bn9n","start":0,"thread":"63bn9n"},"position":"core","nearest_neighbour":"T4-001","why_this_one":"A member disputes the occupation of attention by place content."}

{"fourth":"T4-004","third":"t09","second_order":"keeping place talk in designated threads","code_id":"c0130","author":"mgktLaEmQHC4q55DpeCXFJ0QuhA=","hour_since_open":86.9888888888889,"quote":"We try to, but users keep making new ones. The /r/place has ended, so the posts will die down as well. Bear with us.","cite":{"author":"mgktLaEmQHC4q55DpeCXFJ0QuhA=","end":116,"hour":86.9888888888889,"item":"dft1sdd","start":0,"thread":"63bn9n"},"position":"side","nearest_neighbour":"T4-001","why_this_one":"The moderation response acknowledges incomplete containment after closure."}

Assignment coverage (not practice prevalence): {"mode":"coverage","unit":"codes","n":21,"denominator":{"unit":"codes","n":168,"of":"all delivered r/armenia code records, hours 0 through 97 inclusive"},"receipt":2324}. No code lies at either window endpoint. There is no carries/opportunity/no-opportunity partition because no quantitative prevalence claim is made.

T4-005: Telling who won, who helped and what it was worth

Declaration: coined; source empty; not recalled. Gloss: Giving pixel conflict collective stakes through conquest performances, jokes and accounts of achievement.

Participants and visitors make the event into more than a set of coloured positions: they perform conquest, identify opponents and friends, praise teamwork, joke about loss and value the time spent. These are acts of accounting for a collective struggle from different sides, not a consensus account. Their practical import is what people claim happened and mattered, not proof that those claims caused further work.

Question: What do participants and visitors make of the struggle and its results beyond the placements themselves?

Members: t06, t07, c0081, c0097, c0098, c0100, c0102, c0103, c0104, c0105, c0093. Its accounts and valuations are not, on their own, either renewed work capacity or negotiated limits; forcing it into either dimension would assert an unsupported practical effect.

Gate and variation

Condition: The material performs or narrates conquest, loss, completion, affiliation or the worth of the shared effort, including playful retellings and recognition of teamwork.

Discriminator: Against T4-001, supplies an interpretation or performed victory rather than a practical replacement target; against T4-002, values participation rather than primarily requesting or promising effort.

Varies: From takeover slogans and hostile attribution to mock history, immediate cheers, friendship, time spent and later contrasting accounts of allies.

Is not: A frequency of shared feeling, agreement among speakers, or evidence that symbolic recognition caused participation.

Decide when both: Place a concrete takeover proposal in T4-001. Retain a retrospective achievement claim here even when it names a failed site. Military vocabulary elsewhere is FP register evidence, not automatic membership.

Gate parts: none. This is not a two-part joint requiring multiple placement.

Outside near case: c0015, in T4-001. Invading by recolouring specifies a practical alternative target even though its idiom is martial.

Least sure member: t07. Some jokes are only a thin title, but the diaspora and mock-war-history passages turn the work into a tellable event. Their evaluative play is retained without treating every joke as a motivator. A narrower reading would leave that edge outside; a broader reading would wrongly treat every adjacent utterance as the practice.

Mistaken for: A single community narrative, a demonstrated reward mechanism, or war vocabulary treated as one policy.

Disconfirmation elsewhere: Elsewhere the construct would fail if the accounts did not turn separate actions into recognizable collective stakes, or if the apparent valuations were only unrelated remarks.

Exemplar spread

c0081 from t05; c0055 from t06; c0062 from t07; c0155 from t06; c0162 from t06. These examples show different acts inside this room rather than a representative sample. Early and late examples are contrasted without positing a community-wide conversion. Their source times are the instrument's hours.

{"fourth":"T4-005","third":"t05","second_order":"fighting and narrating flag takeovers","code_id":"c0081","author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","hour_since_open":45.45527777777778,"quote":"The Dutch have declared an outright invasion of the Armenian flag and the grey blob.","cite":{"author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","end":84,"hour":45.45527777777778,"item":"dfq6guq","start":0,"thread":"62y7ms"},"position":"core","nearest_neighbour":"T4-001","why_this_one":"A local invasion declaration makes the conflict publicly recognizable."}

{"fourth":"T4-005","third":"t06","second_order":"celebrating and recounting what the flag effort achieved","code_id":"c0055","author":"z8dgF0tbU5hf9m8xs1SRh4U7yxY=","hour_since_open":35.65972222222222,"quote":"I've spent my whole day trying to keep and get our flag as big as possible instead of going out with friends, it's lit lol","cite":{"author":"z8dgF0tbU5hf9m8xs1SRh4U7yxY=","end":276,"hour":35.65972222222222,"item":"dfptjk9","start":154,"thread":"62x4ti"},"position":"core","nearest_neighbour":"T4-001","why_this_one":"Time spent instead of socializing is valued as enjoyment."}

{"fourth":"T4-005","third":"t07","second_order":"joking through the great flag war","code_id":"c0062","author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","hour_since_open":40.06111111111111,"quote":"You missed the Greek genocide 2.0 and the great flag war of 2017.","cite":{"author":"/Vz/VXHXy7Fz1N9dWqphKyxDI/g=","end":65,"hour":40.06111111111111,"item":"dfq0cd6","start":0,"thread":"62x4ti"},"position":"core","nearest_neighbour":"T4-001","why_this_one":"Mock history makes the pixel conflict a tellable shared episode."}

{"fourth":"T4-005","third":"t06","second_order":"celebrating and recounting what the flag effort achieved","code_id":"c0155","author":"BIa7E1LDgdvnnYUOhE7jLocs9nM=","hour_since_open":77.34722222222223,"quote":"We lost our first flag, and failed at our second location attempt, finally securing a little spot above the Indian flag.","cite":{"author":"BIa7E1LDgdvnnYUOhE7jLocs9nM=","end":139,"hour":77.34722222222223,"item":"dfsd0ai","start":19,"thread":"632tpb"},"position":"core","nearest_neighbour":"T4-001","why_this_one":"A participant distinguishes failed locations from the eventual secured one."}

{"fourth":"T4-005","third":"t06","second_order":"celebrating and recounting what the flag effort achieved","code_id":"c0162","author":"lPjH8M2jiEg3wE3IHk2crFDyaxA=","hour_since_open":82.87361111111112,"quote":"I'm glad we made out with something. I damn near lost it when I checked back and the Dutch had taken over. Way to pull together as a team everyone. Haghtanag!!!","cite":{"author":"lPjH8M2jiEg3wE3IHk2crFDyaxA=","end":160,"hour":82.87361111111112,"item":"dfsth5j","start":0,"thread":"63azno"},"position":"side","nearest_neighbour":"T4-001","why_this_one":"A retrospective credits teamwork while retaining distress at loss."}

Assignment coverage (not practice prevalence): {"mode":"coverage","unit":"codes","n":41,"denominator":{"unit":"codes","n":168,"of":"all delivered r/armenia code records, hours 0 through 97 inclusive"},"receipt":2328}. No code lies at either window endpoint. There is no carries/opportunity/no-opportunity partition because no quantitative prevalence claim is made.

Dimensions

D01: Keeping a revisable undertaking available for work

Declaration: coined; source empty. A job can continue to be offered and supported even when its location or immediate design changes.

Members: T4-001, T4-002.

Question: What makes the collective undertaking available to be worked on again, rather than merely remembered?

This adds a distinction no member supplies alone. A recoverable target and effort for it are different requirements of a live undertaking. Target revision can be offered without support, while effort can be promised without a settled replacement. This is a contrast in what is made available, not an arrow asserting either causes the other.

Membership predicate: Gather themes whose material makes the undertaking actionable through a revisable target or the contributions available to it.

Gate: Require an explicit orientation to what people can build or to effort offered or sought for that work; retrospective worth alone does not meet it.

Least sure member: T4-002. Help acknowledgements can be retrospective. Their inclusion rests on the theme's concrete requests and conditional commitments, not an assumption that every thank-you renews work. The argument for retaining it is the common question; the argument against is loss of its distinct practical object. Keep both objects explicit rather than importing a common authority.

Varies: How specific and settled the target is, and how available, conditional or inadequate contributions are.

Mistaken for: Persistence of a fixed design, site or permanent workforce.

Disconfirmation elsewhere: If keeping work available required neither a recoverable target nor contributions that could be mobilized, the dimension would add no useful distinction.

Outside near case: c0055 values time spent but does not make further work available or settle competing occupation. Its destination T4-005 remains outside both dimensions. Exemplar evidence follows; the full cited materials above supply the source-bound breadth.

New plan for Armenian flag in place 2.0: coordinates (500, 432)

c0124, [deleted], hour 80.68888888888888; item 63awgq, thread 63awgq; cite receipt 2052.

We are currently fighting on our home turf but I would be happy to help you guys out once the Dutch (hopefully) stop attacking us.

c0038, flUcgcZ/QJJr29uZapvrRMemcGY=, hour 32.253055555555555; item dfplwty, thread 62vu0n; cite receipt 2061.

Confidence: clear. This is a placement judgement, not a sealed final confidence grade.

D02: Limiting what the joint effort may occupy

Declaration: coined; source empty. People contest how far flag work can take over a canvas or a subreddit, using different means and with incomplete control.

Members: T4-003, T4-004.

Question: How are claims on shared space made answerable when collective work competes with other legitimate uses?

This adds a distinction no member supplies alone. Limits concern different forms of occupation: drawings can overrun other pictures, and project discussion can crowd out other subreddit purposes. Negotiating a pixel boundary and redirecting posts employ different means and reveal different limits to control. This is an analytical comparison, not a claim that one produced the other.

Membership predicate: Gather themes in which another claimant's use of space constrains what the effort may occupy or where its discussion may spread.

Gate: Require an articulated limit, objection, access boundary or routing response; merely naming friends, enemies or a drawing site is insufficient.

Least sure member: T4-004. A communication invitation can enable work without limiting occupation. Its link is the venue theme's explicit pairing of access with containment; pixel harm and post clutter still have distinct objects and instruments. The argument for retaining it is the common question; the argument against is loss of its distinct practical object. Keep both objects explicit rather than importing a common authority.

Varies: What is being bounded, whose competing use is invoked, and whether a stated limit holds.

Mistaken for: A single authority effectively governing both pixel placement and public discussion.

Disconfirmation elsewhere: If neither neighbouring users nor other forum uses made a claim that participants had to answer, the supposed common problem of occupation would disappear.

Outside near case: c0055 values time spent but does not make further work available or settle competing occupation. Its destination T4-005 remains outside both dimensions. Exemplar evidence follows; the full cited materials above supply the source-bound breadth.

I placed a black border between our two flags on the right top of Squidward's head

Edit: somebody keeps removing it

c0135, z8dgF0tbU5hf9m8xs1SRh4U7yxY=, hour 55.213055555555556; item dfqvuf3, thread 632tpb; cite receipt 2076.

Removed.
Great idea, but please make the post in the stickied post. We're having an important election today and want to keep the sub clean. Thanks.

c0094, mgktLaEmQHC4q55DpeCXFJ0QuhA=, hour 42.083333333333336; item dfq2e89, thread 62yvdr; cite receipt 2092.

Confidence: arguable. This is a placement judgement, not a sealed final confidence grade.

Separating the dimensions in both directions

D01 asks whether a job and effort can be made available. D02 asks what that work may legitimately occupy, even when the job and effort already exist. A replica coordinate proposal, c0124, passes the first question but states no competing claimant's limit. The moderator's election rationale, c0094, passes the second but supplies no drawing or promised pixel capacity. Both can mention the project; shared topic does not merge their explanatory questions.

I considered one dimension, keeping the flag effort alive. It would hide the distinction between capability to work and limits imposed by others. I also considered putting T4-005 into D01 as motivation. That would require a supported connection from valuation to renewed effort; R3's accounts do not establish it. The theme therefore carries an empty dimension with its reason. No extra dimension is created solely to make every theme fit.

What no higher theme picked up

The complete coder theme t12 remains unpicked. t05 and t09 are only partly picked up after code-level splitting. The two opaque surviving titles, and the delivered duplicate span, remain explicit rather than becoming a miscellaneous category.

I see what you're doing there /u/ phRQZRXYX1NI04Oyn2DTVC3MBQI=...

c0095, [deleted], hour 42.23166666666667; item 62yxpi, thread 62yxpi; cite receipt 2119.

New order at /r/place!

c0049, [deleted], hour 34.748333333333335; item 62xcbs, thread 62xcbs; cite receipt 2123.

c0095 does not describe the called-out conduct. c0049 does not disclose an order or a venue rule. Neither can responsibly become a new higher theme. c0166 is contextual, not an independent incident: the identical item and offsets are delivered as c0167, which receives the actionable-proposal placement. The closed coding is not changed.

Unpicked code-record coverage: {"mode":"coverage","unit":"codes","n":3,"denominator":{"unit":"codes","n":168,"of":"all delivered r/armenia code records, hours 0 through 97 inclusive"},"receipt":2299}. Picked-up code-record coverage: {"mode":"coverage","unit":"codes","n":165,"denominator":{"unit":"codes","n":168,"of":"all delivered r/armenia code records, hours 0 through 97 inclusive"},"receipt":2296}. These are record coverage, not three equally substantive residual acts. The whole-theme remainder is one named coder theme out of the thirteen delivered theme definitions; that is scheme metadata, not an incident frequency.

Pair and assignment review

There is no multiple placement; multiplacement_log.jsonl is empty. The split codes each receive one destination or explicit non-placement. Thus no primary/additional pair requires a joint-versus-lump claim or cross-dimension pair count. The earlier coder regroupings are preserved, including separating neighbours' repair from negotiated borders and venue routing from Reddit containment. The present higher cuts relate those different practices without rewriting their distinction.

Every coder theme is defined and is carried whole, split with every code disposed, or listed unpicked. Every assignment destination appears in the corresponding higher theme's members. No theme and its own codes coexist as members. Every higher theme is gathered by a defined dimension or carries an explicit empty dimension and reason. Coverage classes are disjoint and exhaustive; none is out of scope. These classes are not an empirical prevalence partition. There is no onset contrast across rooms: this record has one onset. There is no supplied coder-conflict register in this case; no fleet agreement or revision-rate claim is imported.

Form findings alongside the topical structure

The prose-only FP-01 concerns how little wording can supply practical reference, with no frequency claim. FP-02 concerns war talk crossing acts, not an additional topic membership. FP-03 concerns unevenly shared references. They can inform the later model, but remain outside dimensions, assignments and coverage masses. R4 must test any proposed connection against episodes, including the failed rescue in E-07, rather than treating this structure as a dynamic model.