Skip to content
eventVerified

Athens allies with Corcyra, a step into the Peloponnesian War file

In 433 BCE Athens made a defensive alliance with Corcyra and fought at Sybota. The dated alliance-war is not the Megarian decree and not the 431 crowding strategy. In the causal graph this event weakens Humanitarian Access, a driver that strengthens People Internally Displaced by Conflict and Violence (IDMC) — an improving welfare path.

Read the full account

In 433 BCE Athens made a defensive alliance with Corcyra and fought at Sybota. The dated alliance-war is not the Megarian decree and not the 431 crowding strategy. Pericles’s documented role is: The demos voted an alliance with Corcyra against Corinth. Pericles backed the policy; unnamed crews fought at Sybota; he did not uniquely row. An alliance is not a trade exclusion. Later editors, printers, and excavators remain named where they appear. Pericles's documented role is: The demos voted an alliance with Corcyra against Corinth.

Context

A Corinthian colony-fight, unnamed triremes, and later Thucydides’ ‘truest cause’ already structure the file. An alliance is not unique authorship of every later killing. Sharing with the demos is required. Named others on the file: Corcyrean envoys, Corinthian opponents, unnamed Athenian crews, and the demos share the alliance. The public setting is the file around -0433-01-01. The instrument stays Athens allies with Corcyra, a step into the Peloponnesian War file. The setting of Athens allies with Corcyra, a step into the Peloponnesian War file is the public file around -0433-01-01. Driver humanitarian-access is attached because the significance names a mechanism from this act, not because a standing list needed coverage.

Why it matters

Complex shared demos vote. Welfare reading worsening. The attached mechanism is A dated alliance put Athens into a Corinthian-Corcyrean naval war as a completed path toward the larger war. Lag to any modern indicator is not treated as zero. This path is attached because the mechanism is named from this act, not because a driver list needed coverage. The welfare reading on this path is worsening.

If a number is not in the two records named above, it is not supplied here.

Who was responsible

Contribution type and responsibility level for each recorded actor — not sole-author shorthand.

  • Pericles

    Person

    Direct responsibility

    responsibility level 0.4 · verified

    The demos voted an alliance with Corcyra against Corinth. Pericles backed the policy; unnamed crews fought at Sybota; he did not uniquely row.

What changed

Fact → Driver → Indicator. Relationship strength orders the paths; it is not the observed indicator movement.

Evidence

The sources behind this fact and its verification state.

Verified2 sources on file
  1. 1.Perseus — Thucydides, HistoryPerseus Digital Library / Tufts · High credibility · verified
  2. 2.Britannica — PericlesEncyclopaedia Britannica · High credibility · verified
What the sources establish

Britannica and Thucydides independently date the 433 Corcyra alliance as distinct from the Megarian file. Official: Britannica — Pericles, Corcyraean alliance (https://www.britannica.com/biography/Pericles-Athenian-statesman (opens in a new tab); Encyclopaedia Britannica). Independent: Perseus — Thucydides, Corcyra and Sybota (https://www.perseus.tufts.edu/hopper/text?doc=Perseus:text:1999.01.0200 (opens in a new tab); Perseus Digital Library). The two URLs are different pages. Where the carrier is a later edition or a received narrative, that limit is stated rather than upgraded to an autograph. Official carrier: Britannica — Pericles, Corcyraean alliance (https://www.britannica.com/biography/Pericles-Athenian-statesman (opens in a new tab); Encyclopaedia Britannica). Independent carrier: Perseus — Thucydides, Corcyra and Sybota (https://www.perseus.tufts.edu/hopper/text?doc=Perseus:text:1999.01.0200 (opens in a new tab); Perseus Digital Library).

Established: 433 Corcyra alliance and Sybota fighting. Established: a sourced public record of Athens allies with Corcyra, a step into the Peloponnesian War file under -0433-01-01.

Confidence is stated on the impact path, not hidden in adjectives. An alliance is not a trade exclusion. Mixed effects of Athens allies with Corcyra, a step into the Peloponnesian War file are separate paths.

Later competitions, monuments, translations, UNESCO listings, museums, and adaptations are not converted into extra lifetime acts.

That reading is an impact-path choice, not a property stored on the Fact itself.

Shared responsibility is part of Athens allies with Corcyra, a step into the Peloponnesian War file. Naming Pericles does not delete co-authors, institutions, or later transmitters. The lag from -0433-01-01 to any measured indicator is not treated as zero. Alternative explanations — weather, other armies, later statutes, or independent cultural change — remain live where the sources do not close them.

Causal path

How this event connects to drivers and indicators in the graph.

  1. ActorPericles
  2. contributed toFactAthens allies with Corcyra, a step into the Peloponnesian War file
  3. weakensDriverHumanitarian Access
  4. strengthensIndicatorPeople Internally Displaced by Conflict and Violence (IDMC)

Cite this page

Factrail. (2026). Athens allies with Corcyra, a step into the Peloponnesian War file. Factrail. https://factrail.ai/facts/per-corcyra-433

https://factrail.ai/facts/per-corcyra-433

Accessed 16 October 2026.

By the Factrail desk · Method: how we source and score · Last reviewed

Dispute this factNamed here, or represent someone who is? Request a right of reply.