Within-case comparisons before arrows

Ordinary — E-02: arranging one repair

The object was a letter in Nassouwe, not an already unified national organization. The thread's opening asked people to replace an A with an O. A reply reported private messages to people making the A. VpdTcUWHU4rQmGhE41b5ZYytTVs= then proposed a joint change rather than independently editing a partially damaged letter. The full turn explains why: otherwise observers could mistake the incomplete correction for vandalism. Its coded portion makes the timing actionable:

c0027, VpdTcUWHU4rQmGhE41b5ZYytTVs=, item dfoskt3, thread 62rwzd, hour 18.953333333333333, offsets 191–325:

om 13:05 ga ik met 2 profielen twee blokjes veranderen, als je dit ook om 13:05 precies doet kunnen we de letter naar een O veranderen

The replies divide work. In dfosm1w, dXct7C8oZGYWZ4wUuixVbJM8k2A= agrees to handle the A's middle and asks which remaining part the partner will take. VpdTcUWHU4rQmGhE41b5ZYytTVs= answers in dfosnbn; dXct7C8oZGYWZ4wUuixVbJM8k2A= specifies two pixel coordinates in dfosoog. These contextual replies establish complementary intentions, not independently observed pixels. dXct7C8oZGYWZ4wUuixVbJM8k2A= then reports success:

c0071, dXct7C8oZGYWZ4wUuixVbJM8k2A=, item dfosqu9, thread 62rwzd, hour 19.10388888888889, offsets 0–23:

Yes, gelukt! High-Five!

VpdTcUWHU4rQmGhE41b5ZYytTVs='s dfosrls, hour 19.124444444444446, joins that assessment. The result is therefore more than an unanswered imperative: the participants answer the plan, divide their intended contribution and recognize a shared completion. The exact instrument hours establish order; no elapsed duration or independently verified canvas success is claimed.

Durability is different. Later in the same thread, dfot5v5 at hour 19.466944444444444 calls for work again because the letter has reportedly become an A. In dfotbsz, the author attributes this to someone with five accounts. That attribution is unverified, but renewed correction is explicit. One successful reported repair does not bind everyone who can recolour the letter. The source gives temporary joint achievement and later renewed demand, not a measured defence rate or a complete governance system. The original coder practice is correcting pixels and holding builders to the plan. Its local success cannot stand for every correction or explain why unrelated readers would comply. This is ordinary because it shows the elementary work of agreeing how to act together; the later reversal makes its limited reach visible.

Unpredicted — E-04: correcting an accusation

An exact-pixel lettering guide in 62sk70 offered a representation for writing the subreddit name above the flag. People then asked whether the letters should be black or purple, and the guide's author answered black. The representation did not make intentions transparent. vGASt1uNGF1KvJqF037tZhRsQag= named a supposed interfering user:

c0077, vGASt1uNGF1KvJqF037tZhRsQag=, item dfowj9a, thread 62sk70, hour 21.633333333333333, offsets 0–54:

ecOGkDwXpRJgQ/blXmAuN9r3bzc= blijft 578,6 oranje maken, verdomme

The accused did not accept the role of saboteur. The answer claims the same correction task, and attributes the apparent discrepancy to what the observer sees when the page is refreshed:

c0078, ecOGkDwXpRJgQ/blXmAuN9r3bzc=, item dfowkrg, thread 62sk70, hour 21.656111111111112, offsets 0–117:

Dat ben ik niet, ik probeer 't juist steeds weer zwart te maken (het is nu ook zwart als je de pagina opnieuw laadt).

The full turn includes a proof link and a claim that the canvas sometimes lags. The image is not inspected and lag is not independently diagnosed. The text nevertheless supplies an alternative explanation that the accuser explicitly acknowledges:

c0079, vGASt1uNGF1KvJqF037tZhRsQag=, item dfowq9p, thread 62sk70, hour 21.735833333333332, offsets 0–89:

Ah, excuus. Dit maakt het wel moeilijk om betrouwbaar /r/cirkeltrek -verraders te vinden.

The relevant change is in attribution, not proof that the underlying pixels were repaired. An apparent enemy becomes a contributor claiming to restore black pixels, and the accuser withdraws this specific allegation. This is unexpected relative to a simple correction-as-enforcement story: identifying wrong colour and naming a user can misidentify a collaborator. An answer can therefore repair the public accusation rather than reinforce it. The reply's 'Dit' connects the apology to the difficulty of identifying traitors; temporal adjacency alone is not the warrant.

The later lettering discussion adds a separate limit. Participants negotiate whether to move the T, whether other letters also deviate, and whether leaving the design as it stands would avoid further confusion. These are contextual developments after this episode's coded attribution endpoint, not one continuous proof of command. The episode closes at the apology because that is the resolved question in the coded chain. It neither establishes that all accusations are false nor that every accused person can obtain retraction. The user's willingness and ability to answer, and the accuser's acknowledgment, matter. Those are precisely the features missing from an unanswered script-stop request. The source practice remains correction/accountability, but its form includes revising who is held responsible.

Stopped early — E-05: promising a limit without delivering it

In the same thread, a different problem concerns neighbouring work. 23wCpZk3S2x3/WMUZd0AvIa8H4Q= says there are no current plans to expand right, and ZTAOMCccOj+XueyAvvz/5sDyuAQ= reciprocates:

c0080, 23wCpZk3S2x3/WMUZd0AvIa8H4Q=, item dfp27ru, thread 62sk70, hour 24.09861111111111, offsets 41–99:

We don't have any current plans on expanding to the right.

c0081, ZTAOMCccOj+XueyAvvz/5sDyuAQ=, item dfp28m2, thread 62sk70, hour 24.1075, offsets 0–44:

Alright cool. I'm not expanding left either.

These words establish an assurance between speakers. They do not identify every placer, appoint either speaker as a delegate, or state a means to prevent others expanding. The exchange is therefore not already evidence of an enforceable border. The later retrieved context contains reported encroachment and an apology to the Diego group. Another Dutch participant then addresses ZTAOMCccOj+XueyAvvz/5sDyuAQ= with an explanation framed in the room's royal language:

c0082, qxTvaUoZ19rSjnH9CCjSp49QPXs=, item dfpa249, thread 62sk70, hour 27.259444444444444, offsets 22–152:

onze onvoorwaardelijke liefde voor Willem was niet te stoppen. Ik hoop dat je genoegen neemt met een plaats in de tijdverstrijking

The final coded response accepts the loss without anger:

c0083, ZTAOMCccOj+XueyAvvz/5sDyuAQ=, item dfpag1l, thread 62sk70, hour 27.423055555555557, offsets 35–147:

I'll assume it's a 'it wasn't personal just business' type thing. In witch case, it's cool no hard feelings here

The reply assumes a 'business' explanation rather than independently verifying the Dutch participant's account. Nor does 'love for Willem could not be stopped' measure anyone's motivation or establish a causal law about patriotism. The supported sequence is assurance, reported loss, apology/explanation, acceptance. It does not establish deliberate betrayal by the initial speaker. Other contributors, changed plans or an ineffective commitment remain possible.

This is the stopped-early case because the particular protection implied by the assurances does not reach its promised practical conclusion in the reported record. The subreddit itself does not stop existing, and other tasks continue. The neighbour's acceptance may close a social dispute without restoring the work. That distinction is analytically important: a peaceful final reply can coexist with a failed spatial accommodation. The source's negotiating practice includes proposals, reciprocal promises and apologies, not just successful cooperation. Compared with the timed repair, this exchange attempts to commit a much less bounded set of actions. The text does not permit measuring that reach; it does permit refusing to equate the two speakers' agreement with control over all orange placements.