No older form is promoted beyond the already disputed *ḱeh₂d- comparison.
CANONICAL RELATIONSHIP RECORD
COVERAGE LEDGER ↗EDGE / 1247knowledge boundaryboundary
A CLAIM
YOU CAN AUDIT.
A relationship—not a generated explanation. Both endpoints, every editorial field, every citation, and every dossier reuse are preserved below.
*ḱeh₂d-
a proposed base glossed with grief, pain, and hatred
OPEN NODE 1096 ↗DESCENDS FROM→
PARENT / EARLIER FORM / boundaryBeyond secure reconstruction · beyond the disputed Indo-European comparison · hazzon deep boundaryUNKNOWN
No securely accepted earlier ancestor or uniquely recoverable original meaning is known.
OPEN NODE 1279 ↗01
THE COMPLETE RELATIONSHIP
EVERY FIELD, NOT A FAIRY TALE
The trail stops before pursuit, persecution, feeling, grief, pain, care, or hatred is reverse-engineered into one universal prehistoric act.
No separate chronology note is attached beyond the endpoint date ranges.
SET-U editorial boundary · Anatoly Liberman · Jacob Grimm
boundary — Secure comparison is strongest inside Germanic; the displayed Indo-European lane remains qualified and semantically unresolved.
reviewed
02
CITATION REGISTER
SOURCES ON THIS EDGE
Hate — definition, etymology, and first known useEtymology note: semantic relations are far from transparent
supportsAUDIT SOURCE ↗ORIGINAL ↗Marks the deep comparison as semantically unresolved.
The shortest history of hatred continued and partly concludedQualified conclusion on pursuit and the deeper comparison
supportsAUDIT SOURCE ↗ORIGINAL ↗Supports an explicit endpoint rather than an invented first meaning.
Proto-Germanic *xatiz, *xatōn-, -ēn- and *xatjan-Pokorny discussion: Germanic evidence does not establish pursue as the root’s basic meaning
contextAUDIT SOURCE ↗ORIGINAL ↗Shows that even the strongest branch-level action account does not recover one prehistoric semantic origin.
03
EDITORIAL REUSE