# Organizing contributions, spatial terms and audiences

Target length: under 1,200 words of model prose, followed by the apparatus.

## Explanation

This room shows organizing without establishing a single organization behind the national address. Speakers recruit pixel effort and specify repairs, visitors seek room or restraint, and respondents either give an operating audience or answer spatially here. Some answers receive explicit acknowledgment. These practices make contributions, terms and audiences concrete. They do not establish a shared mandate, an agreed national goal or the resulting work's survival. The candidate explains observable handling of requests, not a verified command system.

`P01`, specifying and contesting contributions, is already concrete in the repair thread: DtHMHfDITvNQDKyDc92Wa/eB9aM= writes "We gotta coordinate so people understand where we are going, and join in. Upper left corner 1st!" (`c0006`, `dfom3hp`, thread `62pf3j`, hour 13.713888888888889). Yet ytn8lNKKFg1Zs42tAi+sYNMV9YM= attributes the work elsewhere: "It seems it's a creation of /r/Norge, and they've been working at it since yesterday." (`c0007`, `dfom936`, same thread, hour 13.806111111111111). This is descriptive coexistence, not evidence of a later transfer or a causal effect of venue size.

`P07` adds a different public practice: accounting for effort already contributed or limited. REnhdM/tikr8y0NWtMEvjA1KSp8= reports "Helped whole night to keep the heart between us! From a Swede" (`c0016`, `dfqd5k6`, thread `62pf3j`, hour 48.45194444444444). Later ffjFuQxgCTAwvAD6U3VAFQYGHoY= reports "I tried attacking Texas on your behalf but it seems that you guys are too few." (`c0110`, `dfqh28a`, same thread, hour 49.873333333333335). A Scottish defender also says defending the Saltire prevents helping (`c0014`, `dfphtk0`, hour 30.53611111111111). Unlike an instruction, these accounts make performed effort or a limit publicly legible. They are reports, not measured manpower, independently dated action or proof that help preserved pixels. The perceived shortage is the speaker's explanation, not an established causal relation. No arrow links these reports to success or failure.

`P02`, seeking room or restraint, has alternative visible continuations. The referral path `A01` ends with `P04`, locating an operating audience and this room's responsibility. Texas's request in `6340w3`, item `6340w3` (`c0066`, hour 58.501666666666665), asks: "From /r/texas: we peacefully request that you cease the invasion of our flag". 3sz51JBe4fWK4SmPUkh/wf6yGyI= answers "Go to r/norge" in `dfrbw8a` (`c0067`, hour 60.86138888888889). A later contextual pointer, `dfrj27c` at hour 65.79, supplies a thread. The observable next offered action is an address. Its receipt and result are not visible.

A local-answer path, `A03`, reaches `P03`: asserted spatial or support terms. Madeon asks whether Norway can go around its logo; the reply is "Sorry, you have to find another place for your logo, we will claim the area." (`c0011`, `dfp8b66`, hour 26.539444444444445; `c0012`, `dfpbsa2`, hour 27.976666666666667; thread `62pf3j`). Factorio instead receives a report: "We decided on a hanging flag instead of expansion. You guys should be good." (`c0037`, `dfq2fk7`, thread `62yuxs`, hour 42.121944444444445). Its past-tense decision is not demonstrated to have been caused by the visible complaint. Different answers from different speakers do not establish a community-wide reversal.

`A02` connects a substantive reply to `P05`, explicit requester acknowledgment. It is most firmly connected in FFXIV: "No, we have plans for some artwork ourself." (`c0105`, `dfrvohp`, hour 71.73944444444444) precedes HaVdRKQRlkHbJcUfoNdFs48ezEk='s "Duly noted, thanks for the responses everyone, we'll try to look elsewhere." (`c0106`, `dfrx3ig`, hour 72.19805555555556; thread `637igs`). The requester names the responses, supporting a conversational effect, not merely order. Crusader Kings's thanks after a pact report supports acknowledgment, but not the same behavioral change or implementation. Unanswered refusals cannot be treated as failed persuasion.

`P06` remembers affiliation: "It was great fun and glad to see we stayed friends untill the game ended." (`c0108`, `dfs6i7s`, thread `638exb`, hour 75.24). The postgame exchange neither assigns work nor demonstrates durable maintenance. The last coded coordinating turn remains the FFXIV acknowledgment. No irreversible transition at hour 73 or complete dated feedback cycle is grounded.

## Counter-reading

Before searching, the competing account was one cross-platform group using this room as a public front. If a categorical local-boundary reading were wrong, same-request relay, joint policy reports or linked implementation would be present. Literal searches for posted, poll and coordinat in codes (receipts 2944, 2947, 2950) returned matches whose full containing threads were read (3178, 3181, 3183, 3186), not interpreted from hit counts.

The strongest contrary item is `c0056`, `dfr1w91` (TjlAgH7pOIzQAvJvkE4q7QWmxeg=, thread `632j25`, hour 57.31388888888889): "I posted to /r/Norway and a Norwegian Redditor posted to /r/Norge. I've yet to contact the Czech or Dutch". This reported relay defeats pure deflection. The model preserves integration as possible and `P04` as locating an audience, not proving separation. The full Slovak reply also reports official peace policy alongside a channel direction (`dfrohx2`, thread `636ch1`, read 3619). The coded poll report says: "A poll on our discord server resulted in a majority in support of peace between our nations." (`c0087`, `dfrogwe`, thread `636ank`, hour 69.15805555555555). It supplies a participant's explanation of policy, not independent knowledge of electorate, implementation or causation by a particular appeal.

The categorical rival that all organizing happens elsewhere fails at FFXIV's local acknowledged answer. The stronger rival, a partially integrated cross-platform group, remains unresolved. It is compatible with this model of visible acts, but the room cannot establish its membership or command structure.

## Apparatus: elements and range

The source of the model is model/elements.jsonl and model/arrows.jsonl. Relationships run between typed processes grounded in coder themes and higher themes; they are not arrows between theme labels. The model relates presences, not amounts. No degree-of-routing, efficiency or success covariance is claimed.

| Element | Tier and dimension | Range that matters |
|---|---|---|
| `P01`: specifying and contesting contributions | `T4-001`, `D01` | Rally to exact repair or object proposal; priorities can be challenged; no verified execution. |
| `P02`: seeking room or restraint | `T4-002`, `D01` | Admission, preservation, restraint and maintenance offers; some bodies removed. |
| `P03`: answering with asserted terms | `T4-002`, `D01` | Refusal, reservation, reassurance, reported pact or peace; no presumed mandate. |
| `P04`: locating an operating audience | `T4-003`, no dimension | Attribution, helpful direction, rebuke and channel instruction; can coexist with reported relay. |
| `P05`: acknowledging substantive replies | `T4-002`, `D01` | Thanks differs from stated search change; neither proves implementation. |
| `P06`: remembering affiliation | `t09`, no dimension | Honouring and explaining a past alliance, not ongoing maintenance. |
| `P07`: accounting for contributed or limited effort | `t01`, no dimension | Prior help, attempted attack and competing defence commitments; report is not instruction or verified capacity. |

All processes are retained because removing one loses the distinction between contributions, appeals, spatial answers, audiences, acknowledgment, what remains or public accounts of contributed effort. No role or condition is added merely from an ambassador title or a collective "we". A node called formal leadership, common goal or completed handoff was dropped from consideration because none supplies a separately supported process or state here.

## Apparatus: arrows and failure tests

The full required fields, exact support quotes, theoretical samples and reasoned counterexample responses are in arrows.jsonl. These are fair, bounded process readings, not estimates of frequency or effects. Each rests on participant words in support; support_transition is empty, so no instrument-unmeasured interval is reported. Hours are the gateway's forest hours since opening.

| Arrow | Mechanism and failure | Comparison and scope |
|---|---|---|
| `A01`: `P02` to `P04`, transition | Reply supplies another audience as next offered action. Fails as an obligatory relation when only spatial terms are answered, or when address concerns another request. | `E-35` supports, `E-47` contradicts necessity, `E-29` shows relay can accompany referral, `E-34` untestable. Bound to visible referral, not successful handoff. |
| `A02`: `P03` to `P05`, transition | Requester explicitly makes the answer consequential by acknowledgment. Fails if apparent acknowledgment concerns different business or merely analyst-imputed uptake. | `E-20` supports beyond `E-47`; `E-30`, `E-19` have no requester reply, `E-42` lacks checkable identity. Direct negative test remains incomplete, not tested-absent. |
| `A03`: `P02` to `P03`, transition | Request occasions an asserted term of room or support. Fails as an obligatory relation when reply only supplies an operating address. | `E-30` and `E-19` support, `E-32` contradicts necessity, `E-34` untestable. Does not imply request caused earlier decision. |

No base-rate advantage is claimed: base_rate_beaten is null. These claims concern shown connections, not "most" requests. Direct word reading separates them from mere coder thematic adjacency. Fair strength reflects narrow observable conversational mechanisms and incomplete negative tests, not an attempt to infer strong relations from small overlaps. No strong arrow is asserted; live_aftermath is therefore not populated.

The same provenance could manufacture all these relations if coding disproportionately selected connected exchanges. For `A01`, pointer selection could hide ignored requests; the full unanswered Texas promise and FFXIV's local refusal prevent a universal referral sequence. For `A03`, the coder could disproportionately preserve dramatic refusals; full Factorio reassurance and address-only Texas distinguish different reply functions, but not their relative frequencies. For `A02`, selecting thanks could exaggerate uptake; whole threads preserve missing acknowledgments and uncertain identity, limiting the claim to express acknowledgment. These checks do not recover deleted or uncoded off-platform replies.

## Apparatus: dimension projection

Projection is from the element dimension fields and retained arrows, not a new empirical count. Expressed as explicit arrow mass sets for `D01`: in-mass {}, out-mass {`A01`}, internal mass {`A02`, `A03`}. With or without rule-0 double placements these sets are identical; multiplacement_log.jsonl is empty. `P04`, `P06` and the directly coder-grounded `P07` remain outside dimensions. `P07` takes its primary ground from `t01` and supporting contribution reports in `t05`; model evidence does not add or change a theme assignment. At this graph resolution `D01` is a source condition rather than a receiving dimension, but this is a projection descriptor, not evidence that entitlement causes venue boundaries. The internal mechanisms do not warrant a new dimension-level arrow or an effort-to-entitlement causal path.

## Dynamics, unused material and break conditions

There is no grounded loop: loops.jsonl is empty. An unanswered priority challenge could reopen discussion but does not show a return to an earlier organized state. Repeated requests from similarly named groups are not a dated cycle. No causal line links the active refusals to postgame friendship. With theorised relations included, the grounded graph remains `P02` to `P04` (`A01`), `P02` to `P03` (`A03`), `P03` to `P05` (`A02`); without theorised relations it is identical, because no uninstanced relation is drawn. `P01`, `P06` and `P07` have no grounded incoming or outgoing arrow.

All coder themes contribute except the whole-theme work of `t08`, joking in flags, sovereign land, and displaced migrants, which remains contextual through `FP-02`; its live refusal `c0104` still informs the account. `t09` is used directly by `P06` without pretending it entered a higher theme. Coverage sets, not behavioral prevalence, remain in counts-R3.jsonl. No additional placement is created by using contextual code evidence.

The model should break as an explanation of a mandatory request-processing system, an authority hierarchy or implemented cross-venue cooperation: no such necessity or authority is evidenced. A conversation with no spatial request needs only contribution or context processes, not every arrow. A local reply can combine destination and peace report. The paths are not exclusive. A case in which a referral's confirmed receipt changed a plan would require a relay-to-decision step; this room's reported cross-post is insufficient for that step.

## ungrounded relationships

Contribution instruction to completed pixel work; venue referral to accepted cross-venue settlement; an appeal to the creation of the pact or poll it is told about; agreed terms to surviving artwork; and active accommodation to durable friendship remain ungrounded. They are kept apart from instantiated arrows. Off-platform decision making and incomplete records are viable alternatives to ineffectiveness. No absence of these links establishes that the processes never occurred.

## looked-for-and-not-found

The counter-reading searched this room's closed codes for the specified terms, read every returned match's whole thread, and the story census reread all registered episode threads. Within that scope no linked implementation or confirmed receiving-venue answer was established. This is a weak absence claim: selected spans, removed bodies and unseen venues prevent a general negative about cross-platform organization. A poll report and a cross-post report are positive contrary evidence that survives this null. No query-count quota or lexical hit total is treated as a substantive result.

The revised story distinguishes reporting effort (`P07`) from directing it. `E-26` and `E-27` can be narrated as such reports without verifying their activity, capacity or causal impact. `F-005` retains its earlier revision and narrows the structural residue. `E-11` still has permission with missing substantive question and authority; `E-13` has an overwrite proposal challenged as a mistaken target; and `E-42` has an apology whose speaker cannot be matched to the deleted opener. Adding a reporting node cannot repair missing records or explain how the target correction affected work. The selected pass and reasons are recorded in notes-R4.md.

## Independent critic comparison

The accepted critic found no errors against the served candidate and proposed a finer partition. That is not validation of this explanation. I retain `T4-002` rather than separating `t05`: pleas, possession claims, refusals and accommodations make terms of occupancy and support explicit, while `P03` and `P05` distinguish asserted terms from acknowledgment. A refusal can itself specify a workable next move; the rival does not newly explain an episode under the criterion. Its expressive-role and retrospective-recognition singleton themes are defensible descriptions, not disallowed by size. Here `FP-02` preserves joking across unlike acts, and `P06` already models remembrance directly at coder tier. Extra tiers would not establish maintenance or a new process. The resolution remains underdetermined; the disagreement is held beside the retained grouping in notes-R4.md and review-C2.md. `P07` was added from source reports, not because the critic's judgment dictated it.