Athens besieges Potidaea as a Corinthian-colonial revolt

From 432 BCE Athens besieged Potidaea, a Corinthian colony in its alliance-network. The dated siege is not the Corcyra alliance and not the 429 plague death. Pericles’s documented role is: Athenian forces besieged Potidaea after it revolted with Corinthian help. Pericles’ city sent the siege; unnamed soldiers starved a town; he did not uniquely invent siege. A Chalcidic siege is not an Ionian-sea alliance. Later editors, printers, and excavators remain named where they appear. Pericles's documented role is: Athenian forces besieged Potidaea after it revolted with Corinthian help.

Context

Tribute, a Corinthian garrison, and unnamed starved townspeople already sit in Thucydides. A siege is not unique authorship of every later Chalcidic war. Sharing with the demos is required. Named others on the file: Unnamed Athenian soldiers, Potidaean townspeople, and Corinthian helpers share the siege. The public setting is the file around -0432-01-01. The instrument stays Athens besieges Potidaea as a Corinthian-colonial revolt. The setting of Athens besieges Potidaea as a Corinthian-colonial revolt is the public file around -0432-01-01. Driver humanitarian-access is attached because the significance names a mechanism from this act, not because a standing list needed coverage.

Confidence is stated on the impact path, not hidden in adjectives. Mixed effects of Athens besieges Potidaea as a Corinthian-colonial revolt are separate paths.

Why it matters

Complex shared demos war. Welfare reading worsening. 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.

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