RELMUS

A servitor is the simplest piece of practical machinery in the whole of this material, and almost everyone builds it badly the first time. The reason is not that the technique is hard. It is that the technique asks you to do something most people avoid, which is to write down a single repeated task in language precise enough that a stranger could check whether it happened. Everything else in the working is decoration around that one sentence. The spell was popularised in nineteenth and twentieth century ceremonial writing and then developed by Austin Osman Spare, who framed the entity as a displaced part of the self made available for use. The vocabulary of charge, feeding and dismissal comes from an older layer entirely: the tutelary genius, the protective spirit assigned to a person or a place, which had to be fed on a schedule and formally released at the end of a term of service. That inheritance is worth knowing about, because it explains the parts of the practice that feel like bookkeeping. The feeding, in other words, is not an offering. It is the visualisation of a task completed, and the ritual feeds the servitor by remembering the work that has already been done. Modern practice removed the old limit on how many a magician might keep, which is usually presented as a liberation. Practitioners consistently report a practical ceiling far below the folklore number, and the reason is dull and physical: every active servitor occupies attention. This page walks the construction of one servitor in order, because a second one is easier and a tenth is a mistake.

One task, written before anything else

Before you draw a shape, name a colour or light a candle, you write one sentence describing a task you actually repeat. Not a task you admire, not a task you intend to begin next month, not a task phrased as an outcome. A task is something with a beginning and an end that you have done before and will do again. 'Write more' is not a task. 'Sit down and write for twenty-five minutes before checking anything' is a task. The distinction matters because a servitor is a commitment device rather than a claim about the world, and a commitment device needs a trigger. If you cannot say when it fires, you have written a wish.

The second rule is that the sentence has to be checkable by somebody who is not you and does not believe in any of this. That sounds severe and it is exactly the right severity. Write the aim, then hand the sentence to a friend and ask them whether they could tell, from watching you for a week, whether it had happened. If they cannot tell, the sentence is still too soft. Soft sentences are the reason most servitors do nothing, because nothing about a soft sentence ever forces a decision.

The four fields a servitor needs and no more

A servitor specification has four fields and it is worth resisting the urge to add more. The first is the task, written as the checkable sentence. The second is the trigger, which is the observable event that starts the work. The third is the store, which is the physical location where the thing is kept between uses. The fourth is the sign-off, which is the sentence that ends the engagement. Anything beyond these four is elaboration, and elaboration at this stage is a way of avoiding the first field.

The reason for the strict limit is that each extra field creates a thing you can improve later instead of a thing you have to use. A specification with nine fields will be revised for a year. A specification with four fields gets built on Tuesday. If you find yourself refining the description of the shape, that is a signal that the task sentence is not yet good enough, and no amount of visual detail will compensate for a vague task.

Where the servitor is stored, and why the location decides

The store is not a symbolic choice. Pick a physical object that you will pass daily, put the sigil on it, and keep it in a consistent place. A notebook cover, a laptop lid, a specific drawer, a ring. The tradition's advice about dedicated vessels is not superstition; it is that retrieval works better when the object is not competing for attention with a dozen other uses. A symbol on the back of your phone case is retrieved constantly and ignored constantly, which is the worst of both.

There is also a maintenance question that people skip. Wherever the store lives, the charge fades slowly, and the rate of fading depends on how often the object is handled. If the store is somewhere you touch every day, expect to reinforce it every few weeks. If the store is somewhere you touch monthly, you are maintaining a relationship you do not have, and the reinforcement will not happen. Choose the location for a rhythm you will actually keep.

Drawing the shape of a job you actually repeat

Now, and only now, the shape gets designed. Austin Osman Spare's contribution here was to insist that the entity be drawn as a diagram of the function rather than as a picture of a body, and this is a genuinely useful constraint even if you hold none of his metaphysics. A diagram of a function looks like the sequence of actions. Three boxes in a line, with a line entering the first and leaving the last, is a more accurate servitor for a three-stage writing routine than any humanoid figure would be.

The practical advice is to keep the drawing simple enough to redraw from memory in under a minute. A design that takes ten minutes to reproduce is a design that will not be reproduced, and a servitor that cannot be redrawn is a servitor that cannot be reinvoked. This is why diagrams beat illustrations for the purpose: a diagram carries the instruction, an illustration carries the aesthetics.

The trigger, which is the part that does the work

The trigger is the single highest-value field in the specification and it is the one most people leave vague. A good trigger is a sensory event that already happens at the right time. Sitting down at the desk. Closing the door after work. The kettle boiling. A specific alarm. A bad trigger is an intention, because intentions fire when your state is good and go quiet when your state is not, which is precisely when you need it.

Write the trigger in the present tense as a conditional: when the door closes, I sit and write. Then check whether the trigger precedes the task in the physical world. If the task is 'draft the difficult email' and the trigger is 'open the inbox', the trigger fires many times for many emails and you will build a servitor for avoidance. Tune it until the trigger is nearly one to one with the task.

The charge, kept short on purpose

The charge is a period of deliberate attention on the completed specification. Its length is not important; its termination is. The charge ends when you can say the four fields back from memory without looking, because at that point you no longer need the paper. Charging a servitor by rereading the specification for an hour is a way of postponing the moment at which you would have to internalise it.

The older sources would add invocations, names and correspondences at this stage. Adding them is not wrong, and it is a reliable way to spend an evening instead of building a servitor. If you want the fuller apparatus, use it. If you want the machine to work, four fields and a redraw from memory will get you further than a page of names.

The first feeding, on a task you have already done

A feeding is the visualisation of a completed task, and the reason it works is not mysterious. It is rehearsal of the completion. The ritual element is that you do it as a done thing rather than as a plan, and the practical element is that you do it immediately after the real task, while the memory of having done it is still available.

So the first feeding is not a fresh working. Wait for an evening when you have already done the thing the servitor is for, and then spend five minutes on the visualisation rather than on the task. This inverts the usual beginner mistake, which is to charge the servitor and then wait for the work to appear as a result. The order is work first, feeding second, and the repetition of that order is what builds the link.

Releasing it, and the sentence you use

The sign-off is written at the start of the working, while you are still capable of being objective about it. It is a short sentence naming the end of the engagement, and its purpose is to make the end of the servitor a decision rather than an absence. This is inherited from the tutelary genius, whose term of service ended on a date and had a formula.

Two rules make the difference between a clean release and a lingering one. First, the release is verbal and written, and both. Second, you do something concrete with the store afterwards: you break the symbol, you burn the paper, you put the object back in an ordinary drawer. The act of putting the object back into ordinary use is the most reliable version of the release, because it reclassifies the thing in your own behaviour.

The first week with a servitor in the background

The first week feels like nothing happening, and that is the normal experience. The servitor is not supposed to produce anything you would notice as a result. What it does is narrow the number of occasions on which you fail to begin. You will not notice a servitor working; you will notice an absence of the moment where you usually negotiate with yourself about whether to start.

This is also the week in which most people abandon, because the log stays empty. Resist the urge to record 'did not happen' as a failure. The log's purpose in week one is to establish whether the trigger fires at all. If the trigger fired four times and the task happened three times, the specification is working. If the trigger fired zero times, the trigger is wrong and no amount of reinforcing will fix it.

When it stops helping and you will not notice

A servitor that has become furniture is the standard failure, and it is invisible precisely because it is not doing harm. The task got done anyway, by habit, and the servitor is no longer in the causal chain. You can usually detect this by asking what would change if you deleted the whole apparatus. If the honest answer is nothing, it is furniture.

The more common drift is subtler. The task sentence stays the same while the actual work changes, so you are feeding a servitor assigned to a task you no longer perform. The specification quietly stops matching the life. A monthly five-minute audit of the four fields against the last month of behaviour catches this, and it is the cheapest maintenance in the whole practice.

Retiring it before it becomes furniture

Retirement should be scheduled rather than discovered. Decide a review date when you build the servitor, and put it in the same place as the specification. Three months is a reasonable interval for a single-task servitor. At the review, you either confirm the four fields, narrow them, or run the sign-off.

The reason to force the decision is that servitors accumulate, and each one costs a little attention even when idle. The folklore number is in the dozens or hundreds. The number that survives contact with weekly life is one to three. If you find yourself with four, the fourth is almost always the one you have not touched in six weeks, and releasing it costs you nothing.

The one working worth building first

If you only ever build one, build it for a task that is dull, small, frequent and slightly aversive. Not the important one. The important one is where you will bring your own ambivalence and the servitor will inherit it. The dull, small, frequent, slightly aversive task is where the four-field specification can do its job without your judgement getting involved.

A reasonable first choice is the twenty-five minutes of writing before you check anything, the inbox ritual, or the physical tidying that you keep postponing. Whatever you pick, write the sentence this week, build the four fields, and put a date on the review. The second servitor will be faster. The tenth will be a mistake, and you will know it by the fact that you cannot remember which of them you have fed.

Frequently Asked Questions

How many servitors can I realistically maintain?

One to three. Every active servitor occupies a little attention whether or not it is producing anything, and the folklore numbers of dozens or hundreds do not survive contact with weekly life. The practical symptom of exceeding your own capacity is that you stop being able to remember which ones you have fed, and at that point none of them are receiving anything useful.

What is the difference between a feeding and an offering?

A feeding is the visualisation of a task you have already completed, done immediately after the real task while the memory is available. An offering is a gift given to the entity. The servitor tradition inherited its vocabulary from the tutelary genius but dropped the offering, and the visualisation of completed work is what actually maintains the link between the specification and the behaviour.

Does the servitor have to be drawn as a figure?

No, and a diagram of the function is usually better. Austin Osman Spare framed the entity as a displaced part of the self available for use, which suggests drawing the sequence of actions rather than a body. Keep the design simple enough to redraw from memory in under a minute, since a design you cannot reproduce is a design you cannot reinvoke.

What if my task sentence is too vague to check?

Rewrite it until a non-believer could tell from watching you for a week whether it had happened. If the answer to that test is no, the sentence is too soft, and a soft sentence never forces a decision. Phrases like 'write more' or 'be more creative' are the usual culprits; phrases with a duration, a location and a starting event are the fix.

How often should I reinforce the charge?

Often enough to match how often you touch the store. A symbol on something you handle daily fades in a few weeks; a symbol on something you handle monthly is a relationship you are not maintaining, so pick a store location for a rhythm you will actually keep. The monthly four-field audit is usually more valuable than repeated reinforcement, because it catches the specification drifting away from the actual behaviour.