# Episodes before arrows

Target length: under 1,500 words.

## Ordinary: the mushroom and gameboy, `E-03`

The surviving conversation begins as a dispute about damage. Jupiter asks the Czech flag builders to leave neighbouring work alone; a Czech participant says the smaller work should not have been built on an existing place. Jupiter answers that the mushroom preceded expansion. A proposed semi-transparent wedge would preserve overlapping work, but the speakers do not report adopting that proposal. YjelzzlIbjdgrAh0Hne+232+3II= later apologizes:

`c0103`, YjelzzlIbjdgrAh0Hne+232+3II=, hour 45.604166666666664, item `dfq6pqx`, thread `62zd7d`:

> I won't encroach on your stuff anymore. My apologies.


The full source explains that YjelzzlIbjdgrAh0Hne+232+3II= watched a timelapse and could not vouch for anyone else. This is a reported change in one person's understanding and conduct. It cannot establish that the crowd stopped expanding. Jupiter then explicitly stops fighting:

`c0104`, Igb+3px/yG8WiUCDjVnQhe0n/To=, hour 46.151666666666664, item `dfq7ps3`, thread `62zd7d`:

> OK Czech, we stop fighting.


The full thread gives the smaller group's size and inability to win as reasons to move. The ordinary example of neighbour help therefore already includes unequal capacity. Repeated relocation fails. In the repair-call thread, Jupiter states a pause in `c0113`, after describing difficulty communicating with rainbowroad. That failure does not end the visible attempt to make something. A new thread identifies Jupiter as the mushroom's creator and asks for gameboy help beside the flag:

`c0127`, Igb+3px/yG8WiUCDjVnQhe0n/To=, hour 47.629444444444445, item `dfqb03m`, thread `6309rl`:

> It would be nice if you could give us a hand since we were nice to you (and stopped fighting).


The appeal explicitly recalls the end of fighting. It gives the reader a connection between earlier restraint and the request, rather than leaving a temporal sequence to imply reciprocity. fqxABR/xdTx/2QZqKo/DMhHt9AA= then promises to help build and defend in `c0128`. Jupiter later promises Czech defense in `c0129`. Source replies also report that the gameboy is done, then discuss defending it. Those reports remain participants' descriptions; no picture was inspected.

This episode runs from the dispute to a reciprocal commitment, not to verified survival. The dated code hours establish the order of the surviving turns, while an undated edit cannot establish the exact time of a renewed promise. The episode can support an account of invoking restraint to seek help. It does not show that gratitude caused contribution, that the original expansion was consensual, or that one apology bound every placer. Its ordinary character concerns recognizable requests and answers, not a claim that such episodes were most frequent. Full source reads: 3044, 3059 and 3062.

## Unpredicted: repeating the flag without observing the old group, `E-16`

After the original event, sWDaLrUKJHzIwyX2EKrmu92i+pw= asks whether anyone will join another Czech flag on a replacement site:

`c0288`, sWDaLrUKJHzIwyX2EKrmu92i+pw=, hour 82.45, item `63bg75`, thread `63bg75`:

> Anyone want to join me in making czech flag at Place knockoff?


The title dates that invitation at hour 82.45. Its body contains an edit calling a site the official replacement and asking people to check it out. The record has no separate time for that edit. The invitation therefore cannot be extended to a later hour by treating the whole edited body as newly posted.

ZTIErk9axWsEISClADxFzMIjX7g= replies that this is another copy among those already encountered. DqsHUNg+c27ot53ATVDk+7K8QiU= questions whether repeating the activity preserves what made the event worthwhile:

`c0291`, DqsHUNg+c27ot53ATVDk+7K8QiU=, hour 91.49888888888889, item `dft7dpn`, thread `63bg75`:

> Doing it again just seems pointless, just like trying to redo r/thebutton


The full source describes unexpectedness and uncertainty about duration as the earlier event's attraction. This is DqsHUNg+c27ot53ATVDk+7K8QiU='s explanation of rejection. It is evidence of one participant's position, not a measured cause of community disengagement. The source supplies no roster of people who joined or declined, and different replies do not reveal a collective decision.

sWDaLrUKJHzIwyX2EKrmu92i+pw= later reports a completed flag:

`c0292`, sWDaLrUKJHzIwyX2EKrmu92i+pw=, hour 95.99833333333333, item `dftj5z3`, thread `63bg75`:

> I've already managed to paint whole flag there.


The full reply says the speaker watches the copies and describes a site's user activity. That activity estimate remains the speaker's report, not an instrument count used in this analysis. Painting a whole flag does not show that the prior Czech participants divided work again or that the old neighbour relationships transferred. The speaker could have painted with strangers or alone; neither is established by this span.

This is an unpredicted test of treating a repeated mark as a continuing undertaking. A reader could expect a recognizable flag, a site and an invitation to recover the former activity. The actual thread preserves skeptical replies alongside the inviter's result. It requires a distinction between another opportunity to paint and a group carrying its work forward. The last observed coordination is the invitation, while the episode's last observation is a completed-work report at hour 95.99833333333333. The later report cannot date continued arranging of work. This episode supports neither collective restart nor the claim that every participant refused to restart. Full source read: 3050.

## Stopped early: the Czech outline, `E-11`

An outline proposal supplies a place and a request:

`c0218`, kI2O4YqdgOn9PKhC6CRyzoOm6Sw=, hour 65.18027777777777, item `dfrid0j`, thread `635mnw`:

> Help me with creating a Czech Republic outline around 113,50.


The title identifies a Czech Republic outline. The body gives coordinates rather than a detailed allocation of labour. +lbr61xMgkqLOgj0sLEyYaq5cZE= answers:

`c0219`, +lbr61xMgkqLOgj0sLEyYaq5cZE=, hour 66.76861111111111, item `dfrk9ch`, thread `635mnw`:

> I'm gonna help


This is a clear willingness statement in the thread. It establishes neither a finished section nor how much work the speaker performed. A later reply assesses whether the proposed space remains available:

`c0220`, d6sLGKDlNoeW5HyhAG/OowgvRUI=, hour 69.13305555555556, item `dfroexe`, thread `635mnw`:

> Well, it's too late now. The void (4chan scripters) has been overtaken by orange (Dutch scripters).


The speaker explicitly connects the too-late judgment to a takeover described in terms of scripting. The inference does not depend solely on putting the helper's earlier promise beside a later disappointment. Yet the claim is limited to what d6sLGKDlNoeW5HyhAG/OowgvRUI= reports: no independent script log or inspected picture verifies who occupied the space or when. The four surviving source items contain no completed-outline report. That is a weak absence in this supplied thread; off-thread work and later outcomes remain unknown.

The proposal ends in the visible record at the too-late assessment. This is the episode boundary under the rule that preserves an explicit stopping assessment. It is not the time when every possible outline effort ceased. A different project, Pat and Mat, later or elsewhere discusses changing bots; that cannot silently supply the missing adaptation here. The outline's own replies show an offer followed by a stated obstacle, without a workaround.

This stopped-early attempt matters because willing hands and a named object are visible together. Their presence is insufficient to establish feasible action. The obstacle concerns control of the intended space, not merely a lack of national interest or an unanswered call. The appropriate explanation must preserve this difference from the gameboy exchange: there, requests and reciprocal commitments continue after failed relocation, whereas here the record supplies a final assessment that the space is already taken. The contrast does not identify which design would have succeeded under other conditions. It places a reported local constraint beside the offered help, retaining uncertainty about execution and survival. Full source read: 3047.
