Higher themes at R3

Target length: under 1,800 words.

These are coined constructs over the unchanged coder themes, not a dynamic model. They travel on exemplars in structure.md. Their source is one room, and none is named from literature. Five themes preserve five questions rather than fill a target shape. The singleton tests event portability; the unpicked material stays unpicked. The stamped cuts are in tier_history.jsonl.

T4-001: Making hands, channels and repair available

Grounded gloss: Recruiting people, directing them to coordinating spaces and arranging repeated repair.

The shared practice is making a contribution available to ongoing work: a person joins, a venue gathers requests, or a script repeats placements. These are different means of availability, not interchangeable tasks. A channel invitation does not show uptake, and an automated hold can obstruct a new plan.

Members: t01, t09, t10. Question: How can scattered contributors become reachable and keep contributing without one task allocator?

Variation: Self-selected manual help to moderator-directed posting and automatic repair; offered to reported action.

Least sure member: t10. Bots make repair available without present hands, but they are not people assembled in a venue. Retain them as a distinct means of persistence, not as proof of a shared authority.

Near case outside: c0013 specifies a slope but supplies neither hands nor access.

Evidence: c0002, c0004, c0072, c0255, c0196; exact words, source attribution, gate and disconfirmation appear in structure.md and the JSONL. Dimension D01.

T4-002: Choosing a workable common mark

Grounded gloss: Arguing over the shape, extent, additions and shared objects that people should make.

Participants turn a recognizable flag into contested instructions about what to place, keep, remove or connect. Technical correctness, recognizable pictures, hostile targets and a shared road all specify the object of work. They vary in precision and legitimacy; holding them together does not imply that a common decision followed.

Members: t02, t03, t04, t08. Question: How does wanting a flag become a disputed but actionable object rather than a settled goal assumed in advance?

Variation: Pixel geometry to symbolic additions and erasure; a national object to a road connecting flags; workable consensus to competing proposals.

Least sure member: t08. A shared road could be read primarily as neighbour cooperation. Its placement here preserves the concrete connection being designed and repaired; reciprocal promises remain in T4-003.

Near case outside: c0197 offers conditional aid without deciding the mark to make.

Evidence: c0013, c0036, c0122, c0095, c0257; exact words, source attribution, gate and disconfirmation appear in structure.md and the JSONL. Dimension D01.

T4-003: Securing help and room without commanding neighbours

Grounded gloss: Requesting aid, bargaining over space and testing whether pacts bind participants.

Participants seek another group's contribution or restraint because they cannot simply order it. Requests invoke past help, spatial claims, apology or a reported agreement. Promises, refusal, failed moves and the distinction between organized allies and rogues expose different limits to what a neighbour can deliver. Cooperation and constrained accommodation remain competing readings within the theme.

Members: t05, t06, t07. Question: How is joint work pursued when participants cannot bind all of their own side, much less a neighbour?

Variation: Small artworks to a powerful neighbour; reciprocal help to refusal; promises to failed aid; pact claims to distrust and rogue distinctions.

Least sure member: t05. Aid need not include explicit bargaining or a return. Retain it because even unconditional aid requires another group's voluntary contribution; do not infer reciprocity from every request.

Near case outside: c0265 recognizes neighbours after work rather than arranging their next act.

Evidence: c0127, c0197, c0103, c0178, c0294; exact words, source attribution, gate and disconfirmation appear in structure.md and the JSONL. Dimension D02.

T4-004: Recognizing contributions and making an ending

Grounded gloss: Thanking others, documenting results and assessing the event as completed work.

Speakers make work attributable and assessable through thanks, praise, corrections to its record and explicit closure. Recognition can occur during work as well as after the event. It can acknowledge difficult relations without claiming that everyone agreed or that recognition renewed participation.

Members: t12, t15. Question: What remains publicly shareable when the acts of placing pixels are no longer the present task?

Variation: Thanks during construction to post-event alliance praise; documentary correction to personal enjoyment.

Least sure member: t15. A timelapse link can be documentation without social recognition. Keep it as making a common ending inspectable in text, without claiming the linked image verifies any outcome.

Near case outside: c0288 requests a new undertaking instead of recounting the old.

Evidence: c0025, c0265, c0286, c0275, c0267; exact words, source attribution, gate and disconfirmation appear in structure.md and the JSONL. Dimension D02.

T4-005: Testing whether the event can be started again

Grounded gloss: Offering replacement canvases, recruiting another flag and disputing repetition.

A replacement makes the technical opportunity recur without establishing that the prior group or purpose transfers. The invitation, skeptical refusal and reported painted flag expose the difference between repeating an object and carrying a shared undertaking forward. This is a singleton higher theme because no other coder theme tests that portability.

Members: t13. Question: What is lost when a recurring technical opportunity is treated as the same social event?

Variation: Sharing a copy to recruiting, rejecting repetition and reporting a completed new flag.

Least sure member: t13. The higher label could merely rename copies. The contrast between invitation and rejection supplies an analytical distinction, but the evidence cannot establish a transfer mechanism.

Near case outside: c0157 offers a venue for the same event rather than a new canvas.

Evidence: c0201, c0288, c0291, c0292; exact words, source attribution, gate and disconfirmation appear in structure.md and the JSONL. No dimension. Portability across replacement events is not answered by the means/object distinction or neighbour recognition alone. No second T4 theme supplies a defensible common portability dimension.

Grouping review

The common practice, not topic or adjacency, decides each bundle. Do not merge military talk, shared art or neighbour praise merely because words overlap. The rejected alternatives in structure.md include a single cooperation theme, internal/external work, an isolated bot theme, a war-to-friendship phase partition and absorbing restart into recruitment. The most consequential remaining uncertainty is t15 with t12: documentation shares public assessment of work but is not necessarily recognition of neighbours. This limits the arguable D02, not the evidence of late thanks itself.

D01 gathers T4-001 and T4-002; D02 gathers T4-003 and T4-004. The first distinguishes available means from specified objects. The second distinguishes sought commitments from credited contributions without assuming that gratitude enforces a pact. Neither establishes a causal relation. T4-005 remains outside both.

What no higher theme picked up

t11, explaining r/place to people arriving late: uneven understanding is a limit on shared knowledge, not by itself work coordination or credit. t14, taunting and insulting across borders: heterogeneous provocations and attribution cannot be lifted as a single organizing practice. Their code coverage is recorded through receipt 2489 in structure.md, with excerpts c0279, c0170 and c0240. The contextual material can still challenge a later model. It is not renamed as a catch-all.