Buildable tools and devices: what they do, what you need, how to build or use them, and a worked example. The interactive ones open a tool.
An instrument
The Servant Foundry
Builds a servitor sheet — name, sigil, one task, a way to feed it, a stop condition and a record — from a purpose and a Grimoire aspect.
What it is
To specify a servitor completely before charging it, so the construct has one task and a way to end.
At a glance
- Inputs
- A purpose; a planet; an element; a lifespan; a seed.
- Outputs
- A servitor sheet with a generated name, a sigil, a task statement, a feeding schedule, a kill condition and a JSON export.
How to use it
- State one task, not a wish. 'Deliver one useful contact each Friday' is a task; 'be more social' is not.
- Choose the planet and element that fit the task.
- Set a lifespan and a kill condition before generating the name.
- Generate the name and sigil. If the name feels wrong, reroll the seed; do not keep a name you dislike.
- Export the sheet. Charge the sigil in gnosis and send the servitor to the task.
- Put the feeding schedule and the kill date in a calendar or a ledger.
What you need
- A browser
- A ledger file
- A calendar
- A place to keep the sigil
A worked example
Purpose: 'surface one useful contact each Friday.' Planet: Mercury. Element: Air. Lifespan: 8 weeks. Kill: 'on the eighth Friday, delete the sigil and close the ledger.' The foundry names it 'VEL-ETH-8', marks it with ☿ and 🜁, and writes the feeding as 'one minute of attention each Wednesday at the Mercury hour'.
Variations
- Use a Moon phase instead of a planet for a time-bound servitor.
- Give the servitor a physical anchor: a printed sigil in a drawer.
- Run two servitors with the same task and different aspects, and compare the records after four weeks.
- Make the kill condition a public date in a shared calendar if the servitor serves a group.
Code sketch
This is a sketch, not a runnable program. It names the shape of the automation; the definitions are yours.
const syllables = ['VEL','ETH','MOR','IX','ARA','SOL','NIM','UR'];
const name = (seed) => { const h = hash(seed); return [0,1,2].map((i) => syllables[(h >> (i*5)) & 7]).join('-'); };Related entries
Practices
Constructs
Correspondences
Workings
Related
One of 110 entries in the Technomancy workshop. How a working is built Is it wrong somewhere?
Mentioned by 11
Every entry that names The Servant Foundry, grouped by section.
⚙ Instruments 3
- The Sigil Forge Related
- The Instrument Workshop Related
- The Servitor Ledger Related
✧ Practices 1
- Servitor work Instruments
⌘ Protocols 1
- Found a servitor Instruments
◈ Constructs 1
- Servitor Instruments
⌬ Correspondences 1
- Mercury — message queue Instrument
❖ Workings 1
- The Mercury Inbox Servitor Instruments
▤ Glossary 1
- Servitor Related
✎ Prompts 1
- Servitor brief Instruments
⌁ Currents 1
- Chaos magic Instruments
More in Instruments
The entries either side of this one in the same section.
- The Sigil Forge Turns a sentence, a Grimoire aspect and a seed into a deterministic sigil, a charge card and a record line.
- The Instrument Workshop Combines a Grimoire aspect, a machine pattern and an instrument form into a buildable brief.
- The Random Rite Generator Composes a one-sitting working from a seed, an aspect and a small library of actions.
- The Egregore Charter Writes a group charter — purpose, members, feeding, boundaries and closing — and marks it with a shared sigil.
- The Correspondence Engine A small table and query function that maps Grimoire aspects to technical patterns.
- The Glitch Oracle Reads a question against a Grimoire aspect and a glitch, error or random draw, and records the reading.
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.