Skip to content

The Proto-Semitic Origins of E1b1b1: The Afro-Asiatic Founding-Fathers of Semitic Identity and Beyond

Aug 2026 · Zenodo (CERN European Organization for Nuclear Research)
Forensic and Genetic Research

Abstract

Version 2 — Changelog / Abstract (Version 2) What's new: Since the original Version 2 draft, this paper has grown from a single-thread argument about E1b1b's Levantine origins into a more rigorously sourced and considerably more self-critical treatment of the same core claim — that E1b1b, not J1-P58, represents the deeper indigenous Levantine paternal substrate underlying Semitic-speaking populations. Below is what actually changed. Subclade resolution (the core argument, tightened). The Samaritan priesthood's E-M78/E-V22 lineage is now explicitly distinguished from the Luria rabbinical line's E-V12, with the Natufian aDNA sample tables, a full non-Semitic J1/J1-P58 global distribution table, and independent G25 autosomal distance data all added as supporting evidence rather than left as prose assertions. E-M81 treated as an open question, not a foregone conclusion. Competing Near Eastern-origin and Northwest African-origin hypotheses are weighed against each other rather than resolved by fiat — including a genuine tension the source literature itself flags (STR diversity pointing east, TMRCA and ancient DNA pointing west). Csaba-Barnabás Horváth's (2021) independent YFull-based TMRCA estimate for E-M81 (~800 BCE) was folded in as a convergent third data point alongside Solé-Morata et al. (2017), modestly strengthening the Northwest African reading without treating either estimate as final. A wider intellectual context for the E-M78/Semitic question. Horváth's "Semitic re-migration" model is presented as a third account of a real paradox — E-M78's genetic diversity peaks in the Levant, but Afro-Asiatic's linguistic diversity peaks in Africa — alongside his separate proposal that specific J1/J2 subclades mark a pre-Semitic Indo-European population in Northern Mesopotamia, which directly reinforces this paper's existing argument that J1/J2 track later population movements rather than deep Semitic ancestry. Both are flagged clearly as a single author's hypotheses from a non-specialist venue, not consensus findings. A full craniofacial-morphology section. Reviews the historical Caucasoid/Negroid classification of Iberomaurusian and Nazlet Khater remains and shows the framework produced contradictory verdicts even among its own practitioners — the same population scored on opposite sides of the same racial axis by the same researchers. Includes a facial-reconstruction gallery graded explicitly by evidentiary tier (peer-reviewed vs. artist interpretation vs. commercial marketing), and is linked directly to the paper's existing "Aspirational Whiteness" discussion with a concrete case study. A primary-source interlude on the Book of Gates. The ancient Egyptian "Four Peoples" (Rmt/Aamu/Nhsyw/Tjhnw) iconography is tested against current genetic and isotopic evidence, identification by identification, with a mixed, honestly reported result — the Aamu/Levantine identification holds up well, Nhsyw/sub-Saharan affinity holds up as real but non-majority, Rmt/East African phenotype is genuinely contested in the literature, and Tjhnw/Sea Peoples fits some tomb versions but not others. Corrective housekeeping on circulating claims. Includes the corrected dating and provenance of the widely shared JK2134/JK2888/JK2911 facial reconstructions, a careful description (without characterizing it as fraudulent) of a circulating social-media claim about a "Saudi Genome Project," and a documented comparison of divergent Queen Tiye reconstructions. The Cohenim Controversy. A new section traces the popular "Cohen Modal Haplotype = J1" framing back to its own founding data — the original "Cohen-1" and "Cohen-2" samples were typed E3b/M78, not J1 — and documents an internal inconsistency between FamilyTreeDNA's consumer migration maps and its own haplogroup-story pages for the same lineage, with reference to the author's companion publication on FTDNA's cartographic accuracy. Also fixed along the way: several duplicate bibliography entries, one incorrect sample citation (Erfurt Ashkenazi), and multiple content-ordering errors introduced during editing were caught and corrected. ________________________________________________________________________________________________________________________________________ The determination of the primary patrilineal genetic signature associated with the emergence of Semitic languages and the ancient Israelite population remains a subject of intense debate in archaeogenetics. This study critically evaluates two competing hypotheses: the "Levantine-Presumption," which posits Y-haplogroup J1-P58 (J1a2b) as the indigenous Semitic marker, and the "Autochthonous-Continuity" model, which identifies E1b1b1 (specifically subclades E-M215 and E-V68) as the true proto-Semitic lineage. By synthesizing temporal sequencing, autosomal ancestry profiles, and the archaeological record of the Natufian and Neolithic Levant, this paper argues that E1b1b1 is the superior candidate for the original, patrilineal Semitic and Israelite lineage. The evidence demonstrates that E1b1b1 exhibits deep continuity in the Levant predating the Bronze Age by millennia, whereas J1-P58 appears abruptly in the region coincident with Indo-Aryan/Indo-Iranian migrations, lacking the requisite pre-Bronze Age indigenous substrate. While the haplogroup J1-P58 is frequently conflated with Semitic identity in modern discourse due to its high frequency among contemporary Arab and Jewish populations, a rigorous archaeogenetic analysis suggests this association is largely a result of later demographic shifts rather than deep ancestral roots. This paper posits that haplogroup E1b1b, specifically subclades E-M215 and E-V68, represents the truly autochthonous patrilineage of the region, deeply rooted in the Natufian and pre-Neolithic populations of the Levant and North Africa. By synthesizing ancient DNA (aDNA) data from Natufian contexts (~12,000 BCE) through the Bronze Age Canaanite and Iron Age Israelite periods, this study demonstrates a continuous presence of E1b1b that predates the Bronze Age influxes of Caucasus-and-steppe-derived J1a, R1a, and R1b. The analysis further examines the genetic profiles of modern Samaritan Cohanim, who, unlike theirdiasporic counterparts, retain E1b1b lineages consistent with the indigenous Levantine substrate. These findings challenge the "Levantine-Presumption" applied to J1-P58 and re-establish E1b1b as the biological marker of the proto-Semitic speaking communities who developed the earliest Semitic languages in situ, long before the arrival of Indo-European groups that would later adopt and propagate these linguistic traditions. Part of a larger work: "Collected Papers on Afro-Eurasian Archaeogenetics and the Bota Surname", which is protected by Copyright Law.

View source

Similar papers

#computer vision Open access Jun 2016

Software Development in Startup Companies: The Greenfield Startup Model

Software startups are newly created companies with no operating history and oriented towards producing cutting-edge products. However, despite the increasing importance of startups in the economy, few scientific studies attempt to address software engineering issues, especially for early-stage startups. If anything, startups need engineering practices of the same level or better than those of larger companies, as their time and resources are more scarce, and one failed project can put them out of business. In this study we aim to improve understanding of the software development strategies employed by startups. We performed this state-of-practice investigation using a grounded theory approach. We packaged the results in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible. This strategy allows startups to verify product and market fit, and to adjust the product trajectory according to early collected user feedback. The need to shorten time-to-market, by speeding up the development through low-precision engineering activities, is counterbalanced by the need to restructure the product before targeting further growth. The resulting implications of the GSM outline challenges and gaps, pointing out opportunities for future research to develop and validate engineering practices in the startup context.

Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al. · 179 citations · ⚡14
#computer vision Open access Oct 2016

Software Startups - A Research Agenda

Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models. Software startup ...

M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al. · 157 citations · ⚡17
#machine learning Review Open access Oct 2016

“Failures” to be celebrated: an analysis of major pivots of software startups

In the context of software startups, project failure is embraced actively and considered crucial to obtain validated learning that can lead to pivots. A pivot is the strategic change of a business concept, product or the different elements of a business model. A better understanding is needed on different types of pivots and different factors that lead to failures and trigger pivots, for software entrepreneurial teams to make better decisions under chaotic and unpredictable environment. Due to the nascent nature of the topic, the existing research and knowledge on the pivots of software startups are very limited. In this study, we aimed at identifying the major types of pivots that software startups make during their startup processes, and highlighting the factors that fail software projects and trigger pivots. To achieve this, we conducted a case survey study based on the secondary data of the major pivots happened in 49 software startups. 10 pivot types and 14 triggering factors were identified. The findings show that customer need pivot is the most common among all pivot types. Together with customer segment pivot, they are common market related pivots. The major product related pivots are zoom-in and technology pivots. Several new pivot types were identified, including market zoom-in, complete and side project pivots. Our study also demonstrates that negative customer reaction and flawed business model are the most common factors that trigger pivots in software startups. Our study extends the research knowledge on software startup pivot types and pivot triggering factors. Meanwhile it provides practical knowledge to software startups, which they can utilize to guide their effective decisions on pivoting.

Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al. · 127 citations · ⚡15
#computer vision Review Open access May 2015

A survey study on major technical barriers affecting the decision to adopt cloud services

In the context of cloud computing, risks associated with underlying technologies, risks involving service models and outsourcing, and enterprise readiness have been recognized as potential barriers for the adoption. To accelerate cloud adoption, the concrete barriers negatively influencing the adoption decision need to be identified. Our study aims at understanding the impact of technical and security-related barriers on the organizational decision to adopt the cloud. We analyzed data collected through a web survey of 352 individuals working for enterprises consisting of decision makers as well as employees from other levels within an organization. The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability. The result from our logistic regression analysis confirms the criticality of the security concern, which results in an up to 26-fold increase in the non-adoption likelihood. Our study underlines the importance of the technical and security perspectives for research investigating the adoption of technology.

Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al. · 111 citations · ⚡8
#computer vision Conference Open access Dec 2013

Affordable and Energy-Efficient Cloud Computing Clusters: The Bolzano Raspberry Pi Cloud Cluster Experiment

We present our ongoing work building a Raspberry Pi cluster consisting of 300 nodes. The unique characteristics of this single board computer pose several challenges, but also offer a number of interesting opportunities. On the one hand, a single Raspberry Pi can be purchased cheaply and has a low power consumption, which makes it possible to create an affordable and energy-efficient cluster. On the other hand, it lacks in computing power, which makes it difficult to run computationally intensive software on it. Nevertheless, by combining a large number of Raspberries into a cluster, this drawback can be (partially) offset. Here we report on the first important steps of creating our cluster: how to set up and configure the hardware and the system software, and how to monitor and maintain the system. We also discuss potential use cases for our cluster, the two most important being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.

P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al. · 110 citations · ⚡7
#computer vision Book Open access Mar 2017

On the Unhappiness of Software Developers

The happy-productive worker thesis states that happy workers are more productive. Recent research in software engineering supports the thesis, and the ideal of flourishing happiness among software developers is often expressed among industry practitioners. However, the literature suggests that a cost-effective way to foster happiness and productivity among workers could be to limit unhappiness. Psychological disorders such as job burnout and anxiety could also be reduced by limiting the negative experiences of software developers. Simultaneously, a baseline assessment of (un)happiness and knowledge about how developers experience it are missing. In this paper, we broaden the understanding of unhappiness among software developers in terms of (1) the software developer population distribution of (un)happiness, and (2) the causes of unhappiness while developing software. We conducted a large-scale quantitative and qualitative survey, incorporating a psychometrically validated instrument for measuring (un)happiness, with 2 220 developers, yielding a rich and balanced sample of 1318 complete responses. Our results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains. We also identified 219 factors representing causes of unhappiness while developing software. Our results, which are available as open data, can act as guidelines for practitioners in management positions and developers in general for fostering happiness on the job. We suggest considering happiness in future studies of both human and technical aspects in software engineering.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 84 citations · ⚡6

Related blog posts