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

Under 3,000 words, rewritten whole at every close. Last written at C5c-13, 2026-10-15 (UTC). Stages A1 to C4 are done; stage B is frozen. J lifted the C5d freeze for serial work in this branch (C5c-07). The four problems (C5c-08 to C5c-11), the fold-in (C5c-12, pass 15) and C5d's work, redone in C5c-13 by J's ruling (16:29 Amsterdam), are done. Stage C5 is finished; the interview follows; stage D waits for J. `validate.py C5`: 0 errors, 0 warnings.

## 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?

## The current account, and the contrary rooms

The account is `account.md`, pass 15 (3,318 words; passes 1, 3, 4, 5 and 8 kept), 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, Stigmergy until C5c-10).** Members post the mark's state (10 of 14 bearing records; F-018); one member, against C2's criterion. 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 (19 of 26 to 36 of 38, two coders). 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.
- **Cut to candidate:** P06 and R02. K01 restored, with no arrow (F-009). 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):
  1. Work after hour 73 is curation of the record (P12; P22 tentative), apart from carrying on (P13).
  2. The prose pass on the declarations comes first, with the rule written first and each amendment a move.
  3. Stigmergy is recut only if it joins what Heylighen 2016 and Grassé 1959 keep apart.
  4. The C5 readers are the second reader of the declarations; QC5-001 adds the field analyst.
  5. J's language ruling stands.
- **Passes 1 to 4 (C5a).** Declarations amended under the prose rule; A04 bounded; P06 and R02 cut; K01 cut and restored (move 92); nine propositions.
- **J, 07:59 to 09:09 Amsterdam.** I decide what enters and leaves the model; the field analyst reads all 36 declarations against the members' quotes (QC5-001).
- **Passes 5 to 8 (C5c-01 to C5c-04).** The readers' errors fixed; Stigmergy recut by three codings (F-018); 94 pieces of field advice accepted, 30 kept (moves 93 to 146).
- **J, 11:02 and 12:01 Amsterdam.** The field analyst's marks are advice; the room is the unit. Passes 9 and 10 restored K02, A10 and P13 to the room, then changed nothing.
- **J, 13:45 and 14:14 Amsterdam (C5c-07, QC5-002).** The freeze is lifted for serial work; argue from organization design; say how each problem serves the two questions. The border package for a second coder is `field-packages-C5b/`.
- **The serial work, passes 11 to 14,** each with its finding in `serial-C5/`: the unit (C5c-08, moves 150 to 163); thin evidence (C5c-09, F-019, F-020, moves 164 to 167); Stigmergy renamed and "aligned" (C5c-10, F-021, F-022, moves 168 and 169); the reason test (C5c-11, F-023, F-014 superseded, move 170).
- **C5c-12 (pass 15), the fold-in.** The findings folded once into the account, the propositions (the border proposition narrowed), the prose test and the model (A16, move 171); F-019's quote restored to the record's spelling.

## Where the run stands

- **C5 outputs:** `account.md` (pass 15) and earlier passes, `propositions.jsonl` (9; earlier passes kept), `prose-test-C5.md` (pass 14 kept), `sketches.md`, `account_passes.jsonl` (15 lines), `notes-C5.md`, and `serial-C5/` (the four findings and the head before the serial work).
- **C5b to C5d outputs:** `author_claims.jsonl`, `RETURN-C5.md`, `_packets-C5/`, `readers-C5/`, `account-readers-C5.md`, `field-packages-C5/`, `field-packages-C5b/`; and, redone at C5c-13, `data_structure-C5.md` (195 rows), `figure-C5.md` (21 boxes, 20 arrows), `implications-C5.md` (13 expectations), `handback-C5.md` and `interview/C5c-13.md`; C5d's versions kept as `-p14`.
- **Ledgers:** `tier_history.jsonl` 561, `model/history.jsonl` 134, `findings.jsonl` 36 lines (23 findings), `model/elements.jsonl` 30 (23 standing), `model/arrows.jsonl` 21.
- **Snaps** run to C5-move-developing-171. Scripts: `out/_analysis/c5*`.
- **Still open in C5:** 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.** QC5-001 and QC5-002 are answered. QC5-003 asks how the freeze is re-recorded (C5d's hash 24d18e0e…; pass 15's e15f9647…). QC4-001 and QC4-002 are answered; `out/_field-link-superseded-C4a` stays 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_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 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 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 abductive` before it runs, with its rules written first.
  - Log every move with `--kind move`, naming its Grodal, Anteby and Holm move, 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, 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.jsonl` are ledger ids.
  - A superseding finding's `supersedes` is 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.
- **The store.**
  - `mem.py codes --third/--fourth ... --json` (label field `first_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 -exec` with braces; awk with system() or `$` fields; env-var prefixes;
  - cat or jq on `out/diary/`; `cut -c` after 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 and the stage file in full, run `diary --last 5`, and log exactly "compacted; head reconciled" with `--kind note` in 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).

## The next comparison

Stage C5 is finished with the model as pass 15 left it. The next comparison is the one the next stage file sets, against the thirteen expectations in `implications-C5.md`.