Verification record · 12 October 2026

The conclusion rests on checked relationships, original contexts and explicit population assumptions.

This record accompanies the readable report. Alcuin made the final assessment. Sonnet 5.5 produced the detailed research and the requested follow-up checks. “Checked by Alcuin” below means a source, script, data table or DNA read was inspected in this investigation. It does not mean that every assertion in a source was verified. The research archive includes working drafts for provenance; this record and the readable report supersede their uncorrected claims.

Alcuin checked the findings that materially changed the comparison.

The principal findings have different verification histories.
FindingSonnet’s workAlcuin’s independent checkRemaining limit
CB-01 contains an ancient man, I37241.C located the public alignment and examined the defining markers. C2 received the raw-read result for challenge.Rebuilt the cached chromosome-Y alignment independently, validated its structure with samtools, and parsed quality-filtered reads at original published hg19 coordinates. Eleven defining sites and two Z18271 sites survive strict trimming after adding the full defining-site panel. The narrower Z18271 assignment is probable: one supporting site has a damage-prone change. Read original Supplementary Tables 1 and 3.The location, community and individual date interval are withheld or absent from the examined table. No new contamination estimate was computed.
I4517’s deep automatic call conflicts with the reads.C independently checked the Megiddo data. C2 was asked to challenge the ancestry interpretation.Fetched the public 145 MB aligned file, indexed it, inspected both opposing-strand reads at ZS231, and checked the site with samtools mpileup. Read the original sample row and burial context.Two reads at one transversion oppose this depth. One conflicting derived CpG-transition read at ZS2434 is retained in the final record. It does not outweigh the two cleaner opposing reads.
R835 does not confirm the old B877 label as modern CB-01.C mapped the older B877 mutation list to today’s finer branches. B2 checked the original Roman context; C2 checked the exact read evidence.Retrieved only the chromosome-Y ranges from the indexed public alignment and independently found ancestral reads at four CB-01 sites plus ZS227 after expanding the defining-site panel.The source’s older branch name grouped mutations now separated across several levels. Sparse reads do not establish every downstream alternative. AADR flags X-chromosome contamination of 1.8–2.9%.
I14846 has a strong Jewish context but thin CB-01 evidence.B read the original cemetery and kinship record. C checked Y sites; D2 corrected the model’s denominator.Read the original sample and quality rows. Rebuilt the chromosome-Y file and found one qualifying derived transversion read. Verified 33 people, 14 males and ten published Y assignments.One read cannot support the same confidence as I37241’s many independent sites. There is no individual radiocarbon date for I14846.
I45358 is an older-diverging relative; I43272 is inside Z642.C examined the public chromosome-Y alignments and branch tables.Rebuilt both alignments and repeated the read parsing. I45358 retains the earlier base at ZS222 in five strict-filter reads; I43272 has derived reads at two Z642-block sites.Alcuin did not independently check all of I43272’s four terminal FT416287 mutations; that deeper result is Sonnet’s read-level analysis.
CB-02 has documented Jewish and Levite-associated relatives.A2 located the original 2026 Moroccan Jewish paper and traced aliases and branching.Inspected the published Figure 4 and adjoining text, the cohort description and ROQ2 discussion. Walked the saved tree independently for BY8508, BY8536/BY8528 and CTS9507.Surname and tradition are mixed in the association. Counts differ within the paper. Neither the older shared node nor ROQ2 has a demonstrated Levite identity.
The Samaritan placement is deeper than the earlier account stated.A and C located the published Samaritan-labelled kit within FGC62618. A2 checked the community labels.Viewed original Waas Figure 1; checked Table 1 and the discussion of Jewish families. Read the original broad Samaritan assignments.The identity of WL329 as the Marhiv family remains an inference; the missing sample supplement was not recovered.
The Z642 rarity calculation cannot supply patriarchal odds.A reproduced the window, aliases, overlaps and threshold sensitivity; A2 independently recalculated the flags.Recomputed the criteria from 139 available original child-country reports; one missing child used the original saved summary. Reproduced 78 selected rows, 66 resolved rows, 65 distinct branches, four A rows, nineteen B rows and one joint result. Verified all eight “Ashkenazi-country” testers were German-labelled.The archive remains a selected commercial database. Unresolved branches, missing community labels and post-observation criteria prevent a calibrated reference probability.
The population quantities cannot be substituted for one another.D audited source code and 1,310 prediction rows. D2 corrected dates, the Erfurt denominator and arrival timing. D3 traced actual father chains and varied incoming paternal membership.Read the actual cutoff, marriage ceiling, birth-stop and forward-recursion code. Independently derived the three modern Y products in pure Python. Reviewed and reran the deterministic cohort calculation; it reproduces the saved mean-field values.The demographic assumptions are not estimated by the ancient data. The large pedigree and the largest conditioned sibling-line simulation were not rerun from scratch.

The targeted read checks retain both positive and negative evidence. A DNA read is one sequenced fragment. Mapping quality estimates how reliably it was placed in the genome. Base quality estimates the confidence in a particular letter. Trimming removes letters near fragment ends, where ancient-DNA damage can be concentrated. These filters reduce common errors; they do not prove authenticity or historical identity.

The independent scripts use GRCh37/hg19 coordinates from Sahakyan’s original Supplementary Table S2, with current-tree aliases checked separately. The original alias lookup contained 232 positions, including fourteen CB-01 sites. C2 found that it missed unnamed or absent markers. The corrected audit contains 247 positions, including all 25 sites in the checked FamilyTreeDNA CB-01 panel and all three sites in its ZS2434/ZS2435 descendant panel. Sonnet checked the added coordinates against the public marker tables and assembly references. The analysis uses samtools 1.24 to read alignments, then parses CIGAR operations explicitly. It removes unmapped, secondary, supplementary, duplicate-flagged and quality-failed alignments. It compares mapping-quality thresholds 20 and 30, requires base quality at least 30, and compares removal of zero, three and seven bases at each end. It collapses repeated observations with identical start, end and strand into a single molecule for the audit. The primary modern tree file has SHA-256 38394cb274e27be2f5cca97237b5cdfb4cd03b3281bba3eb7f201a9eb0389b38. Sahakyan and colleagues, 2021

These hg19 positions retain reads at mapping quality ≥30, base quality ≥30 and seven-base end trimming.
ManMutation names; position; earlier→derived base; retained read countsTarget positions with any base-quality ≥30 read before strict trimming
I37241S20075; ZS227; 17690375; G→T; {'T': 1}
B877; S8223; ZS222; 2709209; T→C; {'C': 6}
FGC13862; Y3083; 7737112; G→T; {'T': 6}
S10608; 7751938; G→T; {'T': 3}
Y3084; ZS231; 7833897; G→T; {'T': 3}
FGC13867; Y3093; Z18265; 8481671; G→T; {'T': 2}
FGC17475; Y7290; ZS2438; 14102079; C→A; {'A': 3}
ZS2401; 14933771; T→G; {'G': 4}
S19350; 17205362; G→A; {'A': 3}
Y3090; ZS238; 17652477; C→A; {'A': 1}
FGC13864; Y3091; Z18284; 21287064; C→A; {'A': 1}
S25313; ZS228; 23207674; A→C; {'C': 1}
FGC13872; Y3092; Z18271; 22026142; C→T; {'T': 4}
S24930; 22961014; C→A; {'A': 2}
CTS5799; Z2296; 16486773; G→T; {'G': 4}
CTS11754; 23252135; G→A; {'G': 3}
ZS2434; 8511782; G→A; {'G': 8}
178
I4517Y3084; ZS231; 7833897; G→T; {'G': 2}
ZS2434; 8511782; G→A; {'A': 1}
35
R835S20075; ZS227; 17690375; G→T; {'G': 1}
FGC13862; Y3083; 7737112; G→T; {'G': 1}
FGC17475; Y7290; ZS2438; 14102079; C→A; {'C': 1}
FGC13876; Y3467; Z18269; 16218220; G→A; {'G': 1}
FGC13874; 16757719; G→A; {'G': 2}
S24930; 22961014; C→A; {'C': 1}
67
I14846Y3084; ZS231; 7833897; G→T; {'T': 1}6
I45358S20075; ZS227; 17690375; G→T; {'T': 1}
B877; S8223; ZS222; 2709209; T→C; {'T': 5}
FGC13862; Y3083; 7737112; G→T; {'G': 3}
FGC13867; Y3093; Z18265; 8481671; G→T; {'G': 1}
FGC17475; Y7290; ZS2438; 14102079; C→A; {'C': 1}
FGC13877; Y14232; Z18267; 14253667; G→T; {'G': 1}
FGC13874; 16757719; G→A; {'G': 4}
S19350; 17205362; G→A; {'G': 2}
FGC13864; Y3091; Z18284; 21287064; C→A; {'C': 1}
S25313; ZS228; 23207674; A→C; {'A': 4}
FGC13872; Y3092; Z18271; 22026142; C→T; {'C': 1}
S24930; 22961014; C→A; {'C': 3}
CTS5799; Z2296; 16486773; G→T; {'G': 3}
CTS11754; 23252135; G→A; {'G': 1}
ZS2434; 8511782; G→A; {'G': 4}
172
I43272S20075; ZS227; 17690375; G→T; {'G': 1}
B877; S8223; ZS222; 2709209; T→C; {'T': 2}
S10608; 7751938; G→T; {'G': 3}
Y3084; ZS231; 7833897; G→T; {'G': 4}
FGC17475; Y7290; ZS2438; 14102079; C→A; {'C': 2}
BZ4063; 14175863; T→A; {'T': 1}
ZS2401; 14933771; T→G; {'T': 1}
FGC13874; 16757719; G→A; {'G': 2}
S19350; 17205362; G→A; {'G': 1}
Y3090; ZS238; 17652477; C→A; {'C': 2}
S25313; ZS228; 23207674; A→C; {'A': 2}
S24930; 22961014; C→A; {'C': 1}
CTS5799; Z2296; 16486773; G→T; {'T': 2}
CTS11754; 23252135; G→A; {'A': 4}
ZS2434; 8511782; G→A; {'G': 2}
159

I37241’s two published double-stranded, partially UDG-treated libraries each have about 10% terminal C-to-T damage. Their mitochondrial-consensus match intervals are 0.992–1.000 and 0.989–0.999. These are authentication-related metrics, not direct estimates of Y contamination. The original table gives mean coverage 3.722 on the autosomal capture targets. That is not whole-Y coverage. Both libraries come from the same individual, so they are not two independent people. Akbari and colleagues, 2026, original tables

I4517’s retained ZS231 observations occur on distinct fragments and opposing strands; both have mapping quality 37 and base quality 36. ZS231 is a G→T transversion, a change that is not the usual ancient C→T or G→A deamination pattern. I14846’s single T at the same site is therefore useful but still thin. His original quality table reports too little data for a male-X contamination estimate. Missing sites are not coded as ancestral.

The independent audit does not turn a marker tally into an automatic terminal assignment. My initial explanation of I37241’s ten-versus-eleven count was wrong: the difference came from the marker list, not quality thresholds. The omitted ZS2401 site, hg19 Y:14,933,771, retains four derived G reads even with mapping and base quality ≥30 and seven-base trimming. I added the full defining-site panel and reran all six men. The final eleven-site result agrees with Sonnet. This correction also added a fourth ancestral CB-01 site, FGC13874, for R835.

The expanded audit retains I4517’s conflicting A at ZS2434, hg19 Y:8,511,782. Its read has mapping quality 37, base quality 32 and fourteen bases to the nearer end. The change is G→A at a CpG site, so ancient damage or recurrence is a more plausible concern than at ZS231. This single read cannot overcome the two independent ancestral G reads at ZS231 without an explanation of the inconsistency. My alias-only script had missed this position because the original spreadsheet left its marker-name field blank. Sonnet found that blind spot; the final table now displays it.

Sonnet withdrew the apparent upstream contradictions for I14846: their mapping quality was zero, so they did not reliably come from the intended Y position. The usable ZS231 read and the published manual J-Y3088 assignment agree. That supplies moderate support for CB-01, but not multiple-site confirmation. The original library table calls its treatment ss.half while AADR calls it ss.USER. Neither source publishes a usable X-contamination estimate for this boy.

The broader analysis excluded inconsistent sites such as Z2293 and Z27715 when they conflicted across otherwise well-supported branches. R835’s source label B877 is especially misleading if read as a modern terminal label: the 2021 marker list spans the present ZS241, FGC13873, FGC13863, ZS227, ZS222 and Z18271 levels. Its label alone cannot establish membership in all of them. Sahakyan and colleagues, 2021

R835’s earlier-related placement also has positive evidence: a non-damage-type T→C change at Z18264/FGC13870 and one at F23384 in the BY143137 family. The lone derived ZS241 G→A read is weaker evidence because damage can cause that substitution. AADR places him at BY143137 and flags hapConX at 1.8–2.9%. FamilyTreeDNA places him more deeply at FTH61646, but that one-man branch was built from this same ancient file; it is not independent confirmation. The ENA sample description establishes Civitanova Marche and an archaeological period range of 27 BC–AD 300. The Antonio burial-detail supplement could not be opened. None of the original sources inspected assigns him a Jewish identity.

The date estimates remain tied to their own methods. FamilyTreeDNA Discover

Published calendar estimates are reported without fitting them to the biblical chronology.
Branch or observationEstimate usedMeaning and qualification
CB-01 / J-ZS222Lipson text: 833 BC, reported 95% interval 1289–440 BC; Table 3: 834 BC, 1291–440 BC. FTDNA snapshot: 840 BC, 1293–449 BC.These estimate the shared ancestor of the tested descendants. They do not date Aaron or the beginning of priestly status.
CB-02 / E-BY8508Lipson Table 3: 691 BC, 1548–17 BC; text: 697 BC, 1555–21 BC.The four newly recruited members do not make this a population prevalence estimate.
CB-03 / J-FGC4992Lipson Table 3: 534 BC, 981–152 BC; text: 539 BC, 987–156 BC.The old regional part of the branch can precede the proposed patriarchal history. A younger surviving ancestor does not require late acquisition of priesthood.
J-Z642FTDNA formation: 2211 BC, 95% 2912–1608 BC. Shared ancestor: 1625 BC, 2245–1095 BC.Formation is tied to the parent-branch estimate, not a directly dated mutation or Abraham’s birth.
J-YSC0000234FTDNA shared ancestor: 3352 BC, 4117–2682 BC.This joins the CB-01 and Z642 sides. It is not Noah’s identification.
E-Y2850 / FGC2185FTDNA shared ancestor: 2211 BC, 2932–1593 BC. YFull snapshot prints 3800 years before its present, with range 3400–4200.This joins the E priestly and Levite-associated ancestries. Point estimates precede Jacob and Levi; databases differ. The modern labels do not date status at the shared node.
E-CTS7178FTDNA shared ancestor: 1555 BC, 2351–897 BC.This joins the CB-02 side with ROQ2’s ancestry. It does not identify a known son of Levi.
I37241, I45358, I43272Original table mean BP: 1850, 1200, 250 years before AD 1950, respectively.These convert to about AD 100, AD 750 and AD 1700. The examined individual table supplies neither individual intervals nor dating methods. They are not exact dates.

The YFull file used by the earlier selection was version 14.04.0: 68,881 nodes and 43,250 terminal haplogroups. Terminal haplogroups are not counts of tested men. Sonnet checked a later public 14.06 tree, which changes the examined candidate ages modestly. The main report uses explicit calendar estimates where available. YFull’s “before present” footnotes for ancient specimens must not automatically be assumed to define every modern-clade clock field. The archive preserves the printed values and the follow-up on that convention.

Lipson uses a stated 0.76 × 10⁻⁹ changes per site per year in its dating pipeline; Sahakyan uses 6.95 × 10⁻¹⁰ with its own uncertainty and Bayesian dating method. Closely matching estimates built from overlapping men and similar clocks are not independent confirmations. No rate was recalibrated here. No estimate for repeated exceptionally late fatherhood was invented. The preprint’s cited supplementary mutation Tables 1–9 were not found among its three deposited supplementary files; public marker tables were used for the targeted tests instead. Lipson and colleagues, 2025 preprint · Sahakyan and colleagues, 2021

The population calculations explain how a paternal frequency can arise before calculating detection.

Let x be the share of resident men on the proposed father line. Let ρ be their surviving-son production relative to other men. Between arrivals, the deterministic calculation uses x_next = ρx / (1 − x + ρx). A value of ρ = 1 preserves the share even when both groups grow. A value below 1 reduces it. A value above 1 increases it. Each incoming cohort adds the assumed number of paternal descendants to the region. The shared denominator follows the source population growth.

The detailed sensitivity uses ρ = 0.95, 1.00, 1.05 and 1.15; it uses 30-year generations and seven modelled arrival cohorts. The earliest main cohorts arrive near 2369 BC; smaller cohorts arrive later. It varies the assumed paternal membership of arriving males through 10%, 50% and 100%. These are alternative assumptions, not fitted estimates. The source population is about 1,002,557 people near 2362 BC, halved to an assumed 501,278 males. Population growth is about 1.0113 per generation and is extrapolated after the last available source-model date.

D3 traced the retained example pedigree instead of inferring Y from overall ancestry. In that one run, 67 of 67 male members of the two departing Levant households have a father chain to Noah. The incoming outside partners in those households are women. After local marriages, only 133 of 183 retained Levant-family males at 2200 BC have that father chain. The latter denominator contains followed family members, not all regional men. The observation describes the programmed example, not real Bronze Age households. Pruning and absent servants or retinues limit it.

The deterministic table uses the expected arrival cohorts, so it is a mean-field reference path. Because reproduction becomes nonlinear when the share is large, it is not exactly the average over random histories. D2 separately simulated 40,000 histories per setting, including random surviving sons and possible extinction. Its household-presence assumptions are independent even though the original runs could contain correlations. D3’s additional survival approximation uses Poisson offspring and density feedback from the deterministic path; it was checked against the full-founder simulation but not separately validated for the smaller founder fractions.

For an already recovered collection, let w be the relative probability that a carrier enters the collection, compared with another man. The carrier share among recovered men is xw / (1 − x + xw). Let r be the conditional chance that a recovered carrier’s informative mutations can be read and recognised. The expected recognised fraction is then r × xw / (1 − x + xw), before allowing false assignments. Under independent sampling, the probability of at least one recognised carrier among n men is 1 − (1 − O)ⁿ. Actual collections require site, date, burial, preservation, kinship and readability information to estimate those terms. A general preservation probability should not be multiplied in again when the denominator already consists of recovered men.

Recognition of a genetic branch is not recognition of Noah. If an older branch was already present among the receiving population, its ordinary local descendants contribute the same broad marker. The observed branch frequency then combines the proposed introduced family with that background. A source-specific private mutation or a securely contextualised narrower relationship is needed to distinguish the histories. This limitation applies even to perfect DNA.

The later forward calculation has a different denominator. It begins with Jacob’s household and computes A_next = (1 − m)A + mA_outside. Its paternal share is a product of (1 − p), where p = 2mφ is the assumed contribution of outside fathers and φ is the male fraction assigned to incorporation. A three-step counting delay is an input, not an established historical fact. The pure-Python independent check reproduces the modern Ashkenazi Y values 0.9137302243, 0.4992375692 and 0.1259263745 for the stated low, middle and high input sets. The zero-delay middle result is 0.4942294721.

The early map, the later pedigree, the community forward calculation and the branch-detection simulations are separate models. The map imports the earlier population model. The pedigree supplies selected ancestry-threshold counts. The forward model constructs an approximate outsider mean from those counts and carries it forward. It does not generate the full early-to-modern population history. The fitted 5–7% or 20% Jacob-share variants target imposed numbers; their resulting fit cannot count as another observation.

The review corrected material errors instead of treating worker drafts as established results.

The final assessment uses these corrections.
Earlier statement or shortcutCorrection used in the report
Every ancient B877 or J-Y3088 label establishes exact CB-01 membership.Read the individual mutations. I37241 is strong; I14846 is tentative; I4517 and R835 contradict the relevant deep placements.
No ancient CB-01 man is known.This describes the 2025 preprint’s claim. The new 2026 I37241 evidence supplies a verified example with withheld context.
A common ancestor younger than Aaron excludes Aaronic descent.Only surviving tested sons’ lines determine that estimate. The founder can be older without clock error. This rule also applies to CB-04–CB-09 and the R1a Levite branch; a young crown alone does not exclude them.
CB-03 must preserve priestly status through its entire 5,500-year branch.The earlier part can belong to regional ancestors. A proposed priestly tradition starts with Aaron, not with the branch’s oldest split.
CB-01 is necessarily priestly throughout every sub-branch.The preprint includes lay and unknown-status descendants. Neither surname nor branch membership alone proves priestly status.
Z642 has an Arabian-only child and an independently predicted multi-diaspora child.The actual rule allows 20% other known origins, excludes several Arabian-related countries, uses unverified country proxies, and was written after the pattern was visible.
66 resolved comparison rows are independent families.There are 65 distinct resolved branches and extensive ancestor–descendant overlap. Twelve original rows remain unresolved.
The brother-line model samples 33 Erfurt men.There are 33 people, 14 males and ten Y assignments. This affects the ancient-carrier calculation separately from the modern-test simulation and its perfect tribal labels.
The pedigree’s declining overall-ancestry count measures paternal disappearance.The model discards low-overall-ancestry people and limits marriages. A retained father chain must be followed separately.
The Levant’s average arrival is 2311 BC.That was an unweighted average across possible household names. The expected-people-weighted date is about 2356 BC, with most expected arrivals near 2369 BC. The final scenarios use cohorts.
Half the incoming household automatically equals Noah-line men.Sex ratio and father-line membership are separate. The retained example supports that membership by its programmed fathers, while the sensitivity explicitly varies the real-history assumption.
CB-01 is established as 2–4% of all Jewish men.That figure was used as a conditioned target without a verified population denominator here. The resulting claim of a measured 100–700-fold excess over a neutral model is not retained.
An unrecognised family requires no assumptions.It needs a history of status, survival and testing that explains both its missing recognition and the recognised priestly families.
AGDP supplies no useful early J1/J2 material.It includes an Early Bronze J2b man and some public overlap with later releases. No known member currently decides the principal family comparison. AGDP includes I1730, an Early Bronze J2b man available publicly elsewhere; it is not devoid of Levantine J2 evidence.

The source record distinguishes inspected data from located material.

AADR was checked against Dataverse version 14.0, released 8 June 2026, carrying v66.p1. The local annotation’s MD5 matched a2db1ac16f0f3558ed66fb251e1d5c7d. Its 23,089 rows represent 21,433 distinct individual identifiers; repeat genetic versions are not additional people. Some important 2026 individuals are absent from that release, so Sonnet also inspected the original later datasets. The inventory covers nineteen dataset/publication entries and 183 individual records, with evidence tiers. Those records are a searched collection, not proof of an exhaustive worldwide census. AADR, v66.p1, Dataverse release 14.0

Primary archaeological and genetic material inspected includes Agranat-Tamir’s sample and kinship workbook; Feldman’s Philistine contexts; Haber’s Sidon and Beirut tables; Waldman’s Erfurt sample and quality workbook; Brace’s Norwich report and supplements; the Tàrrega paper; Akbari’s original individual and library tables; Sahakyan’s marker spreadsheet; Lipson’s preprint and available supplements; Shen and Oefner’s Samaritan studies; Waas’s original figure; Hammer’s original text; Rootsi’s Table 2; and Levy-Toledano’s original PDF and figures. The final supplementary context checks are retained with the relevant workers.

The most consequential access limits are the 2026 study’s anonymised archaeological metadata, deposited under an embargo to 2041; the missing Lipson mutation-table files; Waas’s unrecovered sample supplement; uncertain public documentation of the finer Tsedaka and Danfi family assignments; raw-only Mödling data that were not aligned here; the unverified I14918 burial association; and the Antonio supplement describing burial details for R835. No researchers were contacted. No new laboratory work was commissioned. The investigation did not use an autosomal profile to infer a withheld individual’s religion or precise location.

The execution record confirms Sonnet delegation and discloses auxiliary usage.

Each research launch explicitly requested claude-sonnet-5-5.
AssignmentWork delegatedModels listed in returned usageCompletion recordAdvisor setting
ACandidate histories and selection auditclaude-sonnet-5-5, claude-haiku-5-5completedNot explicitly disabled in this launch
A2E relatives, original associations and fairness correctionsclaude-sonnet-5-5, claude-haiku-5-5completedNot explicitly disabled in this launch
A3Final dating/candidate review and regional modern sourceclaude-sonnet-5-5completedDisabled explicitly
BAncient contexts, release inventory and time coverageclaude-sonnet-5-5, claude-haiku-5-5completedNot explicitly disabled in this launch
B2Context, denominator and accessible-data checksclaude-sonnet-5-5completedDisabled explicitly
CConnected tree, variants, dates and ancient readsclaude-sonnet-5-5, claude-haiku-5-5completedNot explicitly disabled in this launch
C2Challenge of decisive read evidence and date conventionsclaude-sonnet-5-5completedDisabled explicitly
DDemographic-code audit and reproduced outputsclaude-sonnet-5-5, claude-opus-5-5completedNot explicitly disabled in this launch
D2Erfurt correction, arrival scenarios and stage datesclaude-sonnet-5-5completedNot explicitly disabled in this launch
D3Father-chain membership sensitivity and corrected inferencesclaude-sonnet-5-5completedDisabled explicitly

The main research model is recorded as claude-sonnet-5-5 in completed runs. Original A, B, C and A2 records also contain Haiku usage. Original D additionally records Opus usage. The saved usage totals do not identify the purpose of each auxiliary call, and no conversation transcript was retained. Claude documents separate advisor and auxiliary processing features, so an advisor is a possible explanation for the Opus entry, not a verified account of this run. No intentional replacement of the requested main model occurred. Later launches explicitly disabled the advisor and set auxiliary defaults to Sonnet. The final A3, B2, C2 and D3 usage records list only claude-sonnet-5-5. The official advisor documentation describes the optional mechanism; it does not establish why the earlier run recorded Opus.

The launcher used Claude CLI 2.1.296 with an explicit main-model name, safe mode, no session persistence, read/write tools limited by the assignments, and no fallback-model option. Changes to advisor and auxiliary defaults applied only to these process environments. The original projects were treated as read-only. The supervisor retained the final research design and interpretation. Raw worker drafts contain the substantive results but also the errors corrected above; they must not be quoted as the final conclusion.