In a single morning, Iran confirmed the loss of its armed-forces chief, the Revolutionary Guard commander, and the commander of its ballistic-missile force.
View full image ↗AI-generated illustration · Ideogram 4 (fp8) · 2026-08-27How was this image made?
The creative brief sent to the image model. These are instructions, not a record of what actually happened.
In the early hours of 13 June 2025, Israel opened Operation Rising Lion with strikes on Iran's nuclear, missile, air-defense and military-leadership targets, including sites in Tehran and the Natanz enrichment complex — a safeguarded facility the IAEA recorded as attacked between roughly 3 and 8 a.m. local time.
The Israeli military said approximately 200 aircraft used more than 330 munitions against more than 100 targets in the opening overnight wave. Iran confirmed the deaths of Armed Forces chief of staff Mohammad Bagheri, IRGC commander Hossein Salami, and IRGC Aerospace Force commander Amir Ali Hajizadeh — the officer over its ballistic-missile program.
Iran answers in stages
Iran's response came in waves: first more than 100 drones toward Israel, then, after dark, ballistic missiles that reached the Tel Aviv and Jerusalem areas — some landing after midnight, which is why casualty reporting varies by local cutoff. Iran's initial report from the Israeli attacks was 78 killed and more than 320 wounded, preliminary figures for the opening day only.
The U.N. Security Council met in emergency session that afternoon at Iran's request. Israel mobilized reservists as the long-running shadow conflict became an open interstate war.
Whose war, and on what rationale
This was an Israeli operation, not a joint U.S.–Israeli attack: U.S. officials said Washington was informed but did not participate, though U.S. forces helped defend Israel against the retaliation. Direct American offensive strikes came only on 22 June.
Israel called the attack preemptive, against an imminent nuclear and ballistic-missile threat; it came one day after the IAEA Board censured Iran over safeguards noncompliance — but U.S.–Iran nuclear negotiations were still underway, and independent evidence of an imminent Iranian attack was not established. The fighting ran twelve days, and a larger war followed in February 2026.
Researched 23 Aug 2026·6 sources·3 audit passes
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
What the sources leave uncertain
Casualty figures published on June 13 were preliminary and later war-wide totals should not be assigned to the opening day.
Israel characterized the attack as preemptive, but whether the alleged threat was legally or operationally imminent was disputed.
The United States said it was informed but did not participate in the June 13 attack; U.S. forces did help defend Israel against Iran's retaliation.
Some Iranian missiles launched late June 13 landed after midnight on June 14, so casualty reporting varies by local cutoff.
The bombers flew quietly for 18 hours before the first weapon fell — while a decoy group flew west over the Pacific, the real B-2 formation headed east toward Iran.
View full image ↗AI-generated illustration · Ideogram 4 (fp8) · 2026-08-27How was this image made?
The creative brief sent to the image model. These are instructions, not a record of what actually happened.
In the early hours of 22 June 2025 in Iran — the mission had launched the previous evening, U.S. time — the United States attacked the Fordow, Natanz and Isfahan nuclear sites under Operation Midnight Hammer, entering the Iran–Israel war as a direct combatant nine days after Israel's opening attack.
The strike package split by target: seven B-2 bombers dropped fourteen 30,000-pound GBU-57 Massive Ordnance Penetrators on Fordow and Natanz — the weapon's first operational use — while a U.S. submarine, not a bomber, fired more than two dozen Tomahawk cruise missiles at infrastructure at Isfahan. Roughly 75 precision-guided weapons were employed in all.
An 18-hour approach, an unopposed exit
The B-2s — each crewed by two — flew 18 hours outbound before reaching the target area, with a decoy group sent west over the Pacific as the real formation headed east. Per the U.S. account, Iranian fighters did not take off and the strike package reported no shots fired at it on departure.
The deeply buried Fordow enrichment plant, beneath a mountain, was considered especially difficult to attack — and it was attacked with the GBU-57, the bunker-penetrating bomb making its first operational appearance.
Damage claimed vs. damage known
All three sites sustained visible damage, and Iran reported no increase in off-site radiation immediately after the attacks — which did not itself prove the underground facilities or stored nuclear material were undamaged. The IAEA could see impact craters at Fordow but initially said it could not assess conditions inside the underground halls.
The Pentagon's early phrase was 'extremely severe damage' — a battle-damage assessment, not independent verification. Later estimates of how long the strikes delayed Iran's nuclear program differed, and none of them were facts known on 22 June.
Researched 23 Aug 2026·6 sources·3 audit passes
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
What the sources leave uncertain
The operation began during the evening of June 21 in the United States but struck its targets after 2 a.m. on June 22 in Iran; June 22 is the correct local event date.
Initial Pentagon claims of devastation were battle-damage assessments, not independent verification.
The IAEA could see impact craters at Fordow but initially said it could not assess damage inside the underground halls.
Later assessments of how long the strikes delayed Iran's nuclear program differed; those estimates should not be presented as facts known on June 22.
Within hours of the 1:15 a.m. strikes, the man who had held Iran's highest office for more than 36 years was dead — and a temporary leadership council was being formed.
View full image ↗AI-generated illustration · Ideogram 4 (fp8) · 2026-08-27How was this image made?
The creative brief sent to the image model. These are instructions, not a record of what actually happened.
28 February 2026, 1:15 a.m.: two operations, one campaign
U.S. Central Command commenced Operation Epic Fury at 1:15 a.m. on 28 February 2026, as Israel opened its coordinated Operation Roaring Lion. The strikes hit targets across Iran: Revolutionary Guard command facilities, air defenses, missile and drone launch sites, military airfields, government symbols and intelligence targets.
Supreme Leader Ali Khamenei was killed at his compound in Tehran — a strike later reporting attributed to Israel, reportedly timed to a meeting he was holding with senior aides. Iranian state media also reported the deaths of Revolutionary Guard commander Mohammad Pakpour and security adviser Ali Shamkhani.
Retaliation across the Gulf
Iran struck back the same day — and not only at Israel. Hundreds of missiles and drones in the first roughly twelve hours were directed at Israel and at U.S. installations in Bahrain, Kuwait and Qatar, with exchanges continuing into the night.
Iran also imposed restrictions in the Strait of Hormuz, and attacks on vessels were reported; commercial shipping sheltered or avoided the waterway as one of the world's critical energy chokepoints effectively stopped functioning normally. The sustained campaign against shipping developed over subsequent days and months, not all on the 28th.
Succession machinery, not collapse
Khamenei's death did not dissolve Iran's government: the state rapidly created an interim council to exercise the supreme leader's functions pending a successor, declared 40 days of state mourning and a 7-day public holiday. The AP reported both mourning flags at major shrines and some Tehran residents cheering from rooftops.
On war aims, precision matters: Trump publicly urged Iranians to take over their government and U.S. military material referred to dismantling the security apparatus, while Israel's formally stated objective was degrading long-term threats — the allies did not present one consistently stated joint objective. The conflict, and intermittent ceasefires, continued well beyond 28 February.
Researched 23 Aug 2026·6 sources·3 audit passes, 1 issue open
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
What the sources leave uncertain
Early casualty reports varied substantially and should not be treated as final totals.
The opening campaign had overlapping but differently stated U.S. and Israeli objectives; whether regime change was an official joint war aim cannot be reduced to a single uncontested formulation.
Responsibility for individual strikes was sometimes unclear within the coordinated campaign. Later reporting attributed the strike that killed Khamenei to Israel.
The strait's effective closure began immediately, but the sustained campaign of attacks on shipping developed over subsequent days and months; it should not all be compressed into February 28.
The Nabonidus Chronicle records the reversal in a few damaged lines: Astyages mustered his army and marched against Cyrus, king of Anshan — and his own troops revolted, captured him, and delivered him to Cyrus. Traditional chronology puts the start of Cyrus's revolt in 553 BCE and this defeat around 550 BCE.
The contemporary Babylonian chronicle, not merely later Greek tradition, attributes the decisive reversal to the Median army's revolt. Herodotus's Median noble Harpagus, who organizes a conspiracy and defects to Cyrus, is absent from the Babylonian account.
Ecbatana, and treasure sent south to Anshan
Cyrus then advanced on Ecbatana, the Median royal capital, and transferred its booty to Anshan. He held the captured Astyages prisoner.
Persian supremacy replaced Median kingship, although further consolidation of former Median territories continued afterward — not every territory attributed to a Median empire transferred in a single day's operation.
What the broken tablet cannot say
The familiar chronology reconciles different Babylonian evidence, but the Nabonidus Chronicle's year headings for this passage are broken away. The defeat is conventionally placed in Nabonidus's sixth regnal year because the next preserved entry concerns his seventh; other scholars prefer 554–553, and the defensible range runs 554 to 550 BCE.
Greek narratives disagree sharply about Cyrus's family relationship to Astyages, the number and locations of battles, and the roles of Harpagus and other conspirators. Calling the outcome the instantaneous establishment of the Persian Empire compresses a longer process of conquest and consolidation.
Researched 23 Aug 2026·5 sources·3 audit passesDate disputed
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
Date disputed. Sources disagree; the research places it at ~-0550.
What the sources leave uncertain
The familiar 553–550 chronology reconciles different Babylonian evidence, but the Nabonidus Chronicle's year headings for this passage are broken away.
The event is often dated to 550 because the next preserved entry concerns Nabonidus's seventh year; other scholars prefer 554–553 or retain the full 554–550 range.
Greek narratives disagree sharply about Cyrus's family relationship to Astyages, the number and locations of battles, and the roles of Harpagus and other conspirators.
Calling the result the instantaneous 'establishment of the Persian Empire' compresses a longer process of conquest and consolidation.
A contemporary Babylonian astronomical diary records under 29 Aiaru: “The king died. Clouds.” The calendrical entry corresponds to the period from the evening of 10 June to the evening of 11 June, 323 BCE, and the death was logged beside planetary observations, river levels and commodity prices.
The form of the entry indicates a daytime report, making 11 June the preferred modern date; comparison with the Macedonian Royal Diaries places the death probably in the late afternoon.
Fever, silence, and the soldiers filing past
Arrian's account, drawing on the purported Royal Diaries, says Alexander had been in continuous high fever and had become unable to speak, though he recognized his officers. He died in Babylon soon after his soldiers filed past his bed.
What killed him is not recoverable. The underlying disease cannot be diagnosed reliably from the sparse and partly conflicting ancient narratives, and poisoning and modern medical diagnoses alike remain conjectural.
An unborn child and a half-brother
Alexander left no undisputed adult heir at 32. His death immediately opened a struggle among commanders and infantry over whether his half-brother Arrhidaeus, Roxane's unborn child, or another arrangement should inherit the kingship.
Reaching the final Babylon settlement took more than a month, and it did not carve the empire into independent kingdoms: the compromise made Philip III and the future Alexander IV joint kings under effective guardianship, while generals received territorial commands.
Researched 23 Aug 2026·6 sources·3 audit passesDate corrected
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
Date corrected. The research places this at -0323-06-11.
What the sources leave uncertain
The Babylonian date covers sunset-to-sunset, so an earlier death on June 10 followed by delayed reporting cannot be excluded; nevertheless, diary syntax and the Royal Diaries make daytime June 11 the preferred reconstruction.
The detailed illness narratives survive through authors writing centuries later, even where they claim access to Royal Diaries or eyewitness-derived histories.
No proposed diagnosis—malaria, typhoid, West Nile disease, pancreatitis, poisoning, or another condition—can be proved from the surviving evidence.
Stories about omens, Calanus's prophecy, poisoning, miraculous preservation, and Alexander's last words belong to later literary traditions of unequal reliability.
Two Roman armies destroyed two cities hundreds of miles apart in the same year — but no surviving source puts the burning of Corinth and the fall of Carthage on one day.
View full image ↗AI-generated illustration · Ideogram 4 (fp8) · 2026-08-27How was this image made?
The creative brief sent to the image model. These are instructions, not a record of what actually happened.
In 146 BCE, Scipio Aemilianus captured Carthage after six days and nights of street fighting. On the seventh day, the people sheltering in Byrsa negotiated permission to leave.
Appian reports that 50,000 men and women came out of Byrsa, while about 900 Roman deserters and Hasdrubal's family remained at the temple of Eshmun, identified in Appian's text as Aesculapius. Hasdrubal himself surrendered to Scipio while those last holdouts stayed in the temple.
The disposal of a city
Scipio permitted plunder, reserved precious metals and temple property, burned captured arms and unusable ships, and sent a vessel to Rome announcing the victory. The Senate then ordered any surviving structures obliterated, prohibited settlement at Byrsa and Megara, and arranged for annual Roman government of the conquered territory.
Rome did not sow the ground with salt; scholarship identifies that story as a later legend absent from ancient accounts.
The other destruction of that year
Elsewhere in the same year — not on a demonstrably identical day — the consul Lucius Mummius defeated the Achaean League, occupied Corinth and burned it. Pausanias says most Achaeans and Corinthians fled after nightfall, that the Romans killed most people they found, and that Mummius sold women and children into slavery.
The Achaean War was not part of the Punic Wars, even though both ended in 146 BCE. Corinth's Greek civic and political identity disappeared, and a Roman colony was founded there only in 44 BCE.
Researched 23 Aug 2026·8 sources·3 audit passesDate corrected
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
Date corrected. The research places this at -0146.
What the sources leave uncertain
Both destructions are securely dated to 146 BCE, but no reliable surviving source places them on the same day or supplies exact calendar dates.
Appian wrote centuries later and supplies the figure of 50,000 survivors; it should be attributed to him rather than treated as a modern census.
Ancient language about total destruction should not be read as proof that every structure or every inhabitant vanished; archaeological work indicates some activity at Corinth during the period before its Roman refoundation.
No contemporary source records Jesus's birth in 1 BCE, in AD 1, or on a particular calendar day, so no sequence of events can be reconstructed for this assigned date.
The association is retrospective. Dionysius Exiguus introduced his anno Domini numbering in 525 while constructing Easter tables, rather than recording a birth he had dated from contemporary evidence.
1 BCE or AD 1: the epoch is disputed
Dionysius described 525 as years from the incarnation but never explicitly stated a calendar year for Jesus's conception or birth. Alden Mosshammer's reconstruction places the nativity implicit in the Dionysian era on 25 December 1 BCE; Georges Declercq and a recent reanalysis instead argue that Dionysius fixed the incarnation in AD 1.
The two readings are not interchangeable, and conventional BC/AD chronology has no year zero between them.
What the gospels leave out
The gospels themselves identify neither a year nor a date. The commonly cited modern estimate of roughly 6–4 BCE is a historical reconstruction, not a documented birthday, and 25 December is a liturgical date rather than one established by contemporary birth documentation.
The datable consequence belongs to the sixth century: in 525 Dionysius's Easter table introduced anno Domini numbering, whose wider adoption took centuries.
Researched 23 Aug 2026·6 sources·3 audit passesDate disputed
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
Date disputed. Sources disagree; the research places it at -0001.
What the sources leave uncertain
The slug's date, −1, means 1 BCE, while its title begins “AD 1”; those are different years because traditional BC/AD chronology has no year zero.
Dionysius used “incarnation,” whose intended relation to conception and birth is debated, and he never explicitly wrote that Jesus was born in 1 BCE or AD 1.
Modern historical estimates commonly place Jesus's birth several years earlier, but the surviving evidence does not establish a precise year, month or day.
This is a calendrical attribution, not a securely dated historical event.
Tertullian pinned the Passion not merely to a year but to two named Roman consuls and the eighth day before April — a precision the modern evidence cannot support.
View full image ↗AI-generated illustration · Ideogram 4 (fp8) · 2026-08-27How was this image made?
The creative brief sent to the image model. These are instructions, not a record of what actually happened.
The date attached to this entry is an ancient traditional chronology rather than a recovered historical fact. Writing in the early third century, Tertullian dated the Passion to the consulship of Rubellius Geminus and Fufius Geminus — AD 29 — and to 25 March, expressed in Roman fashion as the eighth day before the Kalends of April.
Modern scholarship is far more cautious. One study concludes only that Jesus died around Passover sometime between AD 29 and 34; AD 30 and AD 33 are the most commonly proposed years, and the precise date cannot now be recovered.
What the earliest narratives describe
The Gospel accounts say Pontius Pilate handed Jesus over to Roman soldiers, who led him to Golgotha outside Jerusalem and crucified him. Mark reports two others crucified alongside, soldiers dividing his clothing by lot, and an inscription identifying him as 'King of the Jews' — which John says was written in Hebrew, Latin and Greek, with wording that differs slightly between accounts.
Mark places the crucifixion at the third hour and death at the ninth, conventionally about 9 a.m. and 3 p.m., and says Joseph of Arimathea then obtained Pilate's permission, took down the body, wrapped it in linen and placed it in a rock-hewn tomb before the Sabbath.
Reading the sources carefully
These are theological literary narratives, not trial transcripts, and they differ from one another on the inscription, the chronology relative to Passover and the reported hour. The familiar 'seven last words' appear as a sequence in no single Gospel; they are assembled from four separate accounts.
Outside the Christian sources, the Roman historian Tacitus independently placed the execution of Christus under Pontius Pilate during Tiberius's reign, though he supplied neither a year nor narrative detail.
Researched 23 Aug 2026·6 sources·3 audit passesTraditional date
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
Traditional date. This date is the conventional one, not one fixed by a contemporary record.
What the sources leave uncertain
AD 29 is an ancient traditional chronology, not a securely recoverable historical date. Tertullian anchors it to the consuls Rubellius and Fufius Geminus.
A modern scholarly study concludes only that Jesus died around Passover sometime between AD 29 and 34; AD 30 and AD 33 are the most popular proposed exact years, but the precise date cannot now be recovered: https://www.pure.ed.ac.uk/ws/files/10489469/Dating_the_Death_of_Jesus_Memory_and_the_Religious_Imagination.pdf
The Catholic Encyclopedia preserves a tradition assigning the death to AD 29, but this is not equivalent to a binding Roman Catholic definition of the historical year: https://www.newadvent.org/cathen/08377a.htm
The Synoptic and Johannine chronologies differ in important details, including the relationship of the crucifixion to the Passover meal and the reported hour. The USCCB note on Mark explicitly cautions that Mark's sequence may be liturgical or catechetical rather than precise.
Theodosius I died from illness at Mediolanum — modern Milan — on the night of 17 January 395. Socrates Scholasticus records that he watched victory games earlier that day, became too ill to return after dinner, sent Honorius to preside in his place, and died that night.
The illness itself resists diagnosis. Socrates attributes it to the strain of the recent war and Theodoret calls it dropsy, but that is an ancient diagnostic label rather than a recoverable modern cause of death.
Successors who were already emperors
His sons did not receive the imperial title that day. Arcadius had been Augustus since 383 and Honorius since 393; what changed was that they now carried responsibility for the eastern and western administrations respectively.
Honorius was ten years old, and his western government initially operated under the military dominance of Stilicho, whom Theodosius had placed in a senior western command before his death. Ambrose delivered the memorial oration forty days later, on 25 February, with the boy present.
Not the day the empire split
Calling 395 an instantaneous constitutional division of the Roman Empire oversimplifies: eastern and western administrative divisions and multiple Augusti long predated this death, and the empire continued to be conceived as one Roman polity.
What the following day lacked was a single senior emperor personally directing both courts — Arcadius's eastern and Honorius's western administrations now ran under separate officials and commanders. Even Theodosius's age is uncertain: the listed 48 rests on one reconstruction, while other ancient historians gave the incompatible figure of 60.
Researched 23 Aug 2026·7 sources·3 audit passes
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
What the sources leave uncertain
The exact illness is uncertain. Theodoret's later history calls it dropsy, while Socrates describes an illness followed by sudden deterioration and Zosimus merely says that Theodosius died of disease.
The listed age of 48 is not secure. David Woods dates his birth to about 346 from an ancient notice that he died in his fiftieth year; other ancient historians gave the incompatible age of 60.
Calling 395 an instantaneous or constitutional 'division of the Roman Empire' is an oversimplification. Eastern and western administrative divisions and multiple Augusti long predated this death, and the empire continued to be conceived as one Roman polity.
The Oxford history excerpt explicitly cautions that treating the division as absolute from 395 is a simplification: https://academic.oup.com/book/47282/chapter-abstract/422393315
Federate soldiers assembled at Pavia mutinied on 23 August 476 and proclaimed Odoacer rex — king. The trigger was the collapse of negotiations over their demand for a share, traditionally described as one third, of Italian land or revenues.
Orestes, the dominant commander and father of the emperor Romulus, fled from Pavia toward Piacenza as the revolt turned into an alternative government backed by the army.
What the title was, and wasn't
“Rex Italiae” is too precise for what happened at the acclamation. Contemporary and near-contemporary sources use several royal descriptions, and only Victor of Vita explicitly calls Odoacer king of Italy.
The soldiers' one-third demand is similarly uncertain — Procopius reports land, but it may have meant a portion of tax receipts, and modern scholarship questions a literal mass redistribution of Italian estates. Odoacer's age of 43 is likewise a calculation from an uncertain birth around 433.
An army revolt, not an invasion
This was a military pronouncement by troops already serving in Italy, not a foreign army crossing the Alps. Odoacer commanded no Ostrogothic host; the Ostrogoths under Theodoric invaded his Italy more than a decade later.
Romulus Augustus was still emperor that day. Piacenza fell after a five-day siege, Orestes was dead within days, and only in early September did Odoacer enter Ravenna and depose Romulus Augustus.
Researched 23 Aug 2026·4 sources·3 audit passes
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
What the sources leave uncertain
The date and proclamation as rex are well attested, but 'rex Italiae' is too precise as the title used at the acclamation. Treccani notes that contemporary and near-contemporary sources employ several royal descriptions, while only Victor of Vita explicitly calls him 'king of Italy.'
Odoacer's birth is only approximately dated to 433, so the listed age of 43 is a calculation, not a securely recorded age.
The soldiers' 'one-third' demand may refer to land, as Procopius reports, or to a portion of tax receipts; modern scholarship questions a literal mass redistribution of Italian estates.
After a stay at Quba with the Banu ʿAmr ibn ʿAwf, in 622 Muhammad left for the central settlement of Yathrib with Abu Bakr and an armed escort from the Banu al-Najjar, whose swords turned the final short ride into a public demonstration of protection.
Some residents initially greeted Abu Bakr rather than Muhammad, because Abu Bakr was standing and visible while Muhammad sat silently.
A date-yard becomes a mosque
Muhammad lodged in the courtyard or household of Abu Ayyub al-Ansari. His camel stopped at a date-drying yard belonging to two orphan boys, Sahl and Suhayl, and he negotiated for the ground as the site of his mosque.
Construction began with Muhammad and his followers carrying unburnt bricks and clearing and levelling the site — giving the emigrant community a physical centre in Yathrib.
Dates and distinctions
Arrival at Quba and entry into central Yathrib are two milestones often collapsed into one “arrival in Medina,” since Quba lay within the wider Medinan oasis. The length of the Quba stay is itself disputed: reports give fourteen nights, more than ten, or only several.
The entry date is equally contested, with reconstructions including 24 September, 4 October, and — under a hypothetical intercalated Arabian calendar — a date in July 622. The agreement conventionally called the Constitution of Medina followed not long after his arrival, but no consulted source establishes that it was drafted on this entry date.
Researched 23 Aug 2026·5 sources·3 audit passesDate disputed
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
Date disputed. Sources disagree; the research places it at ~0622-09-24.
What the sources leave uncertain
The exact entry date is highly disputed. Reconstructions include 24 September, 4 October and, under a hypothetical intercalated Arabian calendar, a date in July 622.
The sources conflict over the length of the Quba stay: reports give approximately ten, fourteen or only several nights.
Quba lay within the wider Medinan oasis, so sources saying Muhammad 'arrived in Medina' may mean arrival at Quba rather than his later movement into central Yathrib.
The Constitution of Medina is early and probably followed the Hijra, but scholars dispute its unity and dating; assigning its drafting to this exact day is unwarranted.
The last Sasanian shah died neither in a palace nor in battle: tradition places him hiding in a working mill outside Merv, betrayed by the governor there.
View full image ↗AI-generated illustration · Ideogram 4 (fp8) · 2026-08-27How was this image made?
The creative brief sent to the image model. These are instructions, not a record of what actually happened.
Accounts preserved in Persian and Islamic historical traditions place the fugitive Yazdegerd III near Merv in about 651 after his forces had been defeated and dispersed. He had lost the support of Māhōy Suri, the governor there — the man from whom he had demanded an accounting of taxes — who allied with Nezak Tarkan against him.
Yazdegerd took refuge in a mill and was murdered there after Māhōy's betrayal. He was perhaps 27 or 28, if the report that he was eight at his accession in 632 is accepted.
How much of the story is secure
The safest core is that Yazdegerd died near Merv following Māhōy's betrayal. The killer's identity, motive and the handling of the corpse are less certain, and the traditional sequel — the body thrown into the Merv River, recovered and buried by a Christian cleric — comes from later textual traditions rather than contemporary eyewitness evidence.
Even the year is unsettled. 651 is commonly printed, but Encyclopaedia Iranica records a tradition dating the murder to 650, and no exact month or day is securely established.
A dynastic end, not an institutional one
His death ended the reigning Sasanian dynasty in Iran and the functioning of its court; Māhōy controlled the immediate political situation at Merv. But the Arab conquest had already destroyed the effective Sasanian imperial state by about 650, so the murder marks a dynastic endpoint rather than the moment every imperial institution vanished.
Nor did the claim die with him. His son Pērōz and other descendants continued unsuccessful restoration efforts from Central Asia and China.
Researched 23 Aug 2026·3 sources·3 audit passesDate disputed
How this was checked
Researched from the web into a fact sheet, rewritten from that sheet, then audited against it by a different model. How the pipeline works →
Date disputed. Sources disagree; the research places it at ~0651.
What the sources leave uncertain
The commonly printed year is 651, but Encyclopaedia Iranica records a tradition dating the murder to 650, and calendrical scholarship notes that the evidence does not decisively exclude other regnal-year calculations.
The miller story survives in later Islamic and Persian narratives whose details differ. The safest core is that Yazdegerd died near Merv after Māhōy's betrayal; the killer's identity, motive and handling of the corpse are less secure.
View full image ↗ 
