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
Brick temple towers occupied a mountain-ringed valley, while ports, river settlements, fields and craft centers lay across separate coastal regions.
Agent citationCIT-UNESCO-MY-SON · CIT-SMITHSONIAN-SEA
Setting and material context · 2 registered source URLs · registration is not semantic proof · audit HEM-AUDIT-20260812
How people lived
Court and temple households depended on farmers, fishers, traders and artisans; Cham political authority shifted among regional centers.
Agent citationCIT-UNESCO-MY-SON · CIT-SMITHSONIAN-SEA
Lifeways and community · 2 registered source URLs · registration is not semantic proof · audit HEM-AUDIT-20260812
How people worked
Brickmaking, sculpture, irrigation, ship use, forest-product exchange and agriculture sustained temples and ports.
Agent citationCIT-UNESCO-MY-SON · CIT-SMITHSONIAN-SEA
Work, tools and exchange · 2 registered source URLs · registration is not semantic proof · audit HEM-AUDIT-20260812
Belief, ritual and worship
Shaiva traditions received major royal patronage alongside Buddhism and local spirit and ancestor practices.
Agent citationCIT-UNESCO-MY-SON · CIT-SMITHSONIAN-SEA
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-UNESCO-MY-SON · CIT-SMITHSONIAN-SEA
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.