Servitors, egregores, tulpas and daemons: what each is, how it is made, fed and ended.

A construct

Servitor

A purpose-built construct with one task, a sigil, a feeding method and a kill condition.

What it is

To carry one bounded task that the practitioner can maintain and end.

How to make it

Write the task. Name it. Draw the sigil. Set the feeding and the kill condition. Charge it in gnosis and send it to the task.

A worked example

A Mercury servitor for a weekly contact: eight weeks, fed on Wednesdays, closed on the eighth Friday.

Background

A name, a single-sentence task, a sigil, a feeding method, a lifespan and a kill condition. A servitor with several tasks is a badly specified one.

Keeping it fed

Attention, a repeated phrase, a small offering or a weekly review. Put it on a schedule and log it.

Ending it

Name it, state that the task is finished, destroy or archive the sigil, close the ledger and return the space.

Keeping a record

A servitor sheet and a ledger line for creation, each feeding and the close.

Related entries

One of 110 entries in the Technomancy workshop. How a working is built Is it wrong somewhere?

Mentioned by 32

Every entry that names Servitor, grouped by section.

✧ Practices 5

⌘ Protocols 5

◈ Constructs 3

▤ Glossary 3

⌁ Currents 2

❖ Workings 1

More in Constructs

The entries either side of this one in the same section.

All of Constructs →

New entries, when they land

Occasional notes when a section of the grimoire is added or revised. No account, no tracking across sites, and one line to leave.

Grimoire updates only. Nothing is shared. Every note has an unsubscribe link.