Repeatable practices: what they do, what goes in, what comes out, and a worked example.

A practice

Servitor work

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

What it is

To delegate one bounded task to a construct you can maintain and end.

At a glance

Inputs
One task; a name and sigil; a planet/element; a feeding method; a lifespan; a kill condition.
Outputs
A servitor sheet, a feeding calendar, a ledger and a closing record.

How to do it

Write the task as a single sentence. Name the construct and give it a sigil. Choose a feeding method and a schedule. Set the lifespan and the kill condition before charging. Charge it in gnosis, send it to the task, and log every feeding. At the end, dismiss it and mark the ledger closed.

A worked example

Task: 'surface one useful contact each Friday.' Mercury / Air, eight weeks, fed on Wednesdays at the Mercury hour. The ledger records three feeds and two contacts; the servitor is closed on the eighth Friday.

Variations

  • Use a physical anchor — a printed sigil in a drawer — instead of a digital one.
  • Build two servitors with the same task and different aspects, then compare the records.
  • Make the servitor's feeding a shared group action and its kill condition a public date.

Related entries

Constructs

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

Mentioned by 10

Every entry that names Servitor work, grouped by section.

⚙ Instruments 2

✧ Practices 2

⌘ Protocols 1

◈ Constructs 1

⌬ Correspondences 1

❖ Workings 1

✎ Prompts 1

⌁ Currents 1

More in Practices

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

All of Practices →

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.