# Higher themes

Target length: under 2,200 words excluding participant quotations.

## Basis of the grouping

The groups relate immutable coder themes. All working labels are coined for this analysis; this declaration makes no claim that the words have never appeared elsewhere. They have no literature source and are not verified literature constructs. The preparatory names remain beside the unchanged coded labels. No assignment uses a form-pass finding as a member.

Every quotation below is from placehearts. Examples were chosen for different member practices and difficult boundaries, not frequency. Coded title-only material cannot carry a relationship that appears only in a contextual reply. These are initial structural groupings, with no R4 pass or arrow yet.

## T4-001: Patterned pluralism

Declared coined. Using repeatable hearts as places for different designs and identities.

Members: `t01` (shaping and extending the heart pattern); `t03` (giving countries, causes, and characters a heart).

A repeatable unit makes different contributions recognizable as parts of a shared field. Participants specify rows, orientations and outlines, while others request a place for a country, cause or character within that form. This holds common shape and particular claims together without requiring identical content. It does not establish that each request was accepted or that uniformity was universally abandoned.

Question: How can a recognizable shared form admit distinct contributions?

The least certain member is `t01`: Pattern correction can insist on uniformity, whereas identity requests invite variation. I retain both because their common contribution form makes that tension intelligible; the grouping does not assert a settled preference for diversity. Nearest outside case: A maintenance duty in t10 concerns who must care for a heart, rather than what a contribution can look like. The fixed pattern alone cannot show that a requested identity received a heart.

Disconfirmation: In another setting, distinct designs do not use or depend on a recurring common form, or the repeated form cannot admit any variation.

Mistaken for: Standardization or unrestricted customization; the construct keeps a common format while participants seek varied contents.

Dimension: `D01`.

Evidence spread: contrasting member practices, including a boundary case rather than repeated instances of one request.

`c0013`, `62p7ub` in `62p7ub`, qoypFlw8asiiEw+4FLd+m/cGRpc=, hour 7.9775 (cite receipt 2397):

> If we place the new row's hearts upside-down, the pattern would both look nicer and be more homogeneous.

`c0136`, `62wgj4` in `62wgj4`, BitrZdvFF+dipWqU5I/tero42WY=, hour 31.834444444444443 (cite receipt 2412):

> Proposal to express some (bi) love by filling in some hearts with the bi pride flag

`c0360`, `637jof` in `637jof`, juQzsaGRafCg3zPS14MhwZoMxLQ=, hour 71.63361111111111 (cite receipt 2417):

> Looking at all the country flags and hearts, I wondered: where is my country? I asked my reddit friend to help me make a flag, but I realized that there's no empty space. He's also not interested in it anyway. So can we please reserve a heart for Vietnam?

## T4-002: Routed participation

Declared coined. Making plans, people and decision venues reachable to dispersed builders.

Members: `t02` (putting up the PlaceHearts sign and gathering builders); `t06` (moving decisions into chats, polls, and representatives).

A project needs ways for a willing stranger to find it and reach a conversation that can direct work. Signs, links, representatives and polls provide different routes between scattered activity and a proposed arrangement. Their common practice is connecting participation to a place or interlocutor, not commanding everyone who draws the motif. A claimed representative or an invitation can fail to give access or control.

Question: How can dispersed volunteers find and reach proposed collective decisions?

The least certain member is `t02`: A sign can appear to be mere publicity. The explicit purpose of reaching plans makes it an entry route to work; a purely celebratory banner would fall outside. Nearest outside case: A country-heart design request in t03 can reach a decision maker but its primary object is the proposed contribution. An accessible Discord link does not establish attendance or authority.

Disconfirmation: Builders reach and coordinate work independently of the signs, links, interlocutors and discussion routes described here.

Mistaken for: Centralized command or information broadcast; the evidence establishes routes and claims to standing, not a reliable chain of obedience.

Dimension: `D02`.

Evidence spread: contrasting member practices, including a boundary case rather than repeated instances of one request.

`c0021`, `62puvi` in `62puvi`, i3q07hRGidzxKrLspP9nQkeV2kI=, hour 9.9325 (cite receipt 2407):

> We need a /r/placehearts sign so people know where to get the plans

`c0048`, `62s82c` in `62s82c`, [deleted], hour 19.746111111111112 (cite receipt 2435):

> Unofficial representative of /r/ainbowroad/, lets talk.

`c0353`, `dfrtkcg` in `6379mw`, mEv9OI/WXg2yeUSPOwjasBNldiU=, hour 71.04277777777777 (cite receipt 2441):

> We have compromised with all of our neighbors in the past, but the aggressive actions of /r/Lakers is hard to overlook. If you wish to broker an official compromise, please visit our Discord.

## T4-003: Selective stewardship

Declared coined. Selecting what to spare or restore and seeking or assigning care for it.

Members: `t04` (making room for neighbours and turning crossings into hearts); `t05` (calling for help to defend and repair hearts and nearby work); `t10` (setting rules for which hearts stay and who maintains them).

Keeping a shared area requires choices about which designs, borders and neighbours deserve room or protection and who should supply that work. A boundary compromise, a defense request and a maintenance rule enact different parts of that practice. The category includes contested restraint and failed care; it neither equates all defense with reciprocity nor assumes official speakers control every placer.

Question: How are the objects and responsibilities of care specified in revisable common space?

The least certain member is `t04`: Boundary bargaining can concern room for a new object rather than repair. It belongs here when it specifies what may remain or change and what neighbours should preserve; it does not establish mutual care in every case. Nearest outside case: The plain request for a Vietnam heart in t03 primarily specifies a contribution, without stating a protection or maintenance duty. A generic claim that people liked the hearts does not specify a material object of care.

Disconfirmation: Protection and upkeep occur without any selection of objects, boundaries or responsibilities, or the supposed care is only generic approval with no material target.

Mistaken for: Territorial exclusion or reciprocal altruism; some stewardship makes room for others and some is unilateral, attempted or contested.

Dimension: `D01`.

Evidence spread: background negotiation, explicit duty, a conditional care offer, and a case where repair threatens design.

`c0064`, `62t34n` in `62t34n`, 46kCOT9xsFhj/bBgQLOqBJbR4Ps=, hour 22.669722222222223 (cite receipt 2420):

> My proposal is that the flag will not overwrite the hearts themselves but only the background.

`c0154`, `62wvu9` in `62wvu9`, VmRwsAbKstg3GYmpxTadXGTG3CE=, hour 33.17388888888889 (cite receipt 2472):

> Please maintain your own flag heart!

`c0342`, `6364au` in `6364au`, BmUSTdzfOnurRcOUhbKF8he+g5E=, hour 67.35666666666667 (cite receipt 2432):

> Yay! Japan is finally here! If you can all help me protect Japan I will devote the rest of my time to existing repair of other hearts.

`c0248`, `631qju` in `631qju`, RZDNnhOf+YyR3+i7OLtP7N5wqtw=, hour 51.666666666666664 (cite receipt 2423):

> Feed the Beast is trying to incorporate a heart into our design. Please stop turning it red.

## T4-004: Evaluative reframing

Declared coined. Recasting what pixels mean to justify, redirect or question changing them.

Members: `t07` (turning hateful or empty pixels into love); `t15` (working out what a contested symbol means and what replaces it).

An alteration depends partly on how people read what is there. They describe text as hateful, clearing as something to leave for beauty, or a marked heart as hateful or religious. These readings can redirect proposed work or challenge its justification. Shared vocabulary does not make the readings agree. The category identifies interpretation offered in relation to change, not the correctness of a symbol diagnosis or the effectiveness of a repainting.

Question: How do competing readings of meaning make a proposed alteration desirable or objectionable?

The least certain member is `t15`: A replacement instruction can look like ordinary repair. The surrounding dispute is about what the marked heart means; the chosen exemplars make that interpretation explicit. Repainting without a meaning claim would stay outside. Nearest outside case: The FTB request to stop turning an intended design red in t04 concerns preserving a specific design, without requiring a moral or religious reading. The researcher cannot inspect the picture and decide which participant identified the symbol correctly.

Disconfirmation: The alleged reframing changes only color or shape and offers no changed interpretation, evaluative purpose or reason to alter or preserve the object.

Mistaken for: Consensus-building or purely technical repair; interpretation can remain contested and does not establish agreement.

Dimension: `D01`.

Evidence spread: contrasting member practices, including a boundary case rather than repeated instances of one request.

`c0057`, `62so5d` in `62so5d`, KH15m4DioAtUcvy53rj5AENa5CI=, hour 21.36916666666667 (cite receipt 2444):

> Please help bottom row overwrite the hateful message

`c0076`, `62tree` in `62tree`, MHbXImUov4XJitq1JNbgAICncsU=, hour 24.508055555555554 (cite receipt 2450):

> instead of clearing I want to draw the beauty now.

`c0368`, `dfryuc4` in `637rdh`, 3GhIeFD+HNH4s2b1J4AubSkBG4o=, hour 72.79583333333333 (cite receipt 2509):

> it's a buddhist symbol...
> the maker did not even know the right nazi sign.

## T4-005: Relational regard

Declared coined. Recognizing the worth of shared work and its makers through praise, thanks or mourning.

Members: `t08` (cheering and celebrating the shared work); `t09` (mourning hearts and neighbours that were lost).

Recognition attaches value to work and relationships across different outcomes. Visitors praise a mission, builders thank collaborators, and participants mourn neighbours that disappeared. The common practice is acknowledging an attachment or contribution rather than assigning another pixel task. Its presence does not prove that recognition motivated participation, supplied rewards, or kept a relationship active.

Question: What do participants publicly value when work succeeds or is lost?

The least certain member is `t09`: A memorial may seem to concern an ended tie rather than recognition of participation. Marking the loss still expresses value for the named neighbour; no continuing membership is inferred. Nearest outside case: A time-lapse title in t12 records work without, by its words alone, valuing its makers or relationships. Pleasant wording is not evidence of a motivational reward mechanism.

Disconfirmation: Expressions treated as recognition have no object of shared effort, contribution or relationship, or are only technical records without appreciation or loss.

Mistaken for: Reward provision or durable membership; the text shows recognition, not its motivational effect or a continuing organization.

Dimension: none. The current categories do not supply a second higher theme answering the same recognition question. Records alone do not prove regard, and continuation does not prove attachment..

Evidence spread: contrasting member practices, including a boundary case rather than repeated instances of one request.

`c0086`, `62uv30` in `62uv30`, U8ot3aAawLWwdpxmM4Y2GtwNmqA=, hour 27.405 (cite receipt 2453):

> I wanted to say I love your mission, and I stand by you in spirit!

`c0384`, `63850p` in `63850p`, +ZT7SzMOGppLW3njl7CY5qRqDUw=, hour 73.18888888888888 (cite receipt 2456):

> Ladies and gentlemen, it was an honour and a privilege to create hearts with you all.
> 
> <3

`c0117`, `62vy7z` in `62vy7z`, GaRQM3H0njB0D734eZKw86oavIw=, hour 30.291666666666668 (cite receipt 2461):

> Rest in Peace /r/robotwars

## T4-006: Venue dependence

Declared coined. Recognizing limits on making hearts and trying to carry the work to available venues.

Members: `t17` (realizing the canvas ended without warning); `t18` (carrying the love into successor canvases).

The shared practice has a technical and temporal place of action. Participants discover that placement ended, regret the absence of warning, direct builders to successor services, or plan to resume when a connection holds. These are different responses to whether joint work remains possible in a venue. Grouping them makes that dependency visible without making the shutdown the demonstrated cause of every invitation or claiming successful migration.

Question: How does the availability of a venue enter the possibility of continuing the shared practice?

The least certain member is `t17`: Regret about the warning does not itself continue work. It belongs because it identifies a limit on the possibility of acting in the venue; t18 supplies attempts to find another available place, not its proven effect. Nearest outside case: A direction to the usual Discord in t06 arranges a discussion route, without necessarily changing the venue in which hearts can be made. Remembrance alone can persist with no invitation to make another heart.

Disconfirmation: The capacity to do the proposed work is unaffected by access, closure or failure of the venues participants name.

Mistaken for: Organizational death or successful migration; a closed canvas ends placement there, while continuation and completion elsewhere remain separate empirical questions.

Dimension: `D02`.

Evidence spread: contrasting member practices, including a boundary case rather than repeated instances of one request.

`c0388`, `dfsg3fw` in `63850p`, du7zfVD+hwt+idBILdDx6NRG3To=, hour 78.35027777777778 (cite receipt 2525):

> i was wondering why i couldnt place more hearts... i didnt realise that place was meant to end?

`c0393`, `6386qs` in `6386qs`, S7rv5Vd8TdYqo0jDNgnl83iMkfY=, hour 73.29583333333333 (cite receipt 2530):

> P.S. if you want to keep the love going, some people are continuing at http://pxls.space/ and there is a channel for this in our Discord. What with this basically being the best group of people Reddit has to offer, we're also hoping to continue the lovefest into other games too.

`c0415`, `dfsv4c9` in `63bmzb`, 0wnr/vVPPlz+BGSfm5Fuj5idLio=, hour 83.47 (cite receipt 2532):

> Sounds good, I'll pick back up tomorrow when it's maintaining a connection.

## What no higher theme picked up

The complete assignments retain `t11`, `t12`, `t13`, `t14`, and `t16` without a higher placement. `t11` is critique that qualifies proposed arrangements, `t12` preserves a distinctive recording practice, `t13` keeps jokes visible without turning them into resistance, `t14` leaves an unreadable intention unresolved, and `t16` preserves incompatible retrospective pixel efforts. Their reasons remain in assignments.jsonl. None is a discarded code or an out-of-scope exclusion.

The instrument reports 22 of 417 codes under these unpicked themes (coverage receipt 2947), versus 395 under placed themes (2951). These figures describe source coverage only; no category was selected, ranked or weighted by code mass. A single generalized heading for all five would hide their differences.

The identity question could support a separate higher construct if the later model finds a discriminating practice rather than a topical rename. A record of images does not yet establish how the record affected action, and a pixel feud does not itself establish collective governance.

`c0173`, `62xu79` in `62xu79`, ebvgsTLXE6YiCiivKRor26DPmNo=, hour 36.62861111111111 (cite receipt 2479):

> Losing our identity?

`c0253`, `6325yr` in `6325yr`, 9z/PDp7ExVqmHt41IG4wHREsVYE=, hour 52.86527777777778 (cite receipt 2489):

> Time lapse video of Placehearts from the beginning

`c0378`, `dfsh0k6` in `6383gl`, pWJhHgaAhsUYU/azuoXFnxHsRr4=, hour 78.65972222222223 (cite receipt 2515):

> I don't know how many times I turned that one pixel from pink to black. 
> 
> People suck.

## Coverage bindings

```json
{"for":"unpicked","mode":"coverage","unit":"codes","n":22,"denominator":{"unit":"codes","n":417,"of":"All live placehearts codes, classified by the persisted assignments"},"receipt":2947,"window":{"end":97,"lower":"gte","start":0,"upper":"lte"},"boundaries":{"end":{"hour":97,"ids":[],"items":[]},"start":{"hour":0,"ids":[],"items":[]}}}
{"for":"placed","mode":"coverage","unit":"codes","n":395,"denominator":{"unit":"codes","n":417,"of":"All live placehearts codes, classified by the persisted assignments"},"receipt":2951,"window":{"end":97,"lower":"gte","start":0,"upper":"lte"},"boundaries":{"end":{"hour":97,"ids":[],"items":[]},"start":{"hour":0,"ids":[],"items":[]}}}
```