LIBELULA

LIBELULA belongs to a category of work that looks stranger from the outside than it is from the inside. A named spirit, a sigil, a written office, a standing invitation, and a set of conditions under which you will consider the contact to have happened. This set of notes covers what the classical distinction between evocation and invocation actually protected, why a structured catalogue like the Ars Goetia is genuinely useful rather than decorative, and what the modern chaos framing changes. The honest summary is that this is a technique for installing a specific pattern of attention, and the discipline that keeps it honest is the boring one: you write down what you expected, you write down what happened, and you refuse to score a good mood as a success.

What LIBELULA is

A named spirit treated as a pattern rather than a person. You build a sigil for the name, you give the entity a written office so the role is bounded, and you establish the conditions under which contact counts. That is the whole construction, and it is more like setting up a subroutine than like summoning a collaborator.

The reason people keep a specific name rather than inventing one is that the catalogue entries carry accumulated detail. A spirit described with a rank, a visible form and a set of powers gives you a constraint set to work inside, and constraints are what make the result interpretable rather than a smear of intention.

Where the classical material comes from

The Ars Goetia is the most structured entity catalogue in Western grimoire literature, and the reason is that it is a register. Each spirit gets a rank, a form, an office, and specific powers, which is a format designed for lookup rather than for narrative.

The older distinction between evocation and invocation is worth keeping. In classical ceremonial usage, evocation means a spirit is called to appear, and invocation means its influence is invited to operate through the operator. Most modern usage collapses the two, and the collapse is why a lot of beginner practice feels vaguer than the sources it came from.

Building the invocation from nothing

Write the office first, in one sentence, with a negative clause attached. Not bring me money but handle one specific category of obstacle, and not other people's money. The negative clause is what stops a bounded tool from quietly expanding into a general-purpose excuse to be irrational.

Then reduce the name to a sigil using a method you can reproduce from memory, and then write the contact conditions: time of day, physical state, how long, and what counts as a result you would accept.

The working sequence

Grounding, then sigil, then declaration, then a short silence, then the request in plain language, then dismissal, then the log entry. Grounding first because an ungrounded state produces results you cannot attribute, and the log last because the version you remember is always better than the version that happened.

Keep the whole thing under fifteen minutes. Long invocations drift, and the drift is where self-confirmation enters: the longer you sit with an intention, the more willing you are to read any sensation as confirmation.

In practice, step by step

Ninety seconds of physical grounding: feet on the floor, count ten breaths out loud, name five things you can hear. Then thirty seconds with the sigil, naming the office once and only once. Then the request, said in the first person as a question rather than a command. Then ten seconds of silence. Then the dismissal, which should be as ordinary as the declaration was formal.

The asymmetry is deliberate. Formal at the opening, flat at the close, so the practice has a shape with a beginning and an end rather than a mood that can be extended indefinitely by the person enjoying it.

Why it fails, and what to change

Three failure modes again, and they are stable across all entity work. The first is asking too much, so the aim cannot be scored. The second is skipping grounding, so a tired nervous system supplies the sensation. The third is treating any emotion as contact, which is the specific error that makes this work unrepairable once it starts.

The fix for the third is a hard rule: emotion is not evidence. Heat, tingling, dread, euphoria, a sense of presence, an urge to write something down. All of those are common, all of those are uninformative, and none of them discriminate between a working and a good evening.

Testing without fooling yourself

Score the aim before you start, on a scale you write down, and score it again on a date you set in advance. External checks beat internal ones every time: did the call happen, did the document arrive, did the specific obstacle stop.

Then run a control. Repeat the ritual with a deliberately impossible or trivial aim and see whether your scoring method reports a success. A scoring system that cannot fail is not a scoring system, and this is the cheapest possible way to find out whether yours is one.

Setting up the working space

Paper, a pen, a timer, and a physical anchor for the sigil. The anchor matters more than it sounds: a specific object you touch at invocation and put away afterwards gives the practice a boundary that intention alone rarely supplies.

Timing is unromantic. Same time, same place, same posture. Irregular timing is the most common reason a working feels strong for a fortnight and then evaporates, because the instability was doing the work rather than the technique.

Keeping it alive after the first charge

Revisit the office every few weeks and rewrite it in your own words. If the rewrite comes out identical to the original, you have stopped thinking about what the office is for and are only maintaining a form.

Every couple of months, deliberately use the sigil in a small way that the office does not require. If the tool will not flex at all, it is a talisman you have made, and talismans do not accumulate skill.

Reading the results afterwards

Working signs are behavioural and dull: you reach for the sigil without being reminded, you decline an opportunity because the office does not cover it, and the boundary you wrote in month one still holds when it would have been convenient to ignore it.

Not-working signs are vivid and should be treated as warnings. Escalation, a sense of specialness, an expanding sense of personal significance, the conviction that the entity has plans. All of these read as progress and are the early shape of a practice that has stopped being bounded.

Ethics

Keep the office narrow. The moment the written remit includes other people, money that is not yours, or health and diagnosis, you have left self-directed practice and entered territory that needs an actual teacher, an actual relationship, and considerably more care than a website can supply.

The second ethical line is honesty in the log. A practice built on a record you have edited becomes a practice you cannot learn from, and the person harmed by that is you in six months, trying to work out why it stopped helping.

Mistakes beginners make, and when to stop

Catalogue collecting. Reading entries for a long time before attempting any, which feels like progress and is mostly delay. The countermeasure is to run one small working in week one and let the catalogue be reference rather than curriculum.

Know when to stop an entity relationship. If you find yourself dreading a practice you started, or interpreting ordinary events as messages, the correct response is a clean break and a gap. Continuing past that point is not commitment, and no tradition rewards it.

Frequently Asked Questions

What is the difference between evocation and invocation?

In classical ceremonial usage, evocation is calling a spirit to appear, while invocation is inviting its influence to operate through the operator. Evocation expects a presence in the room; invocation expects an effect in your behaviour. Most modern usage collapses the two, which is why practices built on the sources often feel vaguer than the sources do.

Is a named spirit different from a servitor?

Yes, and the difference is authorship. A servitor is deliberately constructed by you, usually for a specific function you define, and you are its author throughout. A catalogue entity arrives with a pre-existing description, an office and a set of powers, so you are working inside a constraint set rather than building one.

How do I know if the invocation worked?

Score the aim before you start and again on a date you set in advance, using external checks wherever possible. Emotion, tingling, a sense of presence or an urge to write are all common and all uninformative, because none of them discriminate between a working and a good evening. Then run a deliberately trivial control aim to confirm your scoring method can actually fail.

What office should I give the entity?

One sentence with a negative clause attached, narrow enough that you could describe the boundary to someone else without ambiguity. Handle one specific category of obstacle, and not other people's money, not diagnosis, not relationships. The negative clause is what stops a bounded tool expanding into a general-purpose excuse.

How long should an invocation last?

Under fifteen minutes, and shorter for most purposes. Long invocations drift, and drift is where self-confirmation enters, because the longer you sit with an intention the more willing you are to read any sensation as confirmation. Same time, same place and same posture matters more than the duration does.