SACERDOTE de CYDONIA

Most modern writing about entity work uses the words invocation and evocation interchangeably, which loses the single most useful distinction in classical ceremonial practice. Evocation means a spirit is called to appear and be seen. Invocation means its influence is invited to operate through the practitioner without necessarily manifesting. The two have different structures, different risks, and different reasons to exist, and collapsing them is why a lot of entity advice is either terrifying or useless. This is a first-contact route: how to read a name, what the classical catalogue actually gives you, where the modern approach deliberately relaxes the framework, and why Peter Carroll's position that entities are aspects of your own mind is the most practical thing anyone has written on the subject. It is written for someone who has an entity practice in mind and wants the working version rather than the mythology.

The difference the vocabulary was built to protect

In classical usage a spirit was bound, called, and made to appear within a prepared space, where the practitioner could observe it and address it. That is evocation. Invocation was a different operation: the entity's sphere is entered or aligned with by the operator, and the effect is expected to run through the operator rather than in front of them. One is a meeting. The other is a delegation. The modern collapse of the two is not harmless, because it means practitioners who want the safety profile of invocation often end up doing something closer to evocation without preparing for it.

The distinction also determines what you expect. Evocation gives you an image, a sense of presence, and something you can question. Invocation gives you a change in your own state, which is harder to see and considerably easier to use safely. If you are starting, invocation is the better entry point, purely on practical grounds: nothing appears that you then have to dismiss. Choose the operation that does not put a new thing in the room.

What the classical catalogue actually gives you

The Ars Goetia is the most structured entity catalogue in Western grimoire literature, and the structure is the useful part. Each of the seventy-two has a rank, a visible form, a set of powers, and an office. The ranks group them roughly as administrative authority, considerable power, and direct rule. The form tells you what you would expect to see. The office tells you what the thing is for, which is the field you should be selecting on. The powers tell you what it is claimed to do. That is a complete working profile and it is more than most folk traditions offer.

What it does not give you is any evidence that the catalogue describes external beings. It is a structured piece of demonological literature, derived from older Jewish and Christian material and arranged by a seventeenth-century compiler. Reading it as a working document is a choice, and a defensible one. Reading it as a zoology is a different choice and one that will generate more questions than the text can answer. The structure survives either way, so pick the reading that lets you use the structure.

Why the modern approach relaxes the framework

Chaos magic treats entities as independent pattern fragments with a useful function, and its stated ambition is disruption rather than service. The point of working with a named pattern is that it interrupts a repetitive structure in your own thinking. A fixed doctrinal identity is not required for that to work, and insisting on one is often the thing that prevents the work from doing anything. This is a genuinely practical loosening: you can use a name for its shape, its domain, and its way of looking at a problem, without adjudicating what it is ontologically.

Peter Carroll pushed this furthest with a definition that has held up well: entities are best regarded as aspects of the magician's own mind. That single move neutralises nearly all of the practical risk without requiring you to become a sceptic, and it costs you nothing you actually wanted. A pattern fragment is still a pattern you can invoke. The difference is that nothing has to arrive, nothing has to be dismissed, and the whole operation happens where it always happened, which is in the practitioner. If that framing is too reductionist for you, the classical structure is still there and still works as an interpretive frame.

Reading a name before you work with it

A name is not a label for a creature. It is a compression that has carried a specific set of associations for a few centuries, and those associations are the working material. Read the entry, notice which words in it are doing the work, and write down the domain in your own words rather than in the source's. If the description says it grants dignities, ask yourself what you actually mean by a dignity, and whether you want one. Most people who pick a high-profile name do so because the name is famous, and fame in this corpus is a property of the retelling rather than of the office.

Then check the form, and treat it as design guidance rather than as a prediction. If the description gives you a face, you now have a face for a state of mind, and a face is a much better handle than a word. If it gives you a posture or an implement, same thing. This is why the catalogue format is better than a bare list of names. A bare name gives you a word. A profiled entry gives you a shape, a role and a domain, and those three together are enough to do real work with.

1. Read the full entry twice, once for the domain and once for the form
2. Rewrite the domain in your own words before going further
3. Note the rank and ask whether you need that much authority
4. Write down what you actually want from the working

Choosing by office rather than by reputation

Reputation inside this corpus is a product of centuries of retelling, and it correlates with how memorable a name is rather than with how well matched it is to a question. A short, hard-to-pronounce name travels. A name attached to a story travels. A name attached to a film travels fastest of all, because the film needed a figure general audiences would recognise. Select on office and you will almost always be surprised by how well the working goes. Select on recognition and you will keep finding that the famous entry's stated domain does not cover your question at all.

There is also a practical reason to prefer a mid-rank entry for a first working. A high-rank entry's profile tends to be written in the language of sovereignty, and sovereignty is a frame that invites you to ask for authority over circumstances, which is exactly the request most likely to produce the results you did not want. Mid-rank entries are described in administrative language, and administrative language keeps you in the part of the request you can actually specify. Match the register of the entry to the register of what you are asking for.

The invocation, laid out in parts

Start by settling your own state. Almost nobody does this, and it decides whether anything happens at all. A few minutes of ordinary attention, a written statement of what you are doing and why, and enough physical settling that you are not going to be startled by a noise. Then name the entity by its entry, state the domain in your own words, and state the specific thing you want. The specificity is the whole of it: a working aimed at a broad question produces a broad feeling of having done something, which is not a result.

Then pay attention without generating. This is where the classical invocation distinction earns its keep, and where most modern instruction has gone wrong by describing the opposite. You are not building an image, you are noticing what is already there, and the noticing is the technique. If nothing in particular is there, that is a complete and acceptable result and you should log it as one. Finally, close it explicitly, in words, out loud if possible, naming what you are closing and when you will pick it up again. An invocation that has no defined end is the one that starts running in the background, and that is the failure mode this whole section is about.

What the seal is doing

A seal is a name made into a fixed mark, and its function is compression and portability. You cannot hold a full name in mind while also attending to what the invocation is doing, so the name gets written down once and the mark stands in for it. That is a compression in the ordinary information-theoretic sense, and it explains why the same workflow works for a deity name, a plan, a greeting, or a debt. The mark is not the power and it is not the entity. It is a handle that removes a bookkeeping step.

This is worth internalising because it demystifies the construction step, which is where a lot of people get stuck. If you can reduce a sentence to a glyph by any consistent method, you can reduce an entity name to a seal. The traditional circle-and-line geometry exists because it gives you a structure to build in and a form that is visually distinct from an accidental mark on the page, not because the geometry means anything on its own. A seal drawn badly and used properly outperforms a beautiful one that is never drawn, and the people who struggle with this are almost always people who have decided the drawing has to be good before the working can start.

Evocation, and the extra work it requires

If you want an appearance rather than an influence, the preparation is substantially heavier and the failure modes are different. You need a defined space with a defined boundary, a period of abstinence beforehand, a full preparation sequence, and a dismissal that is unambiguous. The space matters more than most people expect, because a space that is not defined gives the invitation no limit and the closing no target. Draw the boundary. Write the closing before the opening, so that you know what you will do.

The most common problem is a closing that is hopeful rather than decisive. If you finish by feeling like the space is clear, you have not closed it. Close by naming, by action, and by a change you can verify: the lights go back to their ordinary setting, the object is put away, the door is opened and shut, and the session is written down. That last part is what makes the difference between a closed session and a session you are still mentally inside. If your evocation work is producing persistent unease rather than relief after closing, that is the signal to reduce the intensity and shorten the sessions rather than to add more apparatus to the next one.

Four ways this goes wrong, in the order it tends to happen

The first is vagueness. A working with no specified ask produces a strong sense of having done something and nothing you can log. The second is unclosed attention, where a practice begun casually is still running in the background a week later because nothing told it to stop. The third is escalating frequency, where an interesting experience is chased rather than recorded, and the record is what made the interesting experiences interpretable in the first place. The fourth is framework shopping, where a disappointing result is explained by a mismatch of tradition rather than by a badly specified request. All four have the same fix, which is a log.

The log is not bureaucracy. It is the only thing that lets you distinguish a method that works from a method you happen to have had a good month around, and it is the only protection you have against your own retrospective editing. Write what you asked, what you did, what happened, and what you would change. Do not write what it meant. If you keep a log for three months, the four failure modes above become visible as patterns rather than as a vague sense that something has gone wrong, and the correction is usually small. Most of the people who report that entity work went badly have no log, and the absence is doing all the work in their diagnosis.

Consent, boundaries and other people

The line in entity work that matters most is not between you and the entity, it is between your practice and the people around you. No entity working should be aimed at changing a specific person's behaviour, and no framing of a spirit's domain makes that a different thing from what it is. Work on your own attention, your own availability, your own boundaries. If a working starts producing a plan to influence somebody, the correct response is to stop and write down what you were actually trying to change in yourself.

Shared and domestic space needs a version of this too. An entity practice that has become part of your household routine affects the people you live with, including people who have not consented to it. A brief explanation of what you are doing, offered once and not defended, resolves most of what would otherwise become friction. Keep the practice in your own space and your own hours. The tradition counsels a short daily practice instead of an escalating one, and that counsel is sound here for the same reason it is sound for sleep: the escalating version leaks outward into other people's lives before it manages to damage yours.

Building a relationship without a theology

If you keep a record, you will find that certain names recur in the same situations, and that is a relationship in the only sense available. You do not need to believe anything about it to notice. A pattern that repeats under similar conditions is a pattern, whether or not anything is doing the repeating. Over a year of notes you will have something more interesting than a belief: a map of which patterns show up when, and what happened each time. That map is genuinely yours and cannot be taken away by a better argument.

The temptation at that point is to upgrade the map into a theology, because a theology answers questions the map cannot. Resist it for a while. The map has a real advantage over a theology: it keeps working when you do not know why something happens, whereas a theology has to be right or it collapses. Carroll's position that these are aspects of your own mind is not a deflation, it is a description that stays accurate whether or not there is anything else in the room. Hold both readings comfortably if you can. The one you act from should be the one that keeps the practice safe and the record honest.

A first working you could defend afterwards

One entity, chosen by office rather than reputation. One written statement of a specific ask, in the imperative, that somebody could observe happening. One invocation, in daylight or early evening, in your own space, lasting ten minutes. One dismissal, said out loud. One log entry written the same day while it is still accurate. Then nothing further for a fortnight, and a second working only if the first produced something you can write down. That is a complete cycle and it costs nothing but attention.

Two additions make it better. Before you begin, decide what result would count as partial, because a practice judged only on full success will be abandoned correctly on the first ordinary day. And after the first month, read your whole log in one sitting rather than in fragments, because the aggregate is where the signal is and the individual entry is usually too small to interpret. If after three months the log shows nothing you can point at, that is a legitimate finding and the correct response is to change the specification, not the intensity. Nothing in this field rewards more force, and the evidence for that is one of the more consistent things in the literature.

Frequently Asked Questions

What is the difference between invoking and evoking a spirit?

Evocation calls a spirit to appear so you can observe and address it, and it needs a defined space, preparation, and an unambiguous dismissal. Invocation invites the influence to operate through the operator instead, which is harder to see and much easier to work with safely. If you are starting, invocation is the better entry point because nothing appears that you then have to close.

Do the seventy-two actually exist?

That question cannot be settled and the catalogue is not evidence either way. What is real is the structure: rank, form, office and stated powers for each entry, which is more working material than most traditions supply. Treat the entry as a profile you can use rather than a zoology you have to believe, and the ambiguity stops being a problem to solve.

Is working with entities dangerous?

The risks are practical rather than supernatural: unclosed attention that runs in the background, escalation when an experience is chased instead of recorded, sleep disruption, and practices that spill into other people's autonomy. Every one of the four is handled identically: a short daily practice instead of an escalating one, a written log, a deliberate closing, and a stop rule fixed in advance. Nothing here requires protection from a spirit.

How do I choose an entity for a first working?

Choose by stated office, not by how well known the name is, and prefer a mid-rank entry for a first attempt because the register is administrative rather than sovereign. Rewrite the domain in your own words and check it actually covers what you want. Fame in this corpus tracks memorability, not suitability, and the difference shows up immediately in how the working goes.

Which app helps most with keeping track of this?

A grimoire that holds the entries, so you can read the office and the form without searching, and a spirit browser that sorts by domain rather than by name, because sorting by domain is the selection method that works. Both are one-time purchases with no account, and both save you the part of the practice that actually breaks down: picking something famous when you needed something appropriate.