# Episodes before arrows

Target length: under 1,300 words.

## Ordinary: `E-04`, retracting a call to fight

This episode is ordinary in the limited sense that it contains an identifiable practical disagreement followed by explicit uptake. It is not chosen as the most frequent form. In thread `62z7n6`, 7wQc0fWT3YJjQ5BHd4I736UqCFA= writes "Fight the dutch" (`c0013`, item `62z7n6`, hour 43.683055555555555). pxkbfuMB5pD8hJcap7MNA2cZBOU= then explains the second dog with clogs and writes "I believe your mods have agreed to this." (`c0014`, item `dfq46vo`, hour 43.83583333333333). The first speaker returns: "I take it back this is great" (`c0015`, item `dfq4mkc`, hour 44.191944444444445). These are cite receipts 3590, 3592 and 3594; complete context is read receipt 3501.

The practical issue is whether the Dutch should be fought. The response gives the hostile caller another interpretation of the proposed dog rather than merely praising the same object. The retraction is important because it belongs to the person who initiated the call. If one person had advocated fighting and another had favoured clogs, their difference would not show that either had revised a position. Here the first and last coded items provide both endpoints of a stated reversal. The explanation sits between them in the same discussion.

The account remains local. pxkbfuMB5pD8hJcap7MNA2cZBOU= qualifies moderator acceptance as a belief, and the reply expresses 7wQc0fWT3YJjQ5BHd4I736UqCFA='s approval, not a tally or a mandate. Other thread responses include a threat that the Dutch will win and a claim that Dutch participants are saving the art. Those voices do not make the coded reversal unanimous. Nor does the text establish what either speaker subsequently placed.

The bracket begins at the fight call and ends at its explicit retraction. Later uncoded praise remains context rather than evidence of more coordination. The coded hours date the items, not the start of all Dutch relations. This episode can support an account of revising a stated stance after a concrete proposal is explained. It cannot by itself support a community-wide conversion, an enforceable agreement, or an explanation of the final image.

## Unpredicted: `E-07`, excluding a curly tail from the plan

This episode was selected because the broad defence theme could encourage reading an overwrite as a hostile attack. The direct response instead describes a plan-based exclusion. In thread `62zhgb`, xsu4p9aQqSoG73uoKtxC1k6szT4= reports "I made two efforts to add the /r/Samoyeds curly tail to goodboye, but it kept being overwritten" (`c0023`, item `dfq5spx`, hour 45.0375). +UlLrDEeNyyxA7fMmUb7YoAMR8c= replies "there's a plan for it all and curly tails just didn't make the cut!" (`c0024`, item `dfq69s4`, hour 45.33611111111111). Cite receipts 3598 and 3600 preserve the words. Read receipt 3504 supplies the complete thread.

The practical issue is which alteration belongs in the dog. A participant wants a tail and describes repeated unsuccessful additions. The answer does not identify a vandal, a script operator or a rival community. It says the plan does not include that feature. This difference matters: holding an agreed image steady can frustrate another friendly contributor. Repeated restoration need not demonstrate hostility, and an unsuccessful alteration need not demonstrate that the group lacks a design.

The reply offers a participant's explanation. It does not independently establish who overwrote the tail, whether they followed the plan, or whether the complaining contributor accepted the answer. No further coded response by that contributor records a decision to stop. Later responses in the served thread praise the dog. Those are neither confirmation of an overwrite mechanism nor proof that the tail remained absent.

The bracket therefore covers a reported alteration attempt and the plan-exclusion answer, not a verified construction history. The episode challenges an explanation that treats every maintenance problem as external interference. It also challenges a story in which recruiting volunteers automatically adds their desired features to the common project. The selected object can exclude an offered contribution.

This remains unpredicted relative to the unrepaired broad defence grouping, not a claim that the R3 structure cannot describe it. The split upper placement already distinguishes exclusion from script constraints. The dynamic model should preserve that repair while refusing to turn the response alone into a verified causal account of pixel restoration.

## Stopped early: `E-39`, soliciting reciprocal Mettaton help

The complete served thread `636vam` contains one request. At hour 69.81805555555556, 8yTdKzEusbdL8t3HKJq81JxQdB0= writes "could I get some help making a Mettaton face? I'll donate my resources to anything you need as well" (`c0069`, item `636vam`; cite receipt 3614). The full item also supplies a grid link, starting coordinates and a report of the chin forming. Read receipt 3506 supplies that context. No linked response appears in this served thread.

The practical issue is obtaining work for another image. The request specifies the desired task and promises resources in return, addressing readers as potential collaborators. It therefore supplies more than shared enthusiasm or a greeting. At the same time, a stated offer is not a completed trade. The author may have acted alone, received help elsewhere or received none; this text does not distinguish those possibilities.

The episode stops at the request because the public record provides no next turn on that issue. This is an observed stopping point, not a finding that the activity was abandoned. The source window and the subreddit venue do not encompass all communication. A missing reply here is a weak absence, scoped to this thread, and cannot be extended to Discord or the finished Mettaton image.

The contrast with the fight-call episode is useful. In that episode, a returning speaker explicitly takes up an explanation. Here no returning recipient accepts, rejects or redirects the offered exchange. The request still counts as organizing under the prior's prospective rule, but an effectiveness claim would need additional evidence of uptake. A story which narrates every appeal as successful cooperation would overstate this record.

The bracket retains a single coded act rather than inventing a settlement. The model should describe the offer and its usable task context, then stop at the same evidentiary limit. It should also allow offers to be redirected where another thread supplies a response, without borrowing that response to fill the gap here.