*SET-U

GRAPH-WIDE SEARCH

MEASURE THE GRAPH ↗

NOT JUST A DICTIONARY LOOKUP

6 EVIDENCE COLLECTIONS

SEARCH
THE GRAPH.

Find a modern word—or search sideways through reconstructed roots, historical forms, meanings, languages, scholars, sources, claims, disputes, and witnesses.

WIKTIONARY VIA KAIKKI / WIKTEXTRACT

Imported dictionary evidence

SOURCE-IMPORTED · UNREVIEWED

These are source reports, not reviewed *SET-U ancestry. A list of templates or numbered etymologies is not an ancestor chain. Scholarly disagreements remain in the original source text.

35,981 English word records · 45,491 etymology sections in this online subset

PARTIAL ENGLISH COVERAGE · FULL CORPUS REMAINS LOCAL

2 source sections across 1 headword matching “Code”. These are separate from the reviewed results below.

Open the permanent entry for code →
codeEnglish (en) · Etymology 1Source text

Etymology tree Latin caudex Latin cōdex Old French codebor. Middle English code English code From Middle English code (“system of law”), from Old French code (“system of law”), from Latin cōdex, later form of caudex (“the stock or stem of a tree, a board or tablet of wood smeared over with wax, on which the ancients originally wrote; hence, a book, a writing.”). Doublet of codex. Verb etymology 1, verb sense 7 is an ellipsis of code blue (“medical emergency”).

Original Wiktionary entry and references ↗
codeEnglish (en) · Etymology 1Source text

Etymology tree Latin caudex Latin cōdex Old French codebor. Middle English code English code From Middle English code (“system of law”), from Old French code (“system of law”), from Latin cōdex, later form of caudex (“the stock or stem of a tree, a board or tablet of wood smeared over with wax, on which the ancients originally wrote; hence, a book, a writing.”). Doublet of codex. Verb etymology 1, verb sense 7 is an ellipsis of code blue (“medical emergency”).

Original Wiktionary entry and references ↗

From Wiktionary contributors; extracted by Tatu Ylonen / Wiktextract / Kaikki.org. Extraction source · CC-BY-SA-4.0. Selected source text is reformatted for display; language and section identity are retained.

Source dump: 2026-10-01 · Extraction: 2026-10-30. These dates identify a dump snapshot, not an individual page revision.

Snapshot checksums and coverage
SOURCE SHA-256
5ff2c072f8099f2d2ce484bd6957bf179f046d2ad37bc36555edf8bb84cb5291
CORPUS SHA-256
c4c2a77325141846709230e11c2959332acd630d53e52905b72d36211251b081
IMPORT RUN
73216b9a9b78ed3830994bf853103716f5a4dc57099e371e9f8fdc468facca26
SUBSET SELECTION
English-only: shortest normalized query first, then binary lexical order; complete word-language and case-variant groups only. This is a bounded online subset, not the full acquired corpus.

INDEPENDENT SOURCE LIBRARY

More sources for this spelling

These are spelling matches, not a claim of identical senses or agreement. Historical accounts retain their own editions and limits; none is automatically promoted into reviewed ancestry.

Browse the independently attributed sources →
45REVIEWED RESULTS
3WORD DOSSIERS
0HISTORICAL NODES
12SOURCES
18CLAIMS
12WITNESSES
01

MODERN ENTRY POINTS

WORD DOSSIERS

3
02

ATTESTED / RECONSTRUCTED / BOUNDARY

HISTORICAL FORMS

0

No reviewed record in this collection contains “code.” Absence describes this graph, not all of linguistic scholarship.

03

WHERE INTERPRETATION IS TESTED

CLAIMS & DISPUTES

18

SCHOLARLY DISPUTES / 12

openboundaryposition text

Is *lˤra the final word on the ancestry of tea?

It is the final reviewed reconstruction in this dossier, not a declaration that no deeper hypothesis exists. No unique deeper form is promoted until a competing analysis is encoded with direct evidence.

openestablishedposition text

Is John 7:23 the first Gothic use of the verb?

Not established. The translation belongs to a fourth-century tradition, the surviving codex is early sixth century, and no complete lost-text or spoken-language archive exists.

openproposedposition text

Did hettan mean hate, pursue, attack, or persecute?

No single gloss exhausts the record. Orel glosses Old English hettan “hate” but Middle High German hetzen “pursue”; the attested enemy forms encode an antagonist, and Liberman argues for pursuit or persecution as an older concrete history.

openprobableposition text

Did Urdu receive cāy directly from Chinese or through Persian?

Rekhta labels the current Urdu headword Persian in origin, while the wider references establish only the Chinese-derived overland family. Persian is therefore probable as the immediate source, not promoted as a uniquely dated event.

openspeculativeposition text

Did Lydian contact cause the loss of initial aspiration?

Gális presents Lydian contact only as a theoretical possibility, not an established cause of Greek psilosis.

resolvedestablishedposition text

Is emoji formed from emotion plus icon?

No. Unicode and Merriam-Webster identify Japanese 絵 e “picture” plus 文字 moji “written character.” Emotion plus icon is the distinct English formation emoticon.

resolvedestablishedposition text

Did fijan denote only an inward feeling?

No. Ayora Estevan analyzes it as an experience verb whose Experiencer takes a Stimulus as accusative object. Surviving objects include people, one’s soul, one’s flesh, evils, and what one does, so the grammar encodes a relation toward an object rather than a free-floating feeling alone.

resolvedestablishedposition text

Does the Codex Argenteus route map the spread of fijan?

No. Werden, Prague, Stockholm, Holland, and Uppsala trace custody of four inspected evidence objects long after Gothic ceased to be a living vernacular in those places.

resolvedestablishedposition text

Does the Codex Argenteus route map the geographic spread of fijands?

No. Werden, Prague, Stockholm, Holland, and Uppsala trace custody of evidence objects long after Gothic ceased to be a living vernacular in those places.

resolvedestablishedposition text

Were any underlying manuscript objects directly inspected for this dossier?

No. This review inspected the ONW article and its expanded source-reported records, not the Wachtendonck Psalms copies, Leiden Willeram codex, Groningen gloss object, or rhymed-text witnesses.

resolvedestablishedposition text

Does the Codex Argenteus route map the spread of hatan?

No. It maps custody of the two directly inspected evidence objects. The codex traveled through Werden, Prague, Stockholm, Holland, and Uppsala long after Gothic ceased to be a living vernacular in those places.

resolvedestablishedposition text

Does the Codex Argenteus custody route map the spread of hatis?

No. It maps the custody of the directly inspected evidence object. The manuscript traveled through Werden, Prague, Stockholm, Holland, and Uppsala long after Gothic ceased to be a living vernacular in those places; the other hatis tokens survive in separate witnesses.

CONTRARIAN TRUTHS / 6

RANK 6GRADE Aranked reveal

Evidence became a thread you could follow.

Old English cliewen was a ball of thread; the labyrinth metaphor turned it into guidance through uncertainty.

RANK 29GRADE Aranked reveal

One Gothic hate verb survives once—in a command to do good to those who hate you.

Project Wulfila’s only verified hatjan token is hatjandam in Matthew 5:44, directly visible on Codex Argenteus folio 3v. A parallel “love your enemies” command in Luke 6:27 instead uses hatandans from class-III hatan. The translation gloss “hate” therefore hides a genuine grammatical and historical dispute.

RANK 30GRADE Aranked reveal

Gothic hatis—the noun related to English hate—survives chiefly as wrath, including the wrath to come and the wrath of God.

Project Wulfila reports fifteen tokens in hatis, hatiza, and hatize. Fourteen are biblical; Streitberg maps the family chiefly to Greek orgē, gives Galatians 5:20 thumos, and flags Ephesians 4:31 because both stand together. Codex Argenteus folio 129r directly preserves hatiza in “the wrath to come.” Even the paradigm resists simplification: synchronic neuter a-stem, historically an i-stem remodeled into it.

RANK 31GRADE Aranked reveal

Gothic’s two hate verbs trade places across two passages.

The complete surviving hatan corpus contains only hatandane in Luke 1:71 and hatandans in Luke 6:27. In Luke 1, fijandam supplies enemies while hatandane supplies those hating; in Luke 6, hatandans supplies enemies while fijandam supplies those hating. Both Codex Argenteus pages are directly inspected. The lexical swap—and the class-III versus class-I dispute—cannot be represented by one timeless translation arrow.

RANK 45GRADE Aranked reveal

One Gothic anger verb survives in one question—and not in its dictionary form.

Project Wulfila’s complete current inventory contains one hatizōn token: hatizoþ in John 7:23, “are you angry at me?” Codex Argenteus folio 94v directly preserves the inflection. The manuscript never writes the normalized infinitive or its editorial macron. Grammar then reveals another layer: hatizōn is a class-II verb built from the consonantal stem hatiz- of hatis “hatred” or “wrath.” One English gloss therefore hides a noun-to-verb formation, one surviving grammatical person, and a sharp boundary between pixels and reconstruction.

RANK 65GRADE Acontrarian claim

A borrowed word can encode a category that English flattens.

Navajo hooghan means home or house within Diné life; English hogan should not be generalized into a label for any Indigenous dwelling.

04

BOOKS / DICTIONARIES / ARTICLES / DATABASES

SOURCES

12
digitized primary source9 CLAIM LINKS

Codex Argenteus facsimile 145 — folio 123r, Luke 1:69–77

Uppsala University Library · Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
digitized primary source7 CLAIM LINKS

Codex Argenteus facsimile 186 — folio 143v, Luke 6:25–30

Uppsala University Library · Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
digitized primary source7 CLAIM LINKS

Codex Argenteus facsimile 6 — folio 3v, Matthew 5:42–47

Uppsala University Library · Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
digitized primary source6 CLAIM LINKS

Codex Argenteus facsimile 60 — folio 94v, John 7:22–28

Uppsala University Library · Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
digitized primary source4 CLAIM LINKS

Codex Argenteus facsimile 57 — folio 33r, John 7:2–8

Uppsala University Library · Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
digitized primary source3 CLAIM LINKS

Codex Argenteus facsimile 228 — folio 164v, Luke 10:17–21

Uppsala University Library · Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
digitized primary source3 CLAIM LINKS

Codex Argenteus facsimile 31 — folio 27r, Matthew 10:34–40

Uppsala University Library · Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
digitized primary source3 CLAIM LINKS

Codex Argenteus facsimile 96 — folio 76v, John 12:19–25

Uppsala University Library · Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
digitized primary source2 CLAIM LINKS

Codex Argenteus facsimile 157 — folio 129r, Luke 3:5–9

Uppsala University Library · Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
digitized primary source1 CLAIM LINKS

Codex Argenteus facsimile 276 — folio 57v, Mark 1:6–13

Uppsala University Library; Project Codex Argenteus Online / 1927

citation-key prefixAUDIT EVERY USE ↗
technical reference15 CLAIM LINKS

FAQ — Emoji and Pictographs

Unicode Consortium

author or editorAUDIT EVERY USE ↗
manuscript catalog7 CLAIM LINKS

The history of Codex argenteus

Uppsala University Library / 2026

source titleAUDIT EVERY USE ↗
05

FIRST USES & HISTORICAL OBJECTS

ATTESTATION WITNESSES

12
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Mark 1:11

liufs / liufs / early 6th century

Codex Argenteus facsimile 276 — folio 57v, Mark 1:6–13witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Matthew 5:44

hatjan / hatjan / early 6th century

Codex Argenteus facsimile 6 — folio 3v, Matthew 5:42–47witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Luke 3:7

hatis / hatis / early 6th century

Codex Argenteus facsimile 157 — folio 129r, Luke 3:5–9witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Luke 1:71

hatan / hatan / early 6th century

Codex Argenteus facsimile 145 — folio 123r, Luke 1:69–77witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Luke 6:27

hatan / hatan / early 6th century

Codex Argenteus facsimile 186 — folio 143v, Luke 6:25–30witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, John 7:7

fijan / fijan / early 6th century

Codex Argenteus facsimile 57 — folio 33r, John 7:2–8witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, John 12:25

fijan / fijan / early 6th century

Codex Argenteus facsimile 96 — folio 76v, John 12:19–25witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Luke 1:71

fijan / fijan / early 6th century

Codex Argenteus facsimile 145 — folio 123r, Luke 1:69–77witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Luke 6:27

fijan / fijan / early 6th century

Codex Argenteus facsimile 186 — folio 143v, Luke 6:25–30witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Matthew 5:43

fijands / fijands / early 6th century

Codex Argenteus facsimile 6 — folio 3v, Matthew 5:42–47witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Matthew 5:44

fijands / fijands / early 6th century

Codex Argenteus facsimile 6 — folio 3v, Matthew 5:42–47witness-title prefix / OPEN RECORD ↗
DIRECTLY INSPECTEDmanuscript

Codex Argenteus, Matthew 10:36

fijands / fijands / early 6th century

Codex Argenteus facsimile 31 — folio 27r, Matthew 10:34–40witness-title prefix / OPEN RECORD ↗
06

SEARCH IS DISCOVERY, NOT PROOF

EVERY RESULT OPENS A PERMANENT EVIDENCE RECORD.

Matching text only locates a record. It does not raise confidence, settle a dispute, establish cognacy, or turn a source report into direct inspection. Follow the result into its citations and editorial limits.