Interpretation dependency & development

What does this interpretation have to assume?

Expose the premises and inferential steps behind an interpretation so later conclusions cannot hide added assumptions inside a biblical citation.

Chronology boundary: “Earliest in the curated Codex corpus” means only the oldest witness currently curated here. It does not mean “first in history,” “invented by,” or “originated with.” Absence from this dataset is not historical absence.
Passage anchor

John 1:1

Dependency profiles expose premises and inferential steps; they do not add evidence weight. Development dates are 'earliest in the curated Codex corpus' only unless dedicated historical-origin research proves more. Absence from the current corpus is not evidence of historical absence.

0profiled targets
1missing profiles
0curated development threads

Open reader workspace View development API

Curated development threads

Watch premises change—not just names and dates.

A thread is added only after explicit comparative review. Similar subject matter alone is not enough to assert continuity or dependence.

Dependency profiles

Show the argument between the evidence and the conclusion.

Each profile separates direct textual data from literary inference, contextual models, typological/allegorical expansion, later doctrinal premises, and authority shortcuts.

Model contract

Old does not mean true. New does not mean false. Missing does not mean absent.

The development layer tracks the currently curated record and the premises required by an argument. It never turns chronology into authority and never claims a historical origin without dedicated source research.

View dependency/development taxonomy