giorgio/MachineSex
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

paper: claim-narrowing revision from the external review

Browse source 
The review's core instruments adopted: the interpretation/explanation/
prediction ladder is now explicit in §1 (with the decisive pre-merge
epistasis-prediction test stated as the open bar, not claimed); identity
claims scoped (WF exact only in the minimal model, with the
learning-kernel deviation cited against ourselves; Muller's ratchet
scoped to the irreversible arm — recombination reassembles only what
survives); "nobody has / none imports / theory outrun" removed;
merge-don't-average given explicit operator boundaries (output-mean vs
weight-average vs routing vs max-with-oracle; budgets; oracle; capacity
handoff to speciation); a "what these experiments do and do not
establish" scope block added to the speciation section (conflict floor
is information-theoretic, not genetic; epistasis-cliff + snowball =
hypotheses at the neural tier; emergent DMIs = flagship hypothesis,
bounded by our null); "control theory" -> "framework" (subtitle
included); §3/§11 overstatements fixed (frozen core != frozen behaviour;
Baldwin echo, not identity; operational vs archival irreversibility);
claims-at-a-glance table (status/assumptions/evidence/limits) added to
§13. Reviewer's framing sentence adopted as the stated core
contribution. Accessible version calibrated to match. md2tex gains pipe-
table support; PDF rebuilds clean (22 pp). Lessons recorded.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BkRLcc18rwT2Lysu6PbG7v
This commit is contained in:
Giorgio Gilestro 2026-09-06 15:14:28 +01:00
parent d6a5c5cacd
commit 58e6c74609
6 changed files with 238 additions and 86 deletions
Download patch file Download diff file Expand all files Collapse all files

15
tasks/lessons.md Normal file
View file

@ -0,0 +1,15 @@
**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".