Entity Lore and Invocation

The usual way into this material is a list of seventy-two names, and the usual way it goes wrong is that a person spends an evening reading ranks and powers and comes away with a strong sense of having absorbed something, and no idea how to do anything on Monday. There is a different entry point, and it is older and much less structured. Open an alchemical text instead of a catalogue. You will not find seventy-two rows. You will find a sequence of operations described in a language that assumes you already know what several words mean, and the effect is disorienting in a way that turns out to be useful, because disorientation forces you to ask what the operations are actually for. What an alchemical procedure supplies is a thing a name-list cannot: office, form and a definite end point. What it does not supply is the name. Those two things have to come from different places, and working out which comes from where is most of the skill this route teaches.

Starting from a book of procedures

A book of procedures describes operations. You heat, you dissolve, you combine, you wait, you repeat, and at some point the text either tells you the work is finished or it tells you to begin again. This is a fundamentally different kind of document from a catalogue, and the difference is what makes it the better starting point for a beginner. A catalogue tells you what exists. A procedure tells you what to do. When you are new, the second is worth considerably more, because the first produces a very convincing feeling of having done research while producing nothing you can use. Reading a procedure forces the question of implementation within the first page, because a page of instructions about dissolving something will not let you sit comfortably as a reader.

There is a second reason this entry point works, and it is less obvious. A procedure has a shape, and the shape is legible to someone who has never seen it before. You can look at a page of an alchemical text and see, even through the archaic vocabulary, that this is a sequence with stages and a termination. You can therefore apply structural judgement to it, which means you can ask the useful questions: what is this stage for, what would failure look like, how do I know it is finished. You cannot ask those questions about a table of powers. The most valuable habit in this field is asking the second set, and a procedure document teaches the habit by existing in a form that invites it.

The two words, before you read anything

Before any procedure, the two terms that cause the most confusion in this area are worth fixing in place. Evocation, in classical ceremonial usage, means calling a spirit so that it appears. Invocation means inviting its influence to operate through the operator. In other words, one is about arrival and the other is about transmission. Most modern usage has collapsed them into a single word used for both, and the collapse loses exactly the distinction that a beginner needs, because it removes the question of what you are asking for. Are you asking for something to be present, or are you asking for its influence to be worked through you? Those are different requests with different risks and different failure modes.

Fixing the distinction early also gives you a check on any source you read later. If a text describes a procedure and the outcome is an experience of presence, it is describing something in the evocation register. If the outcome is described as a change in how you behave, think or feel afterwards, it is in the invocation register. Texts that mix them without noticing will also mix them in ways that produce procedures that cannot be evaluated, because you will not know what you were supposed to be looking for. A large fraction of the confusion in this field is traceable to a single word doing two jobs, and it is fixable for free.

The four fields, and where you get them from

Most structured work in this area involves four fields for each entry: rank, visible form, office, and powers. It is worth being precise about where each of these can be obtained, because a procedure text and a name-list supply different ones. Rank comes from the name-list, or from the lineage you are working within, and it tells you almost nothing actionable. Visible form is genuinely hard to source and is usually the field people invent. Office is the one that matters and it is the one a procedure document supplies well. Powers, in most name-lists, are descriptions of a reputation rather than capabilities.

The reason a procedure is the better source is that it tells you the office by showing you the work. An alchemical text does not say, in modern terms, this entity administers contracts. It describes a sequence of operations, and if you read the sequence closely you can extract a function from it, because the operations are a function. A description of dissolution and recombination is a description of breaking something down and putting it back together in a different configuration, and that is an office. You can write it in a line, and the line will be defensible because you can point at the text that supports it.

What an alchemical text gives you that a list of names does not

It gives you an end point. This is the significant advantage and it is not a small one. Almost everything that goes wrong in a first working goes wrong because there was no defined point at which to stop, so the working drifted, and a drifting working cannot be evaluated because you never reached a state that could have been right or wrong. A procedure document has a termination built into its structure, because the whole genre depends on knowing when the work is done. Even when the vocabulary is impenetrable, the structure tells you that the text expects an end, which is more than a catalogue will ever give you.

It also gives you a defensible way to fail. A sequence with stages can fail at a stage, and a failure at a stage is a specific thing that you can describe, correct and repeat. A name-list working can only fail as a whole, which means a failure gives you no information beyond the fact that it did not work. This is not a philosophical preference. It is the practical difference between a practice that can be learned and one that can only be repeated, and it is the reason practitioners who build their own sequences from procedural sources tend to improve over time while practitioners who borrow only names do not.

Choosing the office before the name

Here is the move that makes this route work, and it is the reverse of what most people do. Choose the office first, from the procedure, and let the name come second or not at all. A name is a handle. An office is a function. The function is what the working will actually consist of, because the function determines what you do and what you watch for, and the handle does not determine anything. If you choose the name first, you will spend your first month researching a reputation and your second month wondering why nothing happens. If you choose the office first, you have a procedure-derived function and a first session available immediately.

The practical form of this is to read a procedure until you can state, in one line, what the operation is for, using verbs rather than nouns. Not what it represents, but what it does. A useful test is whether your line could be attached to a real piece of work you might do. If it cannot, the line is still too abstract, and the abstraction is where inflation starts. Practitioners who report the most difficulty with the line are usually reporting that they have picked a name and are now trying to reverse-engineer a function for it, which is why the order matters more than the words do.

The first hour, in order

The first hour has a shape and it is worth following the shape rather than improvising. First ten minutes: read the procedure again and extract the stages, writing each as a numbered line with a verb. Next fifteen: write the office in one line, using those verbs, and underline the verb. Next fifteen: choose a location, and the reason matters, because a location chosen for a reason will keep you returning to it and a location chosen at random will not. Next ten: write down what you expect to be able to say at the end, in one sentence, before you begin. Last ten: begin.

That last ten is the only part that cannot be prepared, and the preparation you have just done is what makes it bearable. The thing that makes first workings fail is almost never the technique, which is simple. It is the arrival of a state that has nothing to do with the working, and the having spent forty minutes extracting a function from a procedure is a considerable buffer. People who skip the extraction and go straight to the ritual are more exposed to that state, not because the preparation is magic but because the preparation is time spent with the aim in view, and aim-holding is most of what is actually happening.

What the charge is doing

A charge is a period of sustained attention on a constructed object, and the useful description of it is not that it activates anything. It is that it is a stretch of time in which you are not doing anything else, which is a scarce resource, and during which you repeatedly return the aim to mind. That is the whole mechanism that anybody can defend. It produces state change, it produces better familiarity with your own aim, and it produces the specific effect of having acted on the aim deliberately rather than by drift, and none of those require a claim about what the object is doing.

The failure mode in a first charge is not insufficient intensity. It is drift with a strong emotional charge attached, which is easy to mistake for a working. A common pattern: the charge begins, attention wanders to a personal problem, the wandering carries some feeling, and the practitioner later records the feeling as the beginning of contact. This is a very common experience and it is not evidence of anything except that emotions can be strong. The way to tell the difference is to write, immediately after, what you were actually thinking about, and to be as specific as possible. Most first charges turn out to contain a lot of unrelated thinking, and writing it down is the only way to know.

The month, and the four things you write

For the first month, four entries and nothing more. On the day of the working, write the aim as a single sentence in the imperative. On the day after, write what you actually did with your day, in three lines, with no interpretation. At the end of the week, write one line about what you noticed and one line about what you expected to notice. At the end of the month, write which of the four came back to you unprompted, and that is the only finding you are looking for.

The third line of the first entry is the one that will be read most often and is the one people resist writing, which is informative. Many people find that the aim they chose is not one they actually want, and the resistance is generally about the gap between what they can justify wanting and what they want. That gap is a normal thing to have and it is much better to find it in the first month than in the fifth. The month is not meant to produce a result. It is meant to produce a record that a stranger could read and understand what you were doing, which is a higher bar than it sounds and the reason it is worth doing.

The part that surprises beginners

The surprising part is how little material is actually required. There is a version of this practice that involves a long preparation, an appropriate environment, a set of tools, a correct sequence of preliminary actions and a period of abstention beforehand, and a great deal of that apparatus is inherited from a context with different aims. What a first working needs is a function extracted from a text, a place, a fixed amount of time and a written record. Everything else is optional and most of it is more useful as a source of things to think about than as a requirement.

Beginners frequently report the opposite, that they feel they are not prepared. The feeling is real and worth examining rather than acting on. Usually what it amounts to is a mismatch between the effort invested and the size of the task, because effort is the currency that is easy to spend and preparation is a way of spending it. Spending a week on a first working does not make it more likely to work. It makes the waiting harder. If you want to be thorough about the first month, be thorough about the record, not about the ritual, and the result will be a practice you can actually keep doing.

Where the procedure text misleads

A procedure text from any period is written for readers who already share its assumptions, and the assumptions are usually left implicit. This is the main source of the disorientation people report, and it has a specific form: the text refers to entities, stages or materials whose meaning is assumed rather than stated, so a beginner reads a sequence that has invisible holes in it. Filling the holes with a name-list is the natural move and it is the wrong one, because the two documents are not describing the same thing. The procedure describes operations. The list describes reputations. Combining them produces a working whose structure comes from one and whose meaning comes from the other, and the two do not fit.

There is a second failure, and it is subtler. Old procedural texts frequently encode an understanding of the world that is not the understanding of the text, and a beginner cannot see the difference because they are reading for the first time. A description of a process that maps onto chemistry also maps onto something else, and the text is written as though the two are the same statement. Reading it as a description of a process is the safer route and loses some of the resonance. Reading it as a description of the other thing is more satisfying and considerably more likely to produce confident claims that you cannot support. Most practitioners eventually settle on the first reading with a note about the second.

Adding your own entry to the sheet

Once the month is done, extend the sheet. You now have a row with a function taken from a text, and you can add the fields you could not source. Rank, you can leave blank or assign the lowest value, and it will make no difference. Visible form is yours to construct, and it should be a simple shape rather than a detailed one, because a detailed form is a set of claims you will not be able to maintain. Office you already have. Powers, if you include the column at all, should be two items maximum, both of which are things you have actually observed yourself doing, not things the entity is supposed to be able to do.

What you have built at this point is a working document rather than a borrowed one, and the difference is visible when you read it back. A borrowed row is a set of assertions about a being you know nothing about. Your row is a set of decisions about a function you extracted and an aim you chose, and every claim in it can be traced to something you did. This is also the point at which the influence of a name-list can be assessed honestly. If you find yourself adding fields to make a name look more like the borrowed version, that is the moment to stop and ask whether you are building a practice or assembling a costume.

The row worth keeping

Keep the row, keep the month of record, and keep the first procedure text you worked from. These three things together are worth more than a shelf, and the reason is that they constitute a practice you can extend. Most people in this field have a large amount of borrowed material and almost nothing they built, and when the borrowed material stops being interesting, which happens, they have no practice to fall back on. A single well-documented row with a month of honest notes behind it is a foundation you can add rows to, and the additions get easier each time because the format is already established and the honest notes already tell you what to expect.

The value of keeping the record is not that it will ever be read again, though some of it will be. The value is that having written it changes what you are willing to claim. A person with four documented weeks behind them and an empty row for anything external is in a much stronger position than a person with a theory, and the difference is entirely a matter of having put the weeks down. If you take one procedure from this route, take the record. The procedure is a means. The record is the thing that makes you able to tell, in five years, whether any of it worked.

Frequently Asked Questions

Why start with an alchemical text instead of the Ars Goetia?

Because a procedure teaches the habit that a name-list cannot. A name-list tells you what exists and produces a strong feeling of having done research while producing nothing you can use. A procedure has stages and a termination, so it invites the questions that matter, which are what a stage is for, what failure looks like, and how you know it is finished. Those questions are the beginning of being able to build your own work.

What is the difference between evocation and invocation?

In classical ceremonial usage, evocation means calling a spirit so that it appears, and invocation means inviting its influence to operate through the operator. One is about arrival, the other about transmission. Most modern usage collapses them, and the collapse removes the question of what you are asking for, which is the first question worth asking of any working.

Where do the four fields come from if I am not using a name-list?

Rank and powers come from a name-list and a lineage, and neither tells you much you can act on. Office comes from the procedure, because the operations in a text describe a function, and that is the field worth sourcing properly. Visible form is yours to construct, and it should be a simple shape rather than a detailed one, since a detailed form is a set of claims you will not be able to maintain.

How do I know when the work is finished?

That is the advantage of a procedure over a name. Old procedural documents have a termination built into their structure, because the genre depends on it. Even with the vocabulary opaque, the shape tells you the text expects an end. If you have taken your aim from a function extracted out of such a text, you can borrow that termination rather than inventing one, which is much more reliable than stopping when it feels like enough.

Is starting from a procedure text too abstract compared with working with a named entity?

It is the reverse of abstract. A named entity is a handle with no function attached, so you either research a reputation or invent a function for it, and both routes are slower. A procedure gives you a function with verbs in it from the first page, and the verbs are what your session will actually consist of. The named version feels more concrete and produces less, because concreteness and usefulness are not the same property.