Higher themes at R3

These coined constructs preserve the coder-theme IDs and labels. This is a static structure, not a model of relationships or successful outcomes. All exemplars and detailed discriminators are in structure.md.

T4-001: Calibrating collective ambition

Members: t02, t03. Declared coined; source empty; recalled false.

Gloss: Making a proposed mark fit the people willing to help and the work they can maintain.

A joint project becomes tractable by making its demands and its available contributors answerable to one another. Specification gives would-be helpers something concrete to join; small versions, visible patterns and candidate sites make participation imaginable under stated shortages. This is not a claim that recruitment caused a particular redesign. What varies is whether contributors lower immediate demands, imagine later growth, request help, commit or celebrate progress; doubts and unmet requests remain part of this conditional ambition.

Belonging test: The coder theme makes joint canvas work tractable through a proposed specification or the availability, recruitment and orientation of contributors to it.

Nearest-boundary test: Choose this over maintaining coexistence when the practical issue is what helpers can build or join, rather than responding to another project occupying or changing the same space.

Variation: Scale, pattern, site and recognizable form; shortage, invitation, commitment and progress; aspirational plans versus feasible immediate work.

Disconfirmation: In another setting design and participation are fixed independently, and contributors neither adjust the project to capacity nor make capacity relevant to what can be done.

Dimension: D01. Gathers with exposure management as the internal-capacity side of making a project feasible.

T4-002: Maintaining contingent coexistence

Members: t04. Declared coined; source empty; recalled false.

Gloss: Treating overlap as something to accommodate, resist, contact or repair, rather than assuming control of a place.

Maintaining a mark is an interdependent task when other placers can erase, share or alter its space. Contributors distinguish what can be combined from what should be resisted, and describe contacting particular vandals without claiming that all purple placement stopped. The abstraction is the selective treatment of interdependence, not a synonym for any repair. This single coder theme is retained separately because a common shortage does not make neighbour accommodation and recruiting helpers the same practice. Responses vary from an initial blue-corner setback to rainbow coexistence, purple resistance and offers of upkeep; none certifies secure possession.

Belonging test: The coder theme addresses the mark's exposure to other placement through diagnosing encroachment, accommodating overlap, resisting damage, contacting placers or offering upkeep.

Nearest-boundary test: Unlike T4-001, the practical problem is coexistence with others' placement, not defining what the available contributors can build. Unlike T4-003, the account or proposal concerns maintaining work rather than valuing completed participation.

Variation: Avoiding retaliation, combining colours, resisting takeover, reporting limited private contact, and offering repair; unequal and unidentified counterparts.

Disconfirmation: The same response applies regardless of who overlaps the work, or the group maintains its mark without taking others' placement and relative power into account.

Dimension: D01. Gathers with project/capacity calibration as the external-exposure side of feasibility.

T4-003: Retrospective accomplishment without secure possession

Members: t06, t07. Declared coined; source empty; recalled false.

Gloss: Treating final contributions and enjoyable making as accomplishments even while recounting damage and loss.

At closure participants can claim to have contributed and value the making without claiming that the whole array remained intact. Final-pixel accounts establish participation; a survivor claim, repairs and losses complicate the product's continuity; enjoyment supplies an additional way to value the undertaking. These accounts share retrospective evaluation, not a demonstrated motive for earlier labour. What varies is personal authorship, surviving remnant, remembered damage, rebuilding and fun. The theme does not resolve the actual image or turn an invitation elsewhere into a completed continuation.

Belonging test: The coder theme accounts for completed canvas participation or its value through final contributions, reported survival/loss, remembered making or enjoyment.

Nearest-boundary test: Unlike T4-001 and T4-002, these are retrospective accounts of the undertaking rather than specifications or responses directing ongoing work; unlike t08's invitation, they need no new venue or future actionable request.

Variation: Personal final contribution, collective survivor, undated repairs and repeated loss, enjoyment and hope for return.

Disconfirmation: In another setting accomplishment is claimed only when an intact product persists, or final contribution and enjoyment are not used to account for completed work.

Dimension: none. No second distinct higher theme shares its retrospective-evaluation question; a second dimension for this alone would rename it, and D01 would confuse evaluation with ongoing feasibility.

Grouping review

The primary distinction is between making work tractable with potential helpers and maintaining a mark in relation to other placers. D01 gathers those contributions around feasibility, without making them the same practice. The static structure does not assert that either brought about survival. T4-003 instead relates retrospective authorship and valuation, preserving a distinction between loss of the array, a claimed remnant and fun in the making.

A single all-purpose adaptation grouping was rejected because it would hide the different treatment of neighbours. Separating design and recruitment at the higher tier would rename the lower themes and lose their explicitly capacity-conditioned specification. Merging all after-closure speech was rejected because the referral is actionable, not retrospective valuation. Another dimension for the retrospective theme alone would rename it. The singleton t04 abstraction is least certain: it is justified by the selective treatment of interdependence, not code mass, and remains open to reconsideration in R4.

The cuts are stamped history1922,1926,1930; the dimension history1994. No coder theme was recut, split or renamed. No multiple placements exist. All constructs travel on original quoted exemplars, not prevalence counts. Form findings remain prose in form_pass.md, separate from the thematic assignment arithmetic.

Coder themes no higher theme took

• t01: pulling and playing along with a fake season-release April Fools joke — out of scope for canvas organizing; shared playfulness does not connect its purpose to the canvas.
• t05: proposing other Black Mirror words and White Bear changes on the canvas — contextual alternatives without the evidenced capacity adjustment or adoption required by retained themes.
• t08: sending people to go at it again on r/pxlsspace — actionable referral preserved as a limit, without inventing migration or a higher category that simply renames it.