out/_head.md
Saved at D1.D1a: build. This reading copy substitutes participant identifiers in saved text; it is not a new interview response. Reading Markdown.
Participant handles in these reading copies use the pixel stream's identifiers: base64(SHA1(username)), case preserved, without a salt. These are linkable pseudonyms. Profile links are removed; missing-author markers remain. Original research files are unchanged. Quote offsets refer to original text. Source and reading-copy hashes are listed separately.
Source commit: 039abd710fb4, 2026-10-15T21:50:04+02:00. Saved-state date: 2026-10-15T19:49:18Z. Catalogue close receipt Commit date and saved-state date are distinct.
Original GitHub file. Original SHA-256: 93dcee0b9c3ab4e3cb2771f50743f2665fa28d0988b09214c410d153501ab665. Reading-copy SHA-256: 93dcee0b9c3ab4e3cb2771f50743f2665fa28d0988b09214c410d153501ab665.
Head, claude-v43-1 (branch claude-v43-1--C4-field)
Under 3,000 words, rewritten whole at every close. Last written at D1a, 2026-10-15 (UTC). Stages A1 to C5 are done; stage B is frozen. The model is frozen at pass 15 (e15f9647…b3fecd). Leg D1a built the return once: 705 tasks, 705 verdict packets and the sealed expectations.
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 is unchanged: 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)
- Stage C5 is closed. Stage D serves the model frozen at pass 15.
- "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 runs at xhigh effort, as every stage from here on.
- "Keep the room, or groups of rooms, as the unit, and keep the contract's two questions in view."
- QD1-001 (J, 21:19 Berlin): an element may sit in two or more dimensions; the check was wrong.
The build (D1a)
prior.md§7 and §8, written first. §7:w = 4, 2, 1, 0.5;g = 1, 0.5, 0, -1. §8, review prompts: the concept floor, 10 concepts (42 rooms below); the off-platform threshold, 20 pointers, or at least 3 and one for every four concepts (68 rooms past).- The model as prose: 3,591 words under a 6,000-word ceiling; no room named.
- The expectations: 705 lines by rules R1 to R6, sealed: 9,329 instantiations, 311 absences (C01 286, P20 25); 362 rooms not testable on some element.
- The folder: hash 61b03bbf…508a5c; VERSION equals the model hash. Four rooms exceed the declared 1 MB session figure (counting's is 11.4 MB); none is cut.
- The 19 story-miss rooms are listed in the stage notes and carried. The defects and limits are in the stage handback.
The current account, and the contrary rooms
The account is account.md, pass 15 (3,318 words), with
the readers' disagreements in account-readers-C5.md. The
nine propositions are in propositions.jsonl. 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].
- The bare answer. Most calls get no written reply. In written replies, acceptances come bare (25 of 31 to calls to place, F-023) and refusals give a reason (3 of 3; attack calls 23 of 38, F-014). The head-count claim failed (F-015).
- 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, so there the room aligned many hands; the others tried (F-021). A template settles a design inside a thread [A11]. Decided order is coded in 46 of 705 rooms [C01, F-006].
- Direct information sharing (T4-007). Members post the mark's state (10 of 14 bearing records; F-018). Posting the state and sharing templates are carried largely apart (89 rooms both, 80 by chance; F-022).
- Other rooms. Keeping brings talk with neighbours in 235 of 401 rooms [A04]; border talk that came first mostly offered terms. Help names a deal in 63 of 127 rooms where border talk came first, against 23 of 67 [A14; F-020]. Sparing rests mostly on the room's own norm, so A05's mechanism is theorised (F-020). Rooms join coalitions [A19] and cannot make every placer keep an agreement.
- The contest. A call can turn members against a rival [A15]. The same room meets the attack call with sparing, refusal or apology [A16] and border talk [A17].
- Loss (thin). A room that judges it has too few hands moves [A10]; read whole, the judgment came first in 10 of 20 rooms that moved. After doubt and a loss, 10 rooms moved and 11 gave the work 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 curate the record (P12; P22 tentative), apart from carrying on (P13).
- 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.
- Candidates: P06, R02, K03, K04 and P19. 23 elements stand.
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.
The room that most threatens it: thebluecorner. It is a colour faction whose faith names its rivals and rules on guests.
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.
The reasons for the last revisions
- J's rulings of 15 October, 01:29 Berlin (J has
delegated C5 questions to the handler):
- Work after hour 73 is curation of the record (P12; P22 tentative), apart from carrying on (P13).
- The prose pass on the declarations comes first, with the rule written first and each amendment a move.
- Stigmergy is recut only if it joins what Heylighen 2016 and Grassé 1959 keep apart.
- The C5 readers are the second reader of the declarations; QC5-001 adds the field analyst.
- J's language ruling stands.
- The passes of C5. Passes 1 to 10 amended the declarations (P06 and R02 cut; K01 cut and restored), fixed the readers' errors and took the field analyst's advice (QC5-001). J, 11:02 and 12:01 Amsterdam: the field analyst's marks are advice; the room is the unit.
- The serial work, passes 11 to 14 (J's leave at
C5c-07, QC5-002): findings F-019 to F-023 in
serial-C5/(F-014 superseded), folded in once at pass 15. - The freeze. C5d-p2 recorded it at pass 15;
out/_closesis the harness's (QC5-003).
Where the run stands
- D1a outputs:
prior.md§7 and §8; the stage's notes, model prose, expectations and handback;handoff-D/,verdict-D/,sealed/. Scripts:out/_analysis/d1*. - C5 outputs:
account.md(pass 15),propositions.jsonl,implications-C5.md(13 expectations), andhandback-C5.mdwith the files it names. - Ledgers:
tier_history.jsonl561,model/history.jsonl134,findings.jsonl36 lines (23 findings),model/elements.jsonl30 (23 standing),model/arrows.jsonl21. - Still open: the fields the prose rule did not read;
structure-C4.md's stale prose; Critical mass still flagged; the border coders' slight agreement (kappa 0.19). - The questions. QD1-001, QC5-001 to QC5-003, QC4-001
and QC4-002 are answered;
out/_field-link-superseded-C4astays as it is.
Stage C4, in short
The field analyst modelled r/place, sealed from my files: five mechanisms shared; P21, A21 and P22 tentative; the sharpest disagreement is what a template can do. No finding changed.
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 C3, in short
C3a bounded F-006 (O'Mahony and Ferraro; Olson open). C3b took A12's and A16's mechanisms from conversation analysis (F-014, F-015). C3c put the four universal problems to the structure (F-016) and the goal (F-017).
Stage C2, in short
- J's ruling on QC2-002, verbatim: "from here the criterion is a guide, not the judge, and a rise in residue is not a failure. Work pass 5 from pass 4's state. 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. This is the last closing pass. 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." The connection statement: "the first concept of FROM comes before the first concept of TO", null of 500 shuffles within each room (seed 20261014).
- The reviewer (C2b, C2c). QC2-001 (the handler, under J's delegation): serving sections of the pass 3 model file is acceptable.
Stage C1, in short (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 or more of its own.
- QC1-003 (the handler, under J's delegation). Five
revision-rate errors no verb can apply stay in
out/_analysis/c1_unapplied.jsonl; all 34 count in the rate. - Reading rules (
scheme_v2.md). The visitor rule: a theme names an act in the record of the room whose threads hold the words. "The work" is the room's own unless a field names another's. A bare mention of the event holds no act. J's floor: three concepts or more. The named words of T3-010 | T3-149 (attack, war, fight, battle, invasion, raid, conquest). Help between rooms is read from either room's record. A member's own part is T3-003; credit to others is T3-043.
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 inside the placements. A concept counts
toward a placed theme when that theme's must_show takes it
and no field sends it to another placed theme. Order by concept count,
ties by placements; at most three. The bag test: four
themes with three concepts each make a bag.
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_presentnames "twenty themes at most". - The not-flagged bag (J, QB2-013). With no other
theme at the floor,
item_is_a_bagis false andalso_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 scripts, which made one
mem.py call per row of the whole table and grew to 8.5
minutes a write. Never end a turn while a job runs in the background;
run every write and check in the foreground.
The pilot's declarations, and stage B in one line
Agreement is Jaccard on placement sets (alpha on 1 − Jaccard);
primary exact agreement beside, never in place. Gold: 40 items, never
shown to a reader. Stage B: B2 stability 0.807 is the floor every later
figure is read against; B4 ruled 3,288 contested items;
assign_final.jsonl is stage B's settled line,
unchanged.
Open, carried
- From D1a: C02 unpredicted; expectation 13 misses the host rooms; four rooms exceed a session.
- From C4: P21, A21 and P22 for stage D; a request for space answered with terms, in both sources and not in the model.
- From C3: whether the forms differ on the four universal problems or on the remainder; the colour-faction doubt ("a fellow comrade during the button" [PurplePixels/c0165]); Olson, open; the four declined reads.
- From C2: what a mark brings back into its room; the two boundaries for the return; the claim untested for order.
- From C1 and B1:
c1_unapplied.jsonl(5); the form-pass findings, never counted; the B1 bag counts, not reconciled.
Rules kept
Checking.
- Never type an id, an order or a name from memory; check with a script.
- Never log a write before the tool answers. Count a ledger's lines after appending.
- Check a claim about a ledger, a paper or the setting against its source before writing it. Read a check's format before writing a ledger it reads.
Logging.
- There is no
--kind close; log closes as notes. - Log an abductive read with
--kind abductivebefore it runs, with its rules written first. - Log every move with
--kind move, naming its Grodal, Anteby and Holm move, and snap it.
- There is no
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, Edits included, to the same file as parallel calls.
- Count the head's words before the closing line.
Ledger formats.
- Tier events in
account_passes.jsonlare ledger ids. - A superseding finding's
supersedesis the bare id. - Every arrow needs
negative_check. - Proposition ids are the letter N with two digits. The link check does not resolve them, so the head never names one.
- An element cut at C5 becomes a candidate with a history line.
- Tier events in
The store.
mem.py codes --third/--fourth ... --json(label fieldfirst_order);mem.py rooms --with <id> --limit 2000;cite.py --room --code.- The theme a reply sits under does not track its stance.
The permission check refuses:
- deleting a file, even a link;
- shell variables, loops, functions, brace groups, heredocs and words beginning "for_";
find -execwith braces; awk with system() or$fields; env-var prefixes;- cat or jq on
out/diary/;cut -cafter a read;head -n -N.
Write a script in
out/_analysis/instead.Output limits. A Bash output above about 30 KB is cut; measure first. A Read above about 25,000 tokens is refused.
After a compaction, before any other step: read the head, then the stage file, each in full and in that order; run
diary --last 5; and log exactly "compacted; head reconciled" with--kind notein a call of its own.Files and stages.
- Never delete a file; supersede it with a new name. Read the field
only from
out/field. - Do not begin the next leg, and do not summarise it (AGENT.md).
- Never delete a file; supersede it with a new name. Read the field
only from
The next comparison
The return is read against the sealed expectations, the 19 story-miss rooms first. Nothing of it runs on this model until the check leg is launched.