out/within_case.md
Saved at r/thenetherlands: 6.1 local model, R6. This reading copy substitutes participant identifiers in saved text; it is not a new interview response. Reading Markdown.
Participant handles in these reading copies use the pixel stream's identifiers: base64(SHA1(username)), case preserved, without a salt. These are linkable pseudonyms. Profile links are removed; missing-author markers remain. Original research files are unchanged. Quote offsets refer to original text. Source and reading-copy hashes are listed separately.
Source commit: c070d990be88, 2026-10-23T12:38:38+02:00. Saved-state date: not recorded. Not recorded in the catalogue; source commit date is not a close date. Commit date and saved-state date are distinct.
Declared saved-state supplement. Member: workspace/out/within_case.md. Original SHA-256: ecfd62b918d55559f9daa4ebdca088a69396fe4acce8b6836f00e6c6fccd0b62. Reading-copy SHA-256: d7bea7f8ebb89bd6e2f7c18dfefc07c5f656498e7260721e8cd116d46feafdc8.
Episodes before arrows
Ordinary:
E-03, proposing and helping with the flag
The thread begins with uZQPvcOWTSuYwIXkYPLI+K5Gj5o= proposing a large Dutch flag. The title survives but the opening body is removed. We cannot recover its initial dimensions from that opening. In the surviving discussion people propose different locations, locate an existing red patch and ask how large it should be. These are arrangements made in this subreddit, not merely a link announcing that work exists elsewhere.
Voorstel om op /r/place een grote Nederlandse vlag te tekenen
c0052; uZQPvcOWTSuYwIXkYPLI+K5Gj5o=;
hour1.8233333333333333; item 62ms9a; thread
62ms9a; cite3535.
Ik ga je meehelpen daar!
c0053; MEPLY9ggUfl88Div+nViLWE/gaE=;
hour2.116388888888889; item dfnro19; thread
62ms9a; cite3538.
The full reply also asks about dimensions and warns that a large drawing will be difficult to keep. The words therefore couple willingness with an unresolved practical detail, rather than accept every possible Dutch project. Other replies fix the intended red area and explain how to find a pixel's coordinates. fe4bqk3AeN7ahCmQPoAX4e3ud8s='s instruction narrows the immediate task:
Gelieve rood kleuren binnen de lijntjes
c0054; fe4bqk3AeN7ahCmQPoAX4e3ud8s=;
hour2.366388888888889; item dfnshd4; thread
62ms9a; cite3540.
A later problem is an approaching rainbow. MEPLY9ggUfl88Div+nViLWE/gaE= asks what to do; uZQPvcOWTSuYwIXkYPLI+K5Gj5o= suggests shifting right; fe4bqk3AeN7ahCmQPoAX4e3ud8s= instead proposes watching a little longer.
Kijk het nog ff een uurtje aan eerst
c0056; fe4bqk3AeN7ahCmQPoAX4e3ud8s=;
hour2.8027777777777776; item dfntxko; thread
62ms9a; cite3544.
This last turn is not a record that the group waited or moved. The episode ends with alternatives still open. Its ordinary quality is the concrete movement from a recognizable image to willingness, bounds and a renewed question about where to work. It does not establish a settled leader or a successful drawing. Later replies in the same thread urge replacing other flags and report planning in Discord and cirkeltrek; their later date and different practical target do not turn this exchange into one continuous accepted plan. Full-thread read3516 supplies the context; those later statements cannot retroactively settle this early question.
Unpredicted:
E-20, following up the museum plan
The museum exchange appears inside a monthly collection of Dutch material, not a dedicated production meeting. The collection links to a promise about hanging the finished work in a museum. That linked page was not opened and supplies no independent evidence here. The coded exchange itself begins with 4n1TLGJmfLZx9GkRKksECuW9gX4= asking the named person for progress:
Hoe staat het met het museumplan FQ19tz2gdjIiQWUp402mIYRxXfQ=?
c0412; 4n1TLGJmfLZx9GkRKksECuW9gX4=;
hour93.83722222222222; item dftcfkq; thread
63d73s; cite3548.
FQ19tz2gdjIiQWUp402mIYRxXfQ= answers that the task needs at least a month, money and a specialist company. The source says:
Duurt minstens een maand. Ben maar een arme student buiten mijn buitenbaantje en uitprinten en inlijsten kost nogal wat! Dit gaat niet zomaar door de printer. Moet bij een speciaal bedrijf worden geprint op speciaal papier.
c0413; FQ19tz2gdjIiQWUp402mIYRxXfQ=;
hour96.30722222222222; item dftk6us; thread
63d73s; cite3550.
This is an explanation of delay by the person addressed. It is not a measured causal estimate, a paid commission or proof that a supplier has accepted the work. The reply turns a general promise into specific outstanding requirements: printing and framing are costly, and an ordinary printer will not do. The follow-up asks which museum:
Kun je alvast verklappen welk museum?
c0414; 4n1TLGJmfLZx9GkRKksECuW9gX4=;
hour96.37555555555555; item dftkf3t; thread
63d73s; cite3552.
No destination answer or delivered print is observed within the window. Placement has already ended at hour73, yet people still seek a practical next step concerning the finished work. The distinction matters: this is neither continued pixel placement nor just thanks for a completed action. The surprising form is a reproduction project with expenses and a new timescale, not another battle for pixels. It challenges a telling that ends all arranging when placement ends. It was remembered in the prior, so its selection claims no surprise of discovery: the earlier structural distinction alone would not have generated its requirements. Full-thread read3518 includes later out-of-window suggestions, which are excluded from the account. An unfinished display plan remains the supported endpoint.
Stopped
early: E-10, requesting an Armenian border or alliance
At hour31.165555555555557, u+sJvopAiWbIA/enEFG/EQJlqvY= posts a request identifying Armenia as the flag immediately to the left. The speaker claims to represent that subreddit and describes a numerical disadvantage. Representation and relative numbers are the participant's claims, not verified memberships or a count supplied by this study.
Hello, I represent /r/Armenia, the flag to your immediate left. We are few in numbers and will surely die out if your expansion continues, would negotiations of a border and perhaps an alliance be possible?
c0308; u+sJvopAiWbIA/enEFG/EQJlqvY=; item
62w8sk; thread 62w8sk; hour31.165555555555557;
cite3546.
The request does several practical things. It identifies neighbours, names a threatened consequence of continued expansion and proposes border negotiation or an alliance as a possible response. It addresses readers as people who might affect expansion. None of that makes those readers able to bind every Dutch placer, and the prediction of dying out is not an observed outcome. Nor is a question proof that an alliance began.
The complete served thread at3520 contains only this request. A separate thank-you referred to in the episode register has removed text, so it cannot recover substantive terms or show who accepted them. This limits the early-stop claim: the public exchange available here stops before a negotiated answer; it does not establish that all discussions stopped or that no agreement existed elsewhere. There is no rejection to infer from silence, no treaty to infer from the proposed alliance, and no final flag condition to infer from the warning.
Later Armenian preservation appeals and a Dutch dissenter's repair statement belong to a renewed encounter, not to an imagined continuous response chain from this post. Keeping the earlier request separate preserves the missing link. It is especially useful against an account in which asking neighbours automatically produces reciprocal restraint. This episode has a practical approach but no observed agreement or uptake. A fuller telling would need a substantive answer tied to this request and evidence of what followed. Missing bodies and unseen venues keep that evidence unavailable rather than negative.