# Structure

Target length: under 4,200 words.

## Scope and placement criterion

This initial R3 structure relates coder themes directly to higher themes. There is no third-order tier. It follows C1 sections 7 and 8 and C2 Part A section 2 through the room key. Detailed cards for the dynamic model are not acted on here. Coding and optional names remain unchanged.

The cut is preferable if it explains a common practice across different exchanges while preserving opposed positions and different outcomes. Shared vocabulary, adjacency, a shared country name or a repeated destination do not establish that common practice. Each theme travels on exemplars, not a prevalence claim. The higher-theme gates below place whole coder themes, not every individual code anew; coded fragments and the theme's internal borderline cases remain explicit.

No coder disagreement register or third-order scheme exists for this room. The descriptive labels below are exactly the delivered labels. Placement tests are my R3 tests, not invented quotations from a source gate. All evidence comes from this room. Attribution and hour accompany every exemplar; quotes were returned through cite. Selected contrasts maximize functional range, not frequency.

## Coder themes and repaired borderlines

### `t01`: rallying to build, fix, and defend the flags

Recruiting and orienting pixel effort, including correction and competing priorities. It is not an agreed design or evidence of execution. The borderline is attack recruitment: its imperative can resemble a claim in `t02`, but the theme gathers ways of summoning and directing contributions. Place the whole theme under `T4-001`; do not infer that each code is semantically disjoint from every code of its neighbour. Variation runs from an unspecified patriotic rally to an exact start corner, and from growth to defensibility. Its separating test is contribution specification versus terms of another claimant's occupancy.

Travels on exemplars; no prevalence count or three-way prevalence partition is claimed. Analyst placement test: "The material recruits, locates, specifies or prioritizes contributions to building, repairing, defending or furnishing a flag."

`c0006`, `dfom3hp` (thread `62pf3j`, DtHMHfDITvNQDKyDc92Wa/eB9aM=, hour 13.713888888888889): "We gotta coordinate so people understand where we are going, and join in. Upper left corner 1st!"

`c0027`, `62sncg` (thread `62sncg`, [deleted], hour 21.291666666666668): "Keep our flag the same size as it is, a larger territory is harder to defend. Focus efforts on protecting our flag from getting desecrated by the Swedes instead."

`c0044`, `62zbly` (thread `62zbly`, JdcxP91MpSRDBIJbkdhTg5qtLns=, hour 44.191944444444445): "Why are we spending time expanding to Day9 when it's only making the flag unsymmentrical, and meanwhile Crusider Kings are actually over our flag?"

### `t02`: taking space for Norwegian flags and art

Pressing a spatial claim, including refusing another project's room and justifying space for art. It is not agreement or an observed takeover. Its nearest neighbour is `t01`: the Danish conversion imperative is both a task proposal and a claim, but this coder theme gathers outward possession and exclusion. Art is a reason for the refusal in `c0059`, not a specific image instruction. Variation runs from proposed conversion to a direct refusal. Whole-theme placement in `T4-002` retains the original coding seam without pretending every code admits only one reading.

Travels on exemplars; no prevalence count or three-way prevalence partition is claimed. Analyst placement test: "The material asserts, challenges, proposes, reports or acknowledges terms of spatial coexistence, exclusion or support between canvas claimants."

`c0008`, `dfoytgc` (thread `62pf3j`, k0noOK7TJ5gU0RCAsOSeQumf6vM=, hour 22.7225): "Turn the Danish flag into a Norwegian flag"

`c0012`, `dfpbsa2` (thread `62pf3j`, CUSDPDxFBEnL0wFOG91RAkpcn4Y=, hour 27.976666666666667): "Sorry, you have to find another place for your logo, we will claim the area."

`c0059`, `dfrgd2p` (thread `632nt8`, c5ZCFXU9DpDTwQjL7JuR5wU0ods=, hour 63.54055555555556): "Your flag has to go. It's not aesthetically pretty. We need space for Norwegian art."

### `t03`: putting Norwegian things inside the flag

Making the flag carry recognisable objects rather than only its bands. It is not proof that those objects were built or accepted. Its nearest neighbour is `t02` when art justifies exclusion: an object proposal specifies what to put there, whereas a refusal reserves who gets room. This supports `T4-001`. Preservation of an existing object and proposing a new pawn are the substantive extremes. The carrot is a title-only fragment, not an exemplar proving a particular operation; the source's fuller action gloss is not treated as additional evidence.

Travels on exemplars; no prevalence count or three-way prevalence partition is claimed. Analyst placement test: "The material recruits, locates, specifies or prioritizes contributions to building, repairing, defending or furnishing a flag."

`c0010`, `dfp78sd` (thread `62pf3j`, Lmomr6vQKGWroT+JTe6qtszgHfE=, hour 26.108333333333334): "Don't destroy the ostehøvel, let it be integrated into the flag."

`c0046`, `62zct1` (thread `62zct1`, SvjG/Uq4Bt07tYin6uh/UrrJn2I=, hour 44.35027777777778): "norwegian carrot"

`c0047`, `62ze3s` (thread `62ze3s`, 80vCPv1sGtSd6bEZDmvOIVVBrxk=, hour 44.521388888888886): "Let's get a chess pawn on that flag!"

### `t04`: asking Norway to spare flags, artwork, and room

Addressing Norway with pleas, delegations and challenges about threatened or requested space. It is not proof that Norway accepted responsibility or that a visitor had a mandate. Against `t05`, asking for preservation alone does not show an accommodation; against `t02`, the speaker challenges rather than asserts the Norwegian claim. All contribute to making spatial terms explicit in `T4-002`, while keeping their opposed positions visible. Tone varies from begging to confrontation and the object from existing work to admission. Removed-request titles remain contextual fragments within the closed theme.

Travels on exemplars; no prevalence count or three-way prevalence partition is claimed. Analyst placement test: "The material asserts, challenges, proposes, reports or acknowledges terms of spatial coexistence, exclusion or support between canvas claimants."

`c0011`, `dfp8b66` (thread `62pf3j`, 6vGyM6l11x+FaXUwVXjW98SuKjU=, hour 26.539444444444445): "some members of our subreddit have become worried that your flag is going to cover up our work. Is there any way that you guys could go around us?"

`c0019`, `dfpeytj` (thread `62s1p6`, QRDlKs3KCD2N6Mw6UxBti2z6l1c=, hour 29.315833333333334): "NORWAY SENPAI PLEASE SPARE OUR DUDE"

`c0022`, `dfou2og` (thread `62s629`, ozp8U3WnN4W8ZhK6LEN8hUQ/NJM=, hour 20.156666666666666): "Now we are looking to start a new life, at somewhere that we could live in peace, But the canvas is full. So we want to migrate to your bottom right side of your flag would you accept us ?"

### `t05`: making pacts, hearts, and workable borders

Proposing, reporting or acknowledging ways projects can live alongside one another. It is not uniformly mutual bargaining. A reported pact, a proposed design, an offer of labour and accepting a refusal have different evidential force. Against `t04`, it goes beyond a bare preservation plea into a proposed arrangement, support or response. Against `t02`, accepted refusal is not consent to the refuser's claimed authority: it is the requester's stated next move. Its least consensual edge still belongs in `T4-002` because it articulates how to proceed around another claim. Outcome varies from open proposal to reciprocal thanks to unilateral looking elsewhere.

Travels on exemplars; no prevalence count or three-way prevalence partition is claimed. Analyst placement test: "The material asserts, challenges, proposes, reports or acknowledges terms of spatial coexistence, exclusion or support between canvas claimants."

`c0037`, `dfq2fk7` (thread `62yuxs`, pwvcBTT6om7V+x3tNsJrrRaABbE=, hour 42.121944444444445): "We decided on a hanging flag instead of expansion. You guys should be good."

`c0039`, `dfq2ene` (thread `62yvzd`, pwvcBTT6om7V+x3tNsJrrRaABbE=, hour 42.09527777777778): "We made a pact. We're helping you guys now."

`c0106`, `dfrx3ig` (thread `637igs`, HaVdRKQRlkHbJcUfoNdFs48ezEk=, hour 72.19805555555556): "Duly noted, thanks for the responses everyone, we'll try to look elsewhere."

### `t06`: sending canvas business to r/norge and Discord

Locating or directing canvas business in named venues. It is not demonstrated receipt, membership continuity or effective coordination. Attribution in the early repair thread is weaker than an active referral and is kept as attribution. Against `t07`, the distinctive contribution is an operating destination or audience, rather than explaining this venue's purpose; both fit `T4-003` as ways of locating answerability. Specificity varies from a bare destination to a thread or diplomatic channel. A coded fragment such as the wacky-organization remark requires its already-read item context, not inference from the label alone.

Travels on exemplars; no prevalence count or three-way prevalence partition is claimed. Analyst placement test: "The material locates flag work or canvas discussion in a venue, supplies its audience or route, or defines, enforces or responds to the boundary of this room's responsibility."

`c0029`, `dfp9x9h` (thread `62ue1x`, SCfBf6RzXth1DXYDvOK5hdJUVOA=, hour 27.20388888888889): "Better asked at /r/norge, they are the ones that seem to actually care about /r/place."

`c0061`, `dfr076f` (thread `632xaq`, /zsFBM0+BNiu+TP4+b+d3OzgRuI=, hour 56.75055555555556): "r/norge is the main Norwegian sub, and is coordinating the place flag."

`c0067`, `dfrbw8a` (thread `6340w3`, 3sz51JBe4fWK4SmPUkh/wf6yGyI=, hour 60.86138888888889): "Go to r/norge"

### `t07`: telling r/place visitors this is the tourist and English sub

Defining or contesting this room's responsibility for canvas business, through venue purpose, rejection, apology or distancing. It is not proof that all members reject r/place or that nobody here organizes. Against `t06`, the test is limiting responsibility rather than only giving a route. Both fit `T4-003`; the tourist explanation and pointer can be in the same utterance without being the same move. The Discord takeover allegation is the least secure member: it blames an external subset and contrasts an upset 'us', but does not itself define the tourist sub. Keep it as participant distancing, not a verified causal explanation. The removed r/Place title has no independently recoverable stance.

Travels on exemplars; no prevalence count or three-way prevalence partition is claimed. Analyst placement test: "The material locates flag work or canvas discussion in a venue, supplies its audience or route, or defines, enforces or responds to the boundary of this room's responsibility."

`c0063`, `dfrdpn5` (thread `632xaq`, dl+qWIj9D/KVL3mJ9cUccVbfN4s=, hour 61.80416666666667): "Some kids took over the discord channel and wanted to expand the flag for no other reason than expansion. Lots of us were upset."

`c0080`, `dfrk8lt` (thread `635y62`, KfiMKXUpPg7vcGxtRsSJyXGRIGY=, hour 66.75222222222222): "This sub is mainly for people who want to travel to or move to Norway. You would be better off discussing this in the megathread on r/norge."

`c0092`, `dfrn6db` (thread `636dy9`, ytn8lNKKFg1Zs42tAi+sYNMV9YM=, hour 68.55305555555556): "Jesus, stop spamming the wrong sub, /r/Norge is the sub behind the flag. This is the tourist/English speaking sub."

### `t08`: joking in flags, sovereign land, and displaced migrants

Performing canvas disputes through playful identities and national fictions. It is not a uniform tactic or a separate successful coordination mechanism. Its nearest substantive neighbours vary: the sovereign exchange follows a pact, while the migrant refusal answers a live request. A single T4 home would equate unlike actions or force the rest into that refusal's practice. Contextual status preserves the closed topic theme; the form-pass prose carries its cross-cutting function. The register can diminish stakes, elaborate a shared fiction or refuse admission. Its live refusal remains in `E-47` without a duplicate assignment.

Travels on exemplars; no prevalence count or three-way prevalence partition is claimed. Analyst placement test: "Preserve a register across unlike turn functions without assigning one uniform work practice."

`c0024`, `dfoub38` (thread `62s629`, ozp8U3WnN4W8ZhK6LEN8hUQ/NJM=, hour 20.314722222222223): "eaten by sweden brother, just like they did to our"

`c0042`, `dfq3jxl` (thread `62yvzd`, JdcxP91MpSRDBIJbkdhTg5qtLns=, hour 43.26833333333333): "Why is Crusader Kings on Sovereign Norwegian territory."

`c0104`, `dfrvnny` (thread `637igs`, zDtCo6Y5BBf551T0i+tgBirsRuM=, hour 71.7325): "We can't take any more displaced migrants, sorry. Ask Sweden."

### `t09`: remembering staying friends until the game ended

Looking back on an alliance and explaining its setting. It is not a live pact or proof of care after the event. Against `t05`, its action is retrospective recognition rather than arranging current coexistence. It remains contextual rather than being forced into `T4-002`. Variation runs from honouring an ally to recalling friendship to supplying context for an unfamiliar reader. A new T4 called alliance maintenance would overstate what these passages show, especially the context-only final code.

Travels on exemplars; no prevalence count or three-way prevalence partition is claimed. Analyst placement test: "Preserve retrospective affiliation without inferring live work."

`c0107`, `638exb` (thread `638exb`, 8WgqStU4SfAILMY2/ahzp/4q+N0=, hour 73.83722222222222): "WE WERE HONORED TO BE YOUR ALLY, MUCH LOVE FROM DUTCHIES <3"

`c0108`, `dfs6i7s` (thread `638exb`, pwvcBTT6om7V+x3tNsJrrRaABbE=, hour 75.24): "It was great fun and glad to see we stayed friends untill the game ended."

`c0109`, `dfsbipw` (thread `638exb`, lABEi+kkP6efaGHdG6Mpe2M0I8I=, hour 76.87472222222222): "R/place"

## Higher themes

### `T4-001`: Specifying what to put on the flag

Coined, source empty, recalled false. Gloss: Turning a flag into particular contributions people can make or protect.

Mobilizing people and proposing objects both make the flag actionable: they specify a contribution rather than establish who may occupy contested space. Calls range from broad patriotic recruitment to exact proportions, starting corners and images to retain. A bounded repair and a new chess pawn are different contributions to the same publicly specified project, not evidence of one accepted design.

Question: What are participants being asked to contribute to the flag?

Members: `t01`, `t03`. Gate condition: "The material recruits, locates, specifies or prioritizes contributions to building, repairing, defending or furnishing a flag." Discriminator: Against T4-002, the decisive content concerns a contribution or operation, not permission, exclusion or terms with a neighbouring claimant. What varies: Broad rally to exact pixel instruction; defence to ornament; existing object to proposed addition. What it is not: Not every national claim, completed artwork, or agreement to follow a plan. When both seem possible: Place by the coder theme's practice: t01 and t03 specify work; a refusal justified by future art plans sets terms and belongs to T4-002. No conjunctive two-part gate is imposed.

### `T4-002`: Setting terms for sharing canvas space

Coined, source empty, recalled false. Gloss: Making claims on space answerable through pleas, refusals and proposed accommodations.

Claiming an area, asking its claimants for restraint and proposing a pact all articulate who should be able to remain or act there. The common practice is making terms of occupation explicit, not reaching agreement. One speaker demands relocation, another seeks preservation, and another offers help or accepts looking elsewhere. Their opposition is constitutive of this bundle: goals and authority remain contested rather than assumed shared.

Question: On what terms can different projects occupy or use the canvas?

Members: `t02`, `t04`, `t05`. Gate condition: "The material asserts, challenges, proposes, reports or acknowledges terms of spatial coexistence, exclusion or support between canvas claimants." Discriminator: Against T4-001, it addresses another claimant's room or support relation; against T4-003, it concerns terms on the canvas rather than who should receive the business. What varies: Taking space to sparing it; unilateral appeal to reciprocal acknowledgment; proposed support to reported pact; open request to accepted refusal. What it is not: Not a synonym for successful bargaining, peace, recognized sovereignty or compliance. When both seem possible: A concrete refusal or accommodation remains here even if explained by artwork needs. A pointer without spatial terms is T4-003. Preserve reports and contextual fragments as such. No conjunctive two-part gate is imposed.

### `T4-003`: Locating who can answer for the flag

Coined, source empty, recalled false. Gloss: Assigning canvas business elsewhere while delimiting this room's responsibility.

A venue pointer assigns an audience for active business; an account of this subreddit's travel or language purpose explains or polices why its audience should not bear that business. Both locate responsibility without requiring a decision on the substantive request. Their linkage is not the repeated name r/norge: a route can help a visitor, while a boundary can reject the visitor or distance a speaker from expansion. Claims about who built the flag are participant attributions, not independently established jurisdiction.

Question: Who is being addressed as responsible for canvas business, and where should it be handled?

Members: `t06`, `t07`. Gate condition: "The material locates flag work or canvas discussion in a venue, supplies its audience or route, or defines, enforces or responds to the boundary of this room's responsibility." Discriminator: Against T4-002, the object being settled is the address, audience or responsibility for business, not permission for pixels or a peace agreement. What varies: Attribution to imperative referral; bare name to specified channel; language explanation to operational reach; helpful direction to scolding and distancing. What it is not: Not proof of completed handoff, disjoint memberships, recognized command or no local organizing. When both seem possible: Keep routing and boundary statements distinguishable inside the bundle. Mixed venue/route utterances fit by locating responsibility; substantive local refusals remain T4-002. No conjunctive two-part gate is imposed.

The full construct declarations, disconfirmation tests and source-bound material records are in fourth/fourth.jsonl and fourth/fourth.md. `T4-001` is least secure at `t03`: furnishing a flag could be mere display, but the ostehøvel and pawn explicitly direct contributions; the carrot fragment cannot carry that reading on its own. `T4-002` is least secure at `t05`: offering help is not necessarily negotiating space, but it makes terms of support among claimants explicit. Its range must not be collapsed into consensus. `T4-003` is least secure at `t07`: policing a venue can simply reject business. The explicit travel-purpose plus megathread direction in `c0080` supports the common question of answerability while preserving that difference.

Pairwise separation is operational. Between `T4-001` and `T4-002`, ask whether the distinctive content specifies a contribution or terms for occupying/supporting projects. Between `T4-002` and `T4-003`, ask whether the reply settles spatial terms or the audience that should address them. Between `T4-001` and `T4-003`, a location for a pixel operation differs from a venue for the people deciding it. These are analytic distinctions, not proof of disjoint groups.

## Dimension `D01`: Specifying effort and entitlement

Coined; source empty; recalled false. Members `T4-001` and `T4-002`. Gloss: participation is specified as something to do and as terms for doing it alongside others. Question: how is participation made concrete both as a contribution to a project and as a claim on room shared with other projects?

The explanatory distinction is between making work actionable and making occupation answerable. A common flag does not resolve either. The upper-left instruction in `c0006` specifies contribution; the appeal and refusal in `c0011` and `c0012` set opposed terms of occupancy. The pawn in `c0047` specifies a contribution, while the art rationale in `c0059` refuses another claimant. Together these distinguish what to contribute from whether others can remain, without assuming a causal order or agreed goal.

Membership predicate and gate: gather higher themes specifying canvas contributions or explicit terms on which projects occupy or support one another. Exclude themes whose distinctive question is where business and responsibility lie. This is not an authority hierarchy or a model relation. The least secure member is `T4-002`, whose conflict can look like pure disruption rather than participation. The retained spatial appeals, refusals and acknowledgments show terms being articulated even when cooperation does not follow. Confidence is arguable because this aggregate explains a distinction rather than a demonstrated integrated process.

`T4-003` carries dimension [] with a reason: its distinctive question concerns who receives responsibility, not the contribution or entitlement being specified. A pointer to r/norge does not itself answer the spatial request. Its nearest case inside the dimension is `c0106`, which acknowledges a substantive refusal and proposes looking elsewhere, not a venue to hear the same request. A broad dimension called 'organizing Norway' would hide this separation.

There is no second dimension to compare. I considered no aggregate, leaving all higher themes separate; that would retain the practices but lose the contribution-versus-entitlement distinction made visible by the art cases. I also considered a second 'venue organization' dimension, but one higher theme alone cannot meet the two-member requirement. Splitting routing and boundary statements merely to fill it would manufacture shape. The record does not require that every theme aggregate.

## Grouping review and rejected alternatives

The review compares acts, not nouns. Keeping 'taking space', 'receiving pleas' and 'making accommodations' as separate T4s would preserve the original seams but supply little abstraction above them. Relating them as setting terms explains why opposed moves address the same practical issue without equating their outcomes. Conversely, merging all flag work and spatial conflict into one national project would assume the goal and erase the distinction between exact repair and excluding a neighbour.

I considered separating routing from venue boundary maintenance at the higher tier. They remain distinguishable subpractices, yet `c0080` and `c0092` show how a stated venue purpose locates both an unsuitable audience and an operating one. The common practice is locating answerability, not repeating a name. The Discord blame in `c0063` is retained as a weak edge, not used as an exemplar of a formal jurisdiction.

I rejected folding the whole joking theme into spatial bargaining. The live migrant refusal supports that functional reading, but the 'just a flag' exchange and sovereign coda do not show the same task. The form pass preserves their turn-level differences without inventing a work theme. I rejected treating remembrance as evidence that alliance work persisted. New live demands or maintenance reports would change that decision; the current items recount and explain.

These are initial cuts, not recuts of a previous R3 scheme. The structured tier history records relating for each higher theme and the dimension, with was null and the prompting coder themes. No coder theme is split, no code changes home inside coding, and there are no additional placements or recurring placement pairs to tabulate. No fleet disagreement or onset contrast is available in a single room. Live/aftermath is not a substitute cross-room onset contrast.

## What no fourth-order theme picked up

`t08` and `t09` are the complete unpicked list, not a catch-all. Their reasons are register and retrospective context, respectively. Their code mass is nine of the closed 111-code frame under coverage receipt 2263, not a claim that these acts occurred nine times in the community. The examples already quoted above include the active refusal, sovereign coda and alliance remembrance. Neither theme is discarded; form-pass prose and episodes retain material a later model may use directly.

The aftermath calculation in R2 remains 0 coordinating items of 3 distinct coded items strictly after hour 73, receipt 1320; no item lies at 73. That limited frame is consistent with retrospective context here, not proof that all care or organizing ended.

## Coverage and count limits

counts-R3.jsonl contains instrument-computed records: all coded IDs, 111/111 (receipt 2247); `T4-001` material, 18/111 (2251); `T4-002`, 57/111 (2255); `T4-003`, 27/111 (2259); contextual remainder, 9/111 (2263). These are ID coverage with unit codes in the closed coded frame over [0,97], with no code at either endpoint. They audit assignment reach, not prevalence or understanding. The matched sets are disjoint and exhaust the record. No unmeasured act is zero. Formal count records with mode, unit, denominator, receipt, window and boundaries accompany this account in counts-R3.jsonl.

Every coder theme is defined and occurs in a higher theme's members or the contextual unpicked list. Every higher theme occurs in the defined dimension or carries dimension [] with its reason. No FP finding enters assignment or gate arithmetic. Form-pass findings live only in form_pass.md; their implications inform these comparisons without adding topic members. No arrow, mechanism, feedback loop or causal claim is constructed in R3.