Chronicle of Seert
Arabic chronicle from the 11th century
The Chronicle of Seert, sometimes called the Histoire nestorienne, is an ecclesiastical history written in Arabic by an anonymous Christian writer from the Church of the East, at an unknown date between the ninth and the eleventh century. There are grounds for believing that it is the work of Ishoʿdnah of Basra, who flourished in the second half of the ninth century.
Only part of the original text has survived. The surviving text consists of two long extracts, covering the years 251–422 and 484–650 respectively. The portion of the text covering events beyond the middle of the 7th century has been lost. Parallel to it in some parts is a Haddad Chronicle (also known as the Brief Ecclesiastical Chronicle) first described by Butros Haddad in 1986 and published by him in 2000. The lost Ecclesiastical History of Daniel bar Maryam is sometimes thought to have been a major source of the Chronicle of Seert.
The Chronicle deals with ecclesiastical, social, and political issues of the Persian Christian church giving a history of its leaders and notable members. It details the growth and prospering of the Nestorian Church despite alternating periods of persecution and toleration under the Zoroastrian rulers of Sassanid Persia. The work then celebrates the triumph of the Muslim conquerors in the 7th century as liberators from increasing Zoroastrian oppression.
This brief starts where responsible research should: with the source description of “Chronicle of Seert” as arabic chronicle from the 11th century. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as arabic chronicle from the 11th century. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Apr 30, 2026. The linked authority identifier is Q1088011. VIAF identifies the subject as 177988834. The Library of Congress control number is n2010003297. 1 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1986 and 2000.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Chronicle of Seert”, its source revision and the description used here.
- Expand the search: follow Chronicle of Seert primary sources, Chronicle of Seert archive and Chronicle research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Chronicle of Seert”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Chronicle of Seert” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.