AI-generated visualization based on the cited record and period context. It is not documentary evidence or an authenticated reconstruction of a single event.
How the setting appeared
Dense mudbrick neighborhoods surrounded monumental precincts raised on platforms; canals joined fields, workshops and river routes.
Agent citationCIT-CORE-URUK · CIT-CORE001-URUK-DAI
Setting and material context · 2 registered source URLs · registration is not semantic proof · audit HEM-AUDIT-20260812
How people lived
Most residents lived in modest mudbrick houses and depended on grain, dates, sheep, goats and ration systems.
Agent citationCIT-CORE-URUK · CIT-CORE001-URUK-DAI
Lifeways and community · 2 registered source URLs · registration is not semantic proof · audit HEM-AUDIT-20260812
How people worked
Canal farming, herding, pottery, weaving, administration and long-distance material exchange sustained the city.
Agent citationCIT-CORE-URUK · CIT-CORE001-URUK-DAI
Work, tools and exchange · 2 registered source URLs · registration is not semantic proof · audit HEM-AUDIT-20260812
Belief, ritual and worship
Temple households organized offerings, land, labor and festivals for deities such as Inanna and Anu.
Agent citationCIT-CORE-URUK · CIT-CORE001-URUK-DAI
Belief, ritual and evidence limits · 2 registered source URLs · registration is not semantic proof · audit HEM-AUDIT-20260812
Historical geography
A dated anchor, not an exact border
The local map uses modern coastlines only for orientation. The marker identifies this record's geographic anchor, not the full reach of a community or polity.
Map geometry loads only when requested. Modern outlines are orientation only; historical geography and identities changed through time.
Agent citationCIT-CORE-URUK · CIT-CORE001-URUK-DAI
Historical-geography anchor and stated limits · 2 registered source URLs · registration is not semantic proof · audit HEM-AUDIT-20260812
Evidence register
Guides used for this record
Each registered source ID is paired with its institutional URL for independent checking. Source count is transparent, and duplicate URLs count only once.