HOLPE

Borrowed names come with a shape, and the shape is four fields. Rank, appearance, office, and a list of powers. Most of what gets said about working with named figures is a dispute about which of the four to believe, and most of the argument is misplaced, because three of the four were never designed to be believed. They were designed to be a schema, and the useful question is not whether a rank is real but what a schema with exactly these four slots can and cannot hold for a practice you intend to run for a month.

Why four fields and not one

A schema exists to make a set of heterogeneous sources into a single usable record. Sixteenth-century demonological material, medieval administrative language, and later nineteenth-century editorial framing all describe figures with wildly different vocabularies, and something has to hold them together if you want to work with any of them. Four fields is a minimal structure that survives that job.

It is worth being clear that the schema is a tool for comparison rather than a claim about the nature of anything. The moment you read the four fields as attributes of a being, you have added a fifth claim that the sources do not make and that the schema cannot support. The four fields are a filing system. Treating them as a description of a person is the error that produces both the disappointment and the inflation.

Rank: the field that tells you nothing you can act on

Rank encodes a hierarchy inside a system that has not had an authority to enforce it for several centuries. A duke of the Goetia is a duke because a specific manuscript numbers him as one, and the number is a fact about the manuscript. There is no institution behind it, no court, and no consequence for getting it wrong.

So read rank as a sorting label. It is useful for locating a description in a volume, and it tells you roughly how the compiler thought of the figure, which is a fact about the compiler. What it cannot do is make the figure more or less powerful, and the habit of treating rank as capability is the first step in a direction that ends in disappointment. Keep it in the index; take it out of the working.

Form: the field that does the actual work

An image is the one element of the schema you can act on directly, because attention needs something to be on. Holding a fixed representation in sustained attention is the mechanism of the whole practice, and the form field is what supplies the object. This is why the form is the field to spend time on and the field to keep deliberately plain.

The temptation is to enrich it, and the enrichment does not help. A richly described figure gives you more material to look at and the same mechanism underneath. Three attributes held flat for fifteen minutes will outperform a page of description every time, and the reason is about the capacity of ordinary human attention rather than about the figure. If your restarts are high, the fix is more sessions, not more detail.

Office: the only field you can act on

The office is the claim about what the figure does, and it is the field that turns a description into a working. Everything else in the schema is context. The office is the sentence you charge, the phrase you will get tired of, and the thing you will have to state in one line without hedging.

Narrow it until it would survive an interview question. Most published offices are written to be impressive rather than to be usable, and they run to twenty or thirty words with three verbs and a subordinate clause. The working version is four words and one verb. If your office cannot be stated in one flat sentence without your voice changing, it is still a description rather than an aim, and it will absorb your attention for months without ever being charged.

Powers: the field that is nearly all borrowed language

The powers field is where the schema is weakest, and it is weakest for a reason that has nothing to do with scepticism. It is written in the vocabulary of outcomes, which is a vocabulary that describes rather than acts. Knowing a source says a figure can open doors is no more useful for a charge than knowing a novel says its antagonist can travel between cities.

There is also an obvious incentive problem. Any practitioner who is drawn to a particular figure will find that figure's powers field is unusually vivid, because the field is written to attract exactly this attention. The remedy is structural rather than moral: decide the office before you read the powers, or read the powers only after a month of work with the office alone. Most people will discover they do not need the powers field at all.

What a schema can and cannot hold

It can hold comparison, which is its real function. Two figures with the same office can be compared and the difference is often just a difference in era and compiler, which is worth knowing. It can hold a place in a reference so that you can return to the same text next month. And it can hold a form and an office well enough to run a four-week practice on.

It cannot hold the thing people most want from it, which is a relationship. A schema has no capacity for reciprocity, mutuality, or surprise, and neither does the practice built on it. What it has is a description, and what the practice does is put your attention on a version of that description for a quarter of an hour at a time. That is enough for most people and it is not the same as having found something, and holding both of those facts at once is the whole of the skill.

Why the catalogue was built this way

The most-cited catalogue in this literature presents seventy-two figures with a rank, a visible appearance, an office, and specific powers, and it is the most structured entity record in the Western grimoire tradition. That structure is an achievement of a particular kind of scholarship: it is a taxonomy assembled from heterogeneous material, and the value of a taxonomy is that it lets you look things up.

It also descends, through a book of Enoch fragment, a seventeenth-century conjuration text, and a later medieval-derived compilation, from Jewish and Christian demonological material rather than from practice. Knowing that chain changes how you read the whole thing. You are reading a filing system built by compilers, and using it as a filing system is using it as intended. Reading it as a census of real inhabitants is reading it as something it was never trying to be.

A name with a thin record

Modern practice includes names that appear in no catalogue at all, and a thin record is not a defect. What you have is a name and, if you have written one, a set of fields. The fields can be entirely your own, and when they are, the practice is cleaner because there is no authority to defer to and therefore no inflation to deflate later.

The failure specific to thin records is the assumption that the thinness is a code. A name with one line of description is not hiding a rich one. If your work with it is going well, the reason is that the office is narrow and you have been charging it, and those are two things you control, and neither of them required the record to be deeper.

Writing an office for a name you invented

Two constraints, and they are enough. The office must be something you would recognise as a job, and it must be four words or fewer. Everything else is negotiable: the form can be three attributes, the call can be one sentence, and the charge can be fifteen minutes on a Sunday.

Write two candidate offices and choose the one that makes you slightly uncomfortable, since that is usually the one that has an actual edge to it. If both are comfortable, the name is decoration and you will get nothing from it, because there is no reason for your attention to stay on it. The discomfort is not a moral signal; it is a signal that the aim is not yet a task.

Where the structure starts generating answers you did not ask for

A schema is a question generator. Once you have four fields and a name, you will start asking what the figure would think about a situation that has nothing to do with the office, and the answers will be fluent, specific, and in your own idiom. That fluency is the mechanism, and it is not information arriving from anywhere.

The way to notice is to look at the syntax rather than the content. When a passage in your notes reads as a reply, check whether the question was in your own writing or whether the figure has been asked something. Almost always the question will have appeared in the same sitting, unremarked. The defence is the one already described: keep the form and the office, write the rest as description, and require a decision in a separate column before any of it is logged as contact.

The audit: does your working still match its own field list

Once a month, take your record and check four things. Is the office still four words or fewer? Is the charge being held rather than narrated? Have you written any decision this month that follows from the office? Is the name still doing less work than the office? Any answer that has drifted tells you which part to fix, and the drift is almost always in the name rather than the structure.

This audit takes ten minutes and it is the mechanism that keeps a framework from becoming a costume. Most people find that the office has quietly widened, or that the charge has become a session of descriptive writing, or that the record contains a great deal of material about what the figure is like and nothing at all about what they did. All three are recoverable in a month, and none of them are recoverable without the audit.

When to stop using the schema

Stop when the record has three months of decisions that follow from the office. At that point the practice is doing its job, and the schema is no longer the interesting part: you have a narrow aim, a form, a fixed hour, and a habit. Everything the four fields gave you has been transferred into your own attention and does not need to be consulted.

Also stop if you find yourself reading a new entry in the catalogue every time a working goes quiet, which is a substitution pattern rather than a practice pattern. A new name gives a month of novelty and no accumulation. The same office, charged for a third month, will tell you more than any fresh description ever will, and the comparison between the two is the only reliable evidence you will get that the method is working for you.

Frequently Asked Questions

What do rank, form, office and powers in an entity catalogue actually mean?

They are a schema for filing heterogeneous descriptions, not a set of claims about a being. Rank is a sorting label from a historical hierarchy with no authority behind it. Form is the field you can act on, because attention needs an object. Office is the claim about function, and it is the field that becomes your aim. Powers is descriptive vocabulary about outcomes and is the weakest field for practice.

Should I treat the rank of a spirit as a measure of its power?

No. The ranks come from a specific historical manuscript and encode how its compiler thought about the figure, which is a fact about the compiler. There is no institution behind the hierarchy, so rank cannot translate into capability. Read it as a sorting label for locating a description in a reference, and take it out of the working, because treating it as power is the first step towards expecting outcomes the figure was never associated with.

Is it legitimate to work with a name that has no source text at all?

Yes, and often it is cleaner. A name you invented has fields you wrote, which means there is no authority to defer to and no inflation to deflate. The only discipline required is the same one that applies to a borrowed name: the office must be four words or fewer and must name something you would recognise as a job. A thin record is not a hidden rich one, and there is no code to solve.

How do I stop the entity framework from turning into self-flattery?

Watch the syntax in your own record. When a passage reads as a reply, check whether you asked the question in the same sitting. The defence is structural: keep the form and the office, write everything else as description rather than as dialogue, and require a decision in a separate column before anything is logged as contact. Once a month, check that the office is still narrow and that the decisions column has content.

When is a named-entity working finished?

When your record shows three months of decisions that follow from the office. The practice has then transferred the schema into your own attention, and the fields do not need consulting any more. You should also stop if you find yourself reading a new catalogue entry every time a working goes quiet, since novelty gives you a month of nothing and no accumulation, whereas the same narrow office in its third month is the only real evidence you will get.