# Higher themes

Target length: under 4,100 words.

All entries are coined constructs with empty sources and no recalled literature warrant. Original coder labels, IDs and membership are unchanged. Assignments are single placements; the upper placements of `t04`, `t06` and `t09` are split code by code. The shared practice in each paragraph, rather than vocabulary, co-occurrence or size, warrants its membership. Theme quantities below are coverage of assigned code IDs, not prevalence, agreement or explanatory adequacy. The complete count records and named populations are in `placement_counts.json`.

## `T4-001`: Actionable coordination infrastructure

Making the next contribution usable through a working venue, plans, help calls and corrected instructions.

Participants reduce the uncertainty about where to coordinate or what to do next. A plan publication, an invitation into the operational venue, a reinforcement call and a warning to stop faulty instructions all address that uncertainty. Their objects and level of detail vary. The construct concerns directing usable contributions; it does not assume people comply or that the main deliberation happened on Reddit.

Members: `t01`, `c0027`, `c0061`, `c0075`. Dimension: `D01`. This answers: How does a dispersed reader obtain a next act or common working route?

Belonging condition: Material directs participants toward a working venue, shared specification, local joint task or corrective operational instruction. Separating test: Against offered interdependence, the organising object is the next usable contribution or common working route rather than a relationship of help across community boundaries. Inside the construct: Recruitment, venue referral, design publication, local help solicitation and correction of faulty guidance; specific object and stated detail vary. Excluded: Evidence of implementation, a labour exchange with another group, a decision about whether a feature is legitimate, or a retrospective thank-you. When both fit: Prefer this gate when the material supplies the common working route or instruction. Prefer the assistance gate for a cross-community help relationship, and selective scope for an argument about the intended output. This is not a mandatory two-part gate.

A reader might mistake this for broadcast information alone or a central authority allocating tasks. Disconfirming observation in another setting: Directions and plans have no practical object or usable working route, and only advertise affiliation.

Near case: `c0005` also asks a neighbouring group to move; the Discord route is its upper placement's primary object. Least secure material: `c0027` is only a short help call. Its border-building object comes from the served thread, so it is not a standalone exemplar.

The following source-bound exemplars were chosen purposively for the stated range, not by search. Their original coder themes are `t01`, `t04`. The spread spans the different forms of the shared practice, without implying equal evidence for each.

> join our discord, our main base of operations.

`c0001`, item `62yh1s`, thread `62yh1s`, 9YOvLUrh9PrSKI24tpl2NVeYIYs=, hour 39.638888888888886, offsets 24 to 70; cite receipt 2141.

> If Your working on the heart please use this as a guide

`c0032`, item `62zrat`, thread `62zrat`, [deleted], hour 45.97972222222222, offsets 0 to 55; cite receipt 2144.

> please do NOT use them! they are 100% using the wrong set of coordinates.

`c0075`, item `637tv6`, thread `637tv6`, GcmPzUAj7RDaGA6hvG/BrdAFcJY=, hour 72.38555555555556, offsets 123 to 196; cite receipt 2147.

Assignment coverage: mode coverage, unit codes, n 13; denominator {unit: codes, n: 92, of: all live Goodboye codes in the inclusive hour 0 to hour 97 frame}; receipt 2692. Neither endpoint holds a code. The count describes assignment reach only.

## `T4-002`: Offered interdependence

Seeking, offering or crediting help across community boundaries without presuming a completed exchange.

Participants address another community as a possible source or recipient of work. A protection pledge, an invitation to cooperate and an offer to trade resources each make joint effort depend on a relationship beyond the immediate project readership. The relationship can remain an offer, or appear as retrospective ally credit. Reciprocity is explicit in one request, but is not required or inferred for every appeal.

Members: `t03`. Dimension: `D01`. This answers: How can voluntary work reach beyond its immediate readership?

Belonging condition: Material recruits, offers or credits assistance across a stated community or group boundary. Separating test: Negotiated coexistence concerns rival claims to altering or sharing an output; this gate concerns who may supply help to whose work. Inside the construct: One-way plea, cooperation proposal, protective pledge, willing labour, promised reciprocity and reported alliance credit. Excluded: A completed trade inferred from an offer, public permission to repaint, or a referral to a common planning venue alone. When both fit: Prefer coexistence when permission or terms of a contested shared output decide the act. Prefer this gate when assistance links are the object. Retain context to distinguish a declined offer from successful help. This is not a mandatory two-part gate.

A reader might mistake this for a demonstrated reciprocal exchange or a binding inter-organisational alliance. Disconfirming observation in another setting: The named outside relationships provide no requested, offered or credited assistance and are only affiliation talk.

Near case: `c0044` combines permission and help, but the permission exchange decides its placement with the Dutch negotiations. Least secure material: The retrospective Undertale ally report is credited interdependence, not proof of an executed reciprocal arrangement.

The following source-bound exemplars were chosen purposively for the stated range, not by search. Their original coder themes are `t03`. Only that coder theme carries this upper practice; breadth comes from different acts and exchanges within it. No extra member was added to meet an exemplar quota.

> Goodboye and Nintendo Switch should cooperate as Nintendo Switch has it's own cute doggo now, too.

`c0004`, item `62z00t`, thread `62z00t`, cgnxHoINAxqcJH2ELcdObAP8HdA=, hour 42.591944444444444, offsets 29 to 127; cite receipt 2150.

> i apologize for my country's imperialistic behavior, me and my group will fight for the protection of your doggo

`c0012`, item `62z3ic`, thread `62z3ic`, [deleted], hour 43.10861111111111, offsets 0 to 112; cite receipt 2153.

> could I get some help making a Mettaton face? I'll donate my resources to anything you need as well

`c0069`, item `636vam`, thread `636vam`, 8yTdKzEusbdL8t3HKJq81JxQdB0=, hour 69.81805555555556, offsets 45 to 144; cite receipt 2156.

Assignment coverage: mode coverage, unit codes, n 7; denominator {unit: codes, n: 92, of: all live Goodboye codes in the inclusive hour 0 to hour 97 frame}; receipt 2694. Neither endpoint holds a code. The count describes assignment reach only.

## `T4-003`: Negotiated coexistence

Contesting, revising or reporting the terms on which different claimants can share or change an output.

Participants face another claimant who can interfere with the same work. They state opposition, request permission, correct a misunderstanding or accept a restricted change. The shared practice is working out what each side can allow while retaining its own object. Dutch clogs and the anatomy concession differ in stakes and proposed alteration, yet both make terms and entitlement to speak consequential. Reported cooperation and later ally recognition retain the history of those terms; they do not make the settlement universal or binding.

Members: `t02`, `t07`, `c0029`. Dimension: `D02`. This answers: How are incompatible claims to one output handled, and how far can an acceptance speak for others?

Belonging condition: Material contests, proposes, accepts, revises or reports terms for different claimants to coexist around, or alter, a shared output; authority and conflicting accounts of those terms belong with the issue they qualify. Separating test: Selective project scope decides a project's desired extent or specification without bargaining over another claimant's permission; offered interdependence recruits labour rather than settles rival claims. Inside the construct: Opposition, permission, correction, conditional accommodation, authority claims, explicit mandate limits and retrospective disagreement or alliance credit. Excluded: A demonstrated community-wide settlement, internal aesthetic choice alone, generic ally recruitment or technologically enforced restoration. When both fit: Prefer this gate when the issue is what a competing claimant may do or what terms each party accepts. Internal selection of features belongs to selective scope; an actor forecast to overwrite regardless of terms belongs to reversion-limited control. This is not a mandatory two-part gate.

A reader might mistake this for consensus, a formal treaty or a single community changing its mind. Disconfirming observation in another setting: The supposed parties are unrelated, and no disputed, proposed or reported coexistence terms connect their conduct.

Near case: `c0053` invokes allies while declining expansion; it applies an internal limit rather than negotiating new permission. Least secure material: The later fighting recollection reports an experience rather than a new negotiation. It belongs as a contrary account of the same Dutch relationship, not proof of renewed attack.

The following source-bound exemplars were chosen purposively for the stated range, not by search. Their original coder themes are `t02`, `t07`. The spread spans the different forms of the shared practice, without implying equal evidence for each.

> Is it okay if we, the Netherlands, simply paint your background orange?

`c0016`, item `62zcsr`, thread `62zcsr`, [deleted], hour 44.34916666666667, offsets 0 to 71; cite receipt 2158.

> Agreement with the Dutch to prevent them from destroying these goodboys was to give one clogs.

`c0020`, item `dfq5x8e`, thread `62zdco`, X9C6UMY2Mg/ERoCNZzLtM9r6hJw=, hour 45.11527777777778, offsets 0 to 94; cite receipt 2161.

> Either your doggos get buttholes, or you are called GOOOBOYES.

`c0058`, item `634r2y`, thread `634r2y`, G1il6AsBAhqmG/1gL9EPE9LTMbY=, hour 61.1, offsets 37 to 99; cite receipt 2163.

> Ok. Do what you want with the butthole. Just don't let them vandalise anything else

`c0064`, item `dfrfjeq`, thread `634x2p`, VevQJqYKSAnyHcCJN3txOs8w9AA=, hour 62.952777777777776, offsets 0 to 83; cite receipt 2165.

Assignment coverage: mode coverage, unit codes, n 24; denominator {unit: codes, n: 92, of: all live Goodboye codes in the inclusive hour 0 to hour 97 frame}; receipt 2697. Neither endpoint holds a code. The count describes assignment reach only.

## `T4-004`: Selective project scope

Setting which features and extent count as the shared project, including deliberate refusals.

Participants define the object they want to make by proposing or excluding changes. A plan can exclude a tail, a sign can preserve a destination, and fairness can limit spatial expansion. These choices each bound the intended project. Reasons vary between appearance, recognition, routing and regard for others. A refused alteration can maintain the selected object; it need not be an enemy attack. This construct does not imply everyone accepted the specification.

Members: `t05`, `c0023`, `c0024`, `c0052`, `c0053`, `c0059`, `c0060`. Dimension: `D02`. This answers: How is the work's intended object bounded and contested?

Belonging condition: Material proposes, selects, refuses or reports exclusion of a feature, label or spatial extent of the shared project on design, routing, plan or legitimacy grounds. Separating test: Negotiated coexistence handles rival claimants' terms and permission. This gate specifies the intended object or deliberately limits it. Reversion-limited control concerns inability to change it rather than a reason to refuse. Inside the construct: Feature addition, sign wording, centring, plan exclusion, expansion question, alliance restraint and fairness to other artworks. Excluded: A forecast that bots will defeat an addition, an operational blueprint with no choice under discussion, or a binding vote outcome without a tally. When both fit: Prefer coexistence for a bargain over an outside claimant's permission. Prefer this gate for an intentional design or extent choice. Separate feasibility warnings from deliberate restraint when splitting a bundled theme. This is not a mandatory two-part gate.

A reader might mistake this for a fixed inherited goal or general resource scarcity. Disconfirming observation in another setting: The exclusions only reflect inability to act, with no proposed, selected or rejected specification or stated boundary for legitimate work.

Near case: `c0068` predicts Swedish bot destruction; it does not give a reason to choose restraint as right or desired. Least secure material: The isolated balance title leaves its precise intended change unknown; its original design grouping is retained, but it is not an exemplar for a particular specification.

The following source-bound exemplars were chosen purposively for the stated range, not by search. Their original coder themes are `t05`, `t04`, `t06`. The spread spans the different forms of the shared practice, without implying equal evidence for each.

> Proposal: put pants on the right doggo.

`c0033`, item `62zrcc`, thread `62zrcc`, T89xGs8gpChlL7XOU+XFgGwct5c=, hour 45.98555555555556, offsets 0 to 39; cite receipt 2187.

> it is alright, we are redesigning a more compact text that centers properly

`c0036`, item `dfq8jys`, thread `62zx9e`, Cvm9W+8FKUeizeUJyEpy/Rg5w58=, hour 46.565, offsets 0 to 75; cite receipt 2190.

> there's a plan for it all and curly tails just didn't make the cut!

`c0024`, item `dfq69s4`, thread `62zhgb`, +UlLrDEeNyyxA7fMmUb7YoAMR8c=, hour 45.33611111111111, offsets 0 to 67; cite receipt 2192.

> leave it be, its probably the dutches and we dont want to invade our allies

`c0053`, item `dfqj08h`, thread `6313d0`, 9YOvLUrh9PrSKI24tpl2NVeYIYs=, hour 50.560833333333335, offsets 0 to 75; cite receipt 2194.

> i dont think its very fair to other artworks to take that much space

`c0060`, item `dfrdzom`, thread `634v0q`, 9YOvLUrh9PrSKI24tpl2NVeYIYs=, hour 61.964166666666664, offsets 39 to 107; cite receipt 2197.

Assignment coverage: mode coverage, unit codes, n 13; denominator {unit: codes, n: 92, of: all live Goodboye codes in the inclusive hour 0 to hour 97 frame}; receipt 2700. Neither endpoint holds a code. The count describes assignment reach only.

## `T4-005`: Reversion-limited control

Encountering or anticipating overwrites that restrict intended changes, including reports of script and bot constraints.

Participants describe a gap between the change they want and the change they can sustain. Repeated restoration, hardcoded features and expected bots can make a proposal infeasible even while people discuss or attempt it. Forecast, observed reversion and attributed cause are distinct forms of evidence here. This shared limit differs from choosing not to build. It does not establish that automation controls the entire project, identify every operator, or verify a report of destruction.

Members: `c0072`, `c0074`, `c0079`, `c0081`, `c0092`, `c0067`, `c0068`. Dimension: `D02`. This answers: What limits participants' ability to sustain an intended change?

Belonging condition: Material concerns the feasibility of an intended alteration in the face of reported or expected overwriting, including an explicitly linked proposal and its feasibility warning. Separating test: Selective scope gives grounds for the desired or legitimate output; this gate describes or forecasts a limit on sustaining a desired change. Actionable infrastructure prescribes a next operation rather than reports the constraint. Inside the construct: Repeated reversion, an alleged script operator, hardcoded features, anticipated bots and an attributed unrealised addition. Excluded: Every overwrite being hostile or automated, a forecast treated as an observed loss, or a claim that scripts determined every pixel. When both fit: Prefer selective scope when a stated plan intentionally excludes the change. Prefer operational infrastructure when the act is a corrective instruction. Keep mere tolerance of a transient feature contextual unless it identifies a constraint or decision. This is not a mandatory two-part gate.

A reader might mistake this for automation determinism or lack of volunteers in general. Disconfirming observation in another setting: Intended changes remain freely alterable, or the reported reversions are entirely deliberate shared specifications rather than a reported or expected limit on control.

Near case: `c0024` explains that the plan excluded tails; it supplies a selected specification rather than an automation claim. Least secure material: The lesser-dog warning is prospective and does not report an attempted dog failure. Its paired proposal is retained as the object of that feasibility issue.

The following source-bound exemplars were chosen purposively for the stated range, not by search. Their original coder themes are `t04`, `t06`. The spread spans the different forms of the shared practice, without implying equal evidence for each.

> There are a bunch of different scripts running, most have the blep hardcoded

`c0074`, item `dfrxjva`, thread `637cg7`, Cvm9W+8FKUeizeUJyEpy/Rg5w58=, hour 72.35944444444445, offsets 0 to 76; cite receipt 2199.

> I hope u JayTMars stopped scripting over it sometime.

`c0092`, item `dfqdou0`, thread `630ag0`, oYfXPvXoAgoBgBLCi9dTmP/KEog=, hour 48.65611111111111, offsets 89 to 142; cite receipt 2202.

> Sweedish bots will kill.

`c0068`, item `dfrpen9`, thread `636osz`, s8TRjbvvKgnTledca31I5eTq6wU=, hour 69.555, offsets 0 to 24; cite receipt 2205.

> smol doggos, though we couldn't bring you to life through the onslaught of dutch bots

`c0081`, item `6388y2`, thread `6388y2`, GcmPzUAj7RDaGA6hvG/BrdAFcJY=, hour 73.4413888888889, offsets 69 to 154; cite receipt 2208.

Assignment coverage: mode coverage, unit codes, n 7; denominator {unit: codes, n: 92, of: all live Goodboye codes in the inclusive hour 0 to hour 97 frame}; receipt 2703. Neither endpoint holds a code. The count describes assignment reach only.

## `T4-006`: Artifact-centred affiliation

Using the dog as a reason for participation, a shared origin or a remembered accomplishment.

Participants make a built object a basis for belonging and credit. They explain why they joined its defence, narrate whose creation it was, thank people who maintained it or give it a place in shared history. The practice can be personal or collective, prospective commitment or retrospective appreciation. It preserves a reason to associate without establishing a new joint task. Claims of survival and perfection are remembered accomplishment claims, not an independently checked outcome.

Members: `t08`, `t10`, `c0022`, `c0038`, `c0046`, `c0050`, `c0025`, `c0080`. Dimension: `D03`. This answers: What social attachment and claimed accomplishment does the project produce or leave behind?

Belonging condition: Material narrates, affirms or commemorates a shared artifact as a source of participation, group origin, credit, attachment or accomplished continuity. Separating test: Purpose renewal proposes what the community will do or how its platform will function. This gate states attachment, origin or accomplishment without requiring a new collective activity. Inside the construct: Discovery and commitment, selected origin narration, recognition, thanks, farewell, reported retention, historical status and subscribing. Excluded: A new task inferred from praise, compulsory membership, a factual onset dated from a later recollection, or independently verified image quality. When both fit: Prefer purpose renewal when the turn proposes a new community function or directs activity. Keep retrospective credit and expressed attachment here even when they occur before placement closes. This is not a mandatory two-part gate.

A reader might mistake this for formal organisational membership, a shared goal or continued coordination. Disconfirming observation in another setting: The object is treated as unrelated to participants' affiliation, credit, origin or reason to continue associating.

Near case: `c0089` directs dog posting; it gives new work rather than merely expresses attachment. Least secure material: Pure final-image quality claims carry this theme through the original farewell practice; on their own they do not demonstrate affiliation or objectively perfect survival.

The following source-bound exemplars were chosen purposively for the stated range, not by search. Their original coder themes are `t08`, `t04`, `t10`, `t09`. The spread spans the different forms of the shared practice, without implying equal evidence for each.

> I wanted us to form our own annoying dog (now called goodboye)

`c0047`, item `dfqd8z3`, thread `630ag0`, p9/QDwWM2Q8xVe0NTqGNMhk7WJw=, hour 48.48777777777778, offsets 133 to 195; cite receipt 2211.

> Thank you wonderful people for keeping our beloved G O O D B O Y E alive!

`c0050`, item `630mpc`, thread `630mpc`, dQ/3HFpNRzdEnjmpKZgv2B54X6k=, hour 48.6525, offsets 25 to 98; cite receipt 2214.

> Cloggo & Doggo are now a part of Reddit history.

`c0077`, item `dfs3ign`, thread `6387vy`, s8TRjbvvKgnTledca31I5eTq6wU=, hour 74.26277777777777, offsets 0 to 48; cite receipt 2216.

> I subbed for the goodboye

`c0080`, item `dfsgz40`, thread `6387vy`, c6nyNIznOcDj6XkrhEyuS3Ni2VE=, hour 78.64555555555556, offsets 0 to 25; cite receipt 2219.

Assignment coverage: mode coverage, unit codes, n 19; denominator {unit: codes, n: 92, of: all live Goodboye codes in the inclusive hour 0 to hour 97 frame}; receipt 2705. Neither endpoint holds a code. The count describes assignment reach only.

## `T4-007`: Purpose renewal

Proposing or selecting further functions for the community and its interface while their uptake remains open.

Participants turn an event-created venue toward further activity or a continuing platform role. A mascot and button-art discussion starts while placement remains live; later polls reopen what to do, and a moderator distinguishes possible new canvas work from immediate dog posting. A sidebar offer makes one future path eligible for external support. The common practice is specifying another use for the community, not proving that a permanent goal or institution has formed.

Members: `t11`, `c0056`, `c0057`. Dimension: `D03`. This answers: How does an event-created venue propose another use for itself?

Belonging condition: Material proposes, selects or offers resources for an ongoing community role, interface or activity beyond the immediate shared image-building task. Separating test: Artifact-centred affiliation supplies a reason to belong or remember; this gate supplies a possible next function, decision procedure or activity. Infrastructure addresses operations within the current task. Inside the construct: Mascot role, offered interface work, poll revision, uncertain repeat project, immediate dog posting and conditional sidebar support. Excluded: A poll result reconstructed from a question, delivered restyling inferred from willingness, implemented sidebar recognition or a community-wide future inferred from one directive. When both fit: Prefer this gate when the object is the community's next function or platform role, even if the act supplies a guide or outside help. Prefer affiliation for subscribing, praise, origin or memory alone. This is not a mandatory two-part gate.

A reader might mistake this for a completed goal transition or an institution already reproduced after the event. Disconfirming observation in another setting: The proposed continuations only recount the past and supply no possible new function, activity or means of choosing one.

Near case: `c0080` subscribes because of the dog but gives no new function. Least secure material: `c0057` is a short offer whose interface object comes from its served thread. It stays with that role discussion but cannot independently exemplify a completed or even specific restyle.

The following source-bound exemplars were chosen purposively for the stated range, not by search. Their original coder themes are `t09`, `t11`. The spread spans the different forms of the shared practice, without implying equal evidence for each.

> So is Toby Fox/The Annoying Dog the official mascot of this Sub?

`c0056`, item `632z3o`, thread `632z3o`, /xoHIajru7Xr+bNVL/XojSctYc4=, hour 55.20333333333333, offsets 0 to 64; cite receipt 2222.

> What should /r/goodboye do?#2 decided to add the option to choose multiple answers

`c0087`, item `63a7bs`, thread `63a7bs`, [deleted], hour 78.5911111111111, offsets 0 to 82; cite receipt 2225.

> we  have plans of expanding to another /r/place copycat. but we arent sure yet.

`c0088`, item `63aa08`, thread `63aa08`, 9YOvLUrh9PrSKI24tpl2NVeYIYs=, hour 78.80972222222222, offsets 79 to 158; cite receipt 2228.

> but today we post dogs! post as many as you can!

`c0089`, item `63aa08`, thread `63aa08`, 9YOvLUrh9PrSKI24tpl2NVeYIYs=, hour 78.80972222222222, offsets 160 to 208; cite receipt 2231.

> We'll sidebar you if you choose to be a doggo subreddit!

`c0091`, item `dfskb3s`, thread `63al78`, 7DqNtk//AGpl79LCATEbCq30j8U=, hour 79.80583333333334, offsets 124 to 180; cite receipt 2234.

Assignment coverage: mode coverage, unit codes, n 8; denominator {unit: codes, n: 92, of: all live Goodboye codes in the inclusive hour 0 to hour 97 frame}; receipt 2708. Neither endpoint holds a code. The count describes assignment reach only.

## What no higher theme picked up

No whole coder theme is wholly unpicked. Every split code has its own status in `assignments.jsonl`; there is no catch-all upper theme. `c0073` from `t04` remains contextual:

> They come and go, much like real bleps.

`c0073`, item `dfrvpps`, thread `637cg7`, PJn2wgBZ8W6Bv3xNh3qBNHa8LSs=, hour 71.75, offsets 0 to 39; cite receipt 2497.

The comparison helps read the blep dispute, but it does not itself name an overwrite cause, a governing decision or a new act of affiliation. Promoting it would require the surrounding topic to do all the work. Contextual coverage is mode coverage, unit codes, n 1, denominator {unit: codes, n: 92, of: all live Goodboye codes in the inclusive hour 0 to hour 97 frame}, receipt 2689. No code lies at either endpoint. A context-only status is a statement about this upper partition, not a deletion or a claim the comment was irrelevant.