A good friend of mine, who’s also a decent geomancer to boot, recently emailed me with a question on interpreting a rather troublesome kind of query with geomancy. It’s a problem I’ve encountered before with some people and, occasionally, in my own work, and although I think I’ve implied how to handle the issue in other posts around here or that I’ve written enough to allow the astute geomancer to deduce what to do properly, I think it’s about time I’ve made it explicit what I do in these instances.
As we all know, one of the most important aspects, if not the most important aspect, of the process of divination is the art of asking the query. Knowing how to phrase the query in a clear, concise, and concrete manner that seeks the right amount of information as well as the right information you want is crucially important; as is especially the case with geomancy but as well as with many forms of divination, if you ask a vague query of geomancy, you get a vague answer you can’t do much with. To help out with this, when I perform a geomantic reading for someone, I first figure out what exactly it is they want to know, and it’s sometimes the case that the query they came to me with is not the one they actually want to ask, and it’s very often we radically change the wording that gets to the point of what they want to know.
Still, sometimes you’re stuck with a weird query, and there’s a particular type of query that leads to a lot of consternation among diviners of all types. These are the so-called “inverse queries”, where one asks about something not happening. So, for example, if a proper query has the form “Will X occur?”, then its corresponding inverse query has the form “Will X not occur?”. Any binary query (one that expects a “yes” or “no” answer) can be phrased in such an inverted way, and while it’s preferable that we don’t use inverted queries but phrase them in their more direct, proper way, there are times when we can’t get out of answering such a query with geomancy. It’s obnoxious when those cases happen, but they do, and it’s helpful to know exactly how to handle them when they arise.
First, remember that inverted queries are still just queries, and moreover, they’re binary queries that expect a “yes” or “no” answer. As with all such binary queries, the big technique we want to use to answer them is perfection, which I’ve detailed before in two blog posts here and here. To summarize the technique of perfection, we analyze the motion of figures between and around the houses of the querent and quesited, and depending on whether the significators of the querent and quesited come into contact with each other in some way, we can say that the chart perfects or denies perfection. If the significators contact each other, then the chart perfects and affirms the query, i.e. the chart is saying “yes, it will happen”; if the significators do not contact each other, then the chart denies perfection and negates the query, i.e. the chart replies “no, it will not happen”. This does not say anything about the fortune, misfortune, goodness, badness, helpfulness, or the lack thereof about anything; all perfection determines is whether something will or will not happen. Perfection can happen in one of four ways, with more possibilities in each technique depending on what’s going on in the chart, but the specific methods of perfection don’t really matter for the purposes of answering inverse question.
So, quick example. Let’s say I was just given a job offer, and I want to know whether I should take the job. So, I cast a geomantic chart for the query “Should I take the job?”, which is a proper (not inverse) query. There are two possibilities here:
- The chart perfects: this agrees with the query and gives an affirmative answer, thus, “yes, you should take the job”.
- The chart does not perfect: this disagrees with the query and gives a negative answer, thus, “no, you should not take the job”.
Simple enough, right? All perfection determines is whether the chart says “yes” or “no” to the query, regardless of what’s asked or how it’s asked. This means we can do the same thing with inverse queries in a straightforward, although clumsy, manner. If we use the inverse of the preceding query, let’s say we cast a chart for the query “Should I not take the job?”, and we get one of two answers:
- The chart perfects: this agrees with the query and gives an affirmative answer, thus, “yes, you should not take the job”.
- The chart denies perfection: this disagrees with the query and gives a negative answer, thus, “no, you should not not take the job”.
No, that second “not” there is not a typo. Remember, perfection agrees with what’s been asked, and denial of perfection disagrees with what’s been asked. If it so happens that you get a denial of perfection for an inverse query, then you’re getting a disagreement with a negative, which effectively affirms the positive. So, when the chart says “no, you should not not take the job”, it can be read as “no, you should take the job”; the double negative becomes a positive. Remember, however, that this says nothing about how good or bad the situation is; that’s left up to the nature of the figures themselves, not how they pass around as far as perfection’s concerned.
All this is basically a geomantic form of the theorem of double negation in propositional logic: “if a statement is true, then it is not the case that the statement is not true” or, said another way, A = not (not A). While the idea here is simple enough, and while these types of inverse queries that may or may not be answered through a double negative can be interpreted in a straightforward manner, this causes the practice of geomancy to quickly get unwieldy and confusing for many, so we prefer to use proper queries instead that avoid the whole business of trying to eliminate double negatives. It’s preferable to phrase queries so that you avoid this kind of logical weirdness, and some shades of meaning could be toyed with in ways that haven’t been fully explored. For instance, say that a chart for the query “will I not get the job” perfects by translation; what then? Strictly speaking, this means that there is a third party helping to achieve the query, so someone is helping you not get the job, which could be interpreted as someone arguing against it with the interviewer, stealing the job from you, winning out over you, or something similar depending on the other factors in the chart. This is often a more roundabout and confusing way to ask something when you could more easily ask “will I get the job”, which in many respects is more direct and simpler to interpret.
However, one case when I have found it helpful to ask an inverted query is when I’m confirming something. While it’s generally bad form to ask the same question multiple times of an oracle, I’ve found that it’s good and acceptable practice to confirm something by negating its inverse, and this goes for many forms of divination including geomancy. For instance, say I’m unsure about taking a given job offer, so I ask “should I take the job”, and the chart perfects, so it would seem that I should take the job. Not willing to use that as my sole data point, however, I would then throw another chart and ask “should I not take the job” to confirm its opposite; here, the chart denies perfection, so no, I should not not take the job, i.e. I should take the job. This method of asking a proper query immediately followed up by an inverse query is good for absolutely confirming something along the following lines:
- The proper query is of the form “Should I do X?”
- The inverse query is of the form “Should I not do X?”
- If the proper query perfects and the inverse query denies perfection, we have “yes, you should do X” and “no, you should not not do X”. Both are saying that you should do X, and the agreement between the two strongly confirms this.
- If the proper query denies perfection and the inverse query perfects, we have “no, you should not do X” and “yes, you should not do X”. Both are saying that you should not do X, and the agreement between the two strongly confirms this.
- If the proper query and inverse query both perfect, we have “yes, you should do X” and “yes, you should not do X”. Both are saying that you could do either X or not X equally well, implying that either way is acceptable or suggested, or that it doesn’t matter which course of action you take.
- If the proper query and inverse query both deny perfection, we have “no, you should not do X” and “no, you should not not do X”. Both are saying you should do neither X nor not X, implying that you might be better off looking for a third option to pursue instead of either of these two.
This method of confirming an answer, while it might bug the occasional spirit, tends to work very well in practice, and if you’ve already done all the work of casting a full geomantic chart to get a complete answer to see whether one should pursue a given course of action and the effects thereof, if the need for confirmation is strong enough, it can often be worth the extra work to cast another full geomantic chart just to make sure that the opposite course of action isn’t recommended. In doing so, however, we might find out that we have more options than we thought we did, or that we might want to consider something entirely different besides X and not-X.
Now, all that said, when it comes to asking inverse queries, they may not always have the word “not” in them. The English language has a truly rich and immeasurable vocabulary, and we have many words that are the exact opposite of other words (yes, antonyms are a thing!). So, while it may not be apparent that “should I turn down the job offer?” is an inverse question, it’s easy to see that turning down a job offer is equivalent to not taking the job offer. Once we understand that turning down a job offer is the inverse of taking the offer, we can think of this as an inverted query, and we might switch instead to “should I take the job offer?” for clarity’s sake. This begins to get into the debate of how to properly and best phrase a query, but I think we can see the logic now behind proper queries and inverse queries.