Augury

Augury is the practice from ancient Roman religion of interpreting omens from the observed behavior of birds. When the individual, known as the augur, interpreted these signs, it is referred to as "taking the auspices". 'Auspices' is from the Latin auspicium and auspex, literally "one who looks at birds."[1] Depending upon the birds, the auspices from the gods could be favorable or unfavorable (auspicious or inauspicious). Sometimes politically motivated augures would fabricate unfavorable auspices in order to delay certain state functions, such as elections.[2] Pliny the Elder attributes the invention of auspicy to Tiresias the seer of Thebes, the generic model of a seer in the Greco-Roman literary culture.[3]

Part of a series on
Anthropology of religion
A confident rider, surrounded by birds of good omen is approached by a Nike bearing victor's wreaths on this Laconian black-figured kylix, ca. 550–530 BC
Social and cultural anthropology

This type of omen reading was already a millennium old in the time of Classical Greece: in the fourteenth-century BC diplomatic correspondence preserved in Egypt called the "Amarna correspondence", the practice was familiar to the king of Alasia in Cyprus who needed an 'eagle diviner' to be sent from Egypt.[4] This earlier, indigenous practice of divining by bird signs, familiar in the figure of Calchas, the bird-diviner to Agamemnon, who led the army (Iliad I.69), was largely replaced by sacrifice-divination through inspection of the sacrificial victim's liver—haruspices—during the Orientalizing period of archaic Greek culture. Plato notes that hepatoscopy held greater prestige than augury by means of birds.[5]

One of the most famous auspices is the one which is connected with the founding of Rome. Once the founders of Rome, Romulus and Remus, arrived at the Palatine Hill, the two argued over where the exact position of the city should be. Romulus was set on building the city upon the Palatine, but Remus wanted to build the city on the strategic and easily fortified Aventine Hill. The two agreed to settle their argument by testing their abilities as augures and by the will of the gods. Each took a seat on the ground apart from one another, and, according to Plutarch, Remus saw six vultures, while Romulus saw twelve.

History

According to unanimous testimony from ancient sources the use of auspices as a means to decipher the will of the gods was more ancient than Rome itself. The use of the word is usually associated with Latins as well as the earliest Roman citizens. Though some modern historians link the act of observing Auspices to the Etruscans, Cicero accounts in his text De Divinatione several differences between the auspicial of the Romans and the Etruscan system of interpreting the will of the gods. Cicero also mentions several other nations which, like the Romans, paid attention to the patterns of flying birds as signs of the gods' will but never once mentions this practice while discussing the Etruscans.[6] Though auspices were prevalent before the Romans, Romans are often linked with auspices because of both their connection to Rome's foundation and because Romans were the first to take the system and lay out such fixed and fundamental rules for the reading of auspices that it remained an essential part of Roman culture. Stoics, for instance, maintained that if there are gods, they care for men, and that if they care for men they must send them signs of their will.[7]

Position of the augur

In ancient Rome, the appointment and inauguration of any magistrate, decisions made within the people's assembly and the advancement of any campaign always required a positive auspicium. Unlike in Greece where oracles played the role of messenger of the gods, in Rome it was through birds that Jupiter's will was interpreted.[8][9] Auspices showed Romans what they were to do, or not to do; giving no explanation for the decision made except that it was the will of the gods. It would be difficult to execute any public act without consulting the auspices.

It was believed that if an augur committed an error in the interpretation of the signs, or vitia, it was considered offensive to the gods and often was said to have disastrous effects unless corrected.[10] Elections, the passing of laws, and initiation of wars were all put on hold until the people were assured the gods agreed with their actions. The men who interpreted these signs, revealing the will of the gods were called augures. Similar to records of court precedents, augures kept books containing records of past signs, the necessary rituals and prayers and other tricks of their trade to help other augures and even members of the aristocracy understand the fundamentals of augury.[11]

The augures themselves were not the ones with the final say: Though they had the power to interpret the signs, it was ultimately the responsibility of the magistrate to execute decisions as to future actions.[12] The magistrates were also expected to understand the basic interpretations as they were often expected to take the auspices whenever they undertook any public business.[13]

Until 300 BC only patricians could become augures. Plebeian assemblies were forbidden to take augury and hence had no input as to whether a certain law, war or festival should occur. Cicero, an augur himself, accounts how the monopoly of the patricians created a useful barrier to the encroachment of the populares.[14] However, in 300 BC a new law Lex Ogulnia, increased the number of augures from four to nine and required that five of the nine be plebeians, for the first time granting the ability to interpret the will of the gods to lower classes. With this new power it was not only possible for plebeians to determine the gods will in their favor but it was also now possible for plebeians to critique unfair interpretations by patricians.

Types of auspices

There were five different types of auspices. Of these, the last three formed no part of the ancient auspices.

ex caelō [from the sky]
This auspice involved the observation of thunder and lightning and was often seen as the most important auspice.[15] Whenever an augur reported that Jupiter had sent down thunder and lightning, no comitia (a gathering deemed to represent the entire Roman population) could be held.[16]
ex avibus [from birds]
Though auspices were typically bird signs, not all birds in the sky were seen as symbols of the will of the Gods. There were two classes of birds: Oscines, who gave auspices via their singing; and Alites, who gave auspices via how they flew.[17] The Oscines included ravens, crows, owls and hens, each offering either a favorable omen (auspicium ratum) or an unfavorable depending on which side of the Augur's designated area they appeared on.[18] The birds of the Alites were the eagle, the vulture, the avis sanqualis, also called ossifraga, and the immussulus or immusculus.[19] Some birds like the Picus Martius, the Feronius, and the Parrha could be considered among the oscines and the alites. Every movement and every sound made by these birds had a different meaning and interpretation according to the different circumstances, or times of the year when it was observed.
ex tripudiīs [from the "dance" (of birds feeding)]
These auspices were read by interpreting the eating patterns of chickens and were generally used on military expeditions. Cicero shows that at one point, any bird could perform the tripudium[20] [sacred dance], but that as the practice progressed it soon began customary to use only chickens. The chickens were kept in a cage under the care of the pullarius (keeper of the auspice chickens) who, when the time came, released the chickens and threw at them some form of bread or cake. If the chickens refused to come out or eat, or uttered a cry, or beat their wings, or flew away, the signs were considered unfavourable.[21] Conversely, if the chicken left its cage to feast so that something fell from its mouth and landed on the ground, these signs were termed tripudium solistimum (or tripudium quasi terripavium solistimum [from solum, the ground], according to the ancient writers),[22] and were considered to be a favourable sign.
ex quadrupedibus [from quadrupeds]
Auspices could also be taken from animals who walked on four feet, though these auspices were not part of the original science of augurs, and were never used for state affairs. Often these auspices took the form of a fox, wolf, horse, or dog who crossed a person's path, or was found in an unusual location— the meaning could be interpreted, by an appointed augur, as some form of will of the Gods.[23]
ex dīrīs [from portents]
This category of auspices represented every other event or occurrence which could result in an auspice which does not fit into the above categories. Often actions of sneezing, stumbling, and other slightly abnormal events could be taken as a sign from the Gods to be interpreted.[24]

Offered and requested signs

There were two classifications of auspice signs, impetrative (impetrativa, sought or requested) and oblative (oblativa, unsought or offered). Signs that fall under the category of impetrativa were signs that resulted due to the actions performed by the augur during the reading of the auspice.[13] The other category of signs, oblativa, were momentous events which occurred unexpectedly, while the magistrate was either taking auspices or participating in public debate.[13] Ex Caelo ("from the sky") signs of thunder and lightning or other natural phenomena, would be considered an "offered" sign. Unless the magistrate was accompanied by an augur it was up to them to decide whether or not the “offered” sign was significant.[13]

gollark: Well, obviously you'll have some items available to build stuff from.
gollark: - Checks if the available-items list already contains the item needed. If so, just return that.- If not, checks for recipes to do what is wanted- If one exists, iterate over them (not sure what to *do* with them)- If none exists, we can't do anything, so just return no tasks, no costs and no outputs.
gollark: ```rusttype Items = HashMap<ItemType, u32>;fn quantity(items: &Items, desired: &ItemType) -> u32 { if let Some(available_quantity) = items.get(desired) { *available_quantity } else { 0 }}fn contains(items: &Items, desired: &Item) -> bool { quantity(items, &to_item_type(desired)) >= desired.quantity}fn satisfies(available: &Items, desired: &Items) -> bool { for (typ, desired_quantity) in desired.iter() { if quantity(available, typ) < *desired_quantity { return false } } true}fn to_map(is: &Vec<Item>) -> Items { let out = HashMap::new(); for i in is.iter() { out.entry(to_item_type_clone(i)) .and_modify(|e| { *e += 1 }) .or_insert(0); } out}fn one_item(i: Item) -> Items { let out = HashMap::new(); out.insert(to_item_type(&i), i.quantity); out}#[derive(Debug, Deserialize, PartialEq, Eq, Serialize, Clone)]pub struct CraftingResult { pub tasks: Vec<Recipe>, pub costs: Items, pub outputs: Items}fn solve(desired: Item, available: Items, recipes: &MultiMap<ItemType, Recipe>) -> CraftingResult { if contains(&available, &desired) { // If our available items list already contains the desired item, yay, we can just do nothing return CraftingResult { tasks: vec![], costs: one_item(desired), outputs: one_item(desired) } } if let Some(recipes) = recipes.get_vec(&to_item_type(&desired)) { for recipe in recipes.iter() { let result = solve() // ??? } } else { CraftingResult { tasks: vec![], costs: HashMap::new(), outputs: HashMap::new() } }}```My code, or at least part of it.
gollark: That is NOT THE HARD PART.
gollark: (I'm still confused though)

References

  1. auspic-, auspec- + (Latin: to look, to observe in order to make a prediction; to see omens; from auspex [genitive form auspicis] avi-, stem of avis, "bird" plus -spex, "observer", from specere)
  2. Troxler, Howard, "Electoral Abuse in the Late Roman Republic" (2008). Graduate Theses and Dissertations. https://scholarcommons.usf.edu/etd/537
  3. Gaius Plinius Secundus, Naturalis Historia 7.203.3
  4. J.A. Knudtzon, Die El-Amarna Tafeln (1915:no. 35.26) noted in Walter Burkert, The Orientalizing Revolution: Near Eastern Influences on Greek Culture in the Early Archaic Age (1992), p 42.
  5. Walter Burkert 1992:49, noting Plato's Phaedrus 244C.
  6. Cic. de Div. I.41, II.35, 38; de Nat. Deor. II.4
  7. Cic. de Leg. ii. 13
  8. “Aves internun-tiae Jovis.” Cic. de Divin., ii. 34
  9. “Interpretes Jovis optimi maximi publici augures.” Cic. de Leg., ii. 8
  10. Potter, David. (1994). Prophets and Emperors, p. 152. Cambridge, Massachusetts: Harvard University.
  11. Potter, David. (1994). Prophets and Emperors, p. 154. Cambridge, Massachusetts: Harvard University.
  12. spectio, Cic. Phil. 2,81
  13. Potter, David. (1994). Prophets and Emperors, p. 153. Cambridge, Massachusetts: Harvard University.
  14. F. Guillaumont. (1984). Philosophe et augure, recherches sur la théorie cicéronienne de la divination, Brills. New Pauly footnote 7 “Augures”.
  15. Serv. ad Virg. Aen. II.693; Cic. de Div. II.18, &c.; Festus, s.v. Coelestia
  16. Cic. de Div. II.14, Philipp. V.3
  17. Cic. de Div. II.34
  18. Plaut. Asin. II.1.12; Cic. de Div. I.39
  19. cf. Virg. Aen. I.394; Liv. I. 7, 34; Festus, s.v. sanqualis; Plin. H. N. X.7
  20. A classical and archaeological dictionary of the manners, customs, laws, institutions, arts, etc. of the celebrated nations of antiquity, and of the middle ages: To which is prefixed A synoptical and chronological view of ancient history - P. Austin Nuttall - Printed for Whittaker and co., 1840 - page 601
  21. Liv. X.40; Val. Max. I.4 §3
  22. Cic. de Div. II.34),
  23. See e.g. Hor. Carm. iii. 27.
  24. cf. Serv. ad Virg. Aen. IV.453

Sources

  •  This article incorporates text from a publication now in the public domain: Chambers, Ephraim, ed. (1728). "article name needed". Cyclopædia, or an Universal Dictionary of Arts and Sciences. 1 (first ed.). James and John Knapton, et al. pp. 177–178, 180, 232.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.