# Higher themes

Target length: under 4,000 words.

This is the R3 construct account. The closed coder labels and membership remain unchanged. See structure.md for every coder-theme boundary, its three cited exemplars and the full assignment inventory. All new constructs are coined; no literature claim or R4 model is implied. pass0 denotes the pre-model structure.

## Higher themes

All higher names are coined for this case, with empty source fields. None claims novelty in the literature; comparison waits for R5. Every gate places closed coder practices rather than measuring the frequency of a feature. The following material supplies purposive breadth and depth in this room; every quoted span passes the stated higher gate without needing an unseen canvas.

### `T4-001`: Bounding a temporary public

Declaration: coined. Gloss: Making a place for the special day while keeping or restoring ordinary subreddit use.

Question: How can a temporary event become an accepted way to use a continuing discussion venue, and where does that permission end?

The common practice is configuring a public occasion through rules and their enactment. Enforcing sweetness and restricting place traffic differ in content, but both make participation conditional on the continuing venue's terms. Participant performance and objections matter alongside moderator acts; the theme does not equate authority with compliance.

Gate: Material enacts, tests, closes or enforces the terms under which this subreddit hosts collective event participation. Discriminator: Against `T4-002`: it changes what public participation belongs here, rather than choosing or maintaining the shared canvas object. Against `T4-003`: the boundary is a venue rule, not a claim on another group's canvas space. Variation: Moderator rule and removal, participant enactment and speech repair, objection, closure, or redirect; playful restriction through ordinary policy. Excludes: All friendliness, all venue names, or evidence that moderators command pixel placers. Placement at a possible overlap: Retain the closed theme's primary practice: rules about hosting in `t08` remain here, while work-routing in `t03` stays `T4-002`. Shared destination alone warrants no double placement. This is a single-condition gate; gate_parts is empty.

Outside and near case: Work-routing in `t03` is the nearest excluded practice. It helps people find a plan without necessarily reclaiming the main subreddit. `c0322` is a functional diplomacy referral; `c0349` supplies the normal-use reason that makes it venue governance.

Least certain member, read both ways: `t08` is least certain. Its routine policy and redirects differ from a day of exceptional friendliness, which could justify separate themes. Keeping them together asks the additional question of temporary permission within a continuing public venue. The explicit closure in `c0256` and normal-use reason in `c0349` support that comparison. No rule is claimed to have produced pixel work.

Material choice: Material spans rule enforcement, participant enactment, closure and later routing. It draws on `t01` and `t08` at their different temporal and practical ends; it makes no prevalence claim. The source community is r/thenetherlands throughout. The quote lines retain author, instrument hour and source offsets; no UTC conversion is invented from a gateway that returns hours.

Material from `t01`, making the subreddit heilzaam for the day, position core, nearest higher neighbour `T4-002`. Why this material: Makes content permission explicit.

> Alleen positieve en heilzame content is toegestaan <3

`c0029`; K/O+4lUWIkGjH/1nt4T7mPpPeLQ=; hour 1.1288888888888888; item `dfnofh8`; thread `62mhkz`; offsets 89-142; cite receipt 2423.

Material from `t01`, making the subreddit heilzaam for the day, position core, nearest higher neighbour `T4-002`. Why this material: Shows a participant naming the norm while enacting it.

> Omdat dit vanaf vandaag de norm is! Hier is mijn pupper! 😇🐶💖

`c0091`; dXct7C8oZGYWZ4wUuixVbJM8k2A=; hour 3.2519444444444443; item `62ndhw`; thread `62ndhw`; offsets 0-60; cite receipt 2426.

Material from `t01`, making the subreddit heilzaam for the day, position core, nearest higher neighbour `T4-002`. Why this material: Closes the exceptional permission in the venue's own terms.

> We vinden het na 24 uur wel welletjes geweest, dus we zijn weer back to business.

`c0256`; WwFof85S1CVdowkWg2YobOuHH7I=; hour 24.295; item `dfp2q0z`; thread `62toci`; offsets 0-81; cite receipt 2428.

Material from `t08`, keeping place traffic within subreddit rules, position core, nearest higher neighbour `T4-002`. Why this material: States the ordinary-use reason for routing requests elsewhere.

> Please use /r/PlaceNL or /r/Cirkeltrek or https://discord.gg/S4VPhdk for these requests so this subreddit can still be used normally.

`c0349`; WwFof85S1CVdowkWg2YobOuHH7I=; hour 48.56861111111111; item `dfqdgi8`; thread `630kj1`; offsets 0-133; cite receipt 2477.

Rejected alternative: Separate moderator governance from playful enactment. This would leave the relation between performance, restriction and restoring ordinary use outside the structure. The current grouping keeps that relation a question without assuming one moderator-controlled canvas organization.

Disconfirmation elsewhere: In another setting, invitations and moderation would be unrelated individual acts, with no common participation rule or appeal to ordinary venue use. Discussion jurisdiction is distinct from `D01`'s capacity-versus-mandate question; no second dimension is justified by this tier alone.

### `T4-002`: Aligning contributions around a revisable object

Declaration: coined. Gloss: Trying to work on the same flag, layout and repair rather than overwrite each other.

Question: How can distinct proposals and separately made contributions address a shared object that still requires adjustment and care?

Making a flag, concentrating effort and removing unwanted pixels address different requirements of keeping a recognizable object available for shared work. The explanatory step is to treat the target as something participants must make usable together, rather than presume a national goal fixed it at the start. `c0071`'s same-flag appeal and `c0232`'s overwriting explanation make this practical problem explicit.

Gate: Material proposes, specifies, joins, aligns or preserves a recognizable shared canvas object or the contributions directed to it. Discriminator: Against `T4-003`: the issue is the object and how contributions meet it, rather than the entitlement or cost of extending collective reach. Against `T4-004`: present object-making differs from presenting an achievement as accomplished or pursuing its later display. Variation: Image selection through layout/coordinates and recruitment to vigilance, cleaning or repair; live attempts and reports of participation. Excludes: Any Dutch symbol, evidence all placers obey, or a guaranteed completed image. Placement at a possible overlap: Place mark-making `t02`, work-alignment `t03` and care `t04` here as whole closed practices. Do not duplicate border requests merely because they also need labour; their negotiated relation remains `T4-003`. This is a single-condition gate; gate_parts is empty.

Outside and near case: A takeover directive in `t05` may specify coordinates, yet its practice advances collective extent against other marks. `c0264` is the near case: a timed replacement of Croatia is placed with disputed reach rather than absorbed into technical alignment. `c0316`'s banner suggestion would pursue recognition rather than live object alignment.

Least certain member, read both ways: `t02` is least certain because naming a mark can stop at a proposal or an individual completed drawing. It belongs as the specification of an object that others may address, not as proof they did so. Excluding it would presume that recruiting and care already know their target; keeping it whole requires the stated limit that a recognizable object proposal is not an accepted common goal.

Material choice: The material draws from `t02`, `t03` and `t04`: initial national flag and late cheese proposal give object breadth, while concentration, layout and cleaning give practical depth. These are selected edges and intermediate practical forms, not a claim of an unbroken project across them. The source community is r/thenetherlands throughout. The quote lines retain author, instrument hour and source offsets; no UTC conversion is invented from a gateway that returns hours.

Material from `t02`, putting Dutch and local marks on the canvas, position core, nearest higher neighbour `T4-003`. Why this material: Makes a proposed shared object available.

> Voorstel om op /r/place een grote Nederlandse vlag te tekenen

`c0052`; uZQPvcOWTSuYwIXkYPLI+K5Gj5o=; hour 1.8233333333333333; item `62ms9a`; thread `62ms9a`; offsets 0-61; cite receipt 2431.

Material from `t02`, putting Dutch and local marks on the canvas, position core, nearest higher neighbour `T4-003`. Why this material: Specifies a late addition through an actionable starting place.

> Idee om een blokje kaas toe te voegen aan r/place? (start rechtsonder 620, 35)

`c0377`; [deleted]; hour 70.74388888888889; item `6377bs`; thread `6377bs`; offsets 0-78; cite receipt 2435.

Material from `t03`, joining and directing the shared pixel work, position core, nearest higher neighbour `T4-003`. Why this material: Names the need to concentrate on the same object.

> ja dat is inderdaad niet idiaal. waarschijnlijk moeten we verschuiven.
> Als we maar allemaal met dezelfde vlag bezig zijn komt het wel goed

`c0071`; /1Mk9hfc9I9uOYvDC821Oq2wkz4=; hour 3.700277777777778; item `dfnwuax`; thread `62n832`; offsets 0-138; cite receipt 2440.

Material from `t03`, joining and directing the shared pixel work, position core, nearest higher neighbour `T4-003`. Why this material: Connects a shared layout to the problem of mutual overwriting.

> Dan blijven we niet onszelf de hele tijd overschrijven en kunnen we gericht Oranje en zwarte tegeltjes blijven leggen.

`c0232`; ZlC8lJC2xd8GeO4rAskLnH5UdNY=; hour 23.148611111111112; item `dfozsqf`; thread `62t1k7`; offsets 89-207; cite receipt 2442.

Material from `t04`, watching, cleaning and restoring the work, position core, nearest higher neighbour `T4-003`. Why this material: Describes continuing care of the constructed object.

> Ik ben continu de vervuilende pixels op aan het ruimen. It's a dirty job but someone's gotta do it.

`c0072`; ScXfymoIPLBQf80difXpG3bqXts=; hour 4.395277777777777; item `dfnz1mn`; thread `62n832`; offsets 0-99; cite receipt 2445.

Rejected alternative: Separate image choice from labour and maintenance, or group every directive under coordination. The first loses the problem of identifying what contributions meet; the second loses the difference between making a shared object and claiming another group's space.

Disconfirmation elsewhere: In another setting, a mark would be fully fixed and independent contributions would require no shared target, adjustment or preservation; co-occurrence alone would not carry this construct. Gathered by `D01`.

### `T4-003`: Claiming and disputing collective reach

Declaration: coined. Gloss: Taking more land, asking neighbours to stop, and answering for what was done in the Dutch name.

Question: Who may extend action attributed to the national collective, under which terms, and with what costs or disputed means?

Expansion is addressed both as an opportunity to act and as a demand that affected people accept its reach. Neighbours request restraint or help, a dissenter undertakes repair, and retrospective speakers question the costs. The common practice is advancing or answering a claim about what the collective did or may do. Agreement, refusal and criticism vary within it. They do not form a sequence of moral improvement.

Gate: Material advances, negotiates, refuses, restrains or accounts for the scope, means or costs of action attributed to a canvas collective in relation to other groups. Discriminator: Against `T4-002`: a proposed emblem or repair task alone is not a claim on collective reach. Against `T4-004`: accounting for harm or disputed means differs from making an achieved contribution available for recognition. Variation: Enlargement and takeover, alliances and space requests, help or refusal, restraint and restitution, retrospective criticism and method disclosure; prospective and retrospective positions coexist. Excludes: A consensus, a moral conversion of the community, or verified control of all named groups or bots. Placement at a possible overlap: Keep closed `t11`'s critical accounting here rather than repeat it in commemoration. Border-help `t07` remains here because it addresses another group; routine care `t04` stays `T4-002`. This is a single-condition gate; gate_parts is empty.

Outside and near case: Pure mark specification in `t02` and care in `t04` need no judgement about another group's claim. Retrospective celebration `t09` is close because it too says what we did; the deciding issue here is entitlement, harm or contested means. `c0382`'s pride with fragmentation qualifies control but does not itself make a territorial demand or blame a victim.

Least certain member, read both ways: `t11` is the least certain member of this entire partition. Harm `c0395` directly contests the collective outcome, while `c0398`'s bot account discloses means without itself naming a victim or proposing a boundary. The case for inclusion is that both qualify what collective success can be attributed to and at whose cost; the case for exclusion is that method disclosure could stand as its own explanation. Keeping the closed theme whole retains that difference. The bot excerpt alone cannot establish territorial cause, representative strategy or a treaty, and it is not chosen as a gate-passing T4 exemplar.

Material choice: From `t05`, `t07` and `t11`, these excerpts contrast unilateral enlargement, conditional neighbour restraint, dissent-based repair and retrospective harm. They are spread over live placement and aftermath, with no claim that criticism first arose after closure. The source community is r/thenetherlands throughout. The quote lines retain author, instrument hour and source offsets; no UTC conversion is invented from a gateway that returns hours.

Material from `t05`, pushing the flag and orange line outward, position core, nearest higher neighbour `T4-004`. Why this material: Urges replacing other groups' marks.

> Vergeet niet andere vlaggen om te zetten in de Nederlandse.

`c0059`; 5m5tVYQUYhqc9sFTFJZ5GNt8g0E=; hour 9.175555555555556; item `dfoc37r`; thread `62ms9a`; offsets 0-59; cite receipt 2452.

Material from `t05`, pushing the flag and orange line outward, position core, nearest higher neighbour `T4-004`. Why this material: Explicitly links further territory to strengthening a collective realm.

> Laten we zo snel mogelijk naar links uitbreiden van waar we nu zijn! En zo meer grond overnemen en ons rijk te versterken!

`c0060`; qvLBG+aD6Sd8+yP92bdaHpckRHA=; hour 53.59583333333333; item `dfqr64m`; thread `62ms9a`; offsets 0-122; cite receipt 2455.

Material from `t07`, making and answering requests across canvas borders, position core, nearest higher neighbour `T4-004`. Why this material: Offers conditional reciprocal restraint across a disputed boundary.

> Zweden hier. Gelieve stoppen met het bouwen van uw vlaggenmast in onze vlag en wij zullen stoppen met het uitbreiden van het noorden.

`c0077`; hrpQzYDS+eFxVSd1+Pbvj5x/zlI=; hour 9.0725; item `dfobtrw`; thread `62n832`; offsets 0-133; cite receipt 2468.

Material from `t07`, making and answering requests across canvas borders, position core, nearest higher neighbour `T4-004`. Why this material: States disagreement as the reason for helping repair the neighbour's flag.

> I'm trying to help with your flag, seeing how I didn't agree with the expansion at the western border.

`c0240`; aAiOEeyzNb5zHul5t7g6DzFipe8=; hour 47.053333333333335; item `dfq9mee`; thread `62t1k7`; offsets 0-102; cite receipt 2471.

Material from `t11`, questioning expansion and accounting for harm, position side, nearest higher neighbour `T4-004`. Why this material: Directly qualifies collective success through harm to others.

> Niet om de negatieveling uit te hangen maar we hebben het ook voor enkele andere subreddits verkloot hoor.

`c0395`; fyce1X8NSUq8NaiWh78NaiZ/mno=; hour 79.44361111111111; item `dfsja64`; thread `6384js`; offsets 0-106; cite receipt 2501.

Rejected alternative: Gather moral accounting with commemoration, and separate cooperative from hostile diplomacy. That would organize the tier by valence and could conceal that actors contested reach while making it. The present cut retains opposed positions and keeps participant explanations distinct from established causes.

Disconfirmation elsewhere: In another setting, extension and its means would be governed by a settled mandate recognized by affected parties, with no incompatible claims, refusals or contested accounting. Gathered by `D01`.

### `T4-004`: Turning contributions into a public achievement

Declaration: coined. Gloss: Showing what we made, recounting contributions and trying to give the work a life in display.

Question: How does distributed work become an attributable achievement that can be shown and carried into another public form?

Presenting a result allows people to recount a contribution, value the imperfections and seek another way to show it. The museum plan makes the practical limit plain: a finished pixel work can still require money, specialist printing and a destination. Recognition and material reproduction are different acts in the same effort to make an achievement available beyond its construction.

Gate: Material presents, values, recounts or pursues further public display of a recognizable achieved canvas contribution. Discriminator: Against `T4-002`: the orientation is to an achieved contribution's recognition or afterlife, not live construction alone. Against `T4-003`: the main practice is presenting or carrying achievement, not questioning entitlement, harm or disputed means. Variation: Completion reports, inventories, thanks, pride, timelapse and self-account through a pending museum print; before and after the end of placement. Excludes: Proof all work survived, all participants approve, or the print was delivered. Placement at a possible overlap: Keep `t09`'s positive and qualified recounting here and `t12`'s specific follow-up here; retain `t11`'s critical account in `T4-003`. Do not force mixed ordinary conversation `t10` wholesale into commemoration. This is a single-condition gate; gate_parts is empty.

Outside and near case: A live layout or cleaning call in `t03`/`t04` addresses ongoing construction. Critical harm accounting in `t11` addresses the grounds on which success is claimed. The banner suggestion `c0316` is a close case, but it sits inside heterogeneous ordinary talk `t10`; this structure does not silently move its code or claim every display proposal is assigned here.

Least certain member, read both ways: `t12` is least certain because a progress question and print constraint restart practical work rather than commemorate it. It belongs because the plan concerns carrying this achieved work into display. A print-only T4 would mostly rename its coder theme; hiding it inside a celebration category would falsely imply completion. The explicit pending status supplies the difference within the higher theme.

Material choice: These excerpts draw on `t09` and `t12`, from live-window reported completion through qualified final pride to the post-event production constraint. `t09` supplies recognition and `t12` supplies an unfinished afterlife; no observed delivery connects them. The source community is r/thenetherlands throughout. The quote lines retain author, instrument hour and source offsets; no UTC conversion is invented from a gateway that returns hours.

Material from `t09`, celebrating and recounting what the canvas became, position core, nearest higher neighbour `T4-002`. Why this material: Presents the named project as completed and worthy of celebration.

> Het volkslied is voltooid!! Leve de koning!

`c0236`; tY2TNj8XBDzkfLCr45G8OfBcfhQ=; hour 29.94388888888889; item `dfpgg07`; thread `62t1k7`; offsets 0-43; cite receipt 2485.

Material from `t09`, celebrating and recounting what the canvas became, position core, nearest higher neighbour `T4-002`. Why this material: Attributes achievement while retaining fragmentation.

> Het is jammer dat we zo opgesplitst raakten op het einde. Verder ben ik wel erg trots dat we zover gekomen zijn!

`c0382`; eeMA8c44x0FJFVBFLEAiNpd6UOA=; hour 73.77; item `dfs1wha`; thread `6384js`; offsets 0-112; cite receipt 2488.

Material from `t09`, celebrating and recounting what the canvas became, position core, nearest higher neighbour `T4-002`. Why this material: Values the visible result as a joint accomplishment.

> Ik vind de imperfecties juist wel leuk. Als het helemaal perfect was dan zou het net zo goed door 1 persoon gemaakt kunnen zijn.

`c0390`; jp3D/0kbIo9rmCS7pAgrir4LwEQ=; hour 74.88333333333334; item `dfs5fwn`; thread `6384js`; offsets 0-128; cite receipt 2491.

Material from `t12`, carrying the finished canvas into a museum print, position core, nearest higher neighbour `T4-002`. Why this material: Seeks progress on a specific proposed public afterlife.

> Hoe staat het met het museumplan FQ19tz2gdjIiQWUp402mIYRxXfQ=?

`c0412`; 4n1TLGJmfLZx9GkRKksECuW9gX4=; hour 93.83722222222222; item `dftcfkq`; thread `63d73s`; offsets 0-45; cite receipt 2511.

Material from `t12`, carrying the finished canvas into a museum print, position side, nearest higher neighbour `T4-002`. Why this material: Shows the constraints that keep that afterlife pending.

> Duurt minstens een maand. Ben maar een arme student buiten mijn buitenbaantje en uitprinten en inlijsten kost nogal wat! Dit gaat niet zomaar door de printer. Moet bij een speciaal bedrijf worden geprint op speciaal papier.

`c0413`; FQ19tz2gdjIiQWUp402mIYRxXfQ=; hour 96.30722222222222; item `dftk6us`; thread `63d73s`; offsets 0-223; cite receipt 2513.

Rejected alternative: Keep print production outside achievement, or force it into live object alignment. The first misses why this new work concerns the same recognized accomplishment; the second conflates a finished pixel object with its planned physical reproduction.

Disconfirmation elsewhere: In another setting, result reports and preservation projects would not refer to a recognizable collective accomplishment, or display would be wholly unrelated to the contributions. Achievement and display raise a separate afterlife question; gathering them into `D01` would blur capacity/mandate with recognition.

## Dimension

### `D01`: Collective capacity without a settled mandate

Declaration: coined; source empty; confidence arguable. Gloss: people can work on the same mark while disagreeing about how far it may go. Members are `T4-002` and `T4-003`.

The common question is what practical alignment leaves unsettled about whose space can be taken, who may negotiate and who bears the cost. The added distinction is between being able to contribute to a shared object and being entitled to extend that object or speak for everyone involved. Neither member answers both. This is a structural contrast, not an arrow from capacity to conflict or from conflict to agreement.

Membership predicate and gate: gather a higher theme whose practical question concerns aligning action on the canvas or claiming, limiting and accounting for its collective reach. The distinction requires both kinds within the dimension. Discussion jurisdiction alone and recognition of a result alone fall outside; shared national address is insufficient. Variation concerns target adjustment and care on the capacity side, and extension, restraint, negotiation or disputed means on the mandate side.

The least secure member is `T4-003`. It carries the needed dispute over reach, but retrospective accounts cannot by themselves show a real capacity or an authoritative decision. The dimension holds as a contrast with observed local alignment in `E-04` and `E-05`, not because every dispute became an agreement. `c0071` and `c0232` explicitly describe the need to converge; `c0077` sets reciprocal terms and `c0240` connects repair to disagreement with expansion. Their full cited spans appear above. `c0395` names harm after the event. These dated exemplars supply the evidence; no additional prevalence gate or count supports this distinction. Any absence of a common binding decision is a weak claim about this public record. It does not rule out accepted mandates elsewhere.

The nearest excluded case is `T4-001`: moderators can restrict discussion without directing all placers. Gathering it here would equate authority over a venue with a mandate over the canvas. `T4-004` likewise raises what can be recognized or displayed, rather than deciding who may extend a mark. Both retain empty dimension lists with reasons.

Considered alternative: gather every higher theme under temporary collective identity. That would name the whole case and obscure the difference between a rule, a practical task, a disputed territorial claim and its later display. A second dimension grouping venue rules with commemoration would connect different questions mainly by national vocabulary and chronology. It is not justified. There is no dimension pair requiring a separation test.

Position for later comparison: the standing claim defines a group with a goal. This coined distinction asks what evidence would warrant treating a shared mark as a goal held by such a group, when acting and authorizing diverge. It neither borrows the four-problem framework nor settles that literature comparison before R5. An acknowledged authority that fixed the target and secured agreement and compliance across affected contributors would disconfirm the capacity/mandate separation in another setting.

## Coder themes no higher theme took

`t06`, playing and spotting other 1 April jokes: the surrounding occasion does not establish the specific rule or a shared project.

`t10`, working r/place into ordinary subreddit talk: its newcomer explanation, study distraction, banner proposal, representation discussion and credits do not share one higher practice. The banner is a genuine near case, left visible rather than used to absorb this whole theme. Neither theme is a catch-all; both remain contextual with reasons in assignments.jsonl. Their code mass is15 of414 in the full closed coded window, coverage receipt2741; structure.md gives the complete count record and supporting quotes.