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

Under 3,000 words, rewritten whole at every close. Last written at C4a, 2026-10-14 (UTC). This branch was made from claude-v43-1 after C3c, with no file overrides. Stages A1 to C4 are done; stage B is frozen. Stage C4 (the model against the field) closes at C4a with `done.sh C4 --cut interview`. `validate.py C4` before this close: 0 errors, 0 warnings. Next: the stage after C4, as its stage file says.

## 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 model is `model-C4.md`: stage C3's model with stage C4's changes written in.
- **The spine.** A member starts a mark, members call others to place, the members who come build, and once the mark stands they keep it.
- **The call.** A call is the first part of a pair. Joining is the answer it prefers and comes bare ("I'm in"). Refusing comes with a reason.
- **The host sub.** The calls fill the host sub, and the sub draws a line around canvas talk.
- **Neighbours.** Keeping the mark brings the room to its neighbours: it talks with them, settles borders, trades help, and joins coalitions under attack. Members make these agreements without the power to make every placer keep them. Both my rooms and the field show this.
- **Attacks.** A call can turn members against a rival's work. Most such calls are refused inside the room, and the refusal's reason states the room's norm or the attack's cost.
- **A move.** A room that judges it cannot hold its spot moves, and keeps calling.
- **The close.** It runs in order: celebrated, recorded, carried on. Placement ends at hour 73. Organizing around the canvas's records and copies goes on after it.
- **Decided order** is rare, and gathers in the small factions born on the canvas that govern a territory.
- **A claim, untested for order.** In some rooms a tie from before the canvas names the rival in the attack turn.
- **Two boundaries at the return:** colour factions the canvas gathered, and hosts ruling on guests.
- **The four universal problems (C3c).** The rooms allocate work by members choosing their own tasks, divide the picture by a template, inform through the half-built picture and chats, and reward by credit after the work. 19 of 28 fourth-order themes lie outside the four.
- **Three tentative entries from the field (C4), for stage D:**
  - P21: members dispute who may commit the room to an agreement;
  - A21: an arrow from deals to that dispute;
  - P22: after placement ends, members contest which version of the canvas and the event is kept.

**The room that best supports the account: day9.** It builds, 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, rules on guests by vote and by fit with blue, and splits over doctrine.

**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 body's faith or a host's rule picks rivals and guests, it does not.

## Where the run stands

C4 outputs in `out/`:
- `field-C4.md`, `notes-C4.md`, `handback-C4.md`, `interview/C4a.md`;
- `manifest-C4.txt`, naming two successors written whole: `model-C4.md` and `structure-C4.md`. `concept-C3.md` stands.
- `out/field/` holds byte-identical copies of the field's two files.
- Ledgers: `model/elements.jsonl` (30), `model/arrows.jsonl` (21), `model/history.jsonl` (88), `tier_history.jsonl` (480), `findings.jsonl` (25 lines, 17 findings, unchanged).

Snaps run to C4-move-developing-52. QC4-002 is open. The tier is unchanged: 28 fourth-order themes in eight dimensions and 197 third-order themes.

## Stage C4, in short

- **The field.** A separate analyst modelled the event from r/place, sealed from my files, and marked each claim firm (a public exchange) or provisional (an explanation or a limit): two phases and nine processes.
- **The three claims restated before reading** (dealing with other rooms after keeping the work; decided order rare; each room's order its own): none overturned.
- **List 1, five shared mechanisms:** agreements members cannot make every placer keep; a specified design and the local template; a request for space answered with terms; recording the work; placement ends at hour 73.
- **List 2:** P21 with A21, and P22, entered tentative. Neither changes which of the four problems its theme reaches. The event's phases and a smaller venue after a failed template were not entered.
- **List 3, six items:**
  - what ended at hour 73 (subject; sentence bounded);
  - what a template can do (substantive; the sharpest; prose amended);
  - every room before the canvas (substantive, my own error; prose amended);
  - where authority is questioned (setting; F-006 stands);
  - one early buffer against A04's order (not a count disagreement);
  - dating by the hour of a post (a limit).
- **One change by move:** the prose of Standardization of output and Boundary work amended (C4-move-relating-51). The entries are snapped as C4-move-developing-52. No finding changed.
- **The handler's placement error (QC4-001).** The field arrived at `field/` in the run root, and the validator reads `out/field`. I linked it. The handler then asked for a real copy, made and checked by sha256. The guard refused to delete the link, so it was renamed `out/_field-link-superseded-C4a` and waits on QC4-002.
- **The C3c fork's answers,** set aside for a later stage: the C3a Felin and Zenger ruling (setting, not subject); the arrow from the move back to the goal; Visibility returns; Stigmergy's recalled source.

## J on language (C4, 18:20 Berlin; 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 of every sentence.
- Follow ASD-STE100 about 80% of the time: one idea per sentence, active voice, common words with one meaning, and name the actor and the act.
- Describe what members did, in what order, in how many rooms, and do not write figures of speech. Keep construct names as names, and gloss each in plain words where it first appears.

This changes how I write, not what I claim.

## Stage C3, in short

- **C3a.** O'Mahony and Ferraro: setting; F-006 bounded (7 of 39 rooms against 39 of 666, p 0.014 at held size). Olson: open.
- **C3b.** Conversation analysis (recalled) supplied A12's and A16's mechanisms (F-014). The concept is the preferred acceptance, borrowed; its head-count claim failed (F-015, weak).
- **C3c.** The four universal problems put to the structure (F-016); 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 ruled at 23:24 Berlin: "If I am not back please simply review and make the interview you find appropriate. Then start C2", and "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).
- **Passes 2 to 5.** Story counts, told / with residue / not told: 0/20/0, 14/18/0, 16/16/0, 11/21/0, 16/19/0.
- **The reviewer (C2b, C2c).** QC2-001 (the handler, under J's delegation): serving sections of the pass 3 model file is acceptable. Nine errors, six accepted in full, two in part, one refused.

## 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.**
  - QC4-002, the renamed link.
  - The tentative P21, A21 and P22, for stage D.
  - A request for space answered with terms, which is in both sources and not in my model.
  - Follow-on work after hour 73, which no theme names.
  - The story still carries the dropped head-count claim.
  - Declaration prose written at C1 and never tested.
- **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.
  - One coder for every C3 code and the mapping.
  - The constructs' C1 sources still recalled.
- **From C2.** What a mark brings back into its room. The two boundaries for the return. The claim untested for order.
- **From C1.** Thin constructs (Decided order, Neo-tribes, Symbolic boundaries); `c1_unapplied.jsonl` (5); the form-pass findings, never counted.
- **From B1.** J counts 841 B1 bags; an older head said 846. Not reconciled.
- **My doubts.** Where words carry no speaker's sub I read them as the room's own. The verdicts, the vetting coding and the mapping are mine alone.

## 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 against the ledger, and a claim about a paper against the shelf, before writing it.
  - Keep the field's firm or provisional mark wherever a field claim is used.
- **Logging.**
  - There is no `--kind close` and no `--kind episode`; log those as notes.
  - Log an abductive read with `--kind abductive` before it runs, with its rules written first.
  - Log a move with `--kind move` and snap it.
- **Questions.** A question to J is `mem.py ask "<question>" --assume "<meanwhile>"`. Read an answer with `mem.py asks <id>`.
- **Writing and checks.**
  - Never put a placeholder or a no-op in a command or a log line.
  - Never put an Edit or Write and the check that verifies it in one turn.
  - Count the head's words before the closing line. Never write an id-like token the run does not define in the head.
- **Reading the store.**
  - Draw from the store with `mem.py codes --fourth/--third ... --json` (label field `first_order`); `mem.py codes --grep <re> --json` searches words.
  - `mem.py rooms --with <id>` prints plain text, paged at 80 lines; pass `--limit`.
  - `cite.py` serves by `--room` and `--code`.
  - The theme a reply sits under does not track its stance.
- **The permission check refuses:**
  - deleting a file (`rm`), even a link;
  - shell variables set and expanded; shell loops and words beginning "for_"; shell functions, brace groups and heredocs;
  - `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.** Never delete a file; supersede it with a new name. A generated document that must keep its name is corrected in place with Edit, and its script is fixed too. The field is read from `out/field`.

## The next comparison

The stage after C4, as its stage file says. Carry into it:
- the model as `model-C4.md`, the structure as `structure-C4.md`, and the concept as `concept-C3.md`, borrowed and not leaned on;
- the tentative field entries, which stage D sends to every room;
- J's ruling on language for every sentence written.