No older form or uniquely recoverable concrete meaning is promoted beyond the disputed *ḱeh₂d- proposal.
CANONICAL RELATIONSHIP RECORD
COVERAGE LEDGER ↗EDGE / 1090knowledge 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 · before the disputed Indo-European proposal · hatred deep boundaryUNKNOWN
No securely accepted ancestor or original concrete meaning is currently known beyond the reviewed Germanic family.
OPEN NODE 1097 ↗01
THE COMPLETE RELATIONSHIP
EVERY FIELD, NOT A FAIRY TALE
The trail ends before a convenient story about love and hate, pursuit, grief, or care is mistaken for established prehistory.
No separate chronology note is attached beyond the endpoint date ranges.
SET-U editorial boundary · Anatoly Liberman
boundary — The secure path reaches Germanic; the displayed PIE lane is a qualified proposal, not a settled endpoint.
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 ↗Defines why secure ancestry cannot simply be extended through the proposal.
The shortest history of hatred continued and partly concludedConclusion: pursuit looks promising, broader comparisons remain murky
supportsAUDIT SOURCE ↗ORIGINAL ↗Supports an explicit knowledge boundary rather than a fabricated original meaning.
03
EDITORIAL REUSE