CACrown ArchivesThe cinema collection
Menu
Research dossier · History & Society

War of Actium

War between Mark Antony and Octavian, 32–30 BC

Layered newspapers, civic records and oral-history reels arranged as chronological evidence
History and societyInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionSep 7, 2026
Entity authoritySource title only
Source-derived summary

The War of Actium or Actian War was the last civil war of the Roman Republic, fought between Mark Antony and Octavian. In 32 BC, Octavian convinced the Roman Senate to declare war on the Egyptian queen Cleopatra. Her lover and ally Mark Antony, who was Octavian's rival, gave his support for her cause. Forty percent of the Roman Senate, together with both consuls, left Rome to join the war on Antony's side. After a decisive victory for Octavian at the Battle of Actium, Cleopatra and Antony withdrew to Alexandria, where Octavian besieged the city until both Antony and Cleopatra were forced to commit suicide.

Editorial summary

This brief starts where responsible research should: with the source description of “War of Actium” as war between Mark Antony and Octavian, 32–30 BC. Everything that follows is an evidence route, not borrowed authority.

Editorial reviewA strong contextual entry point for chronology, institutions and public events when official records are distinguished from later interpretation. The current 105-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The selected authority fields contribute no independent date. The account is most persuasive where Actium, between and Mark can be independently traced.
Editorial analysis

Why this record matters

The subject matters to the history & society register because the source frames it as war between Mark Antony and Octavian, 32–30 BC. Its deeper value depends on whether names, dates, institutions and citations support that framing.

Evidence profile

The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Sep 7, 2026.

Critical limits

Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. 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

Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.

Best used for
  • Event chronology
  • Institutional context
  • Locating named record creators
Verify next

Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.

Three-step research path

  1. Establish the record: confirm the title “War of Actium”, its source revision and the description used here.
  2. Expand the search: follow War of Actium primary sources, War of Actium archive and Actium research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “War of Actium”?
  2. Who created the surviving record, and for what administrative purpose?
  3. Which voices are present, absent or mediated by the institution?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “War of Actium” 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.