AT-1631

Joshua 6

URL · Primary evidence / text

partially_verifiedNo recorded retraction flag1 usage record

Source record

This is one canonical bibliographic record with topic-scoped research-use entries. It does not reproduce the paper, book, text, dataset, image, or manuscript and does not imply that full text was reviewed.
Canonical source ID
AT-1631
Accepted usage IDs
AT-1631
Types
URL
Roles
Primary evidence / text
Verification
partially_verified
Archive state
not assessed in this refresh yet
Access
not assessed in this refresh yet
Rights
link-and-citation use only unless a documented license or public-domain basis permits more
Public reproduction
Not cleared; citation and link only.
Correction / retraction
not-applicable/no DOI

Recorded research uses

AT-1631

Jericho

Why Ancient Inquiry uses this citation here

Primary textual source for the conquest and wall-collapse tradition, not archaeological evidence

What this usage does not establish

Bibliographic verification does not by itself establish that the full text was read.
Open topic

Topics citing it and claims using it

Supporting citation for public claim

Joshua 6 attests a conquest and wall-collapse tradition, but Tell es-Sultan archaeology does not securely prove the story exactly as popularly told.

The site and walls are real, but the exact conquest claim is not securely established by archaeology.
Open claim topic
Supporting citation for public claim

Tell es-Sultan has fortifications and destruction phases, but identifying a particular layer with the Joshua event remains disputed rather than established.

Answer / theory: The site has walls and destruction phases, but the simple popular match to Joshua is not established. What supports it: Real fortifications and destruction evidence exist at Jericho. What is weak or disputed: Chronology and identification with the biblical event.
Open claim topic

Access and actions

Joshua 6

Open original

Search Ancient Inquiry

Open complete search

Visual theme

Theme intensity changes decoration only. Evidence and relationship semantics never change.

Prepare an issue report

This static site cannot transmit a correction by itself. It prepares a complete report with page and build provenance for the published corrections channel.

Open corrections instructions