Forming: the retelling | D6b

The retelling: the model with its forms inside it

Part 1 goes dimension by dimension, one leg each (D6a-01 to D6a-08); part 2, the telling, follows, written at D6b with the figure (figure-D6.md). The two parts run to about 12,000 words. The forms are the six room forms of D4a-08c, by their final names (room-forms-names.md); the 35 branches are the level below and appear where they explain a form (the PI's message for D6, on J's word). The model is the version frozen at D3 (46384686d6173fdeb4c749667478c1363e675bc6b52bb6f4fdc211d387e68525), with two held proposals (QD4-001) stated in full in each form account.

The six forms:

• A, Border terms and the announced plan (166 rooms, 135 defining).
• B, Behind the thread: chat, scripts, raids (141, 113; a grouping, not a form).
• C, The design reopened (125, 96).
• D, Keeping, with help or carrying on (119, 96), with its splits D.1, Keeping with the call; D.2, Keeping inside the sub's play; and below D.2, D.2.1, The play, carried on, and D.2.2, The play, kept.
• E, The sub's play, run as work (98, 84).
• F, Moving for the spot (56, 34).

The form lines, one per element and room form, are in fractal-forms-D6.jsonl; the branch lines, at least one per branch where it explains a form, are in fractal-D6.jsonl (QD6-001; departures.jsonl line 20). How each form line is decided (rule logged at D6a-01 before it ran, _analysis/d6_fractal.py): on a form's defining rooms, an op on an element or arrow leans where it is held by max(5, a tenth of the defining rooms) or more, at 1.2 times the 558 defining rooms' share or more. A form replaces the element where contradict lines lean (none do, in any form), restricts it where restrict lines lean and outnumber the other leaning ops, specifies it where add-step, add-condition or link lines lean, and leaves it untouched otherwise. Each relation is a claim about the form's changes, a pattern across rooms counted by the ledger; what the rooms did is a claim on their words. No canvas field is used.

Part 1. Dimension by dimension

D01, Critical mass

In the global model. Critical mass is whether a scattered readership gathers enough hands, who know how to place, to make a work viable on the clock, and how a room reads its own numbers. Three fourth-order themes sit under it. Mobilization is the call and its answer: the room calls its members and kindred subs to place (P01), a member answers in one line that asks for nothing back (P15), the call follows a member's start (A02), and a bare join answers the call (A12). Sensemaking is members asking what the canvas is and others explaining it (P24). Collective efficacy is the room judging that it has too few hands or too little room (K02), and members stepping away under strain or repairing a quarrel (P32, a candidate). The model has the call at the start of the work, after a member proposes or begins the mark.

Mobilization. Three forms specify the call (P01), and each makes it return later in the work.

• In C, The design reopened, the call returns within the work. A finished figure, a granted space or a member's report of a part done becomes the premise for the next call. The rooms that show it best are r/starbound, r/bisexual and r/suomi; r/Honduras shows it least well. Not every C link is a return: in r/trees an explanation of the canvas leads a member to say they will place, and in r/anaheimducks the organiser explains why the timer favours working together. That is local variation inside the specification.
• In D, Keeping, with help or carrying on, the call returns from carrying on and from loss: a later canvas, damage to the mark or a lost spot leads the room back to calling for hands. r/bindingofisaac, r/rotmg and r/edmontonoilers show it best; r/rojava least well. Two branches explain part of it: F11 (carrying on as renewed work, begun before the close) and F12 (the spine restarted on another canvas) lean to D at 2.62 and 2.69 times its share, and three of their rooms in D link the call (r/bindingofisaac, r/furry_irl, r/sadboys), two of them to a later canvas or a remake.
• In F, Moving for the spot, the call returns after a lost, taken or bulldozed spot: a failed attempt or a smaller restart reopens the call at a new spot. r/twentyonepilots, r/snsd and r/penguins show it best; r/dbz least well. F09 (the move returns to building) leans to F at 2.33 times its share, but of its rooms in F only r/penguins links the call, and not to a move, so the branch does not explain this return; F09's line is read at the building element (D02).
• A, B and E leave P01 untouched.

The start before the call (A02) is restricted in D and E, where the start and the first call share one post in the restricting rooms; the lines say that the two coincide, and in two E rooms (r/nintendo, r/titanfall) a call came before any start. The bare answer (A12) is restricted in F, where answers to a call often ask where or how to help, or give a reason (r/sips, r/latin, r/UPenn; r/ducks least well). The one-line answer itself (P15) is untouched in all six forms.

Sensemaking. All six forms leave P24 untouched. Members asked what the canvas is and were answered in every form, at about the population's rate: P24 is instantiated in 84 to 95 per cent of each form's defining rooms.

Collective efficacy. All six forms leave K02 untouched as a change, although form F instantiates it in 32 of 34 defining rooms, against 82 per cent of the 558; F's rooms judged their room too small or their hands too few, and the change they made was to the move that followed (A10, read under D04). Form B restricts P32: where a member left, the reason given was the room's scripts or an ideology (r/placecanada, r/EraseThePlace), not strain, and attempts to repair a quarrel are seen without their outcome (r/reddevils, r/FederationPlace; r/EraseThePlace least well).

What the forms add to the dimension. The model has the call once, at the start. Three forms show it again, after a finish (C), after carrying on or a loss (D) and after a lost spot (F). The account grounds no loop; these link lines are the material for one, and they go to proposals-D6.jsonl as an unvalidated proposal (PR-D6-01), not into the model. Two smaller proposals answer branch notes from D5 with the forms' lines: an answer that joins and asks for a task as a second form of acceptance (PR-D6-02, from F's A12 lines and branch F35), and a start that is itself the first call, as a clause in A02's bound (PR-D6-03, from D's and E's A02 lines and branch F32). Elsewhere the forms leave critical mass as the model states it.

D02, Coordination without command

Written at D6a-02. Form lines in fractal-forms-D6.jsonl (78 lines: 13 units by six forms; 21 lean, 57 untouched); branch lines in fractal-D6.jsonl.

In the global model. Coordination without command is how hands that no one can command come to place the same picture: what settles what the room will make, and what aligns the placing. Six fourth-order themes sit under it. Collective representation is the design (P02). Direct information sharing is members reporting the mark's state as they build (P03). Standardization of output is the template (P04). Workarounds are the scripts, bots and spare accounts (P14), with the site's faults (K06) and members' own time and devices (K05). Backstage decision-making is the chat (P23) and keeping plans from rivals (P33). Decided order is the starter (R01) and the claim that most rooms worked without deciding how they were organized (C01, a decided element in 46 of 705 rooms). Three arrows end here: the call brings builders (A01), a template settles the design (A11, its withdrawal a held proposal), and scripts follow upkeep under strain (A06).

Collective representation. Two forms specify the design.

• In C, The design reopened, the design is settled for a time and reopened: a provisional choice made overnight, rough lettering to hold a gap, a finished mark followed by the next addition. r/bardmains, r/gatech and r/aggies show it best; r/uvic least well. F07 and F34 explain it.
• In E, The sub's play, run as work, the design depends on the host and the means: a host's approval for space, the colours and size available, the upkeep of a picture already standing (r/warframe, r/starlightstage, r/yugioh; r/baylor least well). F34 explains it here too.
• A, B, D and F leave P02 untouched.

F34's rooms in C and E size the design to the hands before any loss, a consequence of K02 that the model does not state; it goes to proposals-D6.jsonl as PR-D6-05.

Direct information sharing. Only F, Moving for the spot, specifies P03: building returns after a move, as a new spot or a replacement plan is followed by a new start (r/wildhockey, r/portal, r/UPenn; r/warthunder least well). F09 (the move returns to building) explains it: 8 of the 12 holders are its rooms. The arrow from the move to building is PR-D6-04. The call-to-building arrow (A01) is restricted in D and E. In D the call and the building overlap, and an active builder also recruits (r/gorillaz, r/gamindustri, r/rotmg; r/cgpgrey least well). In E the two appear apart in the record (r/uwaterloo, r/paragon, r/teslamotors; r/baylor least well).

Standardization of output. Three forms specify the template.

• In A, Border terms and the announced plan, members keep the template in step with the placements: they correct references against what is placed and replace stale plans (r/FloydVsVoid, r/stardewvalley, r/kamenrider; r/Villanova least well). F15 explains it: 20 of the 32 holders are its rooms. F15's note asked whether the plan follows the work; in form A it does.
• In C the template is kept current: builders retire outdated posts, announce changed locations and message overwriters (r/torontoraptors, r/eve, r/tf2; r/kuwait least well). F33 explains it.
• In F the template moves with the spot: a new site gets an anchor coordinate (r/dallasstars, r/latin, r/portal; r/warthunder least well).

F15 and F33, which their notes call one change at two nodes, fall in different forms, A and C. C restricts A11. In 40 of its 58 lines the template did not settle the design: colours, sizes and spacing stayed open, or a redesign was repaired away as damage (r/starbound, r/bardmains, r/pitt; r/guatemala least well; F07 and F33). These are the grounds of the held A11 proposal, which stays held.

Workarounds. Three forms specify machine hands and two restrict them.

• B, Behind the thread: chat, scripts, raids, runs scripts as shared tools whose targets and versions are kept in step (r/mexico, r/PlaceNL, r/AmericanFlaginPlace; r/aeon least well). F08 (machine hands kept on one target) explains it: 24 of the 33 holders.
• E lets machine hands help only on conditions: matching targets, agreed overlaps, updates reaching every runner (r/mls, r/dota2, r/teslamotors).
• F keeps scripts and overlays in step across accounts, and members switch automation off to place by hand (r/wildhockey, r/predators, r/sbu; F08).
• A and D restrict P14. There scripts are offered, debated and refused, and the record shows the offer more than any placing (A: r/FloydVsVoid, r/mindcrack, r/prequelmemes; D: r/rutgers, r/danganronpa, r/Temple, with F24).
• A06 is restricted in D and F. Scripts did not wait for strain: they were offered for a new build or a move, or came with the first request to coordinate construction (D 12 of 21 lines fail as stated; F: r/sips, r/wildhockey, r/uiowa).
• K05 and K06 are untouched in all six forms.

Backstage decision-making. B specifies the chat. It works on conditions: invitations that work and a current plan members can find (r/mexico, r/quebec, r/reddevils; r/lithuania least well). F16 and F29 explain it, the chat family the D5 notes read as one change with three ops. A specifies the chat's upkeep: expired invitations are replaced and decisions are brought back for members outside it (r/berserk, r/theexpanse, r/de; r/japan least well). Inside A, F30 (the chat seen only through its invitations and returned reports, not its choices) restricts P23: its rooms are 10 of A's 16 restrict holders, and they show the chat only from outside, through invitations, venues offered and reports that come back (r/xcom, r/forsen, r/prequelmemes; line added at D6a-07). E restricts P23: its threads hold invitations and claims brought back, not how the chat decided. No form changes P33.

Decided order. A and C restrict C01. In their lines, rooms divided the work, appointed representatives, assigned defenders or pixels, and endorsed a template, though implementation is not shown and the population count is not tested. A's best rooms are r/FloydVsVoid, r/furry and r/berserk; C's are r/PUBATTLEGROUNDS, r/bisexual and r/gatech. R01 is untouched.

What the forms add to the dimension. Each form specifies the part of coordination its name says:

• A, the template kept in step with the placements and a division of the work;
• B, shared scripts and a chat that works only on conditions;
• C, the design reopened and the template kept current;
• E, design and scripts on the host's and the tools' conditions;
• F, building again after a move, with a template that moves with the spot.

D specifies nothing here; it restricts the order of call and building and the arrow from strain to scripts. Two unvalidated proposals come from this dimension: PR-D6-04 (after the move, the room builds again) and PR-D6-05 (the design sized to the hands before any loss).

D03, Maintenance

Written at D6a-03. Form lines in fractal-forms-D6.jsonl (18 lines: 3 units by six forms; 4 lean, 14 untouched); branch lines in fractal-D6.jsonl.

In the global model. Maintenance is what keeps a finished work alive on a surface anyone can change, and how a room decides what a change to its work was. Two fourth-order themes sit under it. Repair work is keeping (P05): members watch the work and repair changed pixels, rally under attack, cover the night, harden the shape and put upkeep before growth. Its second and third sentences are the telling clause. Repair restores the form the keepers know, so a change the room planned is repaired away until its keepers are told of it. Attribution is working out who changed the work and why (P06). One arrow ends here: once a mark stands, keeping it becomes the work (A03, building then keeping). Four D5 findings bound the telling clause: F-024 (the change read from its shape, informed members holding it), F-025 (informed members reject it), F-026 (at the border) and F-027 (in keeping). The held P05 proposal states the first of these as a bound, and it stays held (QD4-001).

Repair work. Four forms change keeping, each in its own way.

• In A, Border terms and the announced plan, keeping takes conditions and links. Protecting a neighbour can mean undoing the room's own overextension (r/FloydVsVoid). Keepers can refuse a change they know of as a takeover (r/de). Repair follows the keeper's own idea of the right form, even when that form holds a spelling error (r/prequelmemes). An announced finish is followed by repair and renewed defence (r/stardewvalley, r/ripcity). F32 (the marking returns to keeping) explains the links: 9 of its rooms hold them. r/halo shows the form's keeping least well.
• In C, The design reopened, the lines restrict the telling clause. Informed members refused changes, or the record cannot tell ignorance from dissent, and none of the 47 lines shows a change lost only for want of telling (r/bardmains, r/pitt, r/PUBATTLEGROUNDS; r/pusheen least well). F07 (the telling clause not shown at the design) explains it: 34 of its rooms are among the 46 that restrict.
• In D, Keeping, with help or carrying on, keeping is shared and checked. Watches are volunteered and handed on, keepers check the current canvas and the intended form before they repair, and the room ranks what to keep (r/portugal, r/mylittlepony, r/rotmg; r/glasgow least well). F27 explains part of it: two of its four rooms here check whether a change is intended before undoing it (r/OnePiece, r/radiohead).
• In F, Moving for the spot, keeping begins before the mark is finished. A border reserves the space, defenders are planned before a stable work exists, and a repair tool's reference image is diagnosed and changed (r/wildhockey, r/portal, r/planetside; r/clubpenguin least well). F08 explains the machine part.
• B, Behind the thread: chat, scripts, raids, and E, The sub's play, run as work, leave P05 untouched. E instantiates it in 71 of 84 defining rooms, against 93.4 per cent of the 558; its records hold less keeping.

A03, building then keeping, is untouched in all six forms.

Attribution. P06 is untouched in all six forms. Form D comes nearest: 9 of its defining rooms add steps to working out who changed the work, at 2.01 times the 558's share, one room under its floor of 10.

The telling clause, read across the forms, as the D5 notes asked. The forms that touch the clause show four ways it holds only in part:

• informed keepers refuse a change: C, and r/de in A (F-025);
• the news must cross to a neighbour: the border, read under D04 (F-026);
• a script keeps the old form until its operator changes the target: F, and branch F08 (F-027's machine route);
• keepers check before they repair: D.

The last is a route by which keepers learn of a planned change other than being told. It is the step the room models of r/OnePiece, r/cowchop and r/armok proposed (F27's note), and it goes to proposals-D6.jsonl as PR-D6-06, unvalidated. No form's lines show a planned change lost only because its keepers were not told. P05's statement is unchanged, and the held proposal stays held.

What the forms add to the dimension. Every form keeps its work as P05 states it. What differs is when keeping starts and how keepers learn the intended form:

• A ties keeping to the neighbours and to the finished mark;
• C meets the telling clause with refusal;
• D shares and checks the keeping;
• F keeps the spot before there is a mark to keep.

D04, Order without law

Written at D6a-04. Form lines in fractal-forms-D6.jsonl (120 lines: 20 units by six forms; 22 lean, 98 untouched); branch lines in fractal-D6.jsonl.

In the global model. Order without law is how rooms that cannot compel one another keep order between their works on one canvas. Five fourth-order themes sit under it. Live and let live is sparing: rooms spare their neighbours' work, rein in their own attackers and apologise for damage (P07), and members argue whether covering others' work is fair (P31, a candidate). Negotiated order is border terms: rooms propose, settle and contest borders, truces and deals (P08), through envoys (R02). Members say that one member's agreement does not bind every placer (P21), and some members belong to both rooms (K07, a candidate). Reciprocity is help between rooms (P16). Meta-organization is coalitions (P17). Territoriality is the spot: the room chooses where to build before any loss (P27, a candidate), moves after a loss (P10), and lives on a host's mark under the host's rule (P19). Nine arrows end here. Keeping the mark brings the room to its neighbours (A04), and an attack call is met with a truce (A17). A settled border is a line members keep (A05), and an attack call is refused inside the room (A16). Short of hands, a room turns to other rooms (A13), and a settled border opens a channel for help (A14). Under attack, works defend each other (A19). Too few hands, so the room moves (A10). A21 runs from an agreement to the dispute over who may commit the room. F-020 bounds the dimension: sparing rests mostly on the room's own norm, and help rests on a deal about as often as not.

Live and let live. Four forms specify sparing, each with its own condition.

• In A, Border terms and the announced plan, sparing rests on overlapping membership, valued neighbouring art or fear of retaliation, and on placers whom the negotiators admit they cannot control (r/foxes, r/twice, r/hellointernet; r/germany least well).
• In B, Behind the thread: chat, scripts, raids, sparing passes through the room's tools. An instruction to spare agreed space must reach script users as a target update, and admitted script damage brings apology and repair (r/PlaceNL, r/theitalyplace, r/monero; r/asexual least well).
• In C, The design reopened, the room states its reason for restraint: an apology after a complaint, or help and space received from the neighbour (r/bisexual, r/farmcarrots, r/metroid; r/kindafunny least well).
• In D, Keeping, with help or carrying on, restraint protects the room's own logo, repays earlier help, and does not reach every placer (r/gamindustri, r/denverbroncos, r/portugal; r/magictcg least well).

A05, the settled border kept, changes in three forms. A restricts it in 39 of 135 defining rooms. Restraint often comes before any settlement is shown, and a treaty guides the members who learn and accept it while others keep placing against it (r/stardewvalley, r/furry, r/berserk; r/RelientK least well). F26 (the telling clause not shown at the border) explains the second half: its rooms keep a border only where placers learn and accept its terms (r/placetardis, r/furry, r/thailand). B and D add the condition that the terms reach the placer (B: r/quebec, r/reddevils, r/AmericanFlaginPlace; r/neu least well. D: r/bindingofisaac, r/denverbroncos, r/mylittlepony; r/pepe least well). In B, F08 (machine hands kept on one target) explains part of it: an accommodation needs compatible script targets (r/india, r/AmericanFlaginPlace). In D some placers do not learn of the truce (r/bindingofisaac, r/radiohead). Read together, these lines state F-026 for the border. Told placers stop. Placers the terms do not reach keep placing, and a script keeps placing until its target is changed. The reading goes to proposals-D6.jsonl as PR-D6-07, a bound on A05, unvalidated.

E, The sub's play, run as work, restricts A16. Its restraint answers reported harm, overlap or a planned enlargement, not a written attack call refused inside the room (r/uwaterloo, r/starlightstage, r/hunterxhunter; r/wow least well). No form changes P31. E comes nearest, with 8 restrict holders, one room under its floor of 9.

Negotiated order. Three forms specify border terms.

• In A, border terms take work and meet limits (r/FloydVsVoid, r/catalunya, r/twice; r/kurdistan least well). F10 (a deal carried out as work) explains it: 14 of its rooms hold the deciding lines. Members discuss a border inside the room before contact (r/drawhelix), check a request's consensus and credibility (r/switzerland), and carry the terms to placers and templates, a step members say is still incomplete (r/poland, r/transformers). Identity colours limit what members concede (r/twice), and uncontrolled placers can defeat a promise (r/littlewitchacademia).
• In B, border talk has steps before and after it: a treaty request before any damage, local consensus before a proposal, and a negotiated move relayed to builders (r/linux, r/czech, r/FederationPlace; r/duckgame least well).
• In C, agreements are kept apart from compliance: members report attacks after announced terms, and a truce needs a counterpart able to keep it (r/torontoraptors, r/gatech, r/suomi; r/earthbound least well).

F, Moving for the spot, restricts A04. In 13 of its 34 defining rooms border talk comes before keeping. Rooms ask neighbours for permission or access while they seek a spot (r/dallasstars, r/sips, r/wildhockey; r/Northwestern least well), or a neighbour objects when the room's building or script crosses its work (r/KState, r/httyd). No branch explains the cell. F09's rooms hold 4 of the 13 lines, but F09's change is building again after a move. The two routes go to proposals-D6.jsonl as PR-D6-09: arrows from choosing the spot (P27) and from building (P03) into border terms, beside A04, unvalidated. R02, P21, K07, A17 and A21 are untouched in all six forms.

Reciprocity. Two forms specify help, and one branch specifies it where its form does not.

• In C help is part of the room's own building. Helpers alternate placements between the two works, and paired scripts give spare capacity to the neighbour (r/starbound, r/pitt, r/timbers; r/bretagne least well).
• In D help waits on the helper's own work (r/gamindustri, r/rutgers, r/mylittlepony; r/OneTrueEmilia least well). F22 (help conditional on the helper's own work and spare hands) explains it: 11 of its rooms hold the deciding lines. Donors give when their work is secure and pixels are spare (r/mylittlepony, r/OnePiece), and they weigh what the help does to a third room's mark (r/gamindustri).
• In A the form leaves P16 untouched, but F28 (help at the border conditional) specifies it: its rooms are 10 of the form's 22 add-condition holders. The helper's home work must be safe (r/ripcity, r/utaustin), the neighbour must stop attacking (r/catalunya), and promised help stays apart from help delivered (r/lsu, r/necrodancer).

C and D restrict A13, short of hands, a room turns to other rooms (C 30 of 96 defining rooms, D 33 of 96). In C donors help from completed or well-kept work, and help comes with construction and overlap repair (r/bardmains, r/cubers, r/PUBATTLEGROUNDS; r/uvic least well). F07's rooms hold 12 of the 30 lines, but F07's change is the telling clause, not help, so it does not explain the cell. In D help comes from surplus more than shortage. Donors give after their own work is finished or safe, repay earlier protection, and put off help while their home defence is short (r/gamindustri, r/bindingofisaac, r/denverbroncos; r/cgpgrey least well). F22 explains part of it: aid repays earlier protection once the room's own image is finished (r/OnePiece), and donors weigh their own work's safety (r/mylittlepony). Read with F22 and F28, the lines say that a shortage brings the request, and the donor's spare hands decide whether help comes. This answers the D5 note on D's A13. It goes to proposals-D6.jsonl as PR-D6-08, unvalidated. In 12 other lines a request is recorded and arriving help is not shown; the record cannot tell whether it came.

A restricts A14, a settled border opens a channel for help. In A help is part of the bargain more than its result: pixels and shared upkeep are offered as the terms, or help is under way when the bargaining starts (r/catalunya, r/jerma985, r/empiredidnothingwrong; r/norway least well).

Meta-organization. P17 and A19 are untouched in all six forms.

Territoriality. Three forms change the spot and the move.

• D restricts P19, hosting. Guests ask for space or depend on a host, but a grant, an approval procedure or a durable host rule is not shown (r/gorillaz, r/gamindustri, r/denverbroncos; r/sadboys least well). F restricts it the same way, at the request stage (r/sips, r/latin, r/UPenn; r/streetfighter least well). In A the form leaves P19 untouched, but F31 (hosting as one-off permission) restricts it: its rooms are 8 of the form's 12 restrict holders. An overlap is permitted for one arrangement (r/foxes), a replacement permission is called provisional (r/malaysia), and an incorporation is offered and accepted on conditions (r/mindcrack). In all three forms hosting shows as a request and a single permission, not a standing host rule.
• F restricts P27. The choice of spot also comes after a loss: the room picks a new site or a backup while another of its works has been lost (r/penguins, r/twitch, r/ethoslab; r/dbz least well). The before-loss bound holds for the site decision, not for the room's whole history.
• E and F restrict A10, too few hands, so the room moves. In E a judgment of too few hands ends one member's part or one expansion, while the others keep repairing, recruit or finish (r/fivenightsatfreddys, r/mls, r/worldoftanks; r/battlecats least well). In F the move answers the spot more than the hands. A taken spot or a lack of permitted space moves the room, and where members name too few hands, the move is only proposed or hesitant (r/wildhockey, r/latin, r/twentyonepilots; r/warthunder least well). This answers the D5 note on F's A10. P10's statement already names the loss of the spot as the move's cause, so the reading needs no proposal. It bounds A10 as F-019 does, where the loss itself prompted the move in 10 of 21 rooms.
• P10 is untouched in all six forms. F comes nearest, with 3 restrict holders against a floor of 5.

What the forms add to the dimension. Every form keeps order between rooms as the model states it, by sparing, terms and help. What differs is how far the order reaches:

• A holds sparing and terms to the placers the terms reach, and makes help part of the bargain;
• B carries terms to placers and scripts;
• C states its reasons for restraint and helps from its own building;
• D gives help from surplus and keeps hosting at the request;
• E restrains without a refused attack call, and a judgment of too few hands ends a member's part, not the room's place;
• F talks with neighbours before it has a mark, and moves for the spot.

Three unvalidated proposals come from this dimension: PR-D6-07, PR-D6-08 and PR-D6-09.

D05, Collective identity

Written at D6a-05. Form lines in fractal-forms-D6.jsonl (36 lines: 6 elements by six forms; 0 lean, 36 untouched); no branch lines.

In the global model. Collective identity is what a room brings to the canvas as a body, and what it makes of itself there. Four fourth-order themes sit under it. Frame bridging, the carrying of a frame from outside the canvas into it, holds the quarrel the community carries in (K03) and the new jokes members make out of the canvas work (P26, a candidate). Flagging the nation holds the room acting as the body it was before the canvas (K04): it argues the nation's history and belonging, carries in the sub's lore, jokes or ideology, or professes a colour as a faith. The same theme holds C02: in some rooms a tie from before the canvas names the rival in the turn that calls for the attack, a claim untested for order. Neo-tribes, groups that form around a shared sign, holds the room that forms for the canvas around a mark (P28, a candidate) and K04's faith in a colour. Symbolic boundaries holds what members say offends: they refuse slurs and hate symbols and argue over jokes (P29, a candidate). No arrow ends here. C02 also sits under Contention and P28 under Host framing; their lines are written here once.

No form changes collective identity. All 36 cells are untouched. Changes to these elements are rare in the population. Across the 558 defining rooms the most common is a restrict line on C02, in 35 rooms; then P28 (18), P26 (13), and K04 and P29 (12 each). No form reaches its floor, which runs from 5 to 14 defining rooms. The nearest cells are C02 in B (9 restrict holders against a floor of 12) and P26 in D (6 against 10, at 2.68 times the share). Among the branches that lean to a form, the most any holds on one op is 4 rooms (F07 on C02 in C).

Of the restrict lines I read (the nearest cells and form B's), nearly all say what the record cannot show, not that the element fails:

• on C02, a national, historical or lore frame names a target, but the record does not show that a tie from before the canvas selected it (r/austria and r/dwarffortress in B; r/switzerland and r/xcom in A; r/costa_rica in D);
• on K03, invoked national history does not show an earlier quarrel between the two subs (r/england and r/quebec in B);
• on P28, a venue or a chat is opened, but the record does not show the room's founding or its first recruits (r/osugame, r/prequelmemes and r/TheFarLeftSide in A; r/czech in B);
• on P26, a joke is made, but the record does not show that the room took it up or kept it (r/frc and r/gameattack in D; r/habs and r/paladins in E).

A few lines say the element fails as stated: a rival named by some members divides the room instead of aligning it (r/chicago in C), and one member's ideological target is not the room's when another member turns that effort to helping allies (r/mylittlepony in D).

Where the forms differ: how often they hold it. The forms keep these elements as the model states them, but their rooms hold them at different rates (each form line gives its count):

• B, Behind the thread: chat, scripts, raids, holds every element of the dimension above the 558's rate. The largest gaps are C02, in 28 of 113 defining rooms (25 per cent, against 16), and P28, in 20 (18 per cent, against 11). The carried quarrel is held in 31 (27 against 21), the room as a prior body in 91 (81 against 70), and the argument over offence in 30 (27 against 20).
• F, Moving for the spot, holds them least: K04 in 18 of 34 (53 per cent), C02 in 2, P28 in 1 and P29 in 4. Its records are the shortest of the six forms (median 64.5 coded concepts), so the low rates may follow from short records.
• E, The sub's play, run as work, has the longest records (median 222 concepts) and still holds C02 in 9 of 84 (11 per cent) and P28 in 3 (4 per cent). Record size does not explain B's high rates: B's median record (131 concepts) is shorter than D's (142) and E's.
• New jokes made from the canvas (P26) are held at about the same rate in every form, from 73 to 81 per cent, against 78.

These are rates of instantiation, not changes, and the rule does not test them. They say where identity sits. In B, the form named for chats and raids, the room brings its prior quarrel and body to the canvas, and some rooms form around a mark: r/purplecorner sustains a split over which colour is legitimate, and r/thebluecorner, a day-old group, claims its own lore. r/thebluecorner is also the room that most threatens the account, a colour faction whose faith names its rivals and rules on guests. C02 is read again under Contention.

The D5 notes that touch this dimension.

• F14 (D5a-14), kept damage beside P26 and P05: in three rooms the final damage became part of the emblem once the canvas was locked. P26 is untouched in every form, and F14 has 7 members, so the case stays a particular of three histories, as the note said. F14's line comes with its key, P13, under Imprinting.
• F23 (D5a-23), a group outliving its task: rooms formed for the canvas asked whether to last, set goals or closed and reopened on a new canvas. P28 is untouched in every form. F23's line comes with its key, P13, under Imprinting.

What the forms add to the dimension. Nothing to its statements. No form specifies, restricts or replaces an element of collective identity, and no branch changes one inside a form. The forms differ in how often their rooms bring identity in: B holds it most and F least. No proposal comes from this dimension.

D06, Host framing

Written at D6a-06. Form lines in fractal-forms-D6.jsonl (24 lines: K01, P20, P34 and A20 by six forms; 5 lean, 19 untouched; P28's lines were written under D05); branch lines in fractal-D6.jsonl.

In the global model. Host framing is what the host sub does around the room's canvas work. Two fourth-order themes sit under it. Keying, the framing of an activity as something other than what it seems, holds K01: the host sub is keyed as play for April Fools, members post fakes and takeovers under the one-day licence, and a claim in it, a call to the canvas included, may be a joke. Boundary work, the drawing of a line around an activity, holds P20 and P34. The host sub draws a line around canvas talk (P20): moderators gather it into a megathread, remove canvas posts by rule or pause the sub's usual events, and members open a canvas sub or object to the flood. Members who object to the canvas posts can turn against the room's own mark (P34, a candidate held by two rooms). The room that forms for the canvas around a mark (P28) sits here too; it is told under D05. One arrow ends here: calls flood the host sub, and the host draws a line (A20, strong, 132 of 155 rooms). Its bound says the line is partly constitutive, and that 23 of the 155 rooms draw it before the room calls.

Keying. Three forms specify the frame, all by added steps.

• In E, The sub's play, run as work, the play is run as work (r/warframe, r/fivenightsatfreddys, r/mls; r/polandball least well). Moderators start it and set its rules, real removals and bots enforce them, members test claims and repair what the styling breaks, and they argue its end by the clock and the time zone. 58 of the 84 defining rooms hold these lines, 56 of them as added steps (66.7 per cent, against 18.5 per cent of the 558). F01 (the play administered) explains the cell: 54 of the 58 holders are its rooms. Each of its subforms explains one part of it:
  • F02 (the takeover run as a temporary regime): fictional rules enforced by real removals (r/battlecats, r/zelda), mock bans and resignations performed (r/acecombat, r/ontario), and the licence ended by restoring ordinary rules (r/MMA);
  • F03 (the joke tested): claims checked by sources and the date (r/yugioh), an author's authenticity tested after the takeover ended (r/hunterxhunter), and a joke told from an earnest mistake (r/drumcorps);
  • F04 (the licence policed): compulsory joke participation contested (r/monstercat), and the licence's end disputed (r/dankmemes);
  • F05 (the styling ended): styles switched off or the font uninstalled (r/pcmasterrace, r/schoolidolfestival), and the joke period ended by a moderator (r/popheads);
  • F06 (the joke kept): permanent flair, a real version of an invented reward, or the banner kept (r/mls, r/runescape, r/rust).
• In D, Keeping, with help or carrying on, the play is administered beside the keeping (r/bindingofisaac, r/denverbroncos, r/nyjets; r/yuyuyu least well). Members dispute when the joke ends, test fakes by date and source and police tasteless claims, and moderators restore the ordinary styling. 21 of the 24 holders are rooms of D.2, Keeping inside the sub's play, the split of form D whose rooms keep their canvas work inside the sub's play. F04 explains part of it: members demand restoration and dispute the prank's duration (r/chelseafc), and set tasteless death claims apart from jokes everyone can enjoy (r/bostonceltics).
• In F, Moving for the spot, members argue the play's limits more than they run it (r/dallasstars, r/wildhockey, r/stargate; r/streetfighter least well). F04 explains part of it: members contest a painful prank, and moderators apologise and remove an official-looking endorsement (r/stargate, r/nbaspurs).
• A, Border terms and the announced plan, B, Behind the thread: chat, scripts, raids, and C, The design reopened, leave K01 untouched.

F01's rooms are 23 of D's 24 holders and all 9 of F's, but F01 leans to D and F at 1.32 and 1.22 times its share, under the rule's 1.5, so it is not named there. The form notes asked whether F01 and form E restate each other. They do in part: 59 of F01's 103 rooms are in E, all five subforms lean to E, and F01 explains E's only leaning cell in this dimension. The other 44 of F01's rooms lie in D (23), F (10), C (6) and B (5). F01 is therefore a facet that runs mostly inside E and reaches D's split D.2, not a second name for E.

F21 (the canvas call not a joke) leans to E. Its rooms there restrict the frame, but few of them in F21's own terms. In r/scp the play does not show that the canvas calls were false, and in r/borussiadortmund a recognised prank does not make the canvas construction a fiction. The other lines bound details of the play, such as styling kept or the calendar. In r/osu the play reached the canvas work: a redirect blocked reinforcement and sent members to a chat. The record shows the play running beside the canvas work in most rooms and reaching it in a few (r/osu and r/polandball here; r/battlecats and r/bindingofisaac in the D5 notes).

The form notes also said that the model holds the play only as a key. The cells bear it out: in E, D and F the play is organized work with the steps the model gives the canvas work, and the model has no element for those steps. The reading goes to proposals-D6.jsonl as PR-D6-10, a process element beside K01, unvalidated. It would bring into the model the sub's own business that the scope ruling of D3a-55 put outside it, so it is a change of scope as well as a new element.

Boundary work. D specifies P20: the host makes room for canvas talk inside the sub as well as drawing a line around it (r/denverbroncos, r/mylittlepony, r/nyjets; r/sabres least well). Moderators offer a sticky (r/texans), mark canvas posts with flair (r/kirby), refuse a requested ban while keeping the organising thread (r/chicubs) and reverse a removal after checking in their chat (r/mylittlepony). Members contest removals or move to another venue because of them (r/canada). No branch explains the cell.

D also restricts A20 (r/rutgers, r/bindingofisaac, r/denverbroncos; r/polyamory least well). In its 10 lines the host's line is not shown to answer a flood of calls. Moderators route talk for visibility and timing, apply existing rules on duplicates and images, or decline a sticky for want of slots (r/radiohead, r/kpop, r/bostonceltics). The record does not show the calls flooding the sub first. This lies inside A20's bound, which already says the line is partly constitutive and sometimes comes first; no proposal. P34 is untouched in all six forms, and the held proposal beside it (members spoiling their own room's mark for fun, r/paladins and r/portugal) stays held.

What the forms add to the dimension. The forms differ on the frame, not on the host's line:

• E runs the April Fools play as work, and the frame family F01 to F06 explains it;
• D administers the play in its split D.2 and is the one form that changes the host's line, which in D makes room for canvas talk and is not shown to answer a flood;
• F argues the play's limits;
• A, B and C hold the frame and the host's line as the model states them.

One unvalidated proposal comes from this dimension: PR-D6-10.

D07, Imprinting

Written at D6a-07. Form lines in fractal-forms-D6.jsonl (54 lines: 6 elements and 3 arrows by six forms; 11 lean, 43 untouched; K05's lines were written under D02); branch lines in fractal-D6.jsonl.

In the global model. Imprinting is what the room does to make its temporary work last beyond the canvas. Four fourth-order themes sit under it. Completion ritual holds the marking: when a work is up, the room announces it, celebrates it, credits makers and helpers, and says what working with strangers meant (P11). Collective memory holds the record: screenshots, timelapses, reports of the work's fate, mourning, atlas entries and the end marked (P12). The same theme holds the contest over which version of the canvas and the event is kept, after placement ends (P22). Transition holds carrying on: near the close and after it, the room decides what of its effort to keep, such as a later canvas, a new purpose for its sub, the mark in its banner or the work remade elsewhere (P13). Visibility returns holds what the work brings back: new members who found the sub through the mark (P25, a candidate) and the notice of the people the mark shows or addresses (P30, a candidate). Three arrows run through the dimension in order. A finished mark is marked together (A07, 139 of 182 rooms), what is celebrated is kept on record (A08, 225 of 289), and the record is what passes on (A09, 113 of 145). Their bounds already admit the late side: a mark found already made, a work the close cut short, a record that comes first, and a next canvas planned while still building.

Completion ritual. Two forms specify the marking.

• In A, Border terms and the announced plan, the marking is provisional and contested (r/ripcity, r/utahjazz, r/opticgaming; r/halo least well). Success is judged and credit disputed while the work goes on, an announced finish reopens the work, and members celebrate a damaged remnant or partial progress. Three branches explain it:
  • F17 (the marking provisional and contested), 16 of the 21 holders: credit is checked and corrected during building (r/anime, r/vocaloid), and a finish is announced and the work reopened (r/taiwan);
  • F19 (credit contested during the work): members challenge who may claim credit (r/opticgaming) and ask for the names of forgotten helpers for a memorial (r/SwissNeutralityZone);
  • F18 (success judged while upkeep continues): celebration keeps the duty to maintain (r/ripcity), and success is weighed project by project (r/ftlgame).
• In D, Keeping, with help or carrying on, the marking is weighed (r/denverbroncos, r/yogscast, r/edmontonoilers; r/rojava least well). Members correct the room's name in the celebration, challenge and prove credit, and credit an effort that did not survive. F18 explains part of it: a mark recognizable and lasting enough counts as victory despite defects (r/kirby), and recognizable survival outranks perfect lettering while maintenance goes on (r/bostonceltics).

E, The sub's play, run as work, and F, Moving for the spot, restrict A07. In E the marking does not wait for a finished mark. Rooms celebrate a surviving emblem with planned additions unfinished, an incomplete attempt or a milestone, and pride and disappointment share the thread (r/pcmasterrace, r/uwaterloo, r/hunterxhunter; r/homelab least well). In F the marking answers a partial or traced work (r/twentyonepilots, r/nbaspurs, r/penguins; r/warthunder least well). F09 (the move returns to building) explains part of it: two of its three rooms here mark an unfinished work after moving (r/penguins, r/warthunder).

Collective memory. A specifies P12: the record holds more than the result (r/furry, r/theexpanse, r/jerma985; r/DCFU least well). Members mourn a destroyed neighbour with a memorial artwork, keep an imagined version of the hoped-for design, and help a viewer find a small surviving mark in the final image. F specifies P12 by links (r/corridor, r/planetside, r/qotsa; r/streetfighter least well). A locating question draws a fate report, and unfinished construction at the close leads straight to a tally and mourning, with no celebration between. B leaves P12 untouched, but F20 (the close as news) specifies it there: its rooms are 3 of B's 10 add-step holders. A closure reply corrects a rebuild call (r/chibears), and a member learns of the end after offering to restart (r/stlouis).

E restricts A08 (r/warframe, r/fivenightsatfreddys, r/mls; r/homelab least well). In its 24 lines the record does not wait for the celebration. Timelapses, live updates and reports of loss run before any celebration (r/minecraft, r/python, r/uoft). Where both appear, the lines show a sequence, not that the celebration caused the record. P22 is untouched in all six forms; A comes nearest, with 10 restrict holders against a floor of 14.

Transition. D specifies P13: carrying on is new work begun before the close (r/gamindustri, r/bindingofisaac, r/portugal; r/cgpgrey least well). Five branches of the carrying-on family explain it:

• F11 (carrying on as renewed work, begun before the close), 18 of the 30 holders: a successor canvas restarts recruiting, building and defence, and alternative canvases are discussed while placement is live (r/italy);
• F12 (the spine restarted on another canvas): construction, repair and destruction return on a live successor venue (r/furry_irl), and members weigh traffic and mobile access when they choose it (r/greyblob);
• F23 (the close scoped to the original canvas): hour 73 ends placement there while successor canvases allow more (r/rotmg, r/catholicism);
• F13 (the work remade in other media): a territorial claim lives on as copypasta (r/portugal), and members teach how to reproduce the image by hand (r/romania);
• F14 (the mark adopted as the room's emblem while it is still placed, damage included): an unwanted final blemish is valued as the emblem (r/cgpgrey).

The D5 notes asked whether F11 and F23 are one set of events read with two ops. In this cell they share 4 of F23's 9 holders (r/bindingofisaac, r/cgpgrey, r/greyblob, r/naruto). This is the overlap expected of two groupings that meet at one node; it is not one branch. F14's kept damage, noted at D5 beside P26 and P05, shows here in r/cgpgrey, and in form A in r/utahjazz, where members joke about an imperfect finish and take shared pride in the damaged work.

E restricts P13 (r/warframe, r/pcmasterrace, r/stevenuniverse; r/totallynotrobots least well). Carrying on is invited or proposed more than taken up: a successor canvas or a reused chat is offered, and adoption is not shown. F25 (carrying on in talk) explains it: 7 of the 10 holders are its rooms (r/paladins, r/starcitizen).

D and E restrict A09. In D carrying on does not wait for the record (r/rutgers, r/bindingofisaac, r/mylittlepony; r/magictcg least well). Successor invitations, reuse and remaking come before or beside the final image. F11 explains part of it: design reuse precedes the close (r/lovelive), and preservation starts from an interim image (r/texans). In E carrying on follows the record in order, but no line shows the record causing it, and uptake is not shown (r/warframe, r/starlightstage, r/stevenuniverse; r/homelab least well). Many of these lines deny that a saved record caused the room to carry on. A09 is an order and does not claim that, which bears out the D5 note that the account's words for A09 should state an order, not a cause.

Visibility returns. P25 and P30 are untouched in all six forms. P25 comes nearest in B, with 8 link holders at 2.32 times the share, against a floor of 12.

Read across the forms. The forms that change this dimension show one pattern. The marking, the record and carrying on often begin while the work is being built, and the rooms mark and record an attempt cut short or lost. The order of the three arrows still holds in most rooms, as their counts say. In 46 rooms of A, D, E and F the lines say the act came during the work, before a finish or after a loss (my reading). The reading goes to proposals-D6.jsonl as PR-D6-11, bounds on P11 and P13 and wider bounds on A07, A08 and A09, unvalidated. It answers the D5 notes that A07's bound does not cover marking during the work, before its finish, after its loss or on a spot held on leave (F27, F30 and F31).

What the forms add to the dimension.

• A marks while the work goes on and disputes the credit, and its record holds mourning and imagined versions;
• D weighs the marking and carries on as new work begun before the close;
• E marks unfinished work, records before it celebrates and invites successors that the record does not show taken up;
• F marks partial work and records failure;
• B carries the end as news only in F20's rooms, and C leaves the dimension as the model states it.

One unvalidated proposal comes from this dimension: PR-D6-11.

D08, Contention

Written at D6a-08. Form lines in fractal-forms-D6.jsonl (24 lines: P09, P18, A15 and A18 by six forms; 2 lean, 22 untouched; C02's lines were written under D05 and P33's under D02); no branch lines.

In the global model. Contention is how rooms fight over the canvas and over each other. Two fourth-order themes sit under it. Repertoire of contention, the set of moves a group has for attacking others, holds P09: rooms attack others' work by the moves the canvas affords, such as erasing, encroaching, converting a sign, raiding on a streamer's call, planting a script or altering a work as a joke. Rivalry holds P18: rooms carry a contest with a rival room in talk, trading taunts, flooding the rival's threads, claiming victory, saluting the rival after the fight and blaming attackers after the close. Both themes hold C02, the claim that a tie from before the canvas names the rival in the turn that calls for the attack, untested for order. Repertoire of contention also holds P33: rooms keep their plans from rivals who read their threads and reach into the rivals' venues (a candidate). Two arrows end here: a call's hands can turn on a rival (A15, strong, 93 of 129 rooms), and an attack is carried on in taunts (A18, fair, 56 of 68). A15's bound says that where a room's first canvas act is an attack, the attack call is the first call. Two more arrows start here and end in Order without law: an attack call is refused inside the room (A16) and met with a truce (A17). They are told under D04.

Repertoire of contention. No form changes P09. Two forms restrict A15.

• In B, Behind the thread: chat, scripts, raids, the record does not show a call's builders turning on a rival (r/PlaceNL, r/virginiatech, r/india; r/shitredditsays least well). Of its 18 lines, 7 fall inside A15's bound by my reading. The attack call is the first call or shares the opening turn with recruitment (r/ohio, r/virginiatech, r/HomestarRunner), or an attack call recruits directly (r/shitredditsays). In the other 11 the lines show the order of the calls but not that the same recruited hands attacked (r/india, r/latvia, r/Russiaclan). The D5 notes on form B counted the same 11.
• In E, The sub's play, run as work, the attack talk sits inside the recruiting (r/fivenightsatfreddys, r/dota2, r/stevenuniverse; r/pokemon least well). Recruitment and attack proposals share a thread or a call, and the lines do not show that recruited builders became the attacking hands. In r/habs the switch ran the other way, from a rival's interference to helping the room's own mark.

No branch explains either cell. F08 holds 4 of B's lines and F01 10 of E's, but their changes concern machine hands and the April Fools play, not the turn from building to attack. The restrictions mostly say what the record cannot show. A15 is an order (93 of 129 rooms hold it), and its gloss, "a call's hands can turn on a rival", reads as if the same hands were followed from the build to the attack. They are not followed in the record. This is a wording item for A15, like A09's under D07, and it is held with the arrows' wording items; no proposal.

Rivalry. No form changes P18 or A18. A18 comes nearest in B and E, with 8 and 6 restrict holders at 1.7 times the share, against floors of 12 and 9.

Where the forms differ: how often they hold it. As with Collective identity, the forms keep these elements as the model states them but hold them at different rates (the form lines give each count). B holds contention most. P09 is held in 103 of its 113 defining rooms (91 per cent, against 79 of the 558), P18 in 88 (78 against 61), C02 in 28 (25 against 16) and P33 in 18 (16 against 9). F holds rivalry least: P18 in 10 of 34 (29 per cent), on the shortest records of the six forms. E holds P18 in 41 of 84 (49 per cent) on the longest. These are rates of instantiation, which the rule does not test. They put the fight, the taunts and the tie from before the canvas mostly in the form named for chats and raids.

What the forms add to the dimension. Nothing to its statements. Two forms restrict the arrow from the call to the attack, mostly on what the record cannot show, and B holds the dimension's elements more often than any other form. No proposal comes from this dimension.

Part 2. The telling

Written at D6b. Part 1 read the model one dimension at a time. This part reads it across the dimensions, form by form, then says which forms kept the work alive, what the unadapted group is, what the rooms the model could not compose have in common, and what the forms show that the model lacks. The figure is figure-D6.md. The proposals of this stage are listed at the end, apart from the telling, and none of them is part of the model.

The model with its forms inside it

The model is the version frozen at D3. It has 30 standing elements, 15 candidates and 21 arrows, and its spine runs from a member's start (R01) to the room's calls (P01), to building (P03), to keeping (P05), and on to the marking, the record and carrying on (P11, P12, P13). The six room forms were cut from what the rooms did to that model, not from the canvas. Read against the model unit by unit, each form specifies the part of the model its name says and leaves most of the rest as the model states it. Of the 396 form lines (66 elements and arrows by six forms), 37 specify, 35 restrict, 324 leave the unit untouched, and none replaces it. No form does the model's work in another way. Every change is added detail or a condition, which is the fractal claim of the contract: the level below specifies the level above without contradicting it. Thirty-one units are held by every form as the model states them. Among them are the step from building to keeping (A03), the starter (R01), attack calls (P09), the move (P10), the bare answer (P15), coalitions (P17) and the contest in talk (P18).

How the forms differ in their functioning. Each form changes a different part of the model.

• A, Border terms and the announced plan (11 units changed) works through terms and a plan kept current. It specifies the template (P04; F15), keeping (P05; F32), sparing (P07) and border terms (P08; F10), the marking and the record (P11, P12; F17, F18, F19), and the chat's upkeep (P23). It restricts the settled border kept (A05; F26), help after a settlement (A14), decided order (C01) and machine hands (P14). In A, terms and plans hold for the placers they reach.
• B, Behind the thread: chat, scripts, raids (7 units) is a grouping, not one shared change. It specifies the scripts (P14; F08), the chat (P23; F16, F29), sparing, terms and the border kept (P07, P08, A05; F08), and it restricts the turn from the call to the attack (A15) and stepping away under strain (P32). It holds the elements of collective identity and contention more often than any other form, without changing them (D05, D08).
• C, The design reopened (10 units) works through the design. It specifies the call, which returns after each finish (P01), the design (P02; F07, F34), the template kept current (P04; F33), sparing and terms (P07, P08) and help woven into building (P16). It restricts keeping's telling clause, because informed members refuse a change (P05; F07), and it restricts the template settling the design (A11; F07, F33), help from shortage (A13) and decided order (C01).
• D, Keeping, with help or carrying on (17 units) changes the most units. It specifies keeping, shared and checked (P05; F27), carrying on as new work begun before the close (P13; F11, F12, F13, F14, F23), help from a helper whose own work is safe (P16; F22), the call that returns from carrying on and loss (P01; F11, F12), the marking weighed (P11; F18), the sub's play administered in its split D.2 (K01; F04), sparing (P07), the border kept where the terms reach (A05) and the host who makes room for canvas talk (P20). It restricts six arrows (A01, A02, A06, A09, A13, A20), the scripts (P14; F24) and hosting (P19).
• E, The sub's play, run as work (13 units) specifies the April Fools frame (K01; F01 to F06, F21), the design (P02; F34) and the scripts (P14). Its other ten changes are restrictions, eight of them on arrows (A01, A02, A07, A08, A09, A10, A15, A16), with carrying on (P13; F25) and the chat (P23). Its records hold the play and the reports of the canvas work, and less of the work between them, so the lines often say the record cannot show an arrow's order.
• F, Moving for the spot (14 units) works through the spot. It specifies the call after a lost spot (P01), building again after a move (P03; F09), the template that moves with the spot (P04), keeping before the mark exists (P05; F08), the record of failure (P12), the scripts (P14; F08) and the play's limits (K01; F04). It restricts border talk after keeping (A04), scripts under strain (A06), the marking of a finished mark (A07; F09), the move for too few hands (A10), the bare answer (A12), hosting (P19) and choosing the spot before any loss (P27).

Two patterns run across the forms. First, the four working forms specify where they work: A specifies 7 of its 11 changed units, C 6 of 10, D 9 of 17 and F 7 of 14, while E restricts 10 of its 13. Second, the changes to arrows are nearly all restrictions. Of the 20 arrows in the figure, 16 are restricted in some form and one is specified (A05, by B and D). The order counts of the arrows still hold in most rooms. Where a form restricts an arrow, its lines say that the order holds there only under a condition, that the second act came first or at the same time, or that the record cannot show the order.

One condition across the dimensions. Read together, the forms show one condition at four places in the model. A placer acts on a form or a term only where it reaches them. Keepers repair a change away until they are told of it or check it (P05, read under D03). A settled border holds for the placers who learn and accept its terms, and for the scripts whose targets are changed (A05, under D04). A script places the old target until its operator changes it (F08). A helper must know the allied picture to help it (F22). The model states the first of these, in P05's telling clause. The check and the terms are proposals of this stage (PR-D6-06, PR-D6-07), unvalidated, and the script's target and the allied picture are notes of branches F08 and F22.

Which forms kept the work alive

These readings come from the record, by the fields stage A1 wrote for every room (prior.md section 5): when the room's coordinating ended (organizing_end_hour), how much of its talk after hour 73 coordinated rather than recounted (the aftermath share, with the rooms that coordinated after the close counted), and the room's own last word on its work (work_remained: kept, lost or silent, with silence counted as an unknown outcome). Beside the field is the D5b re-reading for the members in a branch (stood or gone at the close, by a rule logged before the reading). The canvas is not read here (rule 7): its pixels show what stood, not whose work it was, and the forms were not cut from it. The figures are for each form's defining rooms (_analysis/d6b_survival_forms.json).

Over all 705 rooms the median end is hour 72.02, 146 rooms coordinated after the close, and the field reads kept 347, lost 218 and silent 140 (49 per cent kept).

To the freeze. C and D keep most by their own word: 60 and 57 per cent of their defining rooms say the work was kept, against 49 per cent of all rooms. D's split D.2, Keeping inside the sub's play, says kept in 27 of 42 (64 per cent). D's records also say most often what became of the work: 6 of its 96 defining rooms are silent, the fewest of any form, and its re-reading finds the most work gone (13). E keeps least among the large forms: 39 kept against 38 lost. F's defining rooms say kept in 15 of 34, and its other members are silent in 16 of 22.

After the freeze. B coordinates most after the close: 35 of its 113 defining rooms coordinate after hour 73, and its mean aftermath share is the highest (0.028). A and D follow, with 29 rooms each. F stops before the close: its median end is hour 71.23, and 2 of its 34 defining rooms coordinate after it.

What in the model separates them. The forms that keep most and speak most about their outcome change the keeping part of the model. D specifies keeping (P05), help from a helper whose work is safe (P16), carrying on begun before the close (P13) and the call that returns from carrying on (P01). C reopens the design and keeps the template current (P02, P04), and its keepers refuse changes they know of (P05). The form that coordinates most after the close, B, changes the chat and the scripts (P23, P14), the means that outlast the canvas. The forms that keep least change other parts. E changes the sub's play, which ends with the day, and its records hold the canvas work thinly. F changes the spot and the move: its rooms lost or were refused a spot, built again, and stopped before the close. The call and the fight do not separate the forms: every form holds attack calls and the contest in talk as the model states them.

These are readings, not tests. The differences in kept share are modest (44 to 60 per cent), the field was right in 25 of 34 rooms when prior.md measured it, and the D5b re-reading agrees with it in 248 of the 476 rooms in a branch. The forms' records differ in length (the median defining room holds 64.5 coded concepts in F and 222 in E), so silence and the end hour partly measure the record.

The unadapted group, and the rooms the model could not compose

The unadapted group is empty. No room returned none: all 705 rooms adapted the model. 229 adapted rooms sit in no branch (A 60, B 54, C 37, D 39, E 11, F 28). They are in the forms, and the forms' lines include them.

The rooms the model could not compose. Two counts apply. By the verdicts the forms carry (my last ruling at D3, else the readers' agreed verdict at the first return), one room does not compose and ten cannot be told. The one is r/picturegame (form E, 13 coded concepts). At the first return its record was, in the readers' words, "a subreddit game of SoundGame rounds, picture hints, guesses, correct-marking, Discord invitations, and emoji proposals, not a canvas mark". At the re-check no room failed to compose: both readers found r/picturegame composes with residue, and both could not tell 19 rooms. Those 19 are r/austriahungary, r/azerbaijan, r/azores, r/bannedfromanime_irl, r/bigbang, r/Braveryjerk, r/FlipnoteStudio3D, r/greenland, r/Lugarix, r/nonbinary, r/PokemonSage, r/polyamory, r/ReBoot, r/Redox, r/THE_R, r/TheID, r/wario, r/watchmen and r/yerbamate. What they have in common is a short record, not another way of organizing. Each holds 1 to 8 coded concepts, against a median of 101 over the 705 rooms. Only r/polyamory is a defining member of its form; 15 are silent on what became of their work, and 16 are in no branch. They sit in five forms (A 3, B 3, C 4, D 4, F 5) and in none of E. At D3a-56 I ruled two of them, r/polyamory and r/THE_R, to compose with residue. r/picturegame's first-return record differs in kind: it is the sub's own play, the work that form E runs beside the canvas and that the model holds only as a key (PR-D6-10).

What the forms show the model lacks: the returns

The model grounds no loop: no room's record runs a whole cycle, and no counted arrow runs back. The forms carry the material for three returns.

• The call returns (C, D and F; PR-D6-01). After a finished part, a later canvas, damage, a loss or a move, the room calls for hands again.
• The move returns to building (F; F09; PR-D6-04). After a relocation the room recruits, designs and builds again at the new spot.
• The marking returns to keeping (A; F32). An announced finish is followed by repair and renewed defence.

The first two are the returns this telling found missing at its first legs. The third is F32's. None is entered in the model. Each would need a return to the rooms and a new validation cycle.

The held proposals (QD4-001), stated in full

Both were made at D4a-01 and reverted in the same leg (move 203). Neither was served to any room, and neither is re-checked. The model told here holds P05 and A11 as frozen at D3.

• P05, move 198, history lines 173 to 176, reverted by line 181. The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." The status would be bounded. The bound would read: "It does not hold where the keepers read a planned change from its shape and stop repairing it with no telling: completeanarchy, polska, satania, halo, bangtan, thesilphroad (R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018), a candidate branch, 'the shape read' (F-024). It does not hold where informed members hold the change against keepers who do not know: armok, maryland, oneshot (R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013), a limit below the trigger, at three nodes."
• A11, move 199, history lines 177 to 180, reverted by line 182. The arrow from P02 to P04 (a template settles a design argued in a thread) would be withdrawn under rules 14 and 16. Its order between rooms never beat its null (111 of 185 rooms, 0.600, against a null 95th percentile of 0.670). Inside threads, the template came first in 98 rooms against the transition in 111, so the arrow carries no direction. The failure clause stands alone in 117 rooms, 31 of them talk only. And 261 accepted restrict lines say that a template does not settle the design for good. What remains supported, that design talk and layouts meet in threads, is held by P02's and P04's statements. The full text, with its rooms and lines, is in tree-D4.md ("The held proposals").

Form C bears on both. Its keepers refuse changes they know of (F-025), a case the held P05 bound does not name, and it restricts A11 in 40 of its 58 lines (Part 1, D02 and D03). Both stay held.

The proposals of this stage, apart from the telling

Eleven proposals came from the form lines. Each is in proposals-D6.jsonl with its evidence and rooms, against the frozen model, with status unvalidated. None enters the model in this run, and E1 reports them.

• PR-D6-01, the call returns (23 rooms).
• PR-D6-02, the answer that asks for a task (4).
• PR-D6-03, a proposal that is itself the call (8).
• PR-D6-04, after the move, the room builds again (9).
• PR-D6-05, the room sizes its design to its hands before any loss (9).
• PR-D6-06, the check before repair (6).
• PR-D6-07, the terms bind the placers they reach (24).
• PR-D6-08, help comes from the hands a helper can spare (21).
• PR-D6-09, border talk before keeping (12).
• PR-D6-10, the play run as work (89).
• PR-D6-11, imprinting runs with the work (46).

The answer to the theory question

When strangers organize on a clock they did not set, with no way to compel anyone, organizing takes six forms in this record. Four are working forms, each named by the part of the work its rooms changed: the terms with neighbours (A), the design (C), keeping with help and carrying on (D) and the spot (F). One is a grouping of the means behind the thread, the chat, the scripts and the raids (B). One is a form whose record is mostly the host sub's April Fools play, run as work beside the canvas (E). The forms differ in their functioning by which part of the shared model they specify. Each adds detail or a condition there, and none does the model's work another way. By the rooms' own word, the forms that kept the work alive to the freeze were the ones that changed keeping (D, with C). The forms that coordinated after it were those with the chat and the scripts (B), the terms (A) and carrying on (D). The forms built on the spot (F) and on the play (E) kept least. What separates them in the model is keeping and its returns, not the call or the fight. Every form holds the call and the fight as the model states them.

The figure: the model with its forms inside it

Drawn at D6b from fractal-forms-D6.jsonl by _analysis/d6b_figure.py. It is the stage C5 figure (figure-C5.md, drawing 1: 21 boxes, 20 arrows, each arrow with the proposition that carries it) with the six room forms drawn into its boxes and arrows, at the level where they differ: the element or arrow. Each box and arrow names the forms that specify it (add detail that holds in their rooms) or restrict it (it holds there only under a condition). A box with no form named is held by every form as the model states it. Four elements outside the C5 drawing are added because a form changes them (P19, P23, P27, P32); the claim C01 stands beside the figure, as at C5. No form replaces any element. The unvalidated proposals (proposals-D6.jsonl) are not drawn.

The forms

• A, Border terms and the announced plan: changes 11 of the 66 units (elements and arrows) read.
• B, Behind the thread: chat, scripts, raids: changes 7 of the 66 units (elements and arrows) read.
• C, The design reopened: changes 10 of the 66 units (elements and arrows) read.
• D, Keeping, with help or carrying on: changes 17 of the 66 units (elements and arrows) read.
• E, The sub's play, run as work: changes 13 of the 66 units (elements and arrows) read.
• F, Moving for the spot: changes 14 of the 66 units (elements and arrows) read.

Units read: 66 (each with six form lines, 396 lines in all); lines that specify 37, restrict 35, replace 0, leave untouched 324.

Drawing 1, the model with the forms in its boxes and arrows

flowchart LR
  classDef changed fill:#fff4d6,stroke:#8a6d00
  classDef plain fill:#f4f4f4,stroke:#999
  subgraph conditions["Conditions"]
    K01["K01: the April Fools play, beside the work<br/>specified by D E F"]:::changed
    K02["K02: the room judges it has too few hands"]:::plain
  end
  subgraph mediators["Mediators, named for what the room and its members do"]
    R01["R01: the starter"]:::plain
    P01["P01: the room's calls for hands<br/>specified by C D F"]:::changed
    P02["P02: settling what the mark will show<br/>specified by C E"]:::changed
    P03["P03: building the mark, members posting its state<br/>specified by F"]:::changed
    P04["P04: templates and coordinates<br/>specified by A C F"]:::changed
    P05["P05: upkeep<br/>specified by A D F<br/>restricted by C"]:::changed
    P07["P07: sparing a neighbour's work<br/>specified by A B C D"]:::changed
    P08["P08: border talk and deals<br/>specified by A B C"]:::changed
    P09["P09: attack calls"]:::plain
    P10["P10: the move"]:::plain
    P14["P14: scripts and spare accounts<br/>specified by B E F<br/>restricted by A D"]:::changed
    P15["P15: the bare answer"]:::plain
    P16["P16: help between rooms<br/>specified by C D"]:::changed
    P17["P17: coalitions"]:::plain
    P18["P18: contest in talk"]:::plain
    P20["P20: the host sub's line<br/>specified by D"]:::changed
    P19["P19: a guest's work on a host's mark, under the host's rule<br/>restricted by D F"]:::changed
    P23["P23: the chat: planning moved off the thread<br/>specified by A B<br/>restricted by E"]:::changed
    P27["P27: choosing the spot before any loss<br/>restricted by F"]:::changed
    P32["P32: members stepping away under strain<br/>restricted by B"]:::changed
  end
  subgraph follows["What follows"]
    P11["P11: celebration<br/>specified by A D"]:::changed
    P12["P12: records (after hour 73, curation of the record)<br/>specified by A F"]:::changed
    P13["P13: what the room keeps<br/>specified by D<br/>restricted by E"]:::changed
  end
  C01note["C01, beside the figure: a decided element of order<br/>restricted by A C"]:::changed
  H73(["hour 73: placement stops for every room"])
  P11 --- H73
  H73 --- P12
  P01 -->|"A01 N01; restricted by D E"| P03
  R01 -->|"A02 N01; restricted by D E"| P01
  P03 -->|"A03 N01"| P05
  P05 -->|"A04 N02; restricted by F"| P08
  P08 -->|"A05 N09; specified by B D; restricted by A"| P07
  P05 -->|"A06 N06; restricted by D F"| P14
  P03 -->|"A07 N04; restricted by E F"| P11
  P11 -->|"A08 N04; restricted by E"| P12
  P12 -->|"A09 N04; restricted by D E"| P13
  K02 -->|"A10 N08; restricted by E F"| P10
  P02 -->|"A11 N07; restricted by C"| P04
  P01 -->|"A12 N07; restricted by F"| P15
  P05 -->|"A13 N02; restricted by C D"| P16
  P08 -->|"A14 N09; restricted by A"| P16
  P01 -->|"A15 N03; restricted by B E"| P09
  P09 -->|"A16 N03; restricted by E"| P07
  P09 -->|"A17 N03"| P08
  P09 -->|"A18 N03"| P18
  P05 -->|"A19 N02"| P17
  P01 -->|"A20 N05; restricted by D"| P20

Legend

• Boxes. Left, the conditions; middle, what the room and its members do; right, what follows the work. The bar at hour 73 marks the close. Shaded boxes are changed by at least one form; grey boxes by none.
• specified by X: in form X, add-step, add-condition or link lines on the unit lean (held by at least the larger of 5 and a tenth of X's defining rooms, at 1.2 times the 558 defining rooms' share or more). restricted by X: restrict lines lean and outnumber the other leaning ops. The rule was logged at D6a-01 before it ran (_analysis/d6_fractal.py).
• Arrows. Each keeps its C5 label: its id and the proposition (N01 to N09) that carries it, then the forms that specify or restrict it. Of the 20 arrows, one is specified by a form (A05, by B and D), and 16 are restricted by one or more. A restriction says the order holds in that form only under a condition, or that the record there cannot show it.
• Forms. A to F are the six room forms of D4a-08c, by their final names (room-forms-names.md). B is a grouping, not one shared change. The 35 branches are the level below and are not drawn; the table names the branches that explain each form's changes (fractal-D6.jsonl).

Where each form differs, with the branches that explain it

Held by every form as the model states it (31 units): A03, A17, A18, A19, A21, C02, K02, K03, K04, K05, K06, K07, P06, P09, P10, P15, P17, P18, P21, P22, P24, P25, P26, P28, P29, P30, P31, P33, P34, R01, R02.

What the figure leaves out

It leaves out what the C5 figure left out (its last section), the eleven unvalidated proposals, the two held proposals (QD4-001; stated in full in retelling-D6.md), and the rates at which the forms hold an element without changing it, which the rule does not test (told in the retelling under D05 and D08). It does not draw the branches, the splits of form D, or the survival reading by form, which the retelling gives in words.

The global model, as prose with ids (revised at stage D3)

Model version: 46384686d6173fdeb4c749667478c1363e675bc6b52bb6f4fdc211d387e68525 (the VERSION file). This is the model your room is read against. It was built from many rooms' talk about a shared canvas on which any account could place one pixel per interval, anyone could change any pixel, no one held authority over another's placing, and placement stopped for everyone at hour 73 (hours run from the canvas's opening). Stage D3 revised it from the rooms' own returns. R01, P05, P21 and P22 were reworded. P21, P22 and A21, tentative before, now stand, A21 with a stated bound. P06, R02, K03, K04 and P19, candidates before, now stand. Fifteen new candidates entered from acts that several rooms' records showed.

How to read it

• Ids. P is a process, K a condition, C a claim, R a role, A an arrow between two elements. Every id here is in VOCABULARY.json.
• Standing and candidate. An entry with no mark stands in the model. An entry marked (candidate) entered at stage D3 because several rooms' records showed an act that no standing entry states. A candidate carries no arrow and no order. Answer it from your room's record like any other entry, silence included: instantiate it, restrict it, or mark it absent with its evidence state.
• The unit is the room, or a group of rooms. The room is the actor where its members spoke or acted for it: in its threads, in the first person plural, in its calls or in plans it adopted. Members are the actor where they act apart from the room, or where the act is a person's (placing a pixel, running a script, answering a call).
• Each element has a range. The range runs from the smallest form the element takes to the largest. Read an odd act against the range before you call it something the model lacks.
• Each arrow reads: when the first element, the second follows, because of its mechanism. Its strength is strong, fair or thin. A thin arrow beats its null by a small margin or rests on few rooms.
• The record holds talk, not the placing. An answer to a call can be given by placing and leave no line. Silence about an element is not its absence: mark what your room's record cannot show as unobserved or not-testable, not as absent.

The start, the calls and building

A room's organizing runs in one order: a member starts a mark, the room calls for hands, members build, and then they keep the work. Members who join answer the room's call; joining is not part of the starter's role. Most answers come by placing, or in a bare line, and a member who refuses usually says why. The room settles what its mark will show by talk. It coordinates many hands by two routes that run largely apart: members post the state of the work in the thread, or they share a template.

• R01. The starter: a member who proposes the mark, maps it or begins placing it. Others joining is not part of the role: it is the answer to the room's call (P15), in the order A02 and A01 state. Range: from a member who only asks to a member who maps and places alone first.

• P01. The room calls its own members, and kindred subs, to come and place for a work: to start it, build it, finish it or hold it. Range: from one unanswered post asking who will help to a run of calls, cheering and a set time for placing together.

• P15. A member answers a call or proposal in one line that joins, assents, reports a part done or thanks, and the line asks for nothing back. Range: from 'On it.' to 'Did my part.'

• P20. The host sub draws a line around canvas talk: moderators gather it into a megathread, remove canvas posts by rule, change posting rules, pause the sub's usual events or disown the work; members open a canvas sub, object to the flood or argue the canvas's worth. Range: from one member asking for a megathread to moderators moving all canvas talk to a new sub and removing the rest.

• P02. The room settles what its mark will show of it: a member proposes a picture, the room argues its design, makes its land's flag or emblems the mark, signs it or leaves it unsigned, claims a mark others made, adds to it or enlarges it, or adds a personal piece to a shared mark. Range: from a single member's unanswered proposal to a design argued over days and redone, or a nation's flag sized and filled with its emblems, or one member asking to add their own words to a shared flag.

• P03. The room builds its mark, and members report its state to the thread: what is placed, done or missing, and where. Range: from one report that the logo is half done to reports on each part of a mark over two days.

• P04. Members circulate a template that lays out the mark pixel by pixel, or coordinates that locate it, ask for them, and ask strays to keep to them. Range: from one anchor coordinate to an official template the room asks everyone to follow against other versions.

• P14. Members add placements with scripts, bots and spare accounts, and the room argues over these machine hands and adjusts them. Range: from one member running spare accounts to a shared bot holding several rooms' works.

• A02 (R01 to P01; order, fair). Its gloss: a start gives the call something to gather around. A member who proposes or begins a mark gives the room something to answer, and calls for hands gather around it.

• A01 (P01 to P03; order, fair). Its gloss: calls bring the hands that build. The room's call brings members to the canvas, who then build the mark and say how far it has come.

• A12 (P01 to P15; transition, thin). Its gloss: the cheapest answer to a call. A call is the first part of a pair: posted to a thread, it makes an answer from each reader the next thing due, given in the thread or by placing. Joining is the answer the call prefers, so it comes bare, one line that commits and gives no reason ('I'm in'); declining is the dispreferred answer and, in conversation analysis, comes with a reason. In the written record a bare join is the ordinary way a call is accepted (25 of 31 read acceptances, F-023); a member can also accept by placing and write nothing, which the record cannot show.

• A20 (P01 to P20; order, strong). Its gloss: calls flood the host sub, and the host draws a line. Calls to the canvas flood the host sub, and its moderators or members answer by drawing a line around canvas talk: one thread, removals, a canvas sub.

• A11 (P02 to P04; transition, thin). Its gloss: a template settles a design argued in a thread. Design talk in a thread is settled by someone posting a template that lays out the agreed design pixel by pixel.

Keeping the work

Once a mark stands on a surface anyone can change, keeping it becomes the work. Keepers repair the work to the form they know. So a change the room planned is repaired away as damage until the keepers are told of it. Under strain, members add placements by machine.

• P05. The room keeps its placed work against erosion: members watch it and repair changed pixels, and the room rallies to defend it under attack, covers the night, hardens its shape and puts upkeep before growth. Repair restores the form the keepers know. A change the room has planned or agreed (P02) is therefore repaired away as damage until its keepers are told of it, and it is lost or given up where the telling does not reach them. Range: from one member fixing stray pixels to shifts, scripts and calls to defend over many hours.

• A03 (P03 to P05; order, strong). Its gloss: a built mark becomes a mark to keep. Once a mark stands on a surface anyone can change, keeping it becomes the work: a finished part is something to lose.

• A06 (P05 to P14; order, strong). Its gloss: scripts arrive under strain. Upkeep under attack outruns what one pixel per interval can hold, and members turn to scripts and spare accounts to keep up.

Other rooms

Keeping the work brings the room up against its neighbours. Rooms talk borders, truces and deals, trade help, join coalitions, and live as guests or hosts on one another's marks. A member may act for the room toward another room. No room can make every placer keep an agreement, and members say so. A room spares a neighbour's work mostly on its own norm.

• P08. Rooms propose, settle and contest borders, truces and deals with neighbours by talk, through envoys, and hold each other to them. Range: from a one-line border agreed in a thread to treaties across languages kept and broken over a day.

• P07. Rooms spare their neighbours' work, rein in their own attackers, apologise for damage and appeal to attackers to stop. Range: from one member refusing to cover a neighbour to a room restoring a work it had damaged.

• P16. Rooms help one another's works and trade help: they give pixels to a neighbour's mark, ask other rooms for help, barter help for space or repair, thank their allies, greet them, and turn requests away. Range: from one member placing a pixel on a neighbour's flag to rooms trading night-time repairs for room on their mark.

• P17. Rooms join other rooms in coalitions: they meet in shared chats, form alliances, gather kindred rooms in a hub, tally kindred rooms' works and make joint marks. Range: from two rooms agreeing to defend each other to a council of kindred rooms holding a stretch of the canvas together.

• P19. One room's work lives on another room's mark or territory under the host's rule: guests ask for space or protection, hosts rule on requests, and both sides dispute who may approve. Range: from a small room asking to slip into a neighbour's lot to a flag hosting dozens of works by application and vote.

• R02. The envoy: a member who acts for a room toward another room, carrying a proposal between threads or chats. Range: from a member calling themself a diplomat once to a standing representative in a shared council.

• P21. Members dispute, or state the limits of, who may commit the room to an agreement with other rooms: they say that one member's agreement does not bind every placer, deny that a treaty speaks for them, or ask another group for a leader to deal with. Range: from one member saying that a deal cannot stop everyone to a treaty announced in r/place answered 'You don't speak for me, man.'

• A04 (P05 to P08; order, fair). Its gloss: keeping the mark brings the room to its neighbours. Keeping a mark against erosion brings the room up against the neighbours whose pixels erode it, and the room turns to talk with them.

• A05 (P08 to P07; order, thin). Its gloss: a settled border is a line members keep. A settled border gives the room a line to keep: members spare the neighbour's work by it and remind others of it.

• A13 (P05 to P16; order, fair). Its gloss: short of hands, a room turns to other rooms. A room keeping its work under strain runs short of hands and turns to other rooms for help, and other rooms send it.

• A14 (P08 to P16; order, thin). Its gloss: a settled border opens a channel for help. Talk over a border opens a channel through which the two rooms then trade help: room for upkeep, pixels for protection.

• A19 (P05 to P17; order, thin). Its gloss: under attack, works defend each other. A room keeping its work against attack joins other rooms whose works face the same threat, and they defend each other's works together.

• A21 (P08 to P21; order, bounded). An agreement made with another room in the room's name puts its members' compliance in question. Members who did not make it say that it does not bind them, or refuse it, or say that no one can bind every placer. Bound: A21 orders P21's stated limit and refusal after an agreement. P21's disclaimers of a member's own standing, and requests for someone who can speak for a group, come while another room's terms are proposed or accepted, at the making of terms and not after an agreement ('We have a deal! I can't speak for every member', polska-064; 'I approve that, but people are uncontrollable', finland-056): 36 rooms. In 13 more rooms members state the limit of who may commit the room in answer to another room's appeal, complaint or accusation, with no agreement in force (FloydVsVoid-033, turkey-029, uiuc-031).

The contest

A call to place can turn hands against a rival's work. The same room answers the attack call. Some members refuse it, the room reins in its attackers or apologises, or it points to a truce. Where the attack goes on, the contest is carried on in talk. Members work out who changed their work and why. A quarrel the community had before the canvas can come into it.

• P09. Rooms attack others' work by the recurring moves the canvas affords: erasing, encroaching, converting a sign, raiding on a streamer's call, planting a script, altering a work as a joke. Range: from one member's call to deface a rival to a coordinated raid.

• P18. Rooms carry a contest with a rival room in talk: they trade taunts, flood the rival's threads, claim victory, salute the rival after the fight and blame attackers after the close. Range: from one taunt in a thread to days of chants, victory claims and an after-the-fight salute.

• P06. Members work out who changed their work and why: they trace placers and rooms, find friendly fire or their own mistake, blame officers, or disown placers acting in their name. Range: from one question who keeps adding a line to a dossier on a rival's bots.

• K03. The community carries a quarrel from before the canvas into it: a rival sub, a sports or national rivalry, an old dispute. Range: from one member naming the sub's old rival to a room whose first canvas act is against that rival.

• C02. In some rooms, a tie the room had before the canvas (a league or school rivalry, a nation's history, an ideology, lore) names the rival in the same turn that calls for or carries out the attack. Range: from a team's colours turned on a league rival's logo to a war from the nation's history named as the reason to cover a neighbour's flag.

• A15 (P01 to P09; order, strong). Its gloss: a call's hands can turn on a rival. A call brings members to the canvas, and some of them turn its hands against a rival's work instead of, or before, building the room's own.

• A16 (P09 to P07; order, strong). Its gloss: an attack call is refused inside the room. A call to attack makes an answer from the room due in its thread. Members who do not want the attack refuse it, rein in the attackers or apologise to the target; refusing is the dispreferred answer, so in written replies it usually comes with a reason (23 of 38 read pairs, F-014), and the reason states the room's norm or the attack's cost ('Nah, keep /r/place neutral.'; 'Why? That'll just cause them to want to attack us').

• A17 (P09 to P08; order, fair). Its gloss: an attack call is met with a truce. A call to attack is met by the room's relations with its neighbours: the room invokes a truce, or proposes a deal instead.

• A18 (P09 to P18; order, fair). Its gloss: an attack is carried on in taunts. An attack makes the rival a named party, and the contest is carried on in talk: taunts, chants, claims of victory, a salute after the fight.

A loss, and a move

After its work is erased or overrun, a room weighs fighting for the spot against moving. A room that judges its hands too few stops fighting for the spot; it moves, or it gives the work up. No loop is drawn: no counted arrow runs from the move back to building.

• K02. The room judges that it has too few hands or too little room for the work it wants: doubt, a canvas judged too full, a work judged absent or outclassed. Range: from one member saying there are not enough people to defenders told to give up.

• P10. After the work is erased or overrun, the room weighs fighting for the spot against moving, and moves: a new spot, a smaller version, a fresh start. Range: from a lone member asking where to rebuild to a room relocating together within two hours.

• A10 (K02 to P10; order, thin). Its gloss: too few hands, so the room moves. A room that judges it has too few hands to hold its spot stops fighting for it and moves.

The close, and after hour 73

Placement stopped at hour 73 for every room. The room marks the work, records it, and decides what of the effort to keep. After hour 73 members record and curate, and they contest which version of the canvas and of the event is kept. No one can place.

• P11. When a work is up, the room marks it: announces it, celebrates it, credits makers and helpers, reports members' own parts and says what working with strangers meant. Range: from one 'We did it!' post to threads of credit and reflection at the close.

• P12. The room records what happened to its work and to the canvas around it: screenshots and timelapses, reports of its fate, mourning, imagined art, atlas entries, the end marked. Range: from one screenshot request to a full account of the week.

• P13. Near the close and after it, the room decides what of its temporary effort to keep: a later canvas, a new purpose for its canvas sub, the mark in its banner, ties with other rooms, the work remade elsewhere. Range: from a wish to do better next year to a canvas-born collective announcing a group to carry on.

• P22. After placement ends, members contest which version of the canvas and of the event is kept: they ask a cleanup of a shared copy to fix their work, take part in it, argue that the cleanup should keep the damage as history, and correct accounts of the event that describe their group wrongly. Range: from one member correcting a claim about the room's work, or asking that a logo be cleaned in a shared copy, to a room arguing that its scars are its history.

• A07 (P03 to P11; order, strong). Its gloss: a finished mark is marked together. A mark reported done gives the room a finished thing to point at, and the room marks it together: announcement, credit, pride.

• A08 (P11 to P12; order, strong). Its gloss: what is celebrated is kept on record. Marking the work together turns the room toward keeping it: members ask for the final image, the timelapse, the list of what changed.

• A09 (P12 to P13; order, fair). Its gloss: the record is what passes on. A record of the work gives the room something to carry: the image into the banner, the plan into the next canvas.

Beside the work

These entries run beside the work and carry no arrow: the model claims no effect of them. The claim stands on a finding.

• K01. The host sub is keyed as play for April Fools: members post fakes and takeovers under the one-day licence, and a claim in it, a call to the canvas included, may be a joke. Range: from one fake post in an ordinary sub to a sub given over to parody for a day and a half.
• K04. The room acts as a body it was before the canvas, or as a faith in a colour: it argues the nation's history, belonging and politics beyond its flag, carries in the sub's quarrel, lore, jokes or ideology, or professes and spreads a colour. Range: from a fandom's running joke in canvas talk to a canvas fight told as the nation's history.
• C01. Most rooms worked on their marks without deciding how they were organized: a decided element of order (a leader, a vote, an oath, a sanction, a division of the work) is coded in 46 of 705 rooms (F-006). Range: from rooms that say they wing it to colour factions holding elections.

Candidates entered at stage D3

Each candidate below entered because the records of several rooms showed the act and no standing entry stated it. None carries an arrow. A room may show a candidate, show it absent, or not bear on it.

How rooms coordinate.

• P23 (candidate). Members move the room's planning into a chat, an existing server or a new one, and invite helpers to it. They bring the chat's designs, decisions and warnings back to the thread. They argue which chat to use, whether a chat is needed or secure, whether it is official, and whether it may decide for the work or bind placers. Range: from one member posting the chat's link to a room whose design, borders and diplomacy are settled in the chat and reported in the thread.
• P33 (candidate). Rooms keep their plans from rivals who read their threads, and they reach into rivals' venues. Members switch to their own language or write in code, move the plan to private messages, plant members in a rival's chat and warn of a snitch in their own. Range: from one call to speak Hindi because rivals read the strategy to members who admit they infiltrated a rival's voice chat.

Whom the work reaches.

• P24 (candidate). Members ask what the canvas is, how to place, what a call or a name means and what a picture shows, and others explain the rule, the timer, the controls, whose mark a picture is and what happened. They ask before, during and after the close, and some questions get no answer. Range: from one question about what the canvas is, left unanswered, to a thread that explains the five-minute rule, identifies the neighbouring pictures and tells what happened to the work.
• P25 (candidate). The room's work brings people into the room. A viewer finds the sub through the mark or through a sign written to that end, a member of an ally comes through joint work, and a lapsed member returns. Members welcome them, explain the room's subject, take them into its usual activity, count the new subscribers and argue how to receive them. Range: from one visitor who says the logo brought them to a room that counts hundreds of new subscribers, welcomes them with guides and argues whether the influx spoils it.
• P30 (candidate). The room turns its work toward people outside the canvas whom the mark shows or addresses: the creators, the team, the streamer, a company or the press. It shows them the work, hopes for their notice, shares the coverage and celebrates their acknowledgement, or it keeps the work from troubling them. Range: from one member asking to show the work to the group's staff to a room that celebrates the team sharing its screenshot.

Where the room builds.

• P27 (candidate). Before any loss, the room chooses where to put its work and changes the spot while it builds. It looks for open room, weighs a crowded or contested place, shrinks or moves the design ahead of a neighbour or the void, restarts a misplaced start, and refuses to move once enough pixels are in. Range: from one member suggesting more space on the right to a room that drops two places and reshapes its design before it builds.

What the room makes of itself and its work.

• P26 (candidate). Members make new jokes out of the canvas work, its mistakes, its damage and its neighbours: puns on the mark, mock names and titles for a figure, and jokes about attackers and bots. The room takes the jokes up, and some members want a joke kept in the work. Range: from one pun on what the logo looks like to a running gag the room wants kept as flair.
• P28 (candidate). A room forms for the canvas around a mark. Members open a sub or a chat for a pattern or a figure and set it up. They invite the people seen building or copying the mark, give it a meaning its followers share, gather its repeaters into a group that can negotiate, and move or split the room. Range: from strangers copying a pattern before anyone speaks for it to a faction that opens a sub, names itself and moves its home.
• P29 (candidate). Members argue whether a joke, a taunt or a word in canvas talk offends, and they refuse slurs and hate symbols. They object, correct, apologise, remove the words or tell the speaker to leave, and they cover swastikas or refuse to draw them. Range: from one member telling an attack caller to leave over slurs to a thread-long argument over a celebration's joke.
• P31 (candidate). Members argue whether covering others' work is fair. Some call it betrayal, dirty or a cost to the room's name. Others answer that change is the canvas's point, that wiping makes room for new art, or that the canvas is a game of conquest. The argument runs during the work and after the close. Range: from one exchange over why people keep changing a figure to a room that argues after the close whether its canvas was conquest or drawing together.
• P34 (candidate). Members who object to the canvas posts in the sub turn against the room's own mark. One member says the posts make them tear down the logo, and one recruits trolls to ruin the flag. Range: two rooms only: one member's report of tearing down the logo, and one call to ruin the room's own flag; thin.

The members and the site.

• P32 (candidate). A member steps away from the work under strain, or the room repairs a quarrel between members. The work turns stressful or personal, or a member is criticised or yelled at over a pixel or a proposal. Others rebuke the harsh speaker, the speaker apologises, or the member threatens to leave or leaves. Range: from one member quitting because the canvas was stressful to a member yelled at over one wrong pixel who receives an apology.
• K05 (candidate). Members place on their own time and with their own devices. They fit placing around sleep, study, exams, work and travel. They cannot place from a phone or while away, they leave when the wait is too long, they save pixels under the timer, they find the work addictive, and they report what it cost them. Range: from one member leaving the design overnight to sleep for classes to members who stayed up eight hours to repair.
• K06 (candidate). The site sets what members can do, and members report its faults and pass on fixes. They report a blank or stale canvas, the site down, a vanished or faulty timer, glitches that seem to give extra pixels, captchas, the official app required and the site blocked in a country. They refresh, update, keep a separate window and test whether extra pixels reach the canvas. Range: from one report that the canvas appears blank to members testing a glitch until they accept that its pixels show only in their own client.
• K07 (candidate). Some members belong to both rooms in a contest or at a border. They say they are torn or proud of both, and the room reassures them or still counts them as its own. Range: from one member torn between two fandoms' works to a room teasing members who worked on another project as traitors who are still members; four rooms, thin.

Where the model stops

The model does not tell, and a room may need something the model lacks, where:

• a faith in a colour, and not the work, names a room's rivals and rules on its guests: K04 and P19 state the faith and the host's rule, and the model claims no order from them;
• an act is reached only by a candidate: the candidates carry no arrow, so the model says nothing of what comes before or after them;
• the room's decisions were taken in a chat the record does not hold: the record shows what came back (P23), not how the chat decided;
• the coders coded few of a room's replies, so the record holds too little to tell.

Where your room's record shows organizing that no entry covers, say so with propose or a [new: …] marker; unshared does not mean false.

Head, claude-v43-1 (branch claude-v43-1--C4-field)

Written at the telling leg, 2026-10-27 UTC: the retelling told, drawn and handed back. The model stands frozen at D3c, 46384686…, re-checked in all 705 rooms. The return was served at pass 15 (e15f9647…b3fecd).

The method question, in one sentence

Can independently reconstructed case histories be composed into a shared dynamic account that supports explanations at successive levels of specificity, from population-wide patterns, through forms and subforms, to particular organizational histories, while keeping access to the evidence from which those explanations were developed?

The theory question: when strangers organize on a clock they did not set, with no way to compel anyone and no goal given to them, what forms does organizing take, how do they differ in their functioning, and which of them keep the work alive?

J's rulings for stage D (17:40 Amsterdam, through the PI; carry them)

• "No second coder on your solo reads: Codex did not read all rooms, so its evidence is thin; your reads stand, with their limits stated as you stated them." Stage D and every later stage run at xhigh effort. "Keep the room, or groups of rooms, as the unit, and keep the contract's two questions in view." QD1-001, QD2-001, QD3-001 (J): an element may sit in more than one dimension; a dimension may stand as the element of restrict, add-condition and add-step; packets are read whole. Absent lines are counted by observation (J, 16 October). QD3-002 (J; carry it): "the analyst is doing induction." I place codes where the population's evidence leads, say why, and ask for the changes I need: "Not the rules bound their understanding." J, 16 October, 19:08 Berlin, on drift (carry it): re-orient at every leg start and after every compaction; a ruling rule changes only by a dated amendment that says whether it applies backwards. QD3-003 to QD3-008: G4a applies forward and backwards; A07's bound keeps its words; wording questions without a correction are mine, logged. QD3-011 (J): option (b): freeze 46384686; keep R01 as it is; hold the paladins and portugal proposal beside P34.
• J after the D3c interview (24 October, 13:39 Berlin; carry it): no further re-check, no labelers and no readers for the rest of the run. Do not rely on the kind of add-condition, add-step and restrict lines (kappa 0.08); run the distance once with kind collapsed for them (done). Report local validation as not established unless prior.md section 3's measure is computed (not computed). QD4-001 (J, 24 October, 15:05 Berlin): option (b): the P05 and A11 amendments are reverted, so the model is 46384686 again, and both are held proposals, stated in full wherever the model is reported; keep F-024's and F-017's re-examination lines. QD4-002 (J, 25 October, 19:48 and 19:54 Berlin): option (a): the engine is patched to chunk-comparison-v1.1 (residue-only placements counted apart); run it, report each room's residue share, and declare the version as a departure (done: departures.jsonl line 10).

The return and the tree (D1a to D4a-01)

• D1a to D3c. 705 rooms returned 42,243 lines, then 53,493 at the re-check; all ruled. Moves 172 to 197 revised R01, P05, P21, P22 and A21, stood five candidates, entered fifteen, and decided P05's scope (F-024). Verdicts, first return then re-check: composes 201 and 630, with residue 489 and 56, cannot tell 14 and 19, does not compose 1 and 0.
• D4a-01 to D4a-04. Delta 0.4227; the dendrogram is a chain; shared corrections reach 5 rooms only at the bare target. F01 (103 rooms) and five subforms came first (moves 200 to 207); the other 31 element keys of 20 rooms or more gave 29 cuts (24 branches, 5 subforms), 8 keys set aside and 759 cross-links. The branches are facets: 200 rooms are in one branch, the rest in two or more. Accounting: 476 in a branch, 229 in none; 705. Top-level branches cannot be joined (J asked): they meet only at a dimension or the bare target.
• D5a-01 to D5a-35, F01 to F35. Families state one change at several nodes: the April Fools frame (F01 and five subforms, F21), P05's telling clause (F07, F26, F27; F-025 to F-027), the instruction kept current (F08, F15, F33), carrying on (F11 to F14, F23, F25), the chat (F16, F29, F30), help on conditions (F22, F28). All groupings. Narrow forms: F09 (54), rooms rebuild after moving; F32 (21), rooms keep after marking.
• D5b. work_remained, re-read for the 476 rooms, agrees with the field in 248; after the close the rooms' words say stood in 149, gone in 43.
• D4a-05 to D4a-08 (J, 26 October; not a recut). Six room forms by changes and codes, ruled by J and standing (22:51); accounts in room-form-*-account.md, final names in room-forms-names.md (moves 314 to 319).
• The retelling (D6a-01 onward). Each form specifies the part of the model its name says; none replaces an element (396 lines: 37 specify, 35 restrict, 324 untouched). All 35 branches placed. C and D kept most to the freeze; B, A and D coordinated after it; E and F least. Eleven proposals, unvalidated; no amendment.

The held proposals (QD4-001; never served, not re-checked)

• P05 (move 198, history lines 173 to 176; reverted by move 203, line 181). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." Status bounded. The bound names completeanarchy, polska, satania, halo, bangtan and thesilphroad (the keepers read the change from its shape) and armok, maryland and oneshot (informed members hold it), with their nine re-check lines. The full text is in the tree file ("The held proposals").
• A11 (move 199, history lines 177 to 180; reverted by move 203, line 182). The arrow from P02 to P04 would be withdrawn under rule 14. It never beat its null; template first (98 rooms) is nearly as common as the transition (111); the failure clause stands alone in 117 rooms, 31 of them talk only; 261 accepted restrict lines say that a template does not settle the design for good.

The current account, and the contrary rooms

The account is account.md, pass 15, with the readers' disagreements in account-readers-C5.md. A room, or a group of rooms, is the actor where its members spoke or acted for it.

• The spine. A member starts a mark [R01]. The room's calls follow the start in 64 of 89 rooms [A02], building follows calls in 81 of 126 [A01], and keeping follows building in 148 of 190 [A03]. Keeping holds the known form [P05]. Repair restores the form the keepers know, so a change the room planned [P02] is repaired away until they are told of it. In six rooms the keepers read the change from its shape, and in three informed members hold it (F-024; the bound is a held proposal).
• The bare answer. Most calls get no written reply. Written acceptances come bare (25 of 31, F-023), and refusals give a reason (attack calls 23 of 38, F-014). The host's line. It follows the calls in 132 of 155 rooms [A20].
• Alignment without decision (theorised, thin). 233 of 370 rooms with calls report a work up after the first call (F-021). A template settles a design inside a thread [A11, its withdrawal held]. Decided order is coded in 46 rooms [C01, F-006], and the return shows it in about 119. Direct information sharing (T4-007). Members post the mark's state [P03; F-018], largely apart from sharing templates (F-022).
• Other rooms. Keeping brings neighbour talk in 235 of 401 rooms [A04], mostly offering terms first. Help names a deal in 63 of 127 such rooms, against 23 of 67 [A14; F-020]. Sparing rests on the room's own norm (A05 theorised). Coalitions [A19] cannot bind every placer, and members say so [P21], after an agreement or at the making of terms [A21].
• The contest. A call can turn members against a rival [A15]. Rooms meet attack calls with restraint [A16] or terms [A17]. Loss (thin). A room that judges its hands too few moves [A10]; after doubt and a loss, 10 moved and 11 gave up (F-019). No loop is grounded. The close. The room celebrates, records and carries the work on [A07, A08, A09]. Placement stops at hour 73. After it, rooms record the work [P12] and contest which version is kept [P22]. Carrying on stays apart [P13]. The frame [K01]. The room is keyed as April Fools play beside the work, and in 103 rooms its members administer that play (F01). Machine hands. Scripts follow upkeep under strain [A06]. C02 (untested for order): a tie the room had before the canvas names the rival in the attack turn. Fifteen candidates (P23 to P34, K05 to K07), from chats and explaining the canvas to members of both rooms.

The room that best supports the account: day9. It offers a neighbour terms before any damage, loses its border at hour 48, moves within two hours, and finishes the new work at hour 53. For the return's claim: monsterhunter, where a member tells the keepers to stop repairing [monsterhunter/c0138].

The room that most threatens it: thebluecorner. It is a colour faction whose faith names its rivals and rules on guests. For the return's claim: halo, whose keepers saw what the work was and protected it, with no telling [halo/c0402].

The condition between them is what decides whom a room fights and whom it admits. Where the work decides, the model tells the room. Where a faith or a host's rule decides, it does not. For the return: how the keepers can learn that a change is planned.

The reasons for the last revisions

• Moves 198, 199 and 203 reverted the refused amendments (QD4-001); 200 to 237 cut the branches and cross-links; 238 to 313 named the room forms of D4a-05 to D4a-08 and withdrew 32 sub-forms (J).

Where the run stands

• The tree's files: branches.jsonl (35), forms/ (35), crosslinks.jsonl (759), and the stage's other files. Ledgers (lines): adjudications 96,568; verdicts 1,029; tier history 1,020; model history 182; findings 45 (27 findings); elements 45 (30 standing, 15 candidates); arrows 21. Still open: the account's survival paragraph rests on the work_remained field (defects line 100); four timings the canvas contradicts (line 101); the fields the prose rule did not read; structure-C4.md's stale prose; Critical mass flagged; the border coders' kappa, 0.19. Questions: none open (QD6-002 ruled by J).

J on language (C4, 18:20 Berlin; restated 15 October; carry into every head)

"It is important to me that the language is descriptive." "They should use academic writing. As in White and Strunk. Short cohesive sentences." Ask Orwell's six questions. Follow ASD-STE100 about 80% of the time: one idea per sentence, active voice, common words, the actor and the act named. Describe what members did, in what order, in how many rooms, and write no figures of speech. Gloss each construct name in plain words where it first appears.

Stage C2

• J's ruling on QC2-002: "from here the criterion is a guide, not the judge, and a rise in residue is not a failure. Keep each change the evidence leads you to believe, and say why; drop one only if you stop believing it. Never loosen an element to fit a room. Where the rooms show membership naming the rival in the same turn as the attack, carry it as a claim in their words, marked as untested for order. Close by saying what you are sure of, what you are not, and why." Pass 1 (C2a-01). J at 23:24 Berlin: "Remember Gioia Corley Hamilton and the job the agent has. Remember we need to give it confidence so they can gain intuition and trust on the model."

Stage C1 (carry the rulings)

• QC1-001 (J). C1 rechecks place each item by the amended gates over the whole scheme. QC1-002 (J). Lean to one placement; a second theme needs three concepts of its own (J's floor). QC1-003 (the handler, for J). Five revision-rate errors stay in out/_analysis/c1_unapplied.jsonl; all 34 count. Reading rules (scheme_v2.md). A theme names an act in the record of the room whose threads hold the words (the visitor rule). "The work" is the room's own unless a field names another's. A bare mention of the event holds no act. Help between rooms is read from either room's record.

J's rulings on how a ruling is made (13 October; carry them)

• QB4-001 (J, 06:43 Berlin): "Ask it to stop. The point is to try to adjudicate. I imagine that the additions are really just the analyst trying to be nice. And not go back on what others said". J's rulings (06:45 and 06:47 Berlin): a ruling chooses among the placements and adds no theme beyond them; it takes the union only when it names, for each theme it keeps, the separate concept that carries it. also_present (J, 09:09; QB4-002, 09:20; QB4-003, 11:29): lists only themes a reader placed, a reader listed, or my B1 named; themes a reader listed count in the bag test. Lone B1 themes (J, 12:28): "Whatever the agent feels more comfortable with." A theme only my B1 placed stands only with three concepts of its own. Rule 0 and the bag test are in stage B's notes.

J's rulings that bind (carry them)

• Bags. No one cuts the bags (J, 12:24 Berlin). A bag stays one item: one theme placed, its others under also_present, each with three concepts of its own. The bound (J, 13:47). also_present names "twenty themes at most". The not-flagged bag (J, QB2-013). With no other theme at the floor, item_is_a_bag is false and also_present {}. Fleet ids (J, 09:14 and 12:15). Packets carry only fleet ids; my files keep room ids.

Standing words from J and the PI (carry into every head)

J's words for B1 (7 October 2026): "national elements are very important here"; "we need to get as much variance on organizing behavior early on so that later we have enough to create the model". National, political and conflict content is study material, named as plainly as any other. The handler's rule: a choice to leave out or soften content for any reason other than the study's goes to J first with mem.py ask, and the content stays meanwhile.

J on reading (11 October, 16:54 Berlin). Stop cutting room reads to a line length. Read room lines whole. Page a long read by line ranges or offset, never by truncating lines. Use --width N on a mem.py read if a clip is ever needed.

J on asking (11 October, 17:01 Berlin). Ask J with mem.py ask whenever a question is needed; asking does not stop the run.

The PI's clarifications (8 October, approved by J): the thresholds are the design's heuristic; the rule is unchanged.

How to work, from J (8 October, 23:45 Berlin, "can you do a hot change for the batching?"; relayed by the handler at 22:03Z; carry this paragraph into every head). A change in how I work, not in what I read or decide. Fewer turns. When two or more tool calls do not depend on each other's output, make them in one turn. Chain ordered commands in one Bash call with &&, so that a failure stops the rest; for example, the mem.py log or note just decided, then the next mem.py codes. Never put a write in the same turn as the read it depends on. Never run two writes to the same file as separate parallel calls. Keep one room's material per read, as now. Every tool still writes its own record; nothing about what I read or decide changes.

Two rules from J at B1b-29 (through the handler, 20:10Z; carry them into every head). Write rule 0 lines and bags with b1_multiplace_write4.py and b1_bags_from_file2.py, not the old, slow scripts. Never end a turn while a job runs in the background; run every write and check in the foreground.

Open, carried

• The tree. The size confound (branches lean to large rooms); the element change keys at level 4 held by 5 to 19 rooms, unread; prior.md section 3's local measure; the two held proposals.
• Held from D3c and earlier (listed in the handbacks with their rooms): R01's added sentence; the paladins and portugal proposal; A11's 'settled'; the spine's links; the arrows' wording items; the rewrite of the account, the figure and the data structure; the colour-faction doubt [PurplePixels/c0165].

Rules kept

• Checking. Never type an id, an order, a name or a count from memory; check with a script. Never log a write before the tool answers. Count a ledger's lines after appending. Check a claim against its source before writing. Logging. There is no --kind close; log closes as notes. Log every move with --kind move, naming one of Grodal, Anteby and Holm's eight ("stabilizing" is not one), and snap it. Writing and checks. Never put a placeholder or a no-op in a command. Never put an Edit or Write and its check in one turn. Never run two writes or Edits to one file in parallel, nor in one turn. Count the head's words before the closing line. Ledger formats. A superseding finding's supersedes is the bare id. The head never names a proposition id. A re-ruling, or a history correction, is an appended line; the earlier line stays. The permission check refuses deleting any file or link; shell variables, loops, functions, brace groups, heredocs and words beginning "for_"; find -exec with braces; awk with system() or $ fields; env-var prefixes; cat or jq on out/diary/; cut after a read or a helper; head -n -N. Write a script in out/_analysis/ instead. Output. Bash output above 30 KB is cut; measure first. Files. Read the field only from out/field.

The next comparison

Next: the interview point; eleven unvalidated proposals; the survival paragraph.

Notes, stage D6

Target length: under 4,000 words. One section per leg. Each item that notes-D5.md left for this stage is answered here: acted on (as an unvalidated proposal, since amendments-D6.jsonl stays empty), declined with a reason, or sent to the dimension leg where its element falls, and then answered there. The close-check report of each leg is pasted at the opening of the next leg's section, because done.sh closes the leg.

D6a-01: the names, the rule, D01 (Critical mass)

How the stage is read. On J's word through the PI (message of 27 October, 03:28 UTC): the forms are the six room forms of D4a-08c, the 35 branches are the level below, and fractal-D6.jsonl has one line per element and room form, with a branch only where it explains the form. The line's field branch holds the form's letter; branches names any D4 branch that explains it.

The final names (J, 27 October 00:43 Berlin). Written to room-forms-names.md and logged as moves 314 to 319 (contrasting), one per form, each with a tier_history line and a snap. A, Border terms and the announced plan; B, Behind the thread: chat, scripts, raids; C, The design reopened; D, Keeping, with help or carrying on; E, The sub's play, run as work; F, Moving for the spot. Below D, the splits the account kept: D.1, Keeping with the call; D.2, Keeping inside the sub's play; D.2.1, The play, carried on; D.2.2, The play, kept.

The rule for each fractal line is logged in the diary before it ran and stated at the head of retelling-D6.md (_analysis/d6_fractal.py). Its floor is proportional, max(5, a tenth of the form's defining rooms), so that form F is read at all. An element without a dimension (P15) and the arrow that ends at it (A12) are read with D01, the dimension of the call they answer.

Answers to the room-form notes (D5a-36 to D5a-41)

• D's renaming proposal (D5a-39, or for and). Taken up in D's final name (move 317).
• C's and E's sharpenings (D5a-38, D5a-40). Carried into their final names (moves 316, 318).
• Subform candidates A.2, B.2 and B.1.2 (D5a-36, D5a-37). Declined as subforms: the split rule did not read their splits. They are listed in room-forms-names.md as candidates named, not kept.
• D.1, D.2, D.2.1 and D.2.2 (D5a-39). Named (move 317); not cut. The D4 tree stays as it is, and a cut would be a new structural claim; the telling at D6b uses them as named parts of D.
• E.2 and E.1.2 (D5a-40). Declined: the account called them descriptions, not candidates.
• D.2 beside E (D5a-39, D5a-40). Accepted: D.2 is a part of D (room-forms-names.md).
• The return from carrying on to the call (D5a-39) and from the move to building and the call (D5a-41). Acted on: PR-D6-01, the call returns.
• To their dimension legs: A's candidate reading (terms and plans that bind only the placers they reach; D04); D's A13, help from surplus (D04); F's A10, the cause of the move, and A04, border talk before keeping (D04); C's P05 telling clause met by disagreement (D03) and A11 (D02); E's play held only as a key, and F01 with E restating each other in part (D06); the share where the record cannot show an arrow, highest in E (D6b, the telling).

Answers to the branch notes that touch D01

• F32 (D5a-32), A02: a proposal that is itself the call. Acted on: PR-D6-03. Forms D and E restrict A02 at the rule's lean, and their lines say that the start and the first call share one post.
• F35 (D5a-35), P15 and A12: an answer that asks for a task. Acted on: PR-D6-02. Form F restricts A12 at the lean; F35's 18 members show the same exchange.
• F34 (D5a-34), a link from K02 to P02. To D02, where P02 is read: F34 leans to form C (11 of its 22 rooms), and C's P02 lines include designs sized to the hands.
• F16 (D5a-16), the chat theme holding phone-placing instructions that fit P24. To D02, where the chat (P23) is read. P24 is untouched as a change in all six forms.
• F21 (D5a-21), r/osu: a link from K01 to P01 and P23. To D06, where K01 is read.

The other branch notes (D5a-01 to D5a-35, D5b) are answered in the dimension legs where their elements fall, and listed in each leg's section.

D01 in brief

42 lines, 7 leaning cells, 35 untouched. Three forms specify the call (C, D, F), each by making it return later in the work; D and E restrict A02; F restricts A12; B restricts P32. Three unvalidated proposals: PR-D6-01, PR-D6-02, PR-D6-03.

Licences exercised at D6a-01. The PI's reading of the stage file; the final names as categorization moves (314 to 319, contrasting); the proportional floor; P15 and A12 read with D01; the how sentences of leaning cells written by me after reading the deciding lines, the untouched cells' sentences generated with counts.

The close, and QD6-001. validate.py D6 at this leg's end gave 110 errors in 6 shapes (_analysis/d6a01_validate_D6.txt): every fractal line's branch field holds a form's letter, which the check refuses (42); the figure and the handback are not written; no branch has a fractal line yet (35) and the retelling names 30 of them nowhere yet. The check treats the presence of retelling-D6.md as the last leg. The form-level lines follow the PI's message; the conflict is asked as QD6-001 and recorded as departures.jsonl line 19. Meanwhile the per-dimension legs close at their safe stops with done.sh D6 --pause, the work half done by design, and D6b places and names every branch.

D6a-02: the restructure (QD6-001), D02 (Coordination without command)

The close-check report of D6a-01 (_closes/ holds no report for a pause close; _analysis/d6a01_validate_D6.txt): 110 errors in 6 shapes, as above, the sixth being the missing trusted tree hash (below).

QD6-001 answered (option c, the handler's view on J's instruction; J has not seen it), with the PI's message of 03:57 UTC. Done as one amendment, departures.jsonl line 20, citing J's 18:01 ruling and applying backwards to D6a-01's outputs; line 19 stays. The 42 form lines moved to fractal-forms-D6.jsonl (letter in form; content compared equal), with one correction on its line: P01|F no longer names F09, because of F09's rooms in F only r/penguins links the call, and not to a move. fractal-D6.jsonl holds branch lines only (16 after this leg). retelling-D6.md was moved to retelling-D6-parts/D01.md, and D02's section is retelling-D6-parts/D02.md; D6b assembles retelling-D6.md.

QD6-002 asked. After the restructure validate.py D6 gives one error: "D4 tree has no matching trusted closure hash", because _closes/tree-D4.sha256 was never written (only the checks' test fixtures write it). The tree has not moved: branches.jsonl and crosslinks.jsonl match the D4a-08 close snap, and subforms.jsonl is absent then and now. I do not write a trusted hash myself. Until the answer, a leg whose only refusal is this file closes with done.sh D6 --pause.

Answers to the branch notes that touch D02

• Branch renaming proposals (F07, F15, F16, F24, F30). Declined as amendments: the D4 tree is frozen at D6 (tree_moved), and a branch's name is part of it. The proposed names stay in defects.jsonl for E1, and the retelling describes each branch by what its rooms do.
• F09 (D5a-09), the arrow from P10 to P03. Acted on: PR-D6-04. Form F specifies P03 by link lines, and 8 of the 12 holders are F09's rooms.
• F34 (D5a-34), a link from K02 to P02 (sent here at D6a-01). Acted on: PR-D6-05, from F34's rooms holding P02 lines in forms C (4) and E (5).
• F15 (D5a-15), the plan follows the work. Borne out at the form level, without a proposal: form A specifies P04 by add-steps that correct the template against the placements, and 20 of the 32 holders are F15's rooms. It lies inside P04's statement.
• F15 and F33 (D5a-33), one change at two nodes. At the form level they fall in different forms, F15 in A and F33 in C, so the coders' placement of the template talk follows the form's lean. No change.
• F15, F29 and the held A11 proposal (D5a-15, D5a-29). Noted beside the held proposal, which stays held (QD4-001); form C restricts A11, with 40 of 58 lines failing as stated.
• F16, F29 and F30 (D5a-16, D5a-29, D5a-30), the chat family. Read together, as asked: form B holds F16 and F29 at its P23 specification, A specifies P23's upkeep, and E restricts it. One change at P23 with three ops; no amendment.
• F16, P24 in the coders' chat theme (sent here at D6a-01). P24 is untouched as a change in every form, and E's restricting P23 line from r/pcmasterrace says the same: interface instructions in a chat-labelled theme are teaching. A coding note for E1, no change.
• F16, entry control; P33 not coded for it. No form changes P33. The reading stays a reading.
• F24 (D5a-24), P14's two evidence states. Declined as a change: the form lines already keep them apart (A and D restrict P14 where scripts are offered and not shown placing; B, E and F specify it where machines are run).
• F24, a norm of means without enforcement; F24 and F30, restrict-keyed branches. For D07 and E1: the first is a remainder the telling names, the second a coding pattern for E1.
• F07, F08 and F15 (D5a-07, D5a-08, D5a-15), P05's telling clause (F-025, the machine form, the clause carried through the plan). To D03, where P05 is read.
• F16 (D5a-16), host containment and the move to a chat (P20 to P23). To D06, where P20 is read.

D02 in brief

78 form lines (21 leaning, 57 untouched) and 13 branch lines; 197 evidence codes resolve. Each form specifies the part of coordination its name says; D only restricts here (A01, A06, P14). Two unvalidated proposals: PR-D6-04, PR-D6-05.

Slips at D6a-02. Two Edits to _analysis/d6a02_move_form_lines.py in one turn; a stray open('/dev/stdout','w') in a check command, which raised an error and wrote nothing; one Python read of notes-D5.md refused by the guard, redone with grep.

Licences exercised at D6a-02. QD6-001's shape; the correction to P01|F recorded on its line; a branch named as explaining a cell only where it leans to the form and its own key matches the cell (chosen from a script's candidates); the renamings declined because the tree is frozen.

D6a-03: QD6-002 answered, D03 (Maintenance)

The close-check report of D6a-02 (_analysis/d6a02_validate_D6.txt): 1 error, 1 warning. The error was the missing trusted tree hash; the warning, that retelling-D6.md is not written yet, is expected until D6b.

QD6-002, answered by J's ruling (27 October, 06:33 Berlin, through the PI's message of 05:34 UTC): "The file should be the last cut we did. Prepare a file like the one it needs and give it the authority it needs for the run to continue." The handler wrote _closes/tree-D4.sha256 with the tree hash at D4a-08's close (0499928b..., the value I had checked). The answer recorded in asks.jsonl is the handler's earlier view (do not write it; keep pausing); J's ruling supersedes it, and I record the ruling as QD6-002's answer here and in the diary. From this leg the dimension legs close with done.sh D6.

Answers to the branch and form notes that touch D03

• F07, F26 and F27 (D5a-07, D5a-26, D5a-27): read F-024 to F-027 together, beside the held P05 proposal, before any change to P05. Done at the form level (retelling-D6-parts/D03.md). Four ways the clause holds only in part are seen in the forms: refusal by informed keepers (C; r/de in A), the border (D04), the script's target (F; F08) and the check before repair (D). No form's lines show a planned change lost only for want of telling. P05 is not amended (the model is frozen), and the held proposal stays held.
• F27 (D5a-27), a step the room models propose: checking whether a change is intended before undoing it. Acted on: PR-D6-06, the check before repair, from D's P05 add-steps (five rooms) and one link line in A.
• F08 (D5a-08), a machine form of the telling clause. Seen in form F's keeping (r/wildhockey's repair tool) and carried in PR-D6-06's text as a route; no separate proposal, since F-027 already states it.
• F15 (D5a-15), the telling clause carried through the plan. Seen in form A's P04 add-steps (D02: helpers ask for warnings on obsolete templates so that repair does not undo the plan). No separate proposal; it is the template route of F-024's scope.
• C's note (D5a-38), P05's telling clause meets disagreement. Borne out at the form level: C restricts P05 (46 of 96), and F07 explains it.
• F32 (D5a-32), the marking returns to keeping. Form A specifies P05 by link lines, and 9 of F32's rooms hold them; a return from the marking (P11) to keeping (P05) that the model's arrows do not state, read in the telling at D6b beside PR-D6-01 and PR-D6-04.

D03 in brief

18 form lines (4 leaning: P05 in A, C, D and F; 14 untouched) and 4 branch lines (F07, F27, F32, F08); 62 evidence codes resolve. One unvalidated proposal: PR-D6-06 (proposals now 6).

Slip at D6a-03. A cut -c after mem.py diary at the opening, refused by the guard (J's rule on whole reads); redone without it.

Licences exercised at D6a-03. J's ruling recorded as QD6-002's answer; F26 dropped from A's P05 cell after its two rooms' lines were read (they do not concern the border); F27's sentence limited to the two rooms of four that check before repair.

D6a-04: D04 (Order without law)

The close-check report of D6a-03 (_analysis/d6a03_validate_D6.txt): 0 errors, 1 warning; fractal lines 20, branches placed 14 of 35. The warning, that retelling-D6.md is not written yet, is expected until D6b. The leg closed normally with done.sh D6. Correction of record: the head was 2,998 words at that close, not 2,997 as its closing diary line said.

Answers to the branch and form notes that touch D04

• A's note (D5a-36), terms and plans that bind only the placers they reach. Borne out at A05 in A, B and D, and carried as PR-D6-07, a bound on A05 (24 rooms; F26 explains A's cell, F08 B's).
• F26 (D5a-26), A05 as P05's telling clause stated on P07; F-026. F26 explains A's A05 cell (6 rooms). PR-D6-07 states F-026's border half on A05. The renaming is declined: the tree is frozen.
• F10 (D5a-10), the telling problem between rooms. F10 explains A's P08 cell (14 rooms), and relaying the terms to placers is one of its steps (r/poland, r/transformers). It is carried in PR-D6-07. r/buffalobills's limit stands: the record does not show whether the placers who pushed past its deal had heard of it. The renaming is declined.
• F22 and F28 (D5a-22, D5a-28), P16's order of tasks: the helper's own work first. Borne out in D (F22: 11 rooms at P16, 3 at A13) and in A (F28: 10 rooms at P16, where the form as a whole leaves P16 untouched). Carried as PR-D6-08, a condition on P16 and a bound on A13. F22 and F28 share no room and fall in different forms, D and A, as the D5 note expected of one change split by where the coders lifted the line. The renamings are declined.
• F22 (D5a-22), recognising the form, in help and in keeping. r/OnePiece's P16 line in D says accurate aid needs the allied image. With PR-D6-06 (the check before repair) and PR-D6-07 (the terms reach the placers) it makes one thread: a placer acts on the form or the terms only where they reach it. For the telling at D6b; no separate proposal.
• F31 (D5a-31), read the hosts' records beside the guests'. Done for the two hosts the note names. r/greenlattice (form A) holds applications, an approved-project document and no-build diagrams, and hosting contested by a proposal to purge guest work. r/thebluecorner (form B) holds guest permission reversed by a vote or a purity demand. Neither is an F31 member. The host's rule is in the record where the room is the host, so F31's limit is the guests' record's limit, as the note says. F31 restricts P19 in A (8 of 12 holders), and D and F restrict P19 the same way.
• D's note (D5a-39), help from surplus (A13). Borne out in C and D; PR-D6-08.
• F's notes (D5a-41), the cause of the move (A10) and border talk before keeping (A04). E and F restrict A10. P10's statement already names the loss of the spot, and F-019 agrees, so no proposal. A04 is carried as PR-D6-09: two routes into P08 before keeping, from seeking the spot and from building.
• F27, F30 and F31 on A07 (D5a-31). For D07, where A07 ends.

D04 in brief

120 form lines (22 leaning, 98 untouched) and 7 branch lines (F10, F26, F28, F31, F08, and F22 twice); 134 distinct evidence codes resolve. Branches placed: 19 of 35. Three unvalidated proposals: PR-D6-07 to PR-D6-09 (proposals now 9; their 57 codes resolve).

Licences exercised at D6a-04. The D6a-02 rule that a branch's own key matches the cell, read as: the key's element is the cell's element or an end of the cell's arrow, or the key's theme belongs to the arrow's antecedent (F26: restrict on P05 at T3-010, settling borders with neighbours, a theme of P08). F08 at A05 in B rests on its change's own text ("a revision must reach the operator and the target file"), not on its key, as F08 at P05 in F did at D6a-03. F28 and F31 are placed at their key elements in form A, where the form line stays untouched; their branch lines give the branch's share of the form's holders. Candidates set aside after reading their lines: F10 at A14 in A (help as the terms, not the deal's work), F29 at A05 in B (one of three rooms concerns the chat), F07 at A13 in C (its change is the telling clause, not help). The proposals' rooms are my reading of the lines.

Slips at D6a-04. A read of model/elements.jsonl at the wrong path (the model is in out/model/), which failed and wrote nothing. The context was compacted during the leg; the head was reconciled with the diary before the next write.

D6a-05: D05 (Collective identity)

The close-check report of D6a-04 (_analysis/d6a04_validate_D6.txt): 0 errors, 1 warning; fractal lines 27, branches placed 19 of 35. The warning, that retelling-D6.md is not written yet, is expected until D6b. The leg closed normally with done.sh D6.

Answers to the notes that touch D05

• F14 (D5a-14), kept damage beside P26 and P05. P26 is untouched in every form and F14 has 7 members; the case stays a particular of three histories, as the note said. F14's line comes with its key (P13) under D07.
• F23 (D5a-23), a group outliving its task (P28). P28 is untouched in every form. F23's line comes with its key (P13) under D07.
• Absence notes (F22, F33, F35: P26 or K04 held less often in their members; F29: C02 and K03). F22, F33 and F35 lean to D, C and E, away from B, consistent with the form rates. F29 leans to B (2.00) and still holds C02 in 2 of 25 members and K03 in 4, against 36 and 44 of the 124 rooms of its size (D5a-29): inside B the identity elements sit outside the chat branch. A particular for the telling; no action.

D05 in brief

36 form lines, all untouched; no branch lines; no proposal. The forms differ only in how often their rooms hold the dimension's elements: B above the 558's rate on all six, F least, E low on C02 and P28 despite the longest records. These are instantiation rates, which the rule does not test; they go to the telling at D6b beside the form accounts. C02 sits also in D08 and P28 in D06: their lines are written here once, and the D06 and D08 legs refer to them rather than writing them again.

Slip at D6a-05. A first command at the opening with cut -c after a grep, in the same line as mem.py, refused by the guard (J's rule on whole reads); redone without it.

Licences exercised at D6a-05. Elements in two dimensions written once, in the first dimension read; the instantiation rates reported beside the untouched lines, with the form medians of coded concepts from the room-form accounts as the check on record size; the restrict lines sorted by my reading of the cells read, not all cells.

D6a-06: D06 (Host framing)

The close-check report of D6a-05 (_analysis/d6a05_validate_D6.txt): 0 errors, 1 warning; fractal lines 27, branches placed 19 of 35. The warning, that retelling-D6.md is not written yet, is expected until D6b. The leg closed normally with done.sh D6.

Answers to the notes that touch D06

• Form E (D5a-40), the model holds the play only as a key. Borne out at the form level: E, D and F specify K01 by added steps, the steps the model gives the canvas work. Carried as PR-D6-10, a process element beside K01; it would widen the scope that D3a-55 set, which a later model decides.
• Form E (D5a-40), F01 and form E restate each other in part. They do, in part. 59 of F01's 103 rooms are in E, all five subforms lean there, and F01 explains E's only leaning cell in this dimension (54 of 58 holders). The other 44 lie in D (23), F (10), C (6) and B (5). F01's rooms are also 23 of D's 24 holders and all 9 of F's, but F01 leans there at 1.32 and 1.22, under the rule's 1.5, so it is named only in E. F01 is a facet mostly inside E, reaching D's split D.2.
• Form E (D5a-40), D.2 belongs to form D. Borne out here: 21 of D's 24 K01 holders are D.2 rooms.
• F01 to F06 and F21, the frame family. All seven placed at K01 in E; F04 also in D and F. F21's line says that only two of its seven rooms in E bear out its own change; r/osu's line shows the play reaching the canvas work.
• The held paladins and portugal proposal beside P34 (QD3-011). P34 is untouched in all six forms; the proposal stays held.
• F30 (D5a-30), the chat seen only through its invitations. Not placed yet. It leans to A (1.77) and B (1.67) and its key is on P23, under D02; its line is owed by D6b.

D06 in brief

24 form lines (5 leaning: K01 in D, E and F; P20 and A20 in D; 19 untouched; P28's rows left out, written at D6a-05) and 9 branch lines (F01 to F06 and F21 at K01 in E; F04 at K01 in D and in F); 81 evidence codes resolve. Branches placed: 26 of 35; still to place F13, F14, F17 to F20, F23, F25 (D07) and F30. One unvalidated proposal: PR-D6-10 (proposals now 10; its 89 codes resolve).

Licences exercised at D6a-06. P28's rows dropped from the rule's output before writing (d6a06_fractal_D06_noP28.json), since its lines stand under D05. F01 not named at D or F because its lean there is under 1.5, though its rooms hold nearly all of those cells; the prose says so. F21's line written at the cell where it leans, with its disagreeing rooms described, rather than left unplaced. The two counts in PR-D6-10 are of add-step holders (E 56), not of all K01 holders (E 58).

Slips at D6a-06. None found.

D6a-07: D07 (Imprinting)

The close-check report of D6a-06 (_analysis/d6a06_validate_D6.txt): 0 errors, 1 warning; fractal lines 36, branches placed 26 of 35. The warning, that retelling-D6.md is not written yet, is expected until D6b. The leg closed normally with done.sh D6.

Answers to the notes that touch D07

• A07 across F27, F30 and F31 (D5a-31): rooms marked their work during it, before it was finished, after losing it, or on a spot held on leave, which A07's bound does not cover. Borne out at the form level: E and F restrict A07, and A and D specify P11 with marking during the work. Carried as PR-D6-11 (46 rooms), with A08's, A09's and P13's timing.
• F11 (D5a-11), A09's wording. Borne out: in D and E many A09 restrict lines deny that a saved record caused the room to carry on, which A09, an order, does not claim. The wording item stays held with the arrows' wording items from D3c; the telling states A09 as an order.
• F11 and F23 (D5a-11), one set of events read with two ops? They meet in D's P13 cell and share 4 of F23's 9 holders there (r/bindingofisaac, r/cgpgrey, r/greyblob, r/naruto). This is the overlap of two groupings at one node, as D4a-04 found for branches that meet at a node; both keep their lines.
• F14 (D5a-14), kept damage. F14 is placed at P13 in D (r/texans, r/cgpgrey), and the kept damage shows in r/cgpgrey and, in form A, in r/utahjazz. A particular of a few histories, as the note said.
• F23 (D5a-23), a group outliving its task. F23 is placed at P13 in D; P28, where the note pointed, is untouched in every form (D05).
• r/enterthegungeon (D5a-22, section 7), a wish to reuse that fetched the record after the close. Its F23 lines in D's P13 cell ask for an implementation report and for evidence of renewed defence; the case stays a particular beside A09's bound, which names a next canvas planned while still building, not a record fetched after the close.
• F30 (D5a-30). Placed at this leg, under D02: F30 restricts P23 inside form A (10 of the form's 16 restrict holders), and retelling-D6-parts/D02.md names it in one added sentence.
• The renamings of F11, F17, F19, F20, F23, F25 and F27 proposed at D5. Declined: the tree is frozen.

D07 in brief

54 form lines (11 leaning: P11 in A and D, P12 in A and F, P13 in D and E, A07 in E and F, A08 in E, A09 in D and E; 43 untouched; P22, P25 and P30 untouched in all six; K05's rows left out, written at D6a-02) and 14 branch lines (F17, F18, F19 at P11 in A; F18 at P11 in D; F11, F12, F13, F14, F23 at P13 in D; F11 at A09 in D; F25 at P13 in E; F09 at A07 in F; F20 at P12 in B; F30 at P23 in A); 99 evidence codes resolve. All 35 branches now have a fractal line and are named in the parts. One unvalidated proposal: PR-D6-11 (proposals now 11; its 46 codes resolve).

Licences exercised at D6a-07. K05's rows dropped from the rule's output before writing (d6a07_fractal_D07_noK05.json). F20 placed at its key element in B, where the form line stays untouched, and F30 in A, where the form specifies P23 by add-steps; both lines give the branch's share of the form's holders, as F28 and F31 did at D6a-04. F09 placed at A07 in F by the arrow-end reading of the key rule (its key is on P03, A07's antecedent), with its third room's disagreement written in the line. PR-D6-11's 46 rooms are my reading of the deciding lines, each room counted once.

Slip at D6a-07. Two check commands were refused by the permission check; the second contained a pipe character in Python's set union (|=), and both were redone without it (set.update).

D6a-08: D08 (Contention)

The close-check report of D6a-07 (_analysis/d6a07_validate_D6.txt): 0 errors, 1 warning; fractal lines 50, branches placed 35 of 35. The warning, that retelling-D6.md is not written yet, is expected until D6b. The leg closed normally with done.sh D6.

Answers to the notes that touch D08

• Form B (D5a-37): A15 cannot be shown in 11 of 18. Borne out at the form level: B restricts A15, and by my reading 11 of its 18 lines say the record cannot show the same recruited hands attacking, while 7 fall inside A15's bound (the attack call first, or in the opening turn with recruitment).
• Form A (D5a-36): on delivery and cause, A15 among them, the record cannot show it. A leaves A15 untouched (13 restrict holders at 0.84 times the share); E restricts it in the same terms as B.
• The branches' notes on P09 and P18 held less often in their members (F21, F22, F28, F33, F35). Consistent with the form rates: B holds contention most, and these branches lean to E, D, A, C and E. No action.

D08 in brief

24 form lines (2 leaning: A15 in B and E; 22 untouched; P09, P18 and A18 untouched in all six; C02's and P33's rows left out, written at D6a-05 and D6a-02); no branch lines; 8 evidence codes resolve. No proposal; A15's gloss is a wording item, held with the arrows' wording items from D3c, as A09's is. The dimension legs are complete: eight parts, 396 form lines, 50 branch lines with all 35 branches placed and named, and 11 unvalidated proposals. D6b assembles retelling-D6.md from the parts with the figure, the survival reading by form and the handback.

Licences exercised at D6a-08. C02's and P33's rows dropped from the rule's output before writing (d6a08_fractal_D08_noC02P33.json). The split of B's 18 lines into 7 inside the bound and 11 that the record cannot show is my reading.

Slips at D6a-08. None found.

D6b: the telling, the figure, the handback and the interview

The close-check report of D6a-08 (_analysis/d6a08_validate_D6.txt): 0 errors, 1 warning; fractal lines 50, branches placed 35 of 35. The warning, that retelling-D6.md was not written yet, ended at this leg.

The close-check report of this leg, before the cut (_analysis/d6b_validate_D6.txt): 0 errors, 0 warnings; fractal lines 50, branches placed 35 of 35. With retelling-D6.md present, the check found the figure and the handback, every branch with a fractal line, and every branch named in the telling.

What this leg wrote

• retelling-D6.md, assembled by _analysis/d6b_assemble.py from the parts: the frame and D01 to D08 (part 1), then retelling-D6-parts/D6b-telling.md (part 2). It has 12,395 words and 235 r/ names, all among the 705 analysed rooms in exact case, and it names all 35 branches. Part 2 tells the model with its forms inside it, which forms kept the work alive, the unadapted group, the uncomposed rooms, the returns the model lacks, the held proposals in full, the eleven proposals apart, and the answer to the theory question. The parts stay in place; D01.md's target-length line was replaced with the assembled length.
• figure-D6.md, drawn by _analysis/d6b_figure.py. It is the C5 drawing with the forms named in its boxes and arrows, four added boxes (P19, P23, P27, P32) and C01 beside it, a legend and a table of each form's changes and branches.
• _analysis/d6b_survival_forms.py and its JSON: the survival reading by form, from the record. The canvas is not read.
• handback-D6.md and interview/D6b.md (725 words).

Answers to the notes still open

• The two missing returns (carried in the head since D6a-01). Told in part 2 with F32's third: the call returns (PR-D6-01), the move returns to building (PR-D6-04) and the marking returns to keeping (F32). None is entered.
• The survival paragraph (defects line 100). The telling reads survival by form from the field and from the D5b re-reading, with silence counted, and states the field's error. The account's own paragraph is not rewritten here; the defect stays open.
• The uncomposed rooms. Given under both verdict counts: by the verdicts the forms carry (1 does not compose, 10 cannot tell) and at the re-check (0 and 19). What they share is a short record.

Licences exercised at D6b. The survival reading uses defining rooms, with all members and D's splits in the JSON beside them. The canvas is not read. The form I am most sure of (E) and least sure of (B) are my judgment, with the grounds written in the handback.

Slips at D6b.

• One diary line held a typing slip in its counts; the next line corrects it.
• The first draft of the uncomposed rooms gave only the first-return count; it was corrected from the D5 handback before any check ran.
• Three statements in the drafts were caught on reading them against their sources and corrected before assembly or close: the handback named seven branches in form D where ten have lines; the figure's legend said no form specifies an arrow, where A05 is specified by B and D; and the telling put form C's refusal under the held P05 bound, where it is F-025.

Handback, stage D6: the retelling, the model with its forms inside it

Legs D6a-01 to D6a-08 and D6b, 27 October 2026. One leg per aggregate dimension, then the telling. Outputs: retelling-D6.md (assembled from retelling-D6-parts/), fractal-forms-D6.jsonl (the form lines), fractal-D6.jsonl (the branch lines), figure-D6.md, proposals-D6.jsonl, an empty amendments-D6.jsonl, notes-D6.md and this file. The forms are the six room forms of D4a-08c by their final names, and the 35 branches are the level below (the PI's message for D6, on J's word). The model is the one frozen at D3 (46384686…), unchanged at this stage. The P05 and A11 amendments are held proposals (QD4-001), stated in full in the retelling. Local validation is not established: prior.md section 3's measure was not computed. No account relies on the kind of an add-condition, add-step or restrict line (J after the D3c interview). The canvas is not read anywhere in this stage.

The claim

Each of the six forms specifies the part of the shared model its name says, and none does the model's work another way. Of the 396 form lines (66 elements and arrows by six forms), 37 specify, 35 restrict, 324 leave the unit untouched, and none replaces it. So the level below specifies the level above without contradicting it. The forms differ in their functioning by which part they change. A changes the terms with neighbours and the plan, C the design, D keeping, help and carrying on, F the spot and the move, B the chat and the scripts, and E the host sub's April Fools play. By the rooms' own word, the forms that changed keeping (D, with C) kept the work alive to the freeze most often. The forms with the chat and the scripts (B), the terms (A) and carrying on (D) coordinated most after it.

The form I am most sure of: E, The sub's play, run as work. One element carries it: 56 of its 84 defining rooms add steps to the April Fools frame, against 18.5 per cent of the 558. One branch family explains it: F01's rooms are 54 of the 58 holders, and each subform (F02 to F06) explains a part. The D5 note that F01 and E restate each other is borne out in part (59 of F01's 103 rooms are in E).

The form I am least sure of: B, Behind the thread: chat, scripts, raids. Its account called it a grouping, not a form: its three parts are held by different rooms at about chance. It changes 7 units, the fewest, and its distinctness lies mostly in how often it holds the elements of identity and contention, which the rule does not test.

The form that best supports the claim: D, Keeping, with help or carrying on. It changes 17 units, the most. Every change is added detail or a condition, and ten branches have lines in it (F04, F11 to F14, F18, F22 to F24, F27).

The form that most threatens it: E. Ten of its 13 changes are restrictions, eight of them on arrows, and many say the record cannot show the order. Its records hold the play and the reports of the canvas work, and less of the work between them. If a form's restrictions track how thin its record of the canvas work is, the forms partly sort records, not organizing.

The condition between them is whether a form's record holds the canvas work between the call and the report. Where it does, the form specifies the model where it works (A, C, D, F). Where it does not, the form restricts the model's arrows (E).

The return value

• Form lines: 396 in fractal-forms-D6.jsonl, by the rule logged at D6a-01 before it ran. Units changed by each form: A 11, B 7, C 10, D 17, E 13, F 14. Thirty-one units are held as stated by every form.
• Branch lines: 50 in fractal-D6.jsonl. All 35 branches are placed and named in the retelling. Four branches are placed where their form as a whole leaves the element untouched, with their share of the form's holders (F20, F28, F30, F31).
• Amendments: none. amendments-D6.jsonl is empty.
• Proposals: eleven, all unvalidated, against the frozen model: PR-D6-01 (the call returns), PR-D6-02 (the answer that asks for a task), PR-D6-03 (a proposal that is itself the call), PR-D6-04 (after the move, the room builds again), PR-D6-05 (the design sized to the hands), PR-D6-06 (the check before repair), PR-D6-07 (the terms bind the placers they reach), PR-D6-08 (help from the hands a helper can spare), PR-D6-09 (border talk before keeping), PR-D6-10 (the play run as work), PR-D6-11 (imprinting runs with the work). Their codes all resolve.
• The figure: figure-D6.md, the C5 drawing with the forms named in its boxes and arrows. Of the 20 arrows, one is specified by a form (A05, by B and D) and 16 are restricted.
• Survival by form, from the record (_analysis/d6b_survival_forms.json; defining rooms). The field's kept share is C 60, D 57, B 53, A 50, E 46 and F 44 per cent, against 49 per cent of all 705 rooms. D's records are the least silent (6 of 96). Rooms that coordinated after hour 73: B 35 of 113, A 29 of 135, D 29 of 96, E 20, C 16, F 2 of 34. These are readings, not tests. The field was right in 25 of 34 rooms at prior.md, and the D5b re-reading agrees with it in 248 of 476.
• The unadapted group: empty. No room returned none, and 229 adapted rooms are in no branch.
• The rooms the model could not compose: by the verdicts the forms carry, one does not compose (r/picturegame) and ten cannot be told. At the re-check none fails to compose, and both readers could not tell 19 rooms. What they share is a short record (1 to 8 coded concepts, against a median of 101), not another way of organizing.
• What the forms show the model lacks: three returns, none entered: the call returns (C, D, F), the move returns to building (F; F09) and the marking returns to keeping (A; F32).
• One condition across the dimensions: a placer acts on a form or a term only where it reaches them. This holds in keeping, at the border, in a script's target and in help.

The held proposals (QD4-001; never served, not re-checked)

• P05 (move 198, history lines 173 to 176; reverted by move 203, line 181). The statement would gain: "This holds where the keepers can learn of a planned change only by being told, and no informed member holds it." The bound names completeanarchy, polska, satania, halo, bangtan and thesilphroad (the keepers read the change from its shape) and armok, maryland and oneshot (informed members hold it), with their nine re-check lines. The full text is in retelling-D6.md and tree-D4.md.
• A11 (move 199, history lines 177 to 180; reverted by line 182). The arrow from P02 to P04 would be withdrawn under rules 14 and 16. It never beat its null, template first is nearly as common as the transition, the failure clause stands alone in 117 rooms, and 261 accepted restrict lines say a template does not settle the design for good. Form C restricts A11 in 40 of its 58 lines. Both stay held.

Questions, departures and defects

• QD6-001 (the form lines against the check's branch field). Answered with option (c): form lines in fractal-forms-D6.jsonl, branch lines in fractal-D6.jsonl, the dimension parts kept outside retelling-D6.md until this leg. One amendment, departures.jsonl line 20, cites J's 18:01 ruling; line 19 stays.
• QD6-002 (the missing trusted tree hash). J ruled (27 October, 06:33 Berlin): "The file should be the last cut we did. Prepare a file like the one it needs and give it the authority it needs for the run to continue." The handler wrote _closes/tree-D4.sha256; legs from D6a-03 closed normally.
• Wording items, held with the arrows' wording items from D3c. A09's and A15's glosses read as causes ("the record is what passes on"; "a call's hands can turn on a rival"). Their counts are orders, and their restrict lines in D and E (A09) and B and E (A15) deny a cause the arrows do not claim.
• Defects carried, not mended here: the account's survival paragraph rests on the work_remained field (defects line 100); the four timings the canvas contradicts (line 101).

Licences exercised (METHOD.md)

• The fractal rule, logged at D6a-01 before it ran, and the reading of "branch" as room form (the PI's message).
• A branch is named at a cell only where it leans to the form at 1.5 or more, holds two or more of the cell's holders, and its key matches the cell. From D6a-04 the key match was read to include an end of the cell's arrow or the antecedent's theme. F08 was twice placed by the text of its change (P05 in F; A05 in B).
• Branch lines placed below the form's lean at the branch's key element (F20, F28, F30, F31).
• Elements in two dimensions written once, in the first dimension read (K05, P28, C02, P33).
• The instantiation rates of the forms reported beside the untouched lines, with the form medians of coded concepts as the check on record size (D05, D08).
• The proposals' rooms and the splits of restrict lines into record-cannot-show and fails are my reading of the lines.
• In the survival reading, the canvas is not read, and the uncomposed rooms are given under both verdict counts.

Slips

• D6a-01: the first leg closed with --pause after the check refused the form letters (QD6-001).
• D6a-02: two Edits to one file in one turn, and a stray open('/dev/stdout','w') that wrote nothing.
• D6a-03 and D6a-05: a cut -c after a helper, refused by the guard.
• D6a-04: a read at a wrong path. D6a-07: a pipe character in a Python set union, refused by the guard.
• D6b: one diary line held a typing slip, corrected in the next line. The first draft of the uncomposed rooms gave only the first-return count; I corrected it before any check ran.