# Figure: local organizing without total project control

## Rendered figure and mandatory reading key

![Controller-rendered retained model](display/037acfbbee2fbb5a05788b64ea9e7cccf5b6623fcca30d9c0e63bc093b71fa0d/model.png)

The actual controller drawing uses a stacked layout. Its three arrow labels must be read with these proposition tags: `A01` = `N01`; `A02` = `N02`; `A03` = `N03`. The imposed clock marker is hour 73: placement stops there, while affiliation and prospective work can continue. This caption is part of the figure; those proposition tags and the terminus are not printed inside the controller's image. The requested three-column arrangement below is a precise layout specification, not a claim that the gateway implements it. No source statement or relation was altered to force a different renderer layout.

With-theory view: the image above plus this caption. Without-theory view: the same image and caption. There is no drawable extra conjectural link because neither `A04` nor `A05` has an instance. This is a source limitation, not a claim that the two hypotheses are established.

## Complete source specification and instances

Use the conditions/moves/reports arrangement in `sketches.md`. Draw all ten retained elements once: left `K01` reported or anticipated reversion limits and `K02` personal acceptance without mandate; middle `P01` directing a usable contribution, `P02` seeking/offering/crediting help, `P03` explaining/negotiating terms, `P04` selecting intended features/extent, `P07` explicitly revising a stated position, `P05` affiliating/commemorating and `P06` proposing further community work; right `C01` qualified textual reports of retained principal dogs. Grouping by dimensions remains visible in the accompanying data structure, not as extra process boxes.

Draw exactly these supported arrows, each fair and bounded:
- `A01`, `P03` to `P07`, tagged `N01`: `E-04`, `c0014` "I believe your mods have agreed to this." followed by the same hostile caller's `c0015` "I take it back this is great", with initial `c0013`. The source items are `dfq46vo` and `dfq4mkc`, thread `62z7n6`. This is local explicit uptake, not enacted reconciliation by a whole community.
- `A02`, `P03` to `P04`, tagged `N02`: `E-06`, `c0020` "Agreement with the Dutch to prevent them from destroying these goodboys was to give one clogs.", item `dfq5x8e`, thread `62zdco`; also `E-15`, `c0064` limited anatomy permission, item `dfrfjeq`, thread `634x2p`. This is stated permitted specification, not retained pixels or binding mandate.
- `A03`, `P02` to `P04`, tagged `N03`: `E-09`, `c0035` "If you need help in reclaiming the E, I'm a willing participant." and the explicit response `c0036` "it is alright, we are redesigning a more compact text that centers properly", source items `62zx9e` and `dfq8jys`, thread `62zx9e`. This is redirection of the expressed task, not assignment or completion.

The community scope on each is Goodboye only. It is not a measured cross-community tendency. Evidence is quoted words in linked episodes; the controller's clocks appear in `account.md` and `data_structure.md`, and no interval is calculated by hand. These are the only three links carried by propositions. Neither conjectural `A04` nor `A05` has a supporting instance, so neither may be drawn even in the with-theory view. Render the with-theory and without-theory views from the same source: both therefore have these same supported links, with the omitted hypotheses named in this caption rather than unsupported dashed arrows. Do not invent instances to make the views differ.

Include the imposed terminus at hour 73: placement ends, but affiliation and prospective work need not. No loop is drawn because `model/loops.jsonl` contains no complete dated cycle. There is a middle column of named practical processes, but no earned arrows from every condition or into every reported consequence. The figure is deliberately not an all-connected causal chain.

What it leaves out: ungrounded attachment-to-renewal `A04` and agreement-to-retention `A05`; contextual `c0073`; the four unresolved episode consequences; and the verbal registers of commands, uncertainty, personal disclaimers, gratitude and jokes. No whole coder theme is excluded. The topic-based defence theme is split because directing correction, excluding a friendly addition and describing an unsustainable change do different work. The table and account retain these distinctions and their uncertainty.