# Candidate dynamic model: joinable work without secure possession

## Explanation

Readers did more than make independent Black Mirror references. MHtuaUljST1QhfFWWSdTKiZnBp0= asked whether the room should make the White Bear logo; SrHQ6cwpHufzK0kFjtWvWtX8bpg= answered “Good idea. I'll try and start it off” (`c0008`, `62s5if`, H19.467777777777776; `c0009`, `dfouib2`, H20.449166666666667, thread `62s5if`; cites2921/2924). `P01` names this local adoption, not the automatic conversion of a subreddit into an organization. The objective was proposed and accepted in the exchange; its eventual size and site remained open.

Making that objective joinable required specifications, not merely enthusiasm. oHVsyeaY/1c+HArySkXaDsD14gM= offered a smaller measured image because it would be “far easier to make and maintain” (`c0014`, `dfoxud5`, H22.275, `62s5if`, cite2927). K8FrAKwjV0LGh2qPhrmDrMLXHZc= made larger ambitions conditional on helpers (`c0029`, `dfp25cs`, H24.073055555555555, `62s5if`, cite2936). In the later attack thread Fluff says “we'd need larger numbers though. We're struggling to maintain what we have at the moment” (`c0051`, `dfq9cbo`, H46.93083333333333, `62zxr8`, cite2955). These stated capacity assessments, `K01`, enter proposed feasible work, `P02`, through `A01`. They do not show measured scarcity causing a completed redesign.

Entry questions, `P03`, sometimes occasioned concrete answers. “I'm willing to help, where is the official logo going to go?” (`c0031`, `dfp38tw`, H24.504166666666666) receives a statement of “the plan right now” (`c0032`, `dfp3wra`, H24.77027777777778; both `62s5if`, cites2939/2942); the whole answer repeats the pattern and coordinates. `A02` is this observed request-to-guidance transition. Its strongest contrary item is `c0053`, `dfrdtl7`, H61.8675 in `62zxr8`: “Where is it? I'd be glad to do some maintenance!” (cite2961). No surviving answer is shown. Missing bodies limit absence, but an unconditional request-to-answer account cannot stand. The model does not treat willingness as successful labor allocation.

Neighbour responses, `P04`, remain differentiated. Rainbow is to be accommodated: “Instead of completely cutting through rainbow road” the proposal is black outlines with rainbow interiors (`c0037`, `dfpn5tg`, H32.768055555555556, `62s5if`, cite2948), with recorded endorsements. Purple instead prompts “We must fight back” (`c0045`, `dfpyi4j`, H38.594166666666666, `62s5if`, cite2953). These contrasts between encounters do not establish a community changing its mind. Nor does the earlier warning prove that it caused the rainbow proposal.

The contact mode has one explicit attributed result, `A03`: “Vandals overnight, I PM'd them and they've stopped. Randoms are still pushing the purple though” (`c0052`, `dfq9oq4`, H47.081944444444446, `62zxr8`, cite2958). `C01` preserves the limitation in the same words: addressed vandals reportedly stop, unrelated placement continues. This is thin, uncorroborated causal attribution by a participant, not verified effectiveness or a successful community-wide recovery mechanism.

The original-canvas cutoff, `K02`, is irreversible at H73. The contributor later says they tried adding black, could not access placement and “Then seconds later place was over” (`c0057`, `dfssjhw`, H82.55194444444444, `63ahf5`, cite2969). `A04` relates this terminal interruption to the observed retrospective sequence, `P05`, not to enjoyment as an effect of closure. A remnant is reported, losses and retries recalled, and making valued. The postclosure referral “You can go at it again on r/pxlsspace” (`c0060`, `dfsuejb`, H83.20972222222223, `63ahf5`, cite2975) defeats an all-organizing-ends account. It shows an actionable invitation, not successful migration.

## Adverse episodes and model boundaries

`E-03` is the odd positive case: keeping a recognizable outline need not require erasing another project. The model accommodates that selective response but does not predict neighbour choice. `E-06` is the sharper reach limit: a precise Tesla-A proposal (`c0055`, `631ycf`, H52.25833333333333, cite2964) has no recorded adoption or reception. It cannot be narrated as `P01`'s completed adoption or `P02` yielding a group. `E-08` keeps the original-canvas boundary from becoming a claim that all future coordinating speech ceased.

The explanation should break where participants do not share an actionable object or cannot access a common specification; where nobody answers entry requests; where interfering actors are unidentified or unresponsive to contact; and where a different venue or institutional authority changes the practical conditions. These are process conditions, not a small-corpus disclaimer. Unseen acts and deleted bodies are evidential limits on judging those conditions. Stable membership, authority and survival are not assumed.

## Elements and ranges

The arrows run between typed local processes, conditions and a participant-attributed claim, linked downward to coder themes and higher constructs. They relate presences, reasons and observed transitions, not covarying amounts. Full immutable candidate lines and evidence are in model/elements.jsonl and model/arrows.jsonl.

| Element | Work in the explanation | Range |
|---|---|---|
| `P01` | Proposing and explicitly accepting a common undertaking | `E-02` initial adoption; no final-plan consensus |
| `P02` | Making work joinable through specifications | `E-02` and `E-05` proposed scale/location/pattern; not execution |
| `P03` | Asking where/how to join | `E-02`, `E-05`; no guaranteed answer |
| `P04` | Differentiating accommodation, resistance and contact | `E-03`, `E-05`; one-sided accounts, no treaty |
| `P05` | Claiming contribution and valuing making | `E-07`; retrospective, not prospective reward |
| `K01` | Stated capacity/maintenance limits | `E-02`, `E-05`; not counted staffing |
| `K02` | Original placement unavailable at closure | H73 setting and `E-07` testimony; not all venues |
| `C01` | Reported targeted cessation amid continued random placement | `E-05` contact report only |

## Arrows and disconfirmation

| Arrow | Kind; strength | Mechanism | Failure observation and actual test |
|---|---|---|---|
| `A01`: `K01` to `P02` | co-occurrence; fair | Upkeep/helper assessments restrict proposed feasible scale | Unchanged larger ambition despite the stated constraint; `E-05` instead acknowledges it. `E-06` not testable |
| `A02`: `P03` to `P02` | transition; fair | An entry question occasions restating common work | Missing or unusable reply; `E-05` has no surviving answer. Retain observed `E-02` pair only |
| `A03`: `P04` to `C01` | transition; thin | Targeted PMs reportedly interrupt addressed interference | Same addressed vandals continue; no independent test. `E-02`/`E-03` show no comparable PM report |
| `A04`: `K02` to `P05` | order; fair | Placement interruption makes the attempt terminal, subsequently recounted | Continued original-canvas placement or a misread retrospective account would challenge it; no such failure is observed. `E-08` is outside this relation, a boundary probe rather than a failed instance |

Every arrow rests on cited words; none relies on an invented interval. The within-item PM sequence and the recalled interruption are participant statements, not separately dated observations. No arrow is graded strong; live/aftermath numerical comparison is therefore not claimed on an untestable new denominator. Sampling units are episodes, and comparison results/failure clauses precede strength in the candidate record. Base-rate fields are null because no frequency or statistical association is asserted; a connected statement is not warranted by presence rates.

For `A01`, a coder could have selected only explicit scarcity talk and thereby made constraint appear explanatory. The direct reasons in `c0014` and `c0051` distinguish a local participant argument from that selection artifact, without licensing prevalence. For `A02`, coding may favor answerable exchanges; the full later thread and contrary `c0053` prevent universalizing the selected pair. For `A04`, aftermath coding could manufacture a clean retrospective ending; `c0060` remains actionable under the unchanged prior, and closure's effect on original placement is narrower than the posting-time pattern. These are the strongest candidate arrows; none thereby becomes a verified causal relation.

## Projection and retained structure

`D01`, Feasibility under contingent cooperation, retains `T4-001` and `T4-002`: internal capacity differs from external exposure. `T4-003` remains undimensioned. All three higher themes are coined, unchanged from R3, now marked used in candidate1. The single-member coexistence abstraction is still the least certain; a single adaptation umbrella would conceal the accommodation/resistance contrast. No coder conflict file or cross-room onset contrast exists. No finding changes follow from inclusion metadata alone.

Dimension projection is an inventory, not a higher causal arrow: internal mass `A01`, `A02`, `A03`; incoming mass empty; outgoing mass empty. `A04` lies outside `D01`. There are no multiple placements, so the inventory with and without doubles is identical. Internal arrows have unlike mechanisms (capacity reasoning, answering questions, targeted contact), which do not abstract into one dimension-level causal account. The absence of crossing arrows gives `D01` no measured flow; it remains a feasibility distinction, not proof of drift, inflow or causal isolation.

Used lower themes by coded label: `t02`, working out a White Bear design and where it could hold; `t03`, getting enough people together to place and grow the logos; `t04`, protecting the logos while working around blue, rainbow, and purple pixels; `t06`, claiming a last pixel or logo as r/place ended; `t07`, remembering the White Bear work as damaged, remade, and fun. Unused as explanatory elements: `t01`, pulling and playing along with a fake season-release April Fools joke; `t05`, proposing other Black Mirror words and White Bear changes on the canvas; `t08`, sending people to go at it again on r/pxlsspace. The last two are important boundary evidence, not failed or meaningless practices. Joke and mere-target role nodes were dropped because they add no explanation of shared canvas work; an “official organizer” role would rest on a request's adjective, not an evidenced office.

## ungrounded relationships

Recruitment causing a completed redesign is not grounded: stated need and later proposals do not show the causal course. Accommodation securing survival is not grounded: endorsements are not a verified outcome. Enjoyment motivating earlier labor is not grounded: retrospective value does not establish a prospective incentive. Loss producing a collective return-to-start loop is not grounded: `c0058` recalls personal retries without separately dated events for the whole cycle. Referral producing migration is not grounded: no human uptake appears in its supplied thread.

These are possible relationships, not typed retained arrows or findings. With them imagined, the account would become a smooth adaptation-success-and-renewal cycle. Without them, the retained graph contains only `A01`, `A02`, `A03`, `A04`: feasibility reasoning, local answering, attributed targeted cessation and original-canvas interruption/retrospection. No theorized-only arrow is drawn.

## looked-for-and-not-found

The selected full plan, attack, Tesla and memorial threads do not ground stable assignments, an officer, a shared repair schedule, a mutual rainbow treaty, verified recovery, a dated closed feedback cycle or successful migration. These are weak, scoped absences, not claims that such things never existed off-platform. No keyword hit count substitutes for reading. The strongest competing account remains independent personal attempts later remembered as a group achievement. Explicit adoption and question/answer defeats it for the initial plan, but `c0058` makes it consequential for later repair: the model retains a person's testimony, not a collective cycle.

No loop survives the same-room dated-cycle test, so model/loops.jsonl is empty. The model establishes an actionable common undertaking and limited maintenance attempts; it does not establish which tactic kept a verified array alive. R2's participant-reported final remnant and original-canvas cutoff must not be substituted for that missing relation.

## Critic correction and rival partition

The accepted critic correctly distinguishes a failure of the retained relation from a challenge to an excluded broader claim. For `A04`, the new-venue referral in `E-08` remains important boundary evidence but is not an eligible negative case of original-canvas closure. Its sample verdict is not testable, mechanism_failure_present is false, and negative_check is not-addressed. This is a correction of the annotation, not new support or stronger causal evidence. Original candidate history remains unchanged, with the correction appended.

The critic's rival groups `t02` with `t05` as candidate-object specification and `t03` with `t08` as opening participation. Those are genuine practical commonalities, not merely vocabulary or adjacency, and they require neither uptake nor migration. I retain the current partition because its explanatory question concerns making a particular undertaking feasible: the explicit relation between available helpers and workable scale links `t02` and `t03` locally. The rival makes target generation and participation availability more visible but separates those linked practices, while adding a contextual joke grouping outside the canvas explanation. The difference is analytic emphasis, not refutation or a requirement that all evidence fit. `t05` and `t08` remain boundary evidence with residual initiative unexplained; their lack of uptake alone is not the reason for leaving them unpicked. No higher-tier change follows, and the alternative remains visible in review-C2.md and notes-R4.md.