MachineSex/tasks/lessons.md
Giorgio Gilestro 9b0ca32f51 llm_society: the composed society at LLM scale (C3) — loop, tests, smoke green
E11 re-instantiated in a population of LoRA agents, closing the paper's stated
gap before submission (GG: a weeks-scale experiment a reviewer would demand).
One grounding knob in the evaluation channel (g*verifier + (1-g)*conformity,
exactly E11); inheritance is identical in all arms and deliberately ungrounded
(children distilled from their source's own answers - self-consumption made
literal). Directed sex = complementary pairing + Dirichlet offspring screened
on the arm's own signal (the verifier never enters the no_grounding loop);
QD selection on verifier-free behavioural distance; terminal-degeneration
fallback copies the parent instead of crashing a sweep. Pure operators
unit-tested (155 green); smoke run end-to-end on the local A4000 already
shows the self-consumption signature (conformity up, diversity down in one
generation). Design, falsifiers, cost table: tasks/workorder-llm-society.md.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BkRLcc18rwT2Lysu6PbG7v
2026-09-07 11:55:19 +01:00

39 lines
3.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

**2026-08-11 — Stop padding time estimates.** GG: "You generally massively overestimate the time it
takes to do some work... You're fast." Phase-1 items I scoped as "Week 1" took ~an hour. Rule: state
what will be done and in what order; give a duration only when compute-bound (training walltime), and
base it on measured runtimes, not human-project heuristics.
**2026-08-11 — Correspondence is not identity; interpretation is not prediction (manuscript reviews).**
The external review's core corrections, to internalise for all paper claims: (1) distinguish
interpretation / explanation / prediction and claim only the level the evidence supports; (2) a
minimal model being exactly Wright-Fisher does not make real training "literally" WF — our own
learning-kernel result says otherwise (cite it against ourselves); (3) name the operator every claim
is about (output-mean vs weight-average vs max-with-oracle vs routing are different objects with
different budgets); (4) don't write "nobody has / none imports" — invite no priority disputes; say
"to our knowledge" and state the positive contribution; (5) negative results (E13b) are strengths —
lead with them; (6) "control theory" needs states/controls/dynamics/rule or it's a "framework".
**2026-08-11 — tmux does NOT survive SSH disconnects on this machine.** The tmux server starts inside
the SSH session's systemd scope and gets reaped on logout (lost ~20 min of the epistasis grid; GG:
"SSH disconnected"). Reliable pattern here: `systemd-run --user --collect --unit=<name>
--working-directory="$PWD" bash -c '<cmd>'` — lands in user@.service (kept alive by the desktop
session), survives disconnects; check with `systemctl --user is-active <name>`, logs via redirect.
**2026-08-11 — Internal deliberations must not leak into reader-facing prose.** GG (on the
convergence paragraph): it "carries all the ghosts of our internal brainstorming that should be
completely alien to the readers (this is, alas, a recurring problem with your writing)." The pattern:
strategic concerns from the working process (priority anxieties -> "we cite for priority of
publication"; calibration debates -> "the honest statement"; positioning battles -> "nobody has")
surface as defensive or self-referential prose. Rule: before finalising any reader-facing passage,
ask "does understanding this sentence require knowing how we worked?" If yes, rewrite it as a plain
statement about the literature or the result. Confident papers situate; they do not litigate.
(Promoted to a general rule in the global ~/.claude/CLAUDE.md, 2026-08-11 — it applies to all
reader-facing prose in every project.)
## Terminology: "model" is overloaded in this project (2026-09-07)
In the PNAS manuscript and figures, "model" must mean an AI model. The theory tier is
"population genetics" / "the WrightFisher simulator" / "the minimal inheritance model"
(with the disambiguating adjective), never a bare "model" label — GG flagged Fig. 1's
"Exact model" header as confusing for exactly this reason. When naming tiers, panels, or
headers, reserve the bare word for trained AI systems.