Forming: the tree | D4a-08

Room forms, D4a-08c: six forms, with the core placed

Leg D4a-08, still open, 26 October 2026. J, through the handler (22:00 Berlin): "I think this is good but I would rather have fewer clusters. Also I don't get why the core is still alone. Can we try to have some 4 or 6? If not then it is fine but it is a lot for a short technical appendix. Also 31, 21, 49 is quite small." This file answers on the D4a-08b weighting: the changes weigh two thirds, the codes one third. It sits beside room-forms-D4a05.* to room-forms-D4a08b.*, which are unchanged. Files: room-forms-D4a08c.jsonl (the six forms, with members), room-forms-D4a08c.tsv (every room at six, four and eight forms), and this file. The computation is _analysis/d4a08c_room_forms.py; its rule was logged before it ran.

My answer: six forms. Section 4 gives the reasons and what is lost.

1. The core, placed by its codes

The 21 rooms were kept apart only because the first brief said so. None of them holds a selected change: their change profile is 0, the global model. Each is now placed in the form whose centre its code part lies nearest. I used the code part alone, because a zero change part would favour whichever form's change centre lies nearest 0. The table also gives the placement with the full distance, which differs for some rooms.

• r/startrek goes to the sub's April Fools play at every count. So does r/n64.
• The other 19 rooms spread across the forms. They hold 1 to 8 coded concepts each, so their placement rests on a handful of codes and is weak.
• At six forms the core adds 2 to 6 rooms to each form, 6 of them to the spot.

2. How the forms merge

The cuts nest, so each smaller count joins forms of the larger.

• Eight to seven: raiding (H) joins the work behind the thread, the chat and the scripts (C).
• Seven to six: the plan made and announced (F) joins the terms between neighbours (E).
• Six to five: the work behind the thread, with raiding, joins the design.
• Five to four: the spot joins keeping.

The gap, the length of time a cut lasts as the joining goes on, is longest at four (0.392). It is next longest at seven (0.272), and six comes third (0.178). The eight forms, for reference, with the core placed:

3. Six forms and four forms

At six:

At four:

Where the small forms go. Raiding (35 rooms with the core placed) is gone by six: it sits inside the work behind the thread, which holds 12 of the 21 raiding-heavy rooms. The spot (56 at six) stays a form at six and joins keeping at four. The core no longer stands alone at any count.

4. Which I would stand behind for a short technical appendix

Six. At six, every form I was sure of at eight still stands on its own: the terms between neighbours, the design and its marking, keeping, and the spot. The April Fools play is its own form, the frame beside the canvas work. The pieces I was not sure of are joined into one form and named for what it is, a mixture: the chat, the scripts and raiding, the work behind the thread. Its three signatures are each held by under half its members, so I would not write one account for it. The largest form is 2.96 times the smallest, within J's bound of 3. The smallest form, the spot, has 56 rooms, and the narrow form F09, moving and building again, lives there.

What is lost going down from eight to six:

• Raiding as a form of its own. It remains a pattern inside the work behind the thread.
• The plan made and announced, which I was not sure of. It folds into the terms between neighbours.

Why not four. Four is the clearest split by the gap. It has no small forms, and it reads as four broad orientations: making the mark, the terms with neighbours, holding ground, and the April Fools play. But two of the four lose what made them forms. The design absorbs the chat, the scripts and raiding, and its signature falls from 98 to 73 per cent. Keeping and the spot join into "holding ground", whose signatures are each held by under half its members. The spot is the form with the clearest account that differs from the model (the move followed by building again), and at four it no longer has an account of its own. I would use four only as a one-line summary of the six, not as the forms.

What I am still not sure of at six. The work behind the thread is a mixture, and I would split it at the level below. The forms remain poles of a continuum. The real stability of the cut is low (about 0.21 at every count), and many rooms lie between forms.

5. The room table

One row per room, at six, four and eight forms (also in room-forms-D4a08c.tsv). Core rooms are marked.

The tree, stage D4

Begun at D4a-01, 2026-10-24 (UTC). The taxonomy is read off the adjudicated ledger: the current ledger (the re-check, for all 705 rooms), whose lines were adapted against the model frozen at D3 (46384686…). Every count here comes from a script named beside it.

The model the tree hangs from, and two held proposals

The conceptual root is the global model as frozen at D3 (46384686d6173fdeb4c749667478c1363e675bc6b52bb6f4fdc211d387e68525), and the model in out/model/ is that version. At D4a-01, on J's instruction after the D3c interview, two amendments were made under rule 11 (moves 198 and 199; history lines 173 to 180). The D4 close-check refuses any model move after the D3 freeze (stage_D4.py, vlib.model_moved with no allowance). I asked (QD4-001), and J chose option (b): the same leg reverted both (move 203; history lines 181 and 182), and the model hash is 46384686 again. Both are held proposals: never served to any room, not re-checked, and not part of the model this tree hangs from. They are stated in full in "The held proposals" below. The distances do not read element text or status (adaptation_ledger.shared_lines reads the ledger and its rulings only), so neither the amendments nor the revert changed any distance, key or member here.

The statistic and the frequencies, read before any cut

• Tree-likeness. The delta score on the combined level-3 matrix is 0.4227 (Monte Carlo SE 0.0020; 20,000 nondegenerate quartets, seed 0), over 705 rooms and 26,487 shared lines (_views/tree-likeness.json). The weights (4, 2, 1, 0.5) and grades (1, 0.5, 0, -1) are prior.md section 7's, confirmed. Larger deltas mean less additive distances. The dendrogram is drawn (_views/dendrogram.nwk), but it is a chain: at 12 clusters one group holds 663 rooms, and the others are single rooms or small groups peeling off it (_views/dendrogram.txt). The dendrogram is a view of the dissimilarities, not a chronology and not a validated hierarchy, and it shows no partition of the rooms. The NeighborNet is drawn outside the run, if asked.
• Key frequencies (_analysis/d4a01_key_freq.py). At level 3 there are 5,237 keys: 2,772 held by one room, 1,509 by 2 to 4, 720 by 5 to 19, 208 by 20 to 99, 28 by 100 or more. Every room holds a key, and no room returned none. Corrections: 17 keys in 18 rooms, none held by more than 2 rooms below the bare target. Elaborations: 545 keys in 497 rooms. Specifications: 4,931 keys in all 705 rooms.
• The strongest signal is nearly empty. Shared corrections, the stage's strongest form signal, reach 5 rooms only at the bare target (restrict on P05 in 7 rooms, restrict on R01 in 5). The D3 revisions absorbed the first-return corrections, so the current ledger's groups rest on elaborations and specifications.

The sensitivity check (J after the D3c interview)

The kind of add-condition, add-step and restrict lines is not relied on (the blind check's kappa on them was 0.08). The distance was computed once more with one kind for those three ops (_analysis/d4a01_kind_collapsed.py). The combined distance hardly moves: Pearson 0.9965 and Spearman 0.9967 over 248,160 room pairs, mean absolute difference 0.0024, delta 0.4223 against 0.4227. The average-linkage trees agree at 2 and 3 clusters (ARI 1.00), at 5 (0.886) and 8 (0.922), and less at 12 (0.779). The per-kind views do depend on the kind: for add-step and add-condition the specification lines outnumber the elaboration lines about 2 to 1 and 6 to 1. So no branch takes its members from a per-kind view for those ops; keys are read in the all-kinds matrices.

The rules of the cuts, written before the first cut

• The minimum group size is 5, the default. prior.md sets none. I keep it, since 720 level-3 keys are held by 5 to 19 rooms, and a higher floor would drop most change keys before their lines are read.
• What keys a branch. An element's change key (op add-step, add-condition, link, restrict or contradict), read in the all-kinds matrix, at the deepest ladder level where 5 or more rooms meet on it. Arrow keys cannot key a branch, since the check resolves a key's target against the elements; they are context. Instantiate and absent keys specify the model as it stands and change nothing, so they define no branch.
• When a key becomes a branch. Only when the members' lines, read whole through _analysis/d4_key_lines.py, state one shared change to the element: a step, a condition or a link that the statement does not hold, or holds only in part. Otherwise the group is set aside below, with its reason.
• Subforms. A level-3 child key held by 5 or more of a branch's members, whose lines state a narrower change than the parent's.
• Corrections that meet only at the dimension or the bare target are groupings, not branches: P05's shape read and R01's joining (below).
• Cross-links. A room in two branches that do not nest is declared in crosslinks.jsonl by script, with both keys as the reason.
• Order. By element, from the largest change-key group at level 4 downward. A leg ends at a safe stop after a logged move.
• Ground. The keys, unless a cut's tier_history.jsonl line declares the members' material. The branch's kind field is the majority kind of its members' lines on the key, reported and not relied on.
• Rule 7. I hold every room's canvas outcome and cannot unknow it. No cut reads the canvas, the verdicts or the projections, and each cut is snapped before anything is projected onto it.

The cuts of D4a-01, in the order cut

• F01 (move 200, merging; branch named; level fourth; parent none). Keys: add-step:K01:T4-001. 103 members. Kind: elaboration (specification 60, elaboration 104), not relied on. Ground: keys. the play administered: steps that test, police, end and convert the April Fools frame. K01 states that the host sub is keyed as play for April Fools and that a claim in it may be a joke. In these rooms the frame gains steps that the statement does not hold. Members test whether a claim is a joke by its date, source or link. They police the licence's limits and argue about when it ends. Moderators enforce a takeover's rules by real removals and switch its styling off. A joke can turn into a sincere request or a lasting change. The steps belong to the sub's own play beside the canvas, not to canvas work.
• F02 (move 201, splitting; subform declared; level third; parent F01). Keys: add-step:K01:T3-023. 33 members. Kind: elaboration (elaboration 23, specification 20), not relied on. Ground: keys. the takeover run as a temporary regime. Within F01, a takeover's play becomes a temporary regime: its rules are enforced by real removals, bans and bots, members perform and test them, its styling is made usable or switched off, and its end is set.
• F03 (move 202, splitting; subform declared; level third; parent F01). Keys: add-step:K01:T3-095. 18 members. Kind: specification (specification 12, elaboration 6), not relied on. Ground: keys. the joke tested: members check a claim's truth. Within F01, members test whether a claim is a joke before they act on it: by its date, its source, its plausibility or its marks, and they repair a literal reading.
• F04 (move 204, splitting; subform declared; level third; parent F01). Keys: add-step:K01:T3-032. 13 members. Kind: elaboration (elaboration 15), not relied on. Ground: keys. the licence policed: objections to the play, its limits and its end. Within F01, members object to the play and police the licence: they set limits on taste and repetition, demand labels, deletion, restoration or better jokes, and dispute when the licence ends.
• F05 (move 205, splitting; subform declared; level third; parent F01). Keys: add-step:K01:T3-097. 12 members. Kind: elaboration (elaboration 13), not relied on. Ground: keys. the styling ended: ordinary use restored. Within F01, members and moderators end the prank's styling and restore ordinary use: they switch styles off, ask whether the sub has switched back, and clear what the prank left.
• F06 (move 206, splitting; subform declared; level third; parent F01). Keys: add-step:K01:T3-100. 8 members. Kind: elaboration (elaboration 8), not relied on. Ground: keys. the joke kept: a request that its change last. Within F01, members ask that a joke's change outlast the day: a temporary feature, mode, flair, banner or board is to become permanent, or a joke activity real.

Members are listed in branches.jsonl and in each forms/<id>.md, with every member line's how sentence, the elements the members carry unchanged, one representative concept per member with its ladder, and the mention graph among members. The branches are presented in the order cut, never by size.

Cross-links (move 207, relating; crosslinks.jsonl, 18 lines): F02 and F03: dankmemes, ontario, terraria, warframe, zelda; F02 and F04: bindingofisaac, dankmemes, monstercat; F02 and F05: ontario, schoolidolfestival; F03 and F04: AMD, canucks, dankmemes, magictcg; F03 and F05: minecraft, ontario; F04 and F05: anime_irl, nbaspurs. F06 shares no room with another subform. Every subform nests in F01, so a room in F01 and one subform is not a cross-link.

Groups read and set aside

• Two level-3 groups under F01. add-step on K01 at T3-001 (staging April Fools fake news, 37 rooms) and at T3-048 (reacting to official April Fools, 14 rooms). Their lines state several different steps (testing, an apology, a fake turned into serious talk, financial warnings, troubleshooting), so no narrower shared change holds them. Their rooms stay in F01.
• P05's shape read and R01's joining (cut rule R4). The re-check's corrections meet only at the bare target (restrict on P05 in 7 rooms and add-step on P05 in 2; restrict on R01 in 5). There the aggregation does the work, so they are groupings, not branches. A key holds the op, the target and the node, not the condition, so the keys cannot carry what separates the shape read from the trunk. D3's branch stays a held branch, read from the rooms' material (F-024), not a key branch.
• Arrow keys. The largest change keys are restrict lines on arrows: A04 at T3-010 (87 rooms), A11 at T3-004 (77), A05 at T3-010 (59), A13 at T3-010 (53). A branch cannot be keyed on an arrow (cut rule R1). They are context: most were ruled specifications that the arrows' bounds already state.
• Co-occurring keys. Among the change keys held by 5 rooms or more, the keys their rooms share beyond chance are mostly on the same third-order node (one theme lifting to several elements), so they are not independent definitions (_analysis/d4a01_candidates.txt, section B).

Where the pass stopped

J stops the run after this leg (QD4-001). The pass cut one element, K01, the largest element change key at level 4. These element change keys at level 4, held by 20 rooms or more, were not read for a cut: restrict:P05:T4-006 59; add-step:P14:T4-009 58; link:P03:T4-014 54; add-step:P08:T4-016 47; add-step:P13:T4-028 43; add-condition:P05:T4-013 43; add-step:P04:T4-008 42; add-step:P02:T4-006 41; add-step:P05:T4-013 40; add-step:P23:T4-010 39; add-step:P20:T4-002 36; add-step:P11:T4-026 36; add-step:P12:T4-027 33; restrict:K01:T4-001 32; add-condition:K01:T4-001 31; add-condition:P16:T4-017 30; add-condition:P13:T4-028 30; add-condition:P08:T4-016 29; add-condition:P14:T4-009 28; restrict:P14:T4-009 27; restrict:P13:T4-028 27; restrict:P05:T4-016 27; restrict:P05:T4-013 27; add-condition:P16:T4-016 27; add-condition:P23:T4-010 26; restrict:P23:T4-010 24; restrict:P19:T4-016 23; link:P05:T4-026 23; add-step:P04:T4-006 23; add-condition:P02:T4-006 22; add-step:P01:T4-005 20. Each would be read as F01 was, by cut rules R1 to R3. No comparison (section 5) and no projections (section 6) were built, since they come after the final cut, and this pass is not the final one.

The held proposals (QD4-001, option b)

Both were made at D4a-01 and reverted in the same leg. Neither was served to any room, and neither is re-checked. The model this tree hangs from holds P05 and A11 as frozen at D3.

• P05, move 198 (contrasting), history lines 173 to 176, reverted by line 181 (move 203). 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. Amended at D4a-01, after the D3 freeze (46384686...); not re-checked: no room was served these words." Rooms: completeanarchy, polska, satania, halo, bangtan, thesilphroad, armok, maryland, oneshot. Lines: R-completeanarchy-c187508d7ae3-022, R-polska-dadda7358f9a-049, R-satania-84df196116f3-022, R-halo-b988854ba168-036, R-bangtan-7efe23da0d0c-070, R-thesilphroad-a3f86618e239-018, R-armok-8852b2ab85f8-022, R-maryland-d1b6e2d1d5f3-017, R-oneshot-e840e127e9b2-013.
• A11, move 199 (dropping working hypotheses), history lines 177 to 180, reverted by line 182 (move 203). The arrow from P02 to P04 would be withdrawn (status withdrawn, in_model false). Its reason, as written: "Rule 16 and rule 14: preserve what remains supported, and replace or withdraw what does not. No defensible formulation of A11 as an arrow survives the return. (1) The order between rooms never beat its null (111 of 185 rooms, 0.600; null p95 0.670; base_rate_beaten false), and C2 withdrew it, keeping a transition inside threads. (2) Inside threads, the return's census (D3a-38, re-run as _analysis/d4a01_a11_classes.json) shows the transition in 111 rooms and template first in 98 of the 228 rooms whose lines show both ends; across threads 19 more. The reverse order is nearly as common, so the arrow carries no direction. (3) The failure clause is present and stands alone in 117 rooms: talk only in 31 (berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia) and layout only in 86. (4) The mechanism's word 'settled' is contradicted by 261 accepted restrict lines whose 'how' says a template does not settle the design for good (rival templates, polls, later redesigns, placers who deviate). A reworded arrow (a layout answers design talk in its thread) would be a new claim, never served to any room, with its reverse nearly as common: a co-occurrence, not an arrow. What remains supported, that design talk and layouts meet in threads, is held by P02's and P04's statements and ranges ('a design argued over days and redone'; 'an official template the room asks everyone to follow against other versions'), which stand. The arrow's record keeps its evidence and reasoning." Rooms (the talk-only rooms of the failure clause): berkeley, bih, bitcoin, edboxes, eve, FinalFantasy, guatemala, habs, HomestarRunner, indieheads, ireland, latvia, leagueoflegends, mexico, morrowind, msu, parrots, placeDE, placesnek, polska, portugal, quebec, samuraijack, slovenia, spain, suomi, titanfall, torontoraptors, unitedkingdom, wine, zootopia. Lines (the first-return lines of the census classes talk only, layout only and template first, 216): 2007scape-012, 4chan-011, AMD-012, AmericanFlaginPlace-009, AvoArmy-011, AyyMD-041, CKCrusaders-041, CSUFoCo-015, DestinyTheGame-014, DevonUK-010, FinalFantasy-014, GuardiansOfDatBoi-009, HomestarRunner-015, MonkeyIsland-011, NewMexico-015, ScottPilgrim-015, Temple-041, TsundereSharks-048, adventuretime-041, aggies-050, albania-046, alberta-016, anaheimducks-015, animalcrossing-053, anime-012, argentina-051, armenia-030, bardmains-055, berkeley-038, berserk-012, bih-036, bisexual-012, bitcoin-012, blackmirror-046, borderlands-020, bostonbruins-052, brasil-011, canada-012, catalonia-009, catholicism-011, cfb-048, chibears-010, chicubs-010, cirkeltrek-013, clashroyale-045, completeanarchy-011, criticalrole-043, crusaderkings-039, cubers-014, cuboulder-008, czech-014, dankmemes-045, darksouls-042, detroitlions-049, edboxes-046, edmontonoilers-041, empiredidnothingwrong-013, england-045, ethereum-056, europe-050, eve-049, fivenightsatfreddys-012, flashtv-055, floridagators-035, flyers-035, formula1-048, forsen-010, ftlgame-044, fxKorea-010, gameattack-015, gamindustri-053, gatech-041, ghibli-010, globaloffensive-012, greenbaypackers-011, guatemala-010, habs-011, heyyea-010, hongkong-047, hsv-012, hyperlightdrifter-046, indieheads-056, indonesia-035, ireland-045, italy-035, katawashoujo-041, lakers-009, latvia-029, leagueoflegends-042, lifeisstrange-013, linux-015, littlewitchacademia-012, loliconsunite-010, lost-044, lovelive-041, lsu-049, luxembourg-012, madokamagica-041, magictcg-010, mechanicalkeyboards-042, metalgearsolid-013, mexico-041, miamidolphins-041, minecraft-017, mit-041, mizzou-018, mls-053, monalisaclan-013, morrowind-011, msu-011, muse-048, mylittlepony-011, nVade-013, naruto-010, nbaspurs-056, necrodancer-011, neopets-047, newzealand-046, nightinthewoods-012, nin-012, ockytop-042, opticgaming-012, overwatch-017, parahumans-013, parrots-013, pathofexile-012, pcmasterrace-013, pebble-007, penguins-055, philippines-052, pitt-041, placeDE-041, placecanada-013, placesnek-031, planetside-056, polska-054, portal-012, portugal-082, predators-010, purdue-051, puzzleanddragons-013, quebec-013, radiohead-010, rainbowgrid-006, rangers-045, re_zero-042, redpandas-018, rickandmorty-042, rit-011, rocketbeans-008, rocketleague-011, romania-015, roosterteeth-013, rpi-049, russia-052, rust-010, rutgers-012, samuraijack-047, scp-014, seahawks-014, serbia-051, singapore-016, slovenia-041, smite-010, southpark-012, spacexmasterrace-052, spain-035, ss13-016, ssbpm-012, stardewvalley-058, starryknights-041, stevenuniverse-012, straya-047, suomi-041, survivor-035, sweden-045, tampabaylightning-045, terraria-048, teslamotors-012, tf2-041, thebluecorner-016, theexpanse-012, theitalyplace-054, thepointing-043, thesimpsons-011, tinytardis-009, titanfall-013, torontoraptors-016, totallynotrobots-013, transformers-046, trees-013, turkey-055, twentyonepilots-012, ubc-046, ucf-050, uiuc-011, ultrahardcore-005, undertale-011, unitedkingdom-035, unturned-013, uofm-008, uofmn-035, uruguay-012, utahjazz-009, utaustin-013, uva-042, uwaterloo-011, vegan-043, virginiatech-043, weezer-053, wine-011, witcher-017, worldoftanks-015, xenoblade_chronicles-012, zelda-061, zootopia-012.

Grounds, and what would have changed the cuts

• Grounds. Every cut is grounded on keys alone ("ground": "keys" in each tier_history line). No member's material was read for a cut. The lines' how sentences were read only to test whether a key's rooms share one change (cut rule R2).
• Was any cut attractive because of what its members made? No. I hold every room's canvas outcome and cannot unknow it, but no cut read the canvas, the verdicts or the projections. F01 and its subforms are about the sub's own April Fools play, which the lines say is not canvas work. The first cut was chosen by the size of the element's change-key group at level 4.
• What would have made me choose differently. Shared corrections at the third or fourth order (none reach 5 rooms); a kind I could rely on for add-step, add-condition and restrict lines (J: not reliable, kappa 0.08), which would have let the elaboration view lead; or change keys that co-occur across different nodes in 5 rooms or more, which would have given multi-key branch definitions.
• Local validation. Not established. The labelers mark all 705 rooms unresolved, and prior.md section 3's measure (each second-order theme with a coordinating turn reached by an element or a validated adaptation, or listed unresolved) was not computed (J after the D3c interview).

The accounting (stage D4 section 4), against n_analysed

counts.py gives n_analysed = 705 (census 705, dropped 0). In a branch: 103 (F01 and its subforms). The unadapted group: 0 (no room returned none). Adapted but in no branch: 602. Unreturned at D2: 0. The four counts sum to 705, the analysed set. _views/distance.tsv holds 705 rooms.

Adapted but in no branch, each with why. Every one of these rooms holds accepted keys, so none is unadapted. None holds a key cut at D4a-01, because the pass reached one element, K01. The number after each room is how many level-3 change keys on elements it holds that 5 rooms or more share: the keys a later pass would have read. A room marked 0 holds no such key: its change keys are its own, or on arrows.

2007scape (2); 49ers (6); aceattorney (0); AceOfAngels8 (0); AcePlace (5); achievement_hunter (0); adventuretime (3); aeon (2); aeskwadraat (2); afip (3); aggies (4); ainbowroad (4); albania (0); alberta (0); AmericanFlaginPlace (7); anaheimducks (6); anarchism (1); anarcho_capitalism (0); anarchocapitalism (1); androidgaming (3); animalcrossing (3); anime (4); aoe2 (1); apocalypserising (0); AprilKnights (2); araragi (1); archlinux (5); argentina (1); armenia (2); armok (0); aromantic (1); asexual (1); asexuality (3); asktransgender (2); auburn (1); australia (0); austria (0); austriahungary (0); AvoArmy (2); AyyMD (3); azerbaijan (2); azores (0); babymetal (8); bakchodi (2); bangladesh (2); bangtan (1); bannedfromanime_irl (0); bardmains (5); batman (1); baylor (0); bdsm (0); bees (0); belgium (2); berkeley (1); berserk (6); bigbang (0); bih (2); bisexual (8); bitcoin (2); blackmirror (2); bobross (0); borderlands (3); borussiadortmund (8); bostonbruins (3); brasil (5); Bravenewbies (1); Braveryjerk (0); bretagne (1); btc (1); buffalo (5); buffalobills (4); buffalowizards (1); bulgaria (2); calgaryflames (1); calvinandhobbes (1); cardinals (0); carletonu (0); catalonia (3); catalunya (3); catholicism (4); cavestory (4); CelticFc (1); cgpgrey (2); chess (1); chibears (2); chicago (2); chicubs (2); chile (4); ChronoTrigger (4); churchofhelix (0); cirkeltrek (0); CKCrusaders (2); Clannad (0); clashroyale (1); clg (3); cloud9 (3); clubpenguin (7); cmu (0); coldplay (6); colombia (1); colorado (2); columbia (1); completeanarchy (2); compsoc (1); Cornwall (1); corridor (0); COSI (0); costa_rica (1); counting (1); cowchop (4); croatia (0); crusaderkings (5); CryptoFR (2); crystalclear (2); CSUFoCo (1); cubers (5); cuboulder (0); czech (6); daftpunk (3); darksouls (2); DatBoi (1); davidbowie (2); day9 (1); DCFU (1); de (7); denmark (1); destiny (1); detroitlions (1); detroitredwings (2); DevonUK (2); diablo (2); DiamondClub (0); dmt (2); dofus (0); Dominican (1); donaldglover (1); Dorset (2); dragonquest (3); drawhelix (4); drugs (2); duckgame (2); ducks (0); Dustforce (2); dwarffortress (2); eagles (0); earthbound (5); edboxes (1); eder (1); edmontonoilers (2); eesti (1); egypt (1); ElSalvador (0); empiredidnothingwrong (2); england (0); enterthegungeon (2); epublica (3); EraseThePlace (3); esperanto (5); europe (3); eve (4); evedreddit (0); evex (4); factorio (4); faeria (9); farmcarrots (1); FaroeIslands (1); FederationPlace (4); Fez (3); FinalFantasy (2); finland (1); fireemblem (2); FlaggyFlag (3); FlipnoteStudio3D (1); floridagators (0); FloydVsVoid (11); flyers (4); forsen (7); foxes (4); foxstevenson (0); france (0); frankocean (7); frc (5); freedomplanet (4); ftlgame (3); fullcommunism (1); funhaus (5); furry (4); futanari (1); futurama (2); fxKorea (4); GabrielDropout (2); gameattack (2); gameboy (1); gamindustri (5); gatech (7); genderfluid (1); germany (1); ghibli (2); giantbomb (4); giivasunner (6); glasgow (1); globaloffensive (3); Goodboye (2); gorillaz (1); GranColombia (5); gratefuldead (0); gravityfalls (3); greece (2); greenbaypackers (1); GreenCorner (2); GreenEmpire (0); greenland (0); greenlattice (5); greyblob (4); GrowTheTree (1); GuardiansOfDatBoi (1); guatemala (0); h3h3productions (2); habs (2); halo (1); haskell (0); hatsune (3); hawks (6); hearthstone (3); hellointernet (4); hentai (3); heyyea (2); homelab (1); HomestarRunner (2); homestuck (5); Homura (0); Honduras (1); hongkong (3); hoodr (0); hsv (3); httyd (2); hungary (3); hyperlightdrifter (6); iastate (3); ibo (1); ice_poseidon (0); iceland (1); ik_ihe (2); india (5); indonesia (5); ireland (1); israel (2); italy (3); Jamaica (2); japan (4); jerma985 (3); k_on (2); kamenrider (4); katawashoujo (1); kcroyals (5); kilian (2); kindafunny (2); kingdomhearts (1); konosuba (0); korea (7); KState (5); kurdistan (1); kuwait (1); lakers (2); landry (2); latin (2); latvia (0); leafs (3); leagueoflegends (0); lebanon (3); lego (4); lexington (0); lifeisstrange (1); linux (5); liquicity (1); lithuania (2); littlebusters (0); littlewitchacademia (6); livecounting (3); liverpoolfc (2); lofihiphop (3); loliconsunite (3); loltyler1 (4); lost (2); lovelive (3); lsu (5); luciomains (5); Lugarix (0); luxembourg (2); Madeon (0); madokamagica (6); malaysia (6); malta (1); mamamoo (1); ManningPlace (1); Mario (1); marvel (1); maryland (3); masseffect (3); math (1); mcgill (1); mcgillrobotics (0); mechanicalkeyboards (4); megaman (5); metalcore (3); metroid (3); mexico (2); miamidolphins (2); MiamiHurricanes (0); mindcrack (6); minnesotavikings (1); mit (3); mizzou (3); monalisaclan (7); monero (6); MonkeyIsland (3); monsterhunter (1); montenegro (2); Moondye7 (4); mordhau (1); morrowind (6); msu (5); muse (2); mylittlepony (5); mysterydungeon (5); n64 (0); nascar (4); natsume (1); necrodancer (5); neopets (3); nerf (4); neu (2); neutralmilkhotel (2); NewMexico (4); newzealand (2); nin (3); nlsscirclejerk (3); nonbinary (0); norge (1); Northwestern (0); norway (3); notredame (5); NovaScotia (0); npr (3); nuclearthrone (2); nVade (2); nyu (1); ockytop (3); ohio (3); Okami (3); OKState (3); oltp (0); oman (0); OnePiece (4); onepunchman (2); oneshot (4); OneTrueEmilia (5); opticgaming (4); orderofthebluecorner (1); OrderOfTheKoi (2); osu (4); osugame (4); overwatch (4); pakistan (4); palestine (1); pansexual (0); parabola (2); parahumans (4); paranatural (2); parrots (3); partyparrot (1); pathofexile (4); patriots (2); paydaytheheist (1); pebble (0); penguins (5); pepe (2); Peru (2); peterdraws (1); pgang (0); philippines (2); physical_removal (1); picturegame (1); Pigifs (0); PinkUnion (2); PinkVomitMonster (1); pitt (4); placecanada (3); placeDE (3); placehearts (1); placehfarts (0); PlaceNL (5); placeportalpattern (5); placesnek (3); placestart (3); placetardis (5); pokemon (1); PokemonSage (0); poland (5); polska (5); polyamory (2); portal (4); porterrobinson (5); portugal (4); PORTUGALCARALHO (0); predators (7); prequelmemes (10); Produce101 (0); ProfessorLayton (3); purdue (5); purplecorner (3); PurplePixels (2); pusheen (4); puzzleanddragons (3); python (4); qotsa (0); quebec (6); quq (0); radiohead (3); rainbowgrid (1); rangers (4); raocow (2); ravens (3); re_zero (4); ReBoot (0); redhotchilipeppers (3); Redox (0); redpandas (4); redvsblue (1); RelientK (2); rhythmheaven (1); rickandmorty (4); ripcity (6); riskofrain (2); rit (4); rocketbeans (3); rocketleague (0); rojava (2); roosterteeth (3); rotmg (5); rpi (5); russia (2); Russiaclan (2); rutgers (5); sabres (3); sadboys (5); sakartvelo (0); sakuragakuin (1); satania (4); sbu (1); scotland (0); ScottPilgrim (0); scp (3); seolhyun (3); serbia (1); seventeen (0); sheffield (2); shield (3); shishamo (1); shitredditsays (2); shrooms (0); signal (0); simonfraser (2); singapore (5); sips (6); sixers (3); skyrim (3); Slovakia (0); slovenia (2); smite (1); snsd (1); sonicthehedgehog (4); sooners (4); southafrica (5); southpark (2); soylent (4); spacexmasterrace (4); spain (2); splatoon (2); spongebob (4); SquareSpiral (4); ss13 (2); ssbpm (2); starbound (2); starcitizen (3); stardewvalley (6); starlightstage (8); starryknights (5); startrek (0); starvstheforcesofevil (3); stlouis (3); stlouisblues (0); strangerthings (1); straya (1); Summit1G (3); suomi (4); superman (1); sweden (2); SwissNeutralityZone (4); switzerland (4); SydneyFC (0); tagpro (5); taiwan (2); tampabaylightning (1); teamcube (2); TeamDignitas (1); TeamYellowPlace (2); telegram (3); Temple (3); tenma (1); teslamotors (2); tetris (1); texas (3); texastech (1); tf2 (1); thailand (4); the_pack (1); THE_R (1); TheAdventuresofTintin (0); TheB1G (0); theblackvoid (1); thebluecorner (3); theexpanse (6); TheFarLeftSide (0); Thegreatblackhole (1); TheGreatGreenBox (1); TheHulk (5); TheID (0); theitalyplace (1); thepointing (2); thesilphroad (1); thetreesnetwork (0); timbers (3); tinytardis (2); tokyo (1); toolband (3); torontoraptors (4); touhou (3); traaaaaaannnnnnnnnns (4); TransFlagPlace (1); transformers (3); transgender (1); TreePlace (1); trees (2); truestl (2); TsundereSharks (1); turkey (4); twentyonepilots (2); twice (5); twitch (3); ubc (2); ubreddit (3); ucf (1); udub (2); ufl (1); uiowa (1); uiuc (2); ukplace (2); ukraine (3); UMiami (0); undertale (4); unitedkingdom (1); UNLincoln (0); unturned (5); uofm (3); uofmn (3); uoft (2); UPenn (2); uruguay (0); utahjazz (3); utaustin (3); uva (2); uvic (3); vegan (2); VelvetUnderground (2); vermont (5); vietnam (1); Villanova (1); vim (3); vinesauce (4); virginiatech (4); vocaloid (3); wales (1); wallstreetbets (2); wario (0); warriors (4); warthunder (2); watchmen (0); weezer (3); wine (3); winnipegjets (3); WisconsinBadgers (2); witcher (3); worldpowers (3); WPI (2); wsu (0); xcom (3); xenoblade_chronicles (6); yerbamate (0); yumenikki (0); yuyuyu (4); zootopia (7).

The cuts of D4a-02 (the second pass), in the order cut

The pass read the 31 element change keys at level 4 that D4a-01 left, each held by 20 rooms or more, with the dated amendment R1a to R1c (the level, keys read together, restated statements set aside). Each key's lines were read whole in _analysis/d4a02_keys/ (d4_key_lines_bynode.py). The cuts were written by _analysis/d4_cut_batch.py from the specs _analysis/d4a02_cut_F07.json to F35.json, each logged as a move and snapped when it was written.

• F07 (move 208, merging; branch named; level fourth; parent none). Key: restrict:P05:T4-006. 59 members. Kind: specification (specification 56, elaboration 1, correction 2), not relied on. the telling clause not shown at the design: informed members reject the planned change. P05's added clause says that a planned change is repaired away until its keepers are told. In these rooms the lines limit the clause where the design is settled. About half say that members who know of the change reject it, so repair or recolouring enforces a competing design, and telling does not settle it. The others say the record does not show the untold keepers, the agreed change or the loss that the clause needs. The frozen clause holds here only in part.
• F08 (move 209, merging; branch named; level third; parent none). Key: add-step:P14:T3-028. 50 members. Kind: specification (specification 55, elaboration 1), not relied on. machine hands kept on one target: installing, teaching and updating every runner. P14 says the room adjusts its machine hands. In these rooms the adjusting is a step of its own: members install the script and teach it, and they keep every runner's target current, because a stale target undoes the room's own new design. A revision must reach the operator and the target file, not only the people.
• F09 (move 210, merging; branch named; level fourth; parent none). Key: link:P03:T4-014. 54 members. Kind: specification (specification 53, elaboration 2), not relied on. the move returns to building: relocation followed by renewed construction. The model runs from building to keeping and, after a loss, to the move (P10), but no arrow runs from the move back to building. In these rooms it does: after a relocation the room recruits, designs and builds again at the new spot, and members report the new work.
• F10 (move 211, merging; branch named; level third; parent none). Key: add-step:P08:T3-010. 38 members. Kind: specification (specification 35, elaboration 4), not relied on. a deal carried out as work: prepared in the room, then implemented and relayed. P08 says rooms propose, settle and contest deals and hold each other to them. In these rooms a deal also takes work around it: members prepare it inside the room (local consensus, a contact, checks on the counterpart's credibility), and they carry it out by moving placed work, changing templates and bot targets, and relaying the terms to placers who do not know them.
• F11 (move 212, merging; branch named; level fourth; parent none). Key: add-step:P13:T4-028. 43 members. Kind: specification (specification 31, elaboration 12), not relied on. carrying on as renewed work, begun before the close. P13 says that near the close and after it the room decides what of its effort to keep. In these rooms carrying on is work in its own right, and it starts while placement is live: on another canvas the room recruits, builds and defends again, members remake the work in other media, and the mark is adopted into the room before the close.
• F12 (move 213, splitting; subform declared; level third; parent F11). Key: add-step:P13:T3-054. 22 members. Kind: specification (specification 11, elaboration 11), not relied on. the spine restarted on another canvas. Within F11, the room carries its work to a successor canvas, and there the spine runs again: recruiting, choosing a site, building, defending and losing work.
• F13 (move 214, splitting; subform declared; level third; parent F11). Key: add-step:P13:T3-057. 9 members. Kind: specification (specification 8, elaboration 1), not relied on. the work remade in other media, often before the close. Within F11, members remake the canvas work elsewhere (fan art, games, physical copies, a quoted text), and this often begins while the original is still live.
• F14 (move 215, splitting; subform declared; level third; parent F11). Key: add-step:P13:T3-156. 7 members. Kind: specification (specification 7), not relied on. the mark adopted as the room's emblem while it is still placed, damage included. Within F11, the room takes the mark into its own sub (banner, flair, a room feature) during placement, and it may adopt the damaged form as fitting.
• F15 (move 216, merging; branch named; level fourth; parent none). Key: add-step:P04:T4-008. 42 members. Kind: specification (specification 28, elaboration 15), not relied on. the plan kept current: correcting, updating and re-circulating the template. P04 says members circulate a template or coordinates and ask strays to keep to them. In these rooms the template needs upkeep of its own: members correct the reference against the canvas, replace stale plans, make updates noticeable, route helpers to the current version and message friendly placers who still follow a superseded one.
• F16 (move 217, merging; branch named; level third; parent none). Key: add-step:P23:T3-014. 35 members. Kind: specification (specification 35), not relied on. the chat kept open: invitations renewed, entrants screened, outcomes relayed to the thread. P23 (a candidate) says members move planning into a chat and invite helpers. In these rooms the chat's access is upkeep: members replace expired invitations and broken links, screen who comes in, and relay decisions back to the thread for those outside.
• F17 (move 218, merging; branch named; level fourth; parent none). Key: add-step:P11:T4-026. 36 members. Kind: specification (specification 32, elaboration 5), not relied on. the marking provisional and contested: success judged and credit disputed while the work goes on. P11 says that when a work is up the room marks it: announces, celebrates and credits. In these rooms marking comes while the work is still live and is open to dispute: success is judged by what survives, completion is provisional, upkeep goes on, and credit is challenged and corrected.
• F18 (move 219, splitting; subform declared; level third; parent F17). Key: add-step:P11:T3-009. 15 members. Kind: specification (specification 12, elaboration 3), not relied on. success judged while upkeep continues. Within F17, the room judges success by recognizable survival rather than a perfect mark, treats completion as a milestone, and keeps the obligation to maintain.
• F19 (move 220, splitting; subform declared; level third; parent F17). Key: add-step:P11:T3-043. 14 members. Kind: specification (specification 13, elaboration 1), not relied on. credit contested during the work. Within F17, members dispute and correct who made the work while it is still being placed: accusations, denials, competing labour claims and corrected omissions.
• F20 (move 221, merging; branch named; level third; parent none). Key: add-step:P12:T3-117. 10 members. Kind: specification (elaboration 4, specification 7), not relied on. the close as news: late arrivals told that placement has ended. P12 says the room records what happened and marks the end. In these rooms the end itself must travel: members who did not know offer to rebuild or ask for help, and others tell them that placement has ended and correct the stale call.
• F21 (move 222, merging; branch named; level fourth; parent none). Key: restrict:K01:T4-001. 32 members. Kind: specification (specification 30, elaboration 2), not relied on. the canvas call not a joke: the April Fools frame kept apart from the canvas work. K01 says that a claim in the host sub, a call to the canvas included, may be a joke. In these rooms the play stays with the sub's own business: its fakes and takeovers do not make the canvas calls jokes, and the frame does not decide what the canvas work was.
• F22 (move 223, merging; branch named; level fourth; parent none). Key: add-condition:P16:T4-017. 30 members. Kind: specification (elaboration 3, specification 28), not relied on. help conditional on the helper's own work and spare hands. P16 says rooms help one another, trade help and turn requests away. In these rooms help waits on conditions the statement does not hold: the helper's own work must be safe or finished, the helper must have pixels and time to spare, and the terms (space, non-interference, recognizable help) must hold.
• F23 (move 224, merging; branch named; level fourth; parent none). Key: add-condition:P13:T4-028. 30 members. Kind: specification (specification 25, elaboration 6), not relied on. the close scoped to the original canvas: continuation renewed, uncertain and contested. P13 places the decision near the close and after it. In these rooms the stop at hour 73 binds only the original canvas: on successor canvases placement goes on, and continuation is often one member's attempt, contested or unfinished, and conditioned on tolerable upkeep and access.
• F24 (move 225, merging; branch named; level fourth; parent none). Key: restrict:P14:T4-009. 27 members. Kind: specification (specification 27), not relied on. machine hands debated, not shown placing. P14 says members add placements with scripts, bots and spare accounts, and argue over them. In these rooms only the arguing part shows: scripts are offered, debated, refused or attributed to outsiders, and the room's own machine placement is not shown.
• F25 (move 226, merging; branch named; level fourth; parent none). Key: restrict:P13:T4-028. 27 members. Kind: specification (specification 29, elaboration 1), not relied on. carrying on in talk: proposals and single attempts, not shown taken up. P13 says the room decides what to keep. In these rooms carrying on shows as invitations, proposals and one member's attempt; collective uptake and durability are not shown, and some reuse begins during live placement.
• F26 (move 227, merging; branch named; level third; parent none). Key: restrict:P05:T3-010. 23 members. Kind: specification (specification 22, correction 1), not relied on. the telling clause not shown at the border: informed members contest the terms. As in F07, P05's added clause holds only in part, here where the planned change is a border or compromise agreed with a neighbour: members who know the terms contest them or refuse the concession, or the record does not show untold keepers or the loss.
• F27 (move 228, merging; branch named; level fourth; parent none). Key: restrict:P05:T4-013. 27 members. Kind: specification (specification 27, correction 1), not relied on. the telling clause not shown in keeping: interference seen, its cause and loss not. As in F07, P05's added clause holds only in part, here in watching, repairing and defending: interference with a planned change is seen, but who was told, whether keepers knew, and whether the change was lost for want of telling are not, and informed disagreement also occurs.
• F28 (move 229, merging; branch named; level third; parent none). Key: add-condition:P16:T3-010. 22 members. Kind: specification (specification 20, elaboration 3), not relied on. help at the border conditional: on the home work, the terms and harm to a third room. As in F22, help waits on conditions the statement does not hold, here where neighbours settle borders: the helper's home work comes first, help depends on stopping attacks or on sparing a work, it can entail destroying a third room's mark, and offers often stay offers.
• F29 (move 230, merging; branch named; level third; parent none). Key: add-condition:P23:T3-014. 25 members. Kind: specification (specification 25), not relied on. the chat's reach conditional: access, and the return of decisions to the thread. P23 (a candidate) says members move planning into a chat and bring its decisions back. In these rooms the chat's reach depends on working access, and those outside it learn only what returns to the thread; its decisions do not bind those who cannot see them.
• F30 (move 231, merging; branch named; level third; parent none). Key: restrict:P23:T3-014. 24 members. Kind: specification (specification 24), not relied on. the chat seen only through its invitations and returned reports, not its choices. P23 (a candidate) says the room's design, borders and diplomacy can be settled in the chat. In these rooms the record shows only the outside of the chat: invitations, venue proposals and reports that come back. Its deliberation, membership and authority are not shown.
• F31 (move 232, merging; branch named; level third; parent none). Key: restrict:P19:T3-010. 22 members. Kind: specification (specification 22), not relied on. hosting as one-off permission: requests and leave, no standing host rule. P19 says one room's work lives on another's mark under the host's rule, with hosts ruling on requests. In these rooms hosting shows only as a guest's request and a one-off permission, often provisional or contested; a standing host rule, an approval procedure or durable guest status is not shown.
• F32 (move 233, merging; branch named; level third; parent none). Key: link:P05:T3-009. 21 members. Kind: elaboration (elaboration 18, specification 3), not relied on. the marking returns to keeping: celebration followed by renewed defence. The model runs from building to marking (A07) and from building to keeping (A03), but not from marking back to keeping. In these rooms it does: a celebration or completion post draws renewed defence calls, repair and night cover in its own thread.
• F33 (move 234, merging; branch named; level fourth; parent none). Key: add-step:P04:T4-006. 23 members. Kind: specification (specification 19, elaboration 4), not relied on. the plan kept current while the design settles. As in F15, the template needs upkeep of its own, here while the design is still being settled: members check details against one another's instructions, correct and replace the reference, retire outdated posts and message overwriters, so that one updated plan replaces competing ones.
• F34 (move 235, merging; branch named; level fourth; parent none). Key: add-condition:P02:T4-006. 22 members. Kind: specification (specification 16, elaboration 6), not relied on. the design sized to the hands: scale and detail conditioned on crew, upkeep, space and colours. P02 says the room settles what its mark will show. In these rooms the design is conditioned by what the room can build and keep: its scale and detail depend on the crew it can assemble, the upkeep it can sustain, the space it can protect and the colours available.
• F35 (move 236, merging; branch named; level third; parent none). Key: add-step:P01:T3-002. 18 members. Kind: elaboration (elaboration 17, specification 1), not relied on. the call made workable: answers ask for a task, and callers supply it. P01 says the room calls members and kindred subs to place. In these rooms answering a call is an exchange: a willing member asks what to do, where to start or for backup, and the caller supplies instructions, location cues and visibility (a sticky, other venues), reaching people beyond the room.

Groups read at D4a-02 and set aside

Eight keys did not pass cut rule R2. Their lines state several different changes, or restate what the element's statement holds (R1c).

• add-condition on P05 at T4-013 (43 rooms): members' time and sleep, a stale display, repair that keeps an alteration, upkeep beside growth, upkeep of others' work, and the evidence for the planned-change clause.
• add-step on P02 at T4-006 (41 rooms): polls, provisional fixes, feasibility tests and adopted alterations, most held by 'the room argues its design'.
• add-step on P05 at T4-013 (40 rooms): checking whether a pixel was intended, shifts and handoffs, ranking repair against extension, defence during building; partly held by 'puts upkeep before growth'.
• add-step on P20 at T4-002 (36 rooms): finer forms of the megathread, the removals by rule and the venue that the statement holds.
• add-step on P12 at T4-027 (33 rooms): several steps of recording; its child T3-117 states one and is cut on its own (F20).
• add-condition on K01 at T4-001 (31 rooms): offence and hurt, who can see the joke, and the frame kept apart from the canvas; 15 of its rooms are in F01.
• add-condition on P08 at T4-016 (29 rooms): several conditions of deals; the commonest, that a deal binds only placers who know and accept it, is held by P21 and A19.
• add-condition on P14 at T4-009 (28 rooms): mostly F08's change (targets kept in step) and the rest of several kinds.

Families: one change at several nodes

A branch is keyed at one node, so a change the rooms make in several settings appears as several branches. The ladder joins them only at the dimension or the bare target, where a group is a grouping, not a branch (cut rule R4). The families are named here for D5:

• P05's added clause holds only in part: F07 (where the design is settled), F26 (at the border), F27 (in keeping). In F07 about half the lines say that informed members reject the planned change, and the rest that the record does not show the untold keepers; F26's and F27's lines say one or the other. Together they hold 108 rooms. This is the trunk's limit beside F-024's branch, 'the shape read', and the held proposal of move 198.
• Keeping the shared instruction current: F15 and F33 (the template), with F08 (the machine targets). A stale plan or target undoes the room's own new work, as P05's known-form repair does with people.
• Help conditional: F22 and F28.
• Carrying on: F11 with its subforms F12 to F14, F23 and F25.
• The chat: F16, F29 and F30.
• New links the model lacks: F09 (the move back to building) and F32 (the marking back to keeping).

The overlap

476 rooms are in at least one branch. By the number of branches they are in (subforms counted): 1: 200, 2: 127, 3: 92, 4: 36, 5: 11, 6 or more: 10. crosslinks.jsonl holds 759 lines over 348 pairs of branches that do not nest. The branches cut across one another rather than partition the rooms: a room makes several element-level changes at once. They are facets of the rooms' adaptations, not exclusive forms, and D5 reads them so.

Where the cuts stop

The cuts stop with F35. Every element change key at level 4 held by 20 rooms or more has been read: D4a-01 read K01's, and D4a-02 the other 31. Keys held by 5 to 19 rooms at level 4 were not read for a cut, since J's credit limit (QD4-001) ends the run soon. The rooms they hold, and in no branch, are named below with their counts. This is a stopping rule by key size, not a claim that the smaller keys hold no form.

The comparison (QD4-002)

The comparison was declared in notes-D4.md before its script ran. It did not run: the engine stops on the 335 second-order themes placed on the two residue third-order themes (T3-017 and T3-133), which no fourth-order theme gathers. The question is with J (QD4-002). The projections follow the comparison and are not built either.

The accounting at D4a-02 (stage D4 section 4), against n_analysed

n_analysed = 705. In a branch: 476. The unadapted group: 0 (no room returned none). Adapted but in no branch: 229. Unreturned at D2: 0. The four counts sum to 705, the analysed set.

Adapted but in no branch, each with why. Each holds accepted keys, so none is unadapted, and none holds a key that was cut. The number after each room is how many element change keys at level 4, held by 5 to 19 rooms, it holds: the keys below the pass's size rule. A room marked 0 holds none: its change keys are its own or on arrows, or its lines are specifications only.

2007scape (3); aceattorney (1); AceOfAngels8 (0); achievement_hunter (2); aggies (2); ainbowroad (6); albania (0); alberta (0); anarchism (2); anarcho_capitalism (2); anarchocapitalism (0); androidgaming (1); apocalypserising (0); araragi (2); argentina (2); armenia (3); aromantic (2); asexual (1); asktransgender (1); auburn (2); austria (4); austriahungary (1); azores (0); bangladesh (2); bannedfromanime_irl (0); batman (1); bdsm (1); bees (0); bigbang (0); bih (1); bitcoin (2); blackmirror (2); bobross (0); brasil (3); Bravenewbies (1); Braveryjerk (0); bretagne (3); bulgaria (5); cardinals (1); carletonu (0); chicubs (3); churchofhelix (0); cirkeltrek (1); CKCrusaders (4); Clannad (1); cmu (1); completeanarchy (3); compsoc (1); Cornwall (1); COSI (0); costa_rica (3); counting (1); CryptoFR (2); cuboulder (1); daftpunk (3); DatBoi (1); detroitredwings (2); DevonUK (1); diablo (3); DiamondClub (1); dmt (2); dofus (0); Dominican (4); Dorset (1); drugs (1); duckgame (1); ducks (0); eagles (0); edmontonoilers (7); ElSalvador (2); england (1); europe (3); evedreddit (0); FinalFantasy (2); finland (1); fireemblem (2); FlipnoteStudio3D (1); floridagators (2); foxstevenson (2); france (1); futanari (1); GabrielDropout (2); gameboy (1); genderfluid (1); germany (3); giantbomb (4); glasgow (1); Goodboye (4); gratefuldead (2); greenbaypackers (2); GreenCorner (2); GreenEmpire (0); greenland (0); GrowTheTree (2); guatemala (1); halo (2); haskell (0); homelab (1); HomestarRunner (2); Homura (1); Honduras (2); hoodr (1); hsv (3); iastate (2); ibo (2); iceland (1); ireland (2); k_on (3); landry (2); latin (4); latvia (0); leafs (3); leagueoflegends (2); lexington (1); littlebusters (0); lost (2); Lugarix (0); Madeon (0); madokamagica (4); malta (3); math (1); mcgillrobotics (0); MiamiHurricanes (1); mizzou (1); monsterhunter (1); mordhau (2); mysterydungeon (2); n64 (0); natsume (2); neutralmilkhotel (2); nonbinary (0); norge (0); Northwestern (4); norway (4); NovaScotia (0); npr (3); nVade (5); nyu (3); oltp (1); oman (0); oneshot (4); orderofthebluecorner (1); overwatch (4); pansexual (3); parabola (1); paranatural (5); partyparrot (2); pathofexile (5); peterdraws (1); pgang (0); Pigifs (1); PinkUnion (5); PinkVomitMonster (1); placecanada (4); placehearts (1); placehfarts (0); placesnek (4); PokemonSage (0); Produce101 (0); ProfessorLayton (4); qotsa (1); quq (0); rainbowgrid (4); ReBoot (1); Redox (0); redvsblue (1); rit (5); rocketleague (3); rojava (3); roosterteeth (3); Russiaclan (4); sakartvelo (0); sakuragakuin (3); ScottPilgrim (1); seventeen (1); shrooms (0); signal (0); singapore (4); Slovakia (1); snsd (3); sonicthehedgehog (5); startrek (0); stlouisblues (2); straya (3); Summit1G (3); suomi (4); sweden (2); SydneyFC (0); teamcube (5); TeamDignitas (1); TeamYellowPlace (2); telegram (1); tetris (0); texastech (1); the_pack (2); TheAdventuresofTintin (1); TheB1G (1); Thegreatblackhole (3); TheGreatGreenBox (1); TheID (0); theitalyplace (1); thesilphroad (1); thetreesnetwork (1); traaaaaaannnnnnnnnns (7); transgender (1); TreePlace (2); trees (3); truestl (3); ufl (2); uiowa (2); UMiami (0); UNLincoln (0); uruguay (2); uva (5); vegan (2); VelvetUnderground (1); vermont (2); vietnam (1); Villanova (1); wales (3); wario (0); watchmen (0); winnipegjets (2); worldpowers (2); wsu (1); xenoblade_chronicles (6); yerbamate (0); yumenikki (1); yuyuyu (3).

The comparison (section 5), read at D4a-03

Run at D4a-03 on chunk-comparison-v1.1 (engine sha256 c8d2eb8c7c30...), a departure declared before the run (departures.jsonl line 10; QD4-002), with the stage file's command and defaults: a = 1.0, seeds [0, 1], 200 bootstrap draws and 100 permuted copies per seed. It reads the concept store, the placements, the tiers, the dropped cases and the prior. No verdict, canvas field or branch entered its feature space. Its features are 28 fourth-order themes over 705 rooms; empty compositions: 0. It is a non-adaptation baseline that shares the inductive coding structure, not theory-free evidence.

• All rooms (705 rooms): status supported-diagnostic-cut; k carried 4. At k 4: seed 0: silhouette 0.024, real stability mean 0.151 and median 0.154, null 0.099 and 0.082, margins +0.052 and +0.072, null 95th percentile 0.220; seed 1: silhouette 0.024, real stability mean 0.162 and median 0.160, null 0.108 and 0.099, margins +0.054 and +0.061, null 95th percentile 0.208. The k that clear under both seeds: 3, 4, 5, 6, 7, 8, 9, 10, 11, 12. The largest silhouette at any k under seed 0 is 0.051. The median own-data weight is 0.990. Against the carried Ward/CLR labels at k 4, the Jaccard presence and Hellinger share partitions give ARI -0.007 and -0.008, and a/10 and 10a give 0.145 and 0.164.
• Without the low-information rows (626 rooms): status supported-diagnostic-cut; k carried 2. At k 2: seed 0: silhouette 0.097, real stability mean 0.173 and median 0.146, null 0.074 and 0.017, margins +0.099 and +0.129, null 95th percentile 0.380; seed 1: silhouette 0.097, real stability mean 0.184 and median 0.144, null 0.060 and 0.014, margins +0.124 and +0.130, null 95th percentile 0.307. The k that clear under both seeds: 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12. The largest silhouette at any k under seed 0 is 0.097. The median own-data weight is 0.991. Against the carried Ward/CLR labels at k 2, the Jaccard presence and Hellinger share partitions give ARI 0.014 and -0.005, and a/10 and 10a give 0.143 and 0.556.
• The tier check (descriptive, not proof of form): at k 4, dimension ARI 0.110 and third-tier ARI 0.170. The third tier has 195 columns and 13.52 nonzero per room (6.9 per cent), so its profiles are sparse.
• Low-information rooms (fewer than five placed themes): 79, kept in the primary run and removed in the second.
• The clusters (two-letter codes; no mechanism labels; best-match Jaccard against the branches is descriptive, and ARI against the branches is undefined, since they overlap):
  • VA: 176 rooms, 0 low-information; largest profile shares T4-001 0.256, T4-013 0.112, T4-016 0.099; median concepts 182; mean residue share 0.019; best-match branch F01 (Jaccard 0.187).
  • IT: 292 rooms, 72 low-information; largest profile shares T4-001 0.241, T4-006 0.090, T4-016 0.077; median concepts 56; mean residue share 0.023; best-match branch F01 (Jaccard 0.135).
  • TX: 155 rooms, 5 low-information; largest profile shares T4-013 0.120, T4-006 0.112, T4-016 0.101; median concepts 91; mean residue share 0.010; best-match branch F08 (Jaccard 0.096).
  • CH: 82 rooms, 2 low-information; largest profile shares T4-006 0.127, T4-016 0.112, T4-013 0.087; median concepts 187; mean residue share 0.011; best-match branch F08 (Jaccard 0.100).

The residue share per room (QD4-002)

v1.1 counts a second-order theme placed only on the residue themes T3-017 (carrying on ordinary sub talk) and T3-133 (recovering a hacked sub) with the unplaced concepts, apart from the composition. 199 rooms hold residue concepts (335 themes, 1982 concepts). The residue share is the room's residue concepts over its placed and residue concepts: median 0.000, mean 0.018, maximum 0.503. 78 rooms are at 0.05 or more, 39 at 0.10 or more and 7 at 0.30 or more. Rooms at 0.20 or more: counting 0.50, Madeon 0.44, SydneyFC 0.42, aeskwadraat 0.39, Braveryjerk 0.33, wine 0.32, androidgaming 0.30, soylent 0.29, mls 0.23. For these rooms the composition leaves out a large part of what the coders coded, the room's own ordinary business.

The volume check (section 5), and the size of the rooms

The volume field is the comparison's own count of unique concepts per room (median 101; quartile cuts 50, 101, 209). Percentiles are against random groups of the same size from the 705 rooms (2,000 draws, seed 0).

• The volume verdict for the clusters. The cluster labels explain 0.255 of the variance in log concepts (eta squared), at the 100.0th percentile of the permutation null (null maximum 0.026). By concept quartile (smallest first): VA 3 34 61 78; IT 137 66 48 41; TX 31 64 35 25; CH 5 13 33 31. So the carried partition largely separates rooms by how much the coders coded.
• Branches and size. In a branch, by quartile: 63 122 149 142; in no branch: 113 55 28 33. 11 of 35 branches have a median room size at or above the 95th percentile, and 0 at or below the 5th. A larger room holds more lines and more keys, so it has more chances to share one; the branches lean to the larger rooms for that reason, at least in part. A correlation or this null alone cannot show that a branch's difference is independent of size.

The projections (section 6), after every cut was snapped

python3 tools/projections.py (2,000 permutations, seed 0) wrote projections-D4.jsonl, one line per branch and per cluster. Its verdict for a room is my last ruling at D3, else the readers' agreed verdict, so the first return and the re-check are mixed. The canvas sentence it carries: "The atlas records what survived the last hour of a 97-hour event; it is not a measure of skill, and a large area is not evidence of good organizing (contract section 5)." Each line below gives the verdict counts (composes, with residue, does not compose, cannot tell), the percentile of the does-not-compose share, the median area in pixels with its percentile, and the group's median room size with its percentile.

• F01: 54, 49, 0, 0; does-not-compose percentile 43.5; median area 610.5 px, percentile 67.1; median size 201 concepts, percentile 100.0.
• F02: 18, 15, 0, 0; does-not-compose percentile 47.4; median area 789.0 px, percentile 89.0; median size 223 concepts, percentile 100.0.
• F03: 9, 9, 0, 0; does-not-compose percentile 48.8; median area 349.0 px, percentile 9.4; median size 158 concepts, percentile 93.1.
• F04: 4, 9, 0, 0; does-not-compose percentile 49.0; median area 957.5 px, percentile 88.8; median size 243 concepts, percentile 99.3.
• F05: 6, 6, 0, 0; does-not-compose percentile 49.0; median area 706.5 px, percentile 67.8; median size 183 concepts, percentile 94.7.
• F06: 5, 3, 0, 0; does-not-compose percentile 49.3; median area 1535.25 px, percentile 95.0; median size 308 concepts, percentile 99.5.
• F07: 21, 38, 0, 0; does-not-compose percentile 45.9; median area 770.0 px, percentile 95.3; median size 145 concepts, percentile 98.8.
• F08: 21, 29, 0, 0; does-not-compose percentile 46.6; median area 821.5 px, percentile 96.2; median size 123 concepts, percentile 87.8.
• F09: 22, 32, 0, 0; does-not-compose percentile 45.5; median area 464.25 px, percentile 16.2; median size 127 concepts, percentile 91.9.
• F10: 16, 22, 0, 0; does-not-compose percentile 47.4; median area 696.0 px, percentile 77.7; median size 93 concepts, percentile 27.3.
• F11: 18, 25, 0, 0; does-not-compose percentile 46.7; median area 985.5 px, percentile 99.2; median size 144 concepts, percentile 96.2.
• F12: 9, 13, 0, 0; does-not-compose percentile 48.6; median area 777.0 px, percentile 82.8; median size 114 concepts, percentile 68.6.
• F13: 2, 7, 0, 0; does-not-compose percentile 49.2; median area 3202.0 px, percentile 100.0; median size 239 concepts, percentile 98.2.
• F14: 4, 3, 0, 0; does-not-compose percentile 49.5; median area 588.0 px, percentile 50.7; median size 132 concepts, percentile 71.0.
• F15: 20, 22, 0, 0; does-not-compose percentile 46.8; median area 554.75 px, percentile 39.0; median size 86 concepts, percentile 13.8.
• F16: 13, 22, 0, 0; does-not-compose percentile 47.8; median area 1127.5 px, percentile 99.5; median size 129 concepts, percentile 85.2.
• F17: 12, 23, 0, 1; does-not-compose percentile 47.0; median area 601.25 px, percentile 51.9; median size 104 concepts, percentile 52.5.
• F18: 4, 11, 0, 0; does-not-compose percentile 48.9; median area 462.0 px, percentile 28.9; median size 123 concepts, percentile 71.1.
• F19: 6, 7, 0, 1; does-not-compose percentile 49.1; median area 563.0 px, percentile 45.4; median size 89 concepts, percentile 30.6.
• F20: 2, 7, 0, 1; does-not-compose percentile 49.5; median area 839.0 px, percentile 77.5; median size 90 concepts, percentile 34.3.
• F21: 21, 10, 1, 0; does-not-compose percentile 97.4; median area 406.0 px, percentile 10.8; median size 116 concepts, percentile 74.4.
• F22: 13, 17, 0, 0; does-not-compose percentile 47.6; median area 360.5 px, percentile 6.6; median size 109 concepts, percentile 62.4.
• F23: 8, 22, 0, 0; does-not-compose percentile 47.6; median area 2096.0 px, percentile 100.0; median size 147 concepts, percentile 94.5.
• F24: 12, 15, 0, 0; does-not-compose percentile 48.0; median area 655.0 px, percentile 69.7; median size 144 concepts, percentile 91.6.
• F25: 15, 11, 1, 0; does-not-compose percentile 98.0; median area 1237.5 px, percentile 99.1; median size 196 concepts, percentile 99.5.
• F26: 10, 13, 0, 0; does-not-compose percentile 48.4; median area 1008.0 px, percentile 95.9; median size 135 concepts, percentile 86.0.
• F27: 9, 18, 0, 0; does-not-compose percentile 48.0; median area 1389.5 px, percentile 99.4; median size 196 concepts, percentile 99.8.
• F28: 11, 11, 0, 0; does-not-compose percentile 48.6; median area 1005.5 px, percentile 96.2; median size 120 concepts, percentile 74.0.
• F29: 8, 17, 0, 0; does-not-compose percentile 48.2; median area 1800.0 px, percentile 100.0; median size 238 concepts, percentile 100.0.
• F30: 7, 17, 0, 0; does-not-compose percentile 48.2; median area 836.5 px, percentile 88.0; median size 139 concepts, percentile 88.4.
• F31: 12, 10, 0, 0; does-not-compose percentile 48.6; median area 663.25 px, percentile 67.0; median size 161 concepts, percentile 96.1.
• F32: 5, 16, 0, 0; does-not-compose percentile 48.5; median area 1158.0 px, percentile 98.0; median size 140 concepts, percentile 86.5.
• F33: 10, 13, 0, 0; does-not-compose percentile 48.4; median area 633.0 px, percentile 61.0; median size 86 concepts, percentile 22.6.
• F34: 9, 13, 0, 0; does-not-compose percentile 48.6; median area 442.0 px, percentile 22.7; median size 95 concepts, percentile 37.1.
• F35: 8, 10, 0, 0; does-not-compose percentile 48.8; median area 374.25 px, percentile 12.8; median size 98 concepts, percentile 43.9.
• VA: 64, 112, 0, 0; does-not-compose percentile 38.4; median area 1016.0 px, percentile 100.0; median size 182 concepts, percentile 100.0.
• IT: 165, 116, 1, 10; does-not-compose percentile 79.8; median area 312.0 px, percentile 0.0; median size 56 concepts, percentile 0.0.
• TX: 73, 82, 0, 0; does-not-compose percentile 39.3; median area 642.0 px, percentile 84.2; median size 91 concepts, percentile 5.4.
• CH: 28, 54, 0, 0; does-not-compose percentile 44.3; median area 914.25 px, percentile 99.8; median size 187 concepts, percentile 100.0.

Reading. The one room that does not compose, picturegame (out-of-scope), lies in F21 and F25, so their does-not-compose percentiles are high; every other group's is near the middle. The canvas percentiles follow room size: the groups of large rooms (VA, CH, F11, F23, F29) have large median areas, and IT, the cluster of small rooms, has the smallest. No cut rests on the canvas or the verdicts; each cut was snapped before these were computed (rule 7).

What was drawn, and what was not

• Drawn as views, from the carried distance: the average-linkage dendrogram (_views/dendrogram.nwk), a chain with no partition, and the leaf-to-root view (_views/adaptation-tree.html, .svg, .json), whose root is the frozen global model and whose JSON carries the branches and cross-links. Neither is read as a chronology, an ancestry or a validated hierarchy.
• Not drawn: the NeighborNet (outside the run, if asked), and any tree of forms. The branches overlap (759 cross-links), so they are not a tree; they are facets of the rooms' adaptations.

The final accounting (stage D4 section 4)

Against n_analysed = 705: 476 rooms in a branch, 0 in the unadapted group, 229 adapted but in no branch, 0 unreturned; the four sum to 705. The rooms in no branch are named, with their counts, in the accounting at D4a-02 above; no branch changed since.

How the rooms are allocated to the room forms

Leg D4a-08, 26 October 2026. J ruled through the handler (22:18 Berlin): "6 it is. Please tell the agent to document how they are allocated and the allocation it did earlier, as we need this soon. Also they need to push the full analysis down to the leaves so we get all the further cuts at smaller levels. Not that they needed it, but we do for the graph." The amendment is dated in departures.jsonl (line 16).

The room forms are the six forms of D4a-08c. Sections 1 to 3 say how every room reaches its form. Section 4 describes the tree below the forms, written for the figure. Section 5 gives the earlier allocations in order. The room forms are an addition after the 35 branches, not a recut. branches.jsonl, crosslinks.jsonl, tree-D4.md, room-forms-D4a05.* to room-forms-D4a08c.* and every D5 file are unchanged.

1. The six forms

Each of the 705 analysed rooms is in exactly one form. Defining rooms shaped the forms. Thin rooms and core rooms were placed afterwards (steps 8 and 9). The forms are lettered by their number of defining rooms, largest first; C and D tie at 96. The largest form holds 2.96 times as many rooms as the smallest. Each form's pattern and whether a differing account could be written are in room-forms-D4a08c.md.

2. How a room reaches its form

A room is compared with the others by two profiles. The change profile records where the global model failed the room. The code profile records what the room did. The rule of each step was logged in the diary before its script ran.

Step 1. The rooms and their changes. The unit is the room. A room's selected changes are its ledger lines, accepted or modified at adjudication, that change the model: the ops restrict, add-step, add-condition, link and contradict. Lines that instantiate an element or record an absence change nothing and are left out. 6,637 lines are selected. 6,634 of them carry a lift up the ladder and are used; three carry none. 684 rooms hold at least one selected change. 21 rooms hold none, and they are the core.

Step 2. The change profile. Each selected line counts at three levels of the ladder: its third-order theme, its fourth-order theme and its dimension. Its lift gives these nodes, starting from the second-order theme the line was written from. Two kinds of lines also count as links between nodes.

• An arrow line changes one of the model's arrows. It counts as a link from the arrow's source element to its target element. Each end reaches the ladder through the element's anchors in model/elements.jsonl. At the fourth-order level the end takes the element's fourth-order themes, and a third-order anchor is taken up to its fourth-order theme. At the dimension it takes the dimension that holds that theme. At the third-order level it takes the element's third-order anchors where it has them; otherwise the line's own third-order theme, if that theme lies under the end; otherwise the end's fourth-order theme. One element, P15, is anchored outside the ladder, so its end stays at the element.
• A link-op line proposes a connection the model lacks. It counts as a link from the line's own node to the element's anchor.

An arrow line or a link-op line gives half its weight to its own node and half to its link. A link with several pairs of ends is split equally over the pairs. Every other line gives its whole weight to its node. Columns held by only one defining room are dropped. That leaves 406 third-order columns (262 of them links), 200 fourth-order columns (172 links) and 67 dimension columns (59 links), 673 in all.

Within each level, a room's counts become shares. So rooms are compared by the mix of their changes, not by their number. Each share is replaced by its square root and divided by the square root of 6. The squared distance between two rooms is then the mean, over the three levels, of the squared Hellinger distance between their shares. Each level counts equally. A room with no change sits at 0, the global model with nothing changed.

Step 3. The code profile. A room's coded concepts (package/store/codes.jsonl, 115,388 concepts in the 705 rooms) go up the ladder through the placements of their second-order themes (assignments_final.jsonl). They reach the third-order themes, the fourth-order themes (fourth/fourth.jsonl) and the dimensions (dimensions.jsonl). A concept whose second-order theme is placed in several third-order themes is split equally over them. 407 concepts have no placement and do not count. Columns held by only one defining room are dropped. That leaves 183 third-order columns, 28 fourth-order columns and 8 dimension columns, 219 in all.

Within each level, a room's value on a node is its share of its concepts there minus the mean share over all 705 rooms. This follows J (21:09 Berlin): "Tell it to use the code counts as deviations from a mean normalized use. Same as the changes, 0 should be the global model." A room that uses its codes like the average room sits at 0. The deviations are not divided by their spread. With z-scores a rare theme would weigh as much as a common one, and a room with few codes would take large scores from one or two concepts.

Step 4. The weighting. Each block is scaled to the same total variance over the 558 defining rooms. The change block is scaled as a whole. The code block is scaled level by level, each level at one third of the block. Then the change block is multiplied by the square root of 2/3 and the code block by the square root of 1/3. So the changes hold two thirds of the total variance and the codes one third. A room is one point in 892 columns. The distance between two rooms is the Euclidean distance between their points.

Why two thirds: the changes cluster weakly and the codes strongly. At equal weight (D4a-08) the cut follows the codes and loses the forms of rooms that changed the model in the same way. At two thirds, the eight-form cut keeps 82 per cent of the structure that the changes alone show and 77 per cent of the structure that the codes alone show (room-forms-D4a08b.md, section 1).

Step 5. The floor. A room shapes the forms only if it holds 5 or more selected changes; below that its mix is too coarse. 558 rooms define the forms. The 126 thin rooms, with 1 to 4 selected changes, are placed afterwards.

Step 6. Ward's method. The 558 defining rooms are joined by Ward's method (SciPy linkage, method ward, on the 892 columns). Each join merges the two groups whose merging adds least to the spread within groups. The method seeks compact groups and favours groups of similar size.

Step 7. The cut. The tree is cut into six groups (SciPy fcluster, maxclust 6), and these are the forms. The count is J's ruling, from the counts I offered at D4a-08c; no measure chose it. The six-group cut lasts 0.178 in merge height, the third longest between four and eight (four lasts 0.392, seven 0.272). Stability on matched subsamples is about 0.21 at every count from four to eight. A shuffled null cannot be used with the codes in (room-forms-D4a08.md, section 3).

Step 8. Thin rooms. A thin room has both profiles, built the same way and scaled by the same factors. It goes to the form whose centre is nearest in the 892 columns. A form's centre is the mean point of its defining rooms.

Step 9. The core. A core room has no selected change, so its change profile is 0, the global model. It goes to the form whose centre is nearest in the code columns only. The full distance would add each centre's distance from 0 in the change columns. It would then favour the form whose change centre lies nearest the global model, whatever the room's codes. r/startrek (137 coded concepts) and r/n64 (22) go to E, the April Fools play. The other 19 core rooms hold 1 to 8 coded concepts each, so their placement rests on a handful of codes. The core adds 2 to 6 rooms to each form.

What does not enter. No canvas field, verdict, branch or outcome enters the allocation. The signatures and accounts in room-forms-D4a08c.md describe the forms after the cut; they place no room.

3. How sure the allocation is, and how to reproduce it

The forms are poles of a continuum, not separate kinds. Their stability is low (about 0.21), and many rooms lie between forms. A defining room's form is the Ward group it fell in. A thin or core room's form is a placement at the nearest centre, and it is weaker. A core room's placement rests on its codes alone.

To reproduce, run from the folder root with Python 3, NumPy and SciPy:

python3 out/_analysis/d4a08c_room_forms.py > out/_analysis/d4a08c_forms.json
python3 out/_analysis/d4a08d_room_tree.py > out/_analysis/d4a08d_tree.json

The first script builds the two profiles, the weighting and the Ward tree. It places the thin and core rooms and cuts at four to eight; d4a08c_write.py wrote room-forms-D4a08c.* from its output. The second script repeats the same construction and stops unless it gives the same six forms. It then writes the data for the tree below them (section 4). The change features are computed in out/_analysis/d4a07_features.py, and the ledger is read through tools/adaptation_ledger.py. The inputs, all in out/, are adaptations.jsonl, adaptations-recheck.jsonl, adjudications.jsonl, adaptation-returns.jsonl, model/elements.jsonl, model/arrows.jsonl, assignments_final.jsonl, fourth/fourth.jsonl and dimensions.jsonl, with package/store/codes.jsonl. The first script also reads scheme_final.jsonl for theme names and branches.jsonl to count the takeover rooms in its report; neither enters the distance. Ward's method has no random start, so the result is the same at every run.

4. The tree below the six forms, for the figure

J asked for every further cut below the six. The splits below the forms are the same Ward tree written down to single rooms. They are not named or argued.

The files.

• room-forms-tree.nwk: the tree over all 705 rooms, in Newick format. The leaves are room names, and internal nodes carry their labels. Branch lengths are differences in Ward merge height, so every room lies at the same distance from the root (8.9236).
• room-forms-tree-linkage.tsv: the same tree as a SciPy linkage, one row per join in order of height (704 rows). node is the new node's id; rooms are 0 to 704, in the order of the room table. a and b are the two nodes joined. height is the merge height, and rooms counts the rooms under the node; these four columns load as a SciPy linkage matrix. kind is ward for a join of the Ward tree and placed where a thin or core room hangs from the room it reached. The other columns are label, ward_node (the node's id in the 558-room Ward tree), k_from and k_to (the cuts at which the node is a group) and placed_room.
• room-forms-tree-rooms.tsv: one row per room. It gives the room's role (defining, thin or core), its counts of selected changes and coded concepts, and its form and form name. It gives its label at every cut from k = 2 to 30, and its address down to its leaf. For a placed room it adds how the room was placed, the room it reached, its distance to that room, its drawn height and whether that height was capped.

The labels. Above six, a group is named by the forms it holds, for example B+C. At six, the label is the form's letter. Below six, when a group splits, the larger part takes the group's label plus .1 and the smaller part the label plus .2. So a room's label at a finer cut always extends its label at a coarser cut. The address, the label of the room's leaf, holds every cut at once. For example, a room with the address C.1.2 is in C at six, in C.1 once C splits, and in C.1.2 once C.1 splits. The cut at k is the set of groups left when the joins of the Ward tree are undone from the top until k groups of defining rooms remain.

How placed rooms descend. A thin or core room keeps its form at six. Below six it follows the rule that placed it. At each split it goes to the part whose centre is nearer: by the whole mix for a thin room, by the code columns for a core room. It goes down to one defining room. Above six it takes the merged group that holds its form. In the drawn tree it hangs from the room it reached, at its distance to that room. Where that distance is greater than the height at which the reached room joins the tree, the drawn height is capped at that height, so heights never fall going up. 117 of the 147 placed rooms are capped, and their drawn height shows where they hang, not how near they are. 130 of the 147 meet at least one split where the two centres lie within 5 per cent of each other, so their labels below the forms are weak. I would draw the placed rooms apart from the defining rooms, for example in another colour.

Against the four and eight forms of D4a-08c. In room-forms-D4a08c.tsv the thin and core rooms were placed at each count on their own, so their groups at four and eight did not always nest in their form. Here they nest. 17 placed rooms take a different group at four (16 thin, 1 core), and 17 at eight (13 thin, 4 core). Every room's form at six is unchanged, and so is every defining room's group at every count. The nested sizes are as follows:

• At four: B+C 266, D+F 175, A 166 and E 98 (D4a-08c gave 262, 175, 170 and 98).

• At eight:

  • C (the design) 125;
  • D (keeping) 119;
  • B.1 (the chat and the scripts) 107;
  • E (the April Fools play) 98;
  • A.1 (the terms between neighbours) 96;
  • A.2 (the plan made and announced) 70;
  • F (the spot) 56;
  • B.2 (raiding) 34.

  D4a-08c gave, in the same order, 123, 113, 103, 98, 97, 82, 54 and 35.

The top of the tree. The first split (k = 2) separates the April Fools play (E, 98 rooms) from the other five forms (607). It is the last join, at a height of 8.92; the join before it is at 4.38. At k = 3 the other five part into A+B+C (432) and D+F (175).

Checks (_analysis/d4a08d_check.py, which reads only the written files):

• the six forms equal room-forms-D4a08c.jsonl for all 705 rooms;
• the cuts equal SciPy's fcluster at every k from 2 to 30;
• the labels nest at every cut below six;
• the full linkage is valid and monotone, and its cuts by height give the table's groups at every k from 2 to 30;
• the Newick holds each of the 705 rooms once, with no negative branch length.

5. The earlier allocations, in order

Each cut compared rooms, was an addition after the 35 branches, and sits in its own files, unchanged. Each was superseded by the next on J's word through the handler; none was withdrawn. Tier history moves 238 to 313 named their forms. Sizes are in rooms, in the order of the forms' letters; each ratio is the largest form against the smallest, the core aside.

D4a-05 (moves 238 to 245; room-forms-D4a05.*, script d4a05_room_tree.py).

• Compared: the selected changes only. Each line counted once at its third-order theme, its fourth-order theme and its dimension, at its own lift. A changed arrow counted at the theme of the room's evidence, so which arrow it changed did not enter. The report says an arrow counted "through the third-order theme of its source"; the script counted it at the line's own lift, as the D4a-07 report says. Shares were taken within each level, and third-order themes changed by one room only were dropped. The distance was the Hellinger distance, the three levels counting equally.
• Placed: all 684 rooms with a change, by Ward's method; a room's form was its Ward group. The 21 rooms with no change stayed apart as the core.
• Count and sizes: eight, by the logged rule: the highest silhouette with a bootstrap stability of 0.5 or more, else the most stable count. Every count fell below 0.5, so the most stable count was taken. The sizes were 152, 119, 103, 88, 83, 69, 42 and 28, and the core of 21 (ratio 5.43).
• Superseded because: the smallest form was built from thin rooms, the ratio was above J's bound of 3, the count rule favoured more groups, and J's placement rule had not been applied. I proposed these fixes in the interview, and J replied "Go ahead this sounds good" (19:50 Berlin). The 32 sub-forms declared below the eight (moves 246 to 277) were withdrawn by move 278, because the split below waited for J's talk (18:36 Berlin).

D4a-06 (moves 279 to 286; room-forms-D4a06.*, script d4a06_room_forms.py).

• Compared: the same as D4a-05, with the floor: only the 558 rooms with 5 or more selected changes shaped the forms.
• Placed: by J's rule, taken literally. Each room went to the form whose signature holds most of its selected changes, by count. A signature is the fourth-order themes that a form's defining members change at 1.5 times the defining population's share or more, in a third of them or more. A tie went to the nearest centre and was listed. A room with no change on any signature went by its whole mix. The core stayed apart.
• Count and sizes: the gap between merge heights carried five. Stability on matched subsamples against a shuffled null carried eight. By the logged rule I carried eight and gave five in full. The sizes were 135, 84, 89, 50, 62, 64, 124 and 76, and the core of 21 (ratio 2.70).
• Superseded because: J asked why arrows were not used (20:35 to 20:37 Berlin): "The arrow can work at any level. Just as the T3 are T4 and Ds."

D4a-07 (moves 287 to 294; room-forms-D4a07.*, script d4a07_room_forms.py).

• Compared: the change profile of step 2, with arrows and link-op lines as links at every level, and the floor of 5.
• Placed: by the whole mix. A defining room stayed in its Ward group, and a thin room went to the nearest centre. J's literal rule was reported beside it; under that rule 307 rooms would move. The core stayed apart.
• Count and sizes: eight; the gap and the stability agreed. The sizes were 148, 159, 87, 64, 60, 56, 59 and 51, and the core of 21 (ratio 3.12). The largest form was the middle, B: 159 rooms with a weak signature.
• Superseded because: J asked to use the code counts as well (21:05 Berlin): "How about using the code counts, dimensions for example, as well?"

D4a-08 (moves 295 to 299; room-forms-D4a08.*, script d4a08b_room_forms.py).

• Compared: the change profile of step 2 and the code profile of step 3, at equal weight by total variance. A first run on Hellinger distances between code shares was superseded by J's 21:09 message before it was delivered.
• Placed: by the whole mix of both blocks. The core stayed apart.
• Count and sizes: five, by the gap. Stability against a shuffled null could not choose, because the shuffled copies came out more stable than the data. The sizes were 182, 174, 133, 113 and 82, and the core of 21 (ratio 2.22).
• Superseded because: J asked which cut I would stand behind (21:24 Berlin). At equal weight the codes took over. The five forms explained 0.271 of the code variance and only 0.051 of the change variance. The forms of rooms that changed the model in the same way, machine hands and the spot, dissolved.

D4a-08b (moves 300 to 307; room-forms-D4a08b.*, script d4a08w_room_forms.py --w 0.6667).

• Compared: both profiles with the weighting of step 4: changes two thirds, codes one third.
• Placed: by the whole mix. The core stayed apart.
• Count and sizes: eight, chosen on substance: at eight every form has a change signature, so no form is a middle. The sizes were 121, 112, 102, 96, 96, 77, 49 and 31, and the core of 21 (ratio 3.90).
• Superseded because: J asked for fewer forms, asked why the core was still alone, and found the smallest forms small (22:00 Berlin): "Also 31, 21, 49 is quite small."

D4a-08c (moves 308 to 313; room-forms-D4a08c.*, script d4a08c_room_forms.py). The cut.

• Compared and placed: as in section 2, with the core placed by its codes.
• Count and sizes: six, with four offered as a one-line summary. The sizes are 166, 141, 125, 119, 98 and 56 (ratio 2.96).
• Ruled: J, 22:18 Berlin: "6 it is."

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 D4a-08, 2026-10-26 UTC, an extra leg after the branch accounts, closed on J's word (22:51 Berlin). 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. The comparison (v1.1) does not survive a change of distance; its clusters sort rooms by size (eta squared 0.255). 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. No arrow is testable; 12 names kept.
• 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; added after the accounts, not a recut). Room forms by changes (two thirds, arrows as links) and codes. J ruled six forms, core placed (room-forms-D4a08c.*); allocation in room-forms-allocation.md; tree to the leaves in room-forms-tree.*. The six forms stand (J, 22:51).

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.

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 families of changes as the next stage's material; 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: one account per room form (J, 22:51); the next stage then reads the notes: renamings, the two missing returns, the survival paragraph.

Notes, stage D4

D4a-01: the statistic, the sensitivity check, the first pass (one element), and the held proposals

Leg D4a-01, 24 October 2026 (UTC). The tree itself, its rules and its accounting are in tree-D4.md; the branches are in branches.jsonl, forms/ and crosslinks.jsonl. This file records what was done and why. J stops the run after this leg (QD4-001), so this pass is the last one the run makes.

J's message after the D3c interview, and what was done with each part

1. D3 stays frozen at 46384686, with no further re-check. Done. No labeler or reader was used.
2. The amendments to P05 and A11. They were made as recorded amendments under rule 11 (move 198 on P05, move 199 on A11; history lines 173 to 180), each marked not re-checked with the frozen version beside it. F-024 and F-017 were re-examined in the same act. P05 took the bound, not the widened revision. The reason: the bound keeps the words the 705 rooms were re-checked against and narrows where they hold, while the widened revision adds a route and a holder that no room was served and no re-check can test. A11 was withdrawn: it never beat its null; template first (98 rooms) is nearly as common as the transition (111) of the 228 rooms with both ends; the failure clause stands alone in 117 rooms (talk only 31, layout only 86); and 261 accepted restrict lines say that a template does not settle the design for good.
3. Mark each amendment as not re-checked, beside the frozen version. Done in the records. Since the revert, they appear as held proposals in tree-D4.md, here and in the head.
4. If the close-check refuses the amendments, ask. It did ('model/ and its tiers moved after D3 froze them'; _analysis/d4a01_validate_D4_01.txt). I asked (QD4-001) and did not work around it. J chose option (b) (24 October, 15:05 Berlin). Move 203 reverted both amendments: P05 and A11 are restored byte for byte from the snap of move 197 (_analysis/d4_revert.py, history lines 181 and 182). The model hash is 46384686 again. Both amendments are held proposals, stated in full with their rooms, lines and moves in tree-D4.md ("The held proposals"). F-024's and F-017's D4a-01 lines stay as written. Each finding has one later line that restores its earlier statement and records the held proposal (findings, now 42 lines).
5. Do not rely on the kind of add-condition, add-step and restrict lines; run the distance once with kind collapsed for them. Done (_analysis/d4a01_kind_collapsed.py). The combined distance hardly moves: Pearson 0.9965, mean absolute difference 0.0024, delta 0.4223 against 0.4227. The average-linkage trees agree with ARI 1.00 at 2 and 3 clusters, 0.886 at 5, 0.922 at 8 and 0.779 at 12. No branch takes its members from a per-kind view for those ops, and each branch's kind field is reported, not relied on. Local validation is reported as not established: prior.md section 3's measure was not computed.

Section 1, read before any cut

The delta score is 0.4227 (Monte Carlo SE 0.0020). The average-linkage dendrogram is a chain with no partition: at 12 clusters one group holds 663 rooms. Every room holds a key, and none returned none. Shared corrections reach 5 rooms only at the bare target. The detail is in tree-D4.md.

The pass

• Candidates (_analysis/d4a01_candidates.py, .txt). 274 change keys at level 3 are held by 5 rooms or more. The largest are restrict lines on arrows, which cannot key a branch. Keys that co-occur beyond chance mostly share one third-order node.
• The cut rules were logged and written into tree-D4.md before the first cut. The minimum group size is 5.
• Cut 1, F01 (move 200, merging): the play administered, at the fourth order, key add-step:K01:T4-001, 103 rooms. Its 164 lines were read whole (_analysis/d4a01_lines_K01_addstep.txt).
• Cuts 2 to 6, F01's subforms (moves 201, 202, 204, 205 and 206, splitting), at the third order: F02, the takeover run as a temporary regime (33 rooms); F03, the joke tested (18); F04, the licence policed (13); F05, the styling ended (12); F06, the joke kept (8). Two level-3 groups were set aside, since their lines state several different steps.
• Cross-links (move 207, relating): 18 lines over 6 pairs of subforms.
• The accounting. 103 rooms in a branch, 0 unadapted, 602 adapted but in no branch, 0 unreturned: 705, the analysed set. tree-D4.md names each of the 602 rooms, with the number of shared change keys a later pass would read.

What this pass shows, and what it does not

• The ledger's form signals are weak. The D3 revisions absorbed the shared corrections, and the dendrogram shows no partition. The groups that remain are elaborations of single elements.
• The one element cut, K01, gives a branch about the sub's own April Fools play, not about canvas work. It says that members organized the play itself: they tested it, policed it, ended it and kept parts of it.
• The pass reached one element. 31 element change keys at level 4, held by 20 rooms or more, were not read (tree-D4.md, "Where the pass stopped"). So the tree is a first pass, not a taxonomy of the rooms' forms.
• Not built. The comparison (section 5) and the projections (section 6). They come after the final branch cut, and this is not the final cut of the stage's design. The close-check warns about them at a leg that made a cut. No verdict, canvas field or branch entered any computation of this leg.

For the operator

• validate.py --open D4 reads the startup packet's pattern name rooms-x-adaptations.<level>.<kind>.tsv literally and reports it missing; the sixteen matrices are present.
• stage_D4.py resolves a branch key's target against the elements only, so no branch can be keyed on an arrow, though the largest change keys in this ledger are on arrows.
• stage_D4.py refuses any model move after the D3 freeze, while J's instruction asked for amendments at D4. The two did not meet, and QD4-001 settled it for this run.

Slips

• A tool interruption. The session ended during the command that logged and snapped move 202 and dry-ran F04. The log line and the snap were written. F04's dry-run file was empty, so the dry run was repeated before F04 was written.
• The forms' list of unchanged elements counts arrows. d4_cut.py reads instantiate keys at the bare target, and those include arrows, so F06's list names A12 among "elements". The forms are written once and are not regenerated. Read that line as elements and arrows.
• The amendments were made, then reverted. The two model moves of this leg (198, 199) were undone by move 203 at J's ruling. Each stays on record.

Close-check, D4a-01

validate.py D4 reports 0 errors and 1 warning (_analysis/d4a01_validate_D4_03.txt). The warning: the comparison and the projections are not built; at a leg that made a cut they are built after the last cut. Section 4: 103 in a branch, 0 unadapted, 602 adapted in no branch, 0 unreturned; 705, the analysed set. The first run (d4a01_validate_D4_01.txt) gave the model:moved error, now gone with the revert. The second (d4a01_validate_D4_02.txt) gave the missing notes and the unnamed rooms, now written.

• Written at D4a-01: branches.jsonl (6 branches), forms/ (6 files), crosslinks.jsonl (18 lines), tier_history.jsonl (now 573 lines; 12 stage-D4 lines: 6 cuts and 6 cross-linked pairs), tree-D4.md, this file; model history (now 182 lines: 8 amendment lines and 2 revert lines); findings (now 42 lines: 2 re-examination lines and 2 lines after the revert); the moves 198 to 207, each logged and snapped; QD4-001. Helpers in _analysis/: d4a01_key_freq.py, d4a01_kind_collapsed.py, d4a01_candidates.py, d4_key_lines.py, d4a01_a11_classes.py and d4a01_amend_specs.py (read or write their own outputs only); d4_amend.py, d4_revert.py, d4a01_findings.py, d4a01_findings_revert.py, d4_cut.py, d4a01_specs_K01.py, d4_crosslinks.py and d4a01_tree_append.py (write the files named in their docstrings).
• Unchanged: the model, at 46384686… (elements 45, arrows 21, the tiers), the ledgers and their rulings, the verdicts and every view.
• Questions. QD4-001 is answered. None is open.

D4a-02: the second pass, the comparison, the projections

Leg D4a-02, 25 October 2026 (UTC). The harness opened this leg after QD4-001 had said the run would stop at D4a-01, so the run goes on, and this leg does the stage's remaining work.

The comparison, declared before its script runs (stage D4 section 5)

The final branch cut of the stage is cut 29 of this leg (F35, move 236), and every cut is snapped. No branch is recut after the comparison is seen. The comparison is the chunk-share comparison, run as the stage file gives it: python3 tools/chunk_compare.py --out out --store package/store, the versioned engine (chunk-comparison-v1), with its defaults. Its method, as the stage file and the engine state it:

• Features. One row per room. Columns are the fourth-tier themes, and the counts are unique concept ids by their theme links. A theme placed on several fourth-tier themes splits its weight equally among them. Unplaced concepts are counted apart. Empty compositions are excluded by name. Rooms with fewer than five placed themes are flagged as low-information and kept, and the pipeline is run again without them.
• Smoothing. P = (x + a m) / (n + a), with a = 1.0, since prior.md holds no chunk_concentration line. It is a fractional pseudo-count heuristic. The run reports the median own-data weight and the sensitivity to a/10 and 10a.
• Distances and clusters. Ward on Euclidean CLR vectors. Jaccard presence and Hellinger shares with average linkage, as sensitivities, with adjusted Rand indices at each eligible k.
• Null and resampling. Theme-allocation patterns are permuted among themes. There are 200 accepted bootstrap draws and 100 permuted copies under each of two seeds (0 and 1). Eligible k runs from 2 to min(12, floor(n/2)). A k clears only when both stability margins are positive under both seeds. The k carried maximizes the worst margin, with the smaller k on a tie. If none clears, the result is no-supported-partition.
• What it reads. The concept store, the placements, the tiers, the dropped cases and the prior. It reads no adaptation, branch, verdict or outcome, so it is a non-adaptation baseline that shares the inductive coding structure, not theory-free evidence.
• What I read from it. The empties, a and the median weight; the Rand indices among the three distances; the third tier's sparsity; the tier verdict with its index; the volume verdict with its percentile; the k carried, with and without the low-information rows. Best-match Jaccard against the branches is descriptive. ARI against the branches is undefined, since the branches overlap (759 cross-link lines) and no exclusive cut is named.

The comparison did not run (QD4-002)

python3 -I -B tools/chunk_compare.py --out out --store package/store stopped on its first room: "ValueError: Placement lacks fourth-tier parent: ('2007scape', 't02')" (_analysis/d4a02_chunk_compare_run.txt). The cause is the run's residue. 335 second-order themes in 213 rooms are placed on the two third-order themes that no fourth-order theme gathers: T3-017 (carrying on ordinary sub talk, 334) and T3-133 (recovering a hacked sub, 1). data_structure-C5.md keeps both as residue, and the tiers are closed after C5 (rule 11). The stage file counts unplaced concepts apart; the engine raises on these placements instead. The run wrote no file. I did not edit the engine or the tiers, and I asked J (QD4-002). The projections follow the comparison and are not built.

The pass (cut rules R0 to R7, with the amendment R1a to R1c, logged before it was used)

• Read. The 31 element change keys at level 4 left at D4a-01, each held by 20 rooms or more. Each key's lines were read whole, by level-3 node, in _analysis/d4a02_keys/ (d4_key_lines_bynode.py, run by d4a02_dump_keys.py).
• Cut. 29 cuts, moves 208 to 236: 24 branches and 5 subforms (F12 to F14 under F11; F18 and F19 under F17), from the specs _analysis/d4a02_cut_F07.json to F35.json (d4a02_specs.py). They were written by d4_cut_batch.py, which logs each move only after d4_cut.py reports the write, and then snaps it. The list, with names and what each changes, is in tree-D4.md.
• Set aside. 8 keys, each with its reason in tree-D4.md.
• Cross-links. Move 237: 741 new lines, 759 in all, over 348 pairs of branches that do not nest.
• The accounting. 476 rooms in a branch, 0 unadapted, 229 adapted but in no branch, 0 unreturned; 705, the analysed set. tree-D4.md names each of the 229 rooms with its count of smaller keys.

What the pass shows

• The branches are facets, not exclusive forms. 200 of the 476 rooms are in one branch, and the rest are in two to six or more (subforms counted). A room makes several element-level changes at once, and the keys do not group rooms into a few types. This fits the chained dendrogram and the delta score of section 1.
• Families. One change appears at several nodes, so it appears as several branches. The largest family is P05's added clause holding only in part (F07, F26, F27), beside F-024's held branch. Also: keeping the shared instruction current (F15, F33 and F08), help conditional (F22, F28), carrying on (F11 to F14, F23, F25), and the chat (F16, F29, F30).
• Two links the model lacks. The move leads back to building (F09, 54 rooms), and the marking leads back to keeping (F32, 21 rooms). Neither is an arrow; the next stage reads them for order.
• Many restrict branches are limits of the record. They show what the record does not hold: machine hands not shown placing (F24), the chat seen only from outside (F30), hosting only as one-off permission (F31), carrying on only in talk (F25). They are kept because the element's statement holds only in part there, and they are reported as limits, not as forms of doing.
• Local validation remains not established.

For the operator

• The comparison engine and the residue. tools/chunk_compare.py raises on a placement whose third-order theme no fourth-order theme gathers, but the stage file counts unplaced concepts apart, and this run keeps two residue themes by design (QD4-002).
• The member-name check is a substring check. stage_D4.py refuses a branch name that contains any member's name as a substring, so the room 'de' forbids words such as 'decisions' and 'outside'. Two spec names were changed before writing (F16, F30).

Slips

None in the writes of this leg. Two spec files (F16, F30) were edited after their generator ran, to change a name the check refused; the edits are the names only.

Close-check, D4a-02

validate.py D4 reports 0 errors and 1 warning (_analysis/d4a02_validate_D4_02.txt). The warning is that the comparison and the projections are not built. At a leg that made a cut this is a warning; the stage does not close without them (QD4-002). Section 4: 476 in a branch, 0 unadapted, 229 adapted in no branch, 0 unreturned; 705.

• Written at D4a-02: 29 branches (branches.jsonl, now 35); 29 forms (forms/, now 35); 741 cross-link lines (now 759); 371 stage-D4 tier_history lines (29 cuts and 342 cross-linked pairs; the file now 944 lines); the moves 208 to 237, each logged and snapped; this section and the tree-D4.md sections; QD4-002. Helpers in _analysis/: d4_key_lines_bynode.py and d4a02_dump_keys.py (read the ledger and write the key files), d4a02_specs.py (writes the specs), d4_cut_batch.py (runs d4_cut.py, mem.py log and snap.py), d4a02_tree_append.py (appends to tree-D4.md).
• Unchanged: the model, at 46384686… (history 182 lines, findings 42), the ledgers and their rulings, the verdicts and every view.
• Questions. QD4-002 is open.

D4a-03: the comparison, the projections, the handback

Leg D4a-03, 25 October 2026 (UTC).

A departure: the comparison engine is chunk-comparison-v1.1 (QD4-002), declared before it runs

J answered QD4-002 with option (a) (25 October, 19:48 and 19:54 Berlin). The harness owner patched tools/chunk_compare.py and its trusted copy identically to chunk-comparison-v1.1 (sha256 c8d2eb8c7c309c02de9bb04e10efeaa91071ee2a469823f569a9ab64a42c059f). A second-order theme placed only on third-order residue that no fourth-order theme gathers (T3-017, T3-133) is now counted with the unplaced concepts and reported apart, in the fields residue_themes and residue_concepts. A theme also placed on a gathered node keeps that node. The stage file names chunk-comparison-v1, so this is a departure, declared in departures.jsonl (line 10) before the run. The method declared at D4a-02 stands otherwise: the stage file's command and defaults (a = 1.0; seeds 0 and 1; 200 bootstrap draws and 100 permuted copies per seed; k from 2 to 12). The cuts are final (F35, move 236), and no branch is recut after the comparison is seen. Beside the comparison I report each room's residue share, as J asked: the share of its placed and residue concepts that sit on residue.

The comparison read (detail in tree-D4.md)

• The two verdicts by number. The tier verdict: at the carried k 4, dimension ARI 0.110 and third-tier ARI 0.170. The volume verdict: the cluster labels explain 0.255 of the variance in log concepts, at the 100th percentile of the permutation null (null maximum 0.026).
• The k carried. 4 over all 705 rooms (worst margin +0.052, silhouette 0.024). 2 over the 626 rooms without the 79 low-information rows (worst margin +0.099, silhouette 0.097). Every k from 3 to 12 clears over all rooms, but no silhouette exceeds 0.051. So the null is beaten while the clusters barely separate.
• The sensitivities. Against the Ward/CLR labels at k 4, the Jaccard and Hellinger partitions give ARI -0.007 and -0.008, and a/10 and 10a give 0.145 and 0.164. The partition does not survive a change of distance or of smoothing. The median own-data weight is 0.990, so the smoothing touches the profiles little.
• The empties. None. a = 1.0. The third tier is sparse: 13.52 nonzero of 195 columns per room.
• The clusters. VA 176, IT 292, TX 155, CH 82. They differ mostly by their Keying share (T4-001) and by size: IT holds 137 of the 176 rooms of the smallest quartile. Best-match Jaccard with a branch is 0.096 to 0.187. The coding-structure clusters and the adaptation branches do not match.
• The residue. 199 rooms hold residue concepts. The share per room has a median of 0, and 39 rooms are at 0.10 or more and 7 at 0.30 or more. In these rooms the composition leaves out the room's own ordinary business.

The projections read

The single does-not-compose room (picturegame) lies in F21 and F25. The canvas percentiles follow room size: 11 of 35 branches have a median room size at or above the 95th percentile, and the large-room clusters have the large areas. No difference in what rooms kept on the canvas is read as independent of size. No cut rests on the projections; every cut was snapped before them.

What D4 shows, for D5

• The adaptation tree is a set of facets. The 35 branches overlap (759 cross-links). The comparison's partition, built without the ledger, is weak, unstable across distances, and largely a size partition. Neither gives exclusive forms.
• What the branches say. Rooms add work the model does not state: the play administered (F01), deals carried out (F10), machine targets and plans kept current (F08, F15, F33), chats kept open (F16), help made conditional (F22, F28), and carrying on renewed elsewhere (F11). They limit P05's added clause where informed members reject a planned change (F07, F26, F27). And they show two links the model lacks (F09, F32).
• Local validation remains not established. prior.md section 3's measure was not computed.

Slips

• Three Edits to the handback's script (_analysis/d4a03_handback.py) ran in one turn, and later three Edits to the head ran in one turn, against the rule. Each landed on a separate string.
• One figure in the handback's script was typed (102 rooms for F07, F26 and F27). It was replaced by the computed figure (108) before the handback was written.

Close-check, D4a-03

validate.py D4 reports 0 errors and 0 warnings (_analysis/d4a03_validate_D4_01.txt), including the trusted replay of the comparison engine. Section 4: 476 in a branch, 0 unadapted, 229 adapted in no branch, 0 unreturned; 705.

• Written at D4a-03: departures.jsonl line 10; chunk-share-D4.result.json, .jsonl, .md and .py (by the engine); projections-D4.jsonl (by tools/projections.py); the D4a-03 sections of tree-D4.md and of this file; handback-D4.md; interview/D4a-03.md; the head. Helpers in _analysis/: d4a03_departure.py (writes the departure), d4a03_read_comparison.py and d4a03_volume.py (read only), d4a03_tree_append.py (appends to tree-D4.md) and d4a03_handback.py (writes the handback).
• Unchanged: the branches (35), cross-links (759), tier history (944), the model at 46384686… (history 182, findings 42), the ledgers, the verdicts and every view.
• Questions. QD4-002 is answered. None is open. The stage closes at its interview cut.

D4a-04: can the 25 top-level branches be joined into fewer parents?

Leg D4a-04, 25 October 2026 (UTC), an extra leg on J's instruction (25 October, 21:39 Berlin, through the handler). J finds 35 branches a lot and asked whether the 25 top-level branches can be joined into a smaller set of parents, on grounds the stage and the contract allow, decided from the record. If not, the reasons go here, nothing changes, and D5 runs one leg per branch. J will not be asked again.

The test, written before any computation

A parent is a branch, so it must meet what the stage asks of a branch:

1. Keys. Every member holds every key of the parent at its level (section 2). Members' material can stand beside the keys as a declared ground, never alone.
2. Nesting. A subform nests by adding keys. stage_D4.py accepts a child only if each parent key has the same op and the same target as a child key, and the child's node lifts to the parent's node. So one parent can hold only branches of one element and one op.
3. The level. A group that meets only at the dimension or the bare target is a grouping, not a branch, since the aggregation does the work (section 2; cut rule R4).
4. The source. No list of rooms that belong together may come from anywhere but the ledger (section 2's Forbidden). Rooms that happen to share branches therefore ground no parent.
5. The shared change. A parent, like any branch, needs lines that state one shared change (cut rule R2). Rooms that the parent brings in, beyond its children, must have lines read for that change.

What the record shows (_analysis/d4a04_joins.py, d4a04_joins.txt)

• The handler's facts, checked. 25 top-level branches on 14 elements: yes. By the elements' own dimension field they fall in six dimensions, D02 9, D07 5, D03 4, D04 4, D06 2 and D01 1, as the handler says. But the ladder joins a branch by the node its key lifts to, not by the element's field, and by that lift the count is D02 9, D04 6, D07 6, D06 2, D01 1 and D03 1. F07 lifts to D02, F26 to D04 and F32 to D07, although P05's own field is D03. The Jaccard distance between member sets has median 0.977 and minimum 0.870 (F10 and F26): yes. Average linkage first merges at 0.870 (F10 with F26), not above 0.89. At 0.95 it gives 13 groups, six of which join branches of different elements: yes.
• Joins under rule 2, one element and one op. Only three sets of top-level branches share both.
  • P04 add-step (F15, F33). Their nodes, T4-008 and T4-006, meet first at the dimension: add-step:P04:D02, 85 rooms, 20 of them in neither child.
  • P16 add-condition (F22, F28). T4-017 and T4-016 meet at the dimension: add-condition:P16:D04, 65 rooms, 13 in neither child.
  • P05 restrict (F07, F26, F27). T4-006, T4-016 and T4-013 lie in three dimensions, so they meet only at the bare target: restrict:P05:*, 214 rooms, 106 in none of them. Each parent would sit at the dimension or the bare target, a grouping under rule 3. Each would also take in rooms (20, 13 and 106) whose lines were never read for the shared change, so rule 5 fails too. Reading them would not cure rule 3.
• Families across elements or ops. These are the families named at D4a-02: P05's clause and the marking (F07, F26, F27, F32); the shared instruction kept current (F08, F15, F33); carrying on (F11, F23, F25); the chat (F16, F29, F30); machine hands (F08, F24); the frame (F01, F21); help (F22, F28). None has a key common to its branches, and the rooms in all of a family's branches number 0 to 5. No parent can be grounded on keys under rule 1, and the check refuses the nesting under rule 2. Co-membership alone cannot ground one under rule 4.
• The membership distances. These say the same thing from the other side: the branches hold almost disjoint sets of rooms, and the groups that average linkage forms at 0.95 join different elements with no shared change.

Decision

No join is defensible on grounds the stage and the contract allow. Nothing changes: 35 branches, 25 top-level and 10 subforms, 759 cross-links. D5 runs as the stage says, one leg per branch. The subforms already nest inside their parents (F02 to F06 in F01, F12 to F14 in F11, F18 and F19 in F17), so a parent's leg can hold its subforms' accounts. The families named at D4a-02 are a reading aid for D5's accounts: they state one change across elements or nodes, and each D5 account can cite its family. They are not parents, since nothing in the ledger joins them.

What would have made a join defensible. Either a key held by every member of the branches to be joined, at the third or fourth order (none exists), or a stage rule that accepts parents at the dimension or the bare target (the stage forbids them). Neither holds, so 35 is the number the keys support.

Close-check, D4a-04

validate.py D4 reports 0 errors and 0 warnings (_analysis/d4a04_validate_D4_01.txt), including the trusted replay of the comparison engine. Section 4: 476 in a branch, 0 unadapted, 229 adapted in no branch, 0 unreturned; 705.

• Written at D4a-04: this section; the head; one read-only helper, _analysis/d4a04_joins.py, with its output.
• Slip: two Edits to the head ran in one turn, against the rule; each landed on a separate string.
• Unchanged: the branches (35), cross-links (759), tier history (944), forms, the comparison and the projections, the handback, the model at 46384686…, the ledgers and every view.
• Questions. None is open.

D4a-05: room forms, the top cut (an addition after D5)

Leg D4a-05, 26 October 2026, on J's instruction through the handler, after D5 closed. J, 17:27 Berlin: "I need to tell it to make something with 4 to 8 big forms and then continue clustering down to 700." J, 18:35 Berlin: "I mean as a leg that happened after not instead." J, 18:36 Berlin: the cut is to be gone over with J before the split down to the rooms. The dated amendment is in departures.jsonl (lines 11 and 12). The report is room-forms-D4a05.md; the forms and their members are in room-forms-D4a05.jsonl, and the room table in room-forms-D4a05.tsv.

• What was compared. The rooms' selected changes (accepted restrict, add-step, add-condition, link and contradict lines, on elements and arrows; 6,637 lines in 684 rooms; 21 rooms with none, the core). Shares at the third-order, fourth-order and dimension levels, the levels counting equally; third-order themes changed by one room dropped; Hellinger distance; Ward's method. The rule was logged before the run.
• The cut. Eight forms, A 152, B 119, C 103, D 88, E 83, F 69, G 42, H 28, and the core (21). The logged rule took k = 8, the most stable count (no count from 4 to 8 reached a stability of 0.5). The size ratio is 5.43, because of H; k = 6 would give 2.2.
• Kinds or continuum. A continuum: silhouette 0.030, clusterwise Jaccard 0.25 to 0.36, 296 of 684 rooms fit two forms equally.
• Against the codes. The forms differ there too, weakly (6.7 per cent of the variation in code shares), and they differ in room size.
• The 35 branches spread across the forms; none nests in one.
• Moves. 238 to 245 named the forms (merging). 246 to 277 declared 32 sub-forms before J's message of 18:36 was read; move 278 (dropping) withdrew them as declarations, and they are held as working material in _analysis/d4a05_tree3.json. Each move was logged and snapped.
• Unchanged, checked against the D5b close snap (_analysis/d4a05_unchanged.py, 78 files): branches.jsonl, crosslinks.jsonl, tree-D4.md, the forms, and every D5 file. The model is 46384686….
• Slips. A command with a shell assignment beginning 'for_' that did nothing; a cut after a helper, refused by the guard; the sub-form moves made before J's message was read. All logged.
• Questions. None open. For the talk with J: eight forms or six; whether the three levels should count equally; whether a room should carry weights in several forms; how D6 should relate branches that cut across the forms.

D4a-06: room forms, the top cut redone (an addition after D5)

Leg D4a-06, 26 October 2026. J read my interview answers to his four questions and said (19:50 Berlin, through the handler): "Go ahead this sounds good." The interview ran in a fork and is not in this folder; the fixes were taken from the handler's list. The amendment is dated in departures.jsonl (line 13). The report is room-forms-D4a06.md, with room-forms-D4a06.jsonl and .tsv.

• The fixes. A floor of 5 selected changes before a room helps define the forms (558 rooms define them; 126 thin rooms are placed afterwards; the core of 21 stays). J's placement rule taken literally: each room to the form whose signature holds most of its selected changes, ties listed and broken by the nearest centre. The count chosen by the merge-height gap and by stability on matched subsamples against a shuffled null. The rule was logged before the run.
• The count. The measures disagree: the gap carries 5, stability 8. At 5 the largest group (164 rooms) has no signature; it is three of the eight forms merged. By the logged rule the stability cut is carried and the gap cut given in full.
• The cut. Eight forms, by Ward 151 to 40 rooms (ratio 3.78), placed 135 to 50 (ratio 2.70). 239 rooms move against their whole mix; 181 placements are ties. The count rule draws rooms to forms whose signature themes are common (G grows from 43 to 124).
• Read as rooms. A, C, D and E are one kind each; F mostly; B and H are mixtures (H with a raiding core); G is one kind as cut and a mixture as placed. The misfits are rich rooms whose changes spread over several forms.
• Named sets. Raiding rooms gather in H where raiding is a large part of their changes (19 of 27). Takeover rooms spread over all eight forms; no signature holds the frame. r/startrek is the core's one rich room, fit by the model without change.
• Still a continuum; against the codes the forms differ weakly (7.9 per cent of the variation).
• Moves 279 to 286 named the forms, each logged and snapped.
• Unchanged, checked against the D4a-05 close snap (_analysis/d4a06_unchanged.py, 81 files): branches.jsonl, crosslinks.jsonl, tree-D4.md, the forms, room-forms-D4a05.* and every D5 file.
• Questions. None open. For the talk with J: five forms or eight; weighting the count by how common a theme is, or one theme to one form; weights in several forms for rich rooms; r/startrek apart from the thin core.

D4a-07: room forms with the arrow at every level (an addition after the accounts)

Leg D4a-07, 26 October 2026. J asked (20:35 to 20:37 Berlin, through the handler): "How come arrows are not used?" "The arrow can work at any level. Just as the T3 are T4 and Ds." "Add the arrow and give your ideas as proposals but not mandated." The amendment is dated in departures.jsonl (line 14). The report is room-forms-D4a07.md, with room-forms-D4a07.jsonl and .tsv.

• The arrow at every level. An arrow is lifted as a link from its source element to its target element at each level, through the elements' anchors; at the third-order level an end takes the room's evidence theme when that theme lies under it, and is otherwise held at its fourth-order node; P15, outside the ladder, is held at its element. An arrow line gives half its weight to its evidence node and half to its link. The mapping was logged before the run.
• The proposals. Placement by the whole mix (J's literal rule reported: it would move 307 rooms). B not dissolved by hand; it is the middle of the continuum. The raiding core holds as a group beyond chance (silhouette 0.098, p 0.001) but sits inside B and H. The count kept, and both measures now carry k = 8. The floor of 5 kept. Restricts reported as a check (the cut without them agrees at 0.149), not weighted apart. Link ops lifted as links, my own proposal (without them 0.208).
• The cut. Eight forms, placed 148, 159, 87, 64, 60, 56, 59 and 51 (ratio 3.12, B the middle the largest). Signatures now include links: the design to the template (A11), keeping to scripts (A06), judging hands too few to the move (A10), the move to building, borders to sparing (A05), keeping to borders (A04).
• A differing account. Yes for C, D, F and H's frame; in part for A, E and G; no for B.
• Still a continuum; against the codes the forms differ weakly (7.4 per cent of the variation). Against D4a-06's forms the adjusted Rand index is 0.191.
• Moves 287 to 294 named the forms, each logged and snapped.
• Unchanged, checked against the D4a-06 close snap (_analysis/d4a07_unchanged.py, 84 files): branches.jsonl, crosslinks.jsonl, tree-D4.md, the forms, room-forms-D4a05.*, room-forms-D4a06.* and every D5 file.
• Questions. None open. For the talk with J: which choice of what counts should be the basis, since the cut moves with each; B split below or read as the middle; the raiding core as a sub-form; the whole mix or the literal rule; a wider range than 4 to 8.

D4a-08: room forms on the changes and the codes (an addition after the accounts; open)

Leg D4a-08, 26 October 2026. J, through the handler: 21:05 Berlin, "How about using the code counts, dimensions for example, as well?"; 21:06, "Yes. Please also tell it not to close but write us so we can iterate."; 21:09, "Tell it to use the code counts as deviations from a mean normalized use. Same as the changes, 0 should be the global model." The amendment is dated in departures.jsonl (line 15). The report is room-forms-D4a08.md, with .jsonl and .tsv. The leg is open: J and the handler answer in the conversation, and done.sh waits.

• The blocks. The D4a-07 change block, unchanged (0 the global model), and a code block of deviations from the mean share at each level (0 the average room); no z-scores; levels and blocks equal by total variance over the defining rooms. A first run with Hellinger code shares, made before the 21:09 message, is kept as superseded working material.
• Two amendments while running, logged before their reruns. The shuffled null was redone (code deviations permuted node by node) because raw-count shuffling mixed room sizes; it still came out more stable than the real data, because a node's skewed values make tight groups in every copy. So the stability test cannot choose the count here, and the merge-height gap carries it (k = 5); the stability rule's k = 8 is given in full.
• The cut. Five forms placed 182, 174, 133, 113 and 82 (ratio 2.22): the middle with a raiding core, keeping, the terms between neighbours, the sub's April Fools play, the design and its marking. The cut follows the codes: between-form shares 0.271 for codes, 0.051 for changes.
• Checks. The held-out half of the codes reproduces the forms' code structure (pseudo-F 39.2 against 1.41); the half cuts agree at 0.191; against D4a-07, 0.072.
• Moves 295 to 299 named the five forms, each logged and snapped.
• Unchanged, checked against the D4a-07 close snap (_analysis/d4a08_unchanged.py, 87 files).
• For J: the weight of the codes against the changes; five forms or eight; the April Fools play as a form or as the frame apart; the count without a working null; the core placed by its codes or kept together.

D4a-08, the cut I stand behind (J, 21:24 Berlin: "We need them to stand behind the cut.")

• The cut: changes two thirds, codes one third, eight forms (room-forms-D4a08b.*; moves 300 to 307). It keeps 82 per cent of the change structure the changes alone show and 77 per cent of the code structure the codes alone show; equal weight keeps under half of the change structure. Eight is a judgement on substance: every form has a change signature, and raiding stands apart.
• Sure: the terms between neighbours, the design and its marking, the spot, keeping. A pole, but the frame: the sub's April Fools play. A pattern of uncertain reach: raiding. Not sure: the chat and the scripts, the plan made and announced.
• Still to change: the frame apart; the chat and the scripts split below; a working null for the count; r/startrek placed by its codes; the split-half check on this cut.

D4a-08c, fewer forms and the core placed (J, 22:00 Berlin)

• The core is placed by its codes (the code part of each centre): r/startrek and r/n64 go to the April Fools play; the other 19 spread, on 1 to 8 coded concepts each.
• The merges: raiding into the chat and scripts (eight to seven); the plan announced into the terms between neighbours (seven to six); the chat, scripts and raiding into the design (six to five); the spot into keeping (five to four).
• Six forms (room-forms-D4a08c.*, moves 308 to 313): the terms between neighbours with the plan announced (166), the work behind the thread, a mixture (141), the design and its marking (125), keeping (119), the April Fools play (98), the spot (56); ratio 2.96. Recommended for the appendix. Four is the clearest by the gap but loses the design's signature (98 to 73 per cent) and the spot's own account; I would use it only as a summary.

J's ruling, the allocation and the tree to the leaves (J, 22:18 Berlin: "6 it is.")

• The cut: the six forms of D4a-08c are the room forms (departures.jsonl line 16). The earlier cuts stay as written, superseded and not withdrawn. No new move: the six forms were named by moves 308 to 313.
• The allocation is written out in room-forms-allocation.md: the nine steps by which a room reaches its form, how to reproduce them, and the earlier allocations from D4a-05 to D4a-08c in order. A correction of record is stated there: room-forms-D4a05.md says an arrow counted through the theme of its source, but its script counted every line at its own lift.
• The tree to the leaves (room-forms-tree.nwk, room-forms-tree-linkage.tsv, room-forms-tree-rooms.tsv; script _analysis/d4a08d_room_tree.py): the same Ward tree, with every room's label at k = 2 to 30 and its address to its leaf. Placed rooms keep their form and descend by the rule that placed them. Their drawn heights are capped in 117 of 147 cases, and 130 of the 147 meet a near-equal split below their form. The splits below the forms are a view, not named and not moves. The first split separates the April Fools play from the other five forms.

Handback, stage D4: the taxonomy from adaptations

Legs D4a-01 to D4a-03, 24 and 25 October 2026. The taxonomy is read off the adjudicated ledger (the re-check, all 705 rooms), adapted against the model frozen at D3 (46384686…). The model is unchanged: the P05 and A11 amendments of D4a-01 were reverted (QD4-001) and are held proposals. The detail and the scripts are in tree-D4.md, notes-D4.md, branches.jsonl, forms/, crosslinks.jsonl, chunk-share-D4.* and projections-D4.jsonl.

The claim

The rooms adapted the model in many small shared ways, not into a few forms. 35 branches hold 476 of the 705 rooms, and they overlap: 759 cross-links join 348 pairs of branches that do not nest. A room makes several element-level changes at once. The branches are facets of those changes, not exclusive types. The comparison built without the ledger agrees in its own way: its partition beats its null but barely separates the rooms (silhouette 0.024), does not survive a change of distance, and largely sorts the rooms by how much the coders coded. What the branches say is specific:

• Rooms add work the model does not state. They administer the April Fools play (F01). They carry out deals: they move work, retarget scripts and relay terms (F10). They keep the shared instruction current, because a stale template or bot target undoes their own new work (F15, F33, F08). They keep the chat open (F16). They make help wait on their own work and spare hands (F22, F28). And they carry on by renewing the work elsewhere, often before the close (F11 to F14).
• They limit P05's added clause. In design, at the border and in keeping (F07, F26, F27), informed members reject a planned change, or the record does not show the untold keepers the clause needs.
• They show two links the model lacks. After a move the room builds again (F09). After a celebration it defends again (F32).

The room that best supports it: fivenightsatfreddys. It is in eight branches across seven elements. It runs a takeover as a temporary regime (F01, F02), does not show the telling clause at its design (F07), builds again after a move (F09), carries out a deal (F10), carries on past the close (F23), depends on chat access (F29) and hosts by one-off permission (F31). One room, many facets, no single form.

The room that most threatens it: ainbowroad. It is the largest room in no branch (2,054 concepts). Its shared changes sit on keys held by fewer than 20 rooms, which the pass did not read. A room can hold rich organizing that the branches do not show.

The condition between them is whether a room's change lands on a node that many other rooms use. Where it does, the room appears in a branch, often in several. Where its changes are its own, or shared by only a few rooms at one node, it appears in none. The branches are a census of common changes, not of the rooms' organizing.

The return value

The branches, in the order cut, with the verdict and canvas percentiles

Verdicts are projections.py's map (my last ruling at D3, else the readers' agreed verdict), so the D3 versions are mixed. Each row: id, parent, level, members; composes, with residue, does not compose, cannot tell; the does-not-compose percentile; the median area and its percentile. The canvas percentiles follow room size (tree-D4.md).

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 shape read) and armok, maryland and oneshot (informed members), with their nine re-check lines. The branches F07, F26 and F27 hold 108 rooms where the clause holds only in part.
• 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 is nearly as common as the transition; the failure clause stands alone in 117 rooms, 31 of them talk only.

Questions, departures and defects

• QD4-001 (answered): the amendments were reverted, and the model is the D3 version.
• QD4-002 (answered): the comparison engine was patched to v1.1; declared as a departure (departures.jsonl line 10).
• For the operator. validate.py --open D4 reads the startup packet's pattern name rooms-x-adaptations.<level>.<kind>.tsv literally. stage_D4.py resolves branch keys against elements only, so arrow keys, the largest change keys in this ledger, cannot key a branch. Its member-name check is a substring check: the room 'de' forbids 'decisions' and 'outside'.

Licences exercised (METHOD.md)

• The count set by kinds, not by a head's capacity: exercised. The branches number what the keys and their lines support (35), under rules written before the first cut; the cuts stop at a declared key size.
• An in-sample return in Eisenhardt's spirit: its ledger is the taxonomy's material; the taxonomy cannot corroborate it (section 7).
• Langley's strategy: not exercised at D4; the two links the model lacks wait for an order test.
• Gioia's explosion at the front end: not a D4 licence.

Slips

• At D4a-01 the session ended inside one command; its log line and snap were written, and the empty F04 dry run was repeated.
• F06's form lists the arrow A12 among the elements its members carry unchanged; the forms are written once.
• Two spec names (F16, F30) were changed before writing, after the member-name check refused them.
• At D4a-03 three Edits to this handback's script ran in one turn, against the rule; each landed on a separate string.