Complete examples: what it is, what you do, what you need, how to test it and how to close it. Copy one, change a part, keep the test.
A repeatable working
The Mercury Inbox Servitor
A bounded servitor that surfaces one useful contact each Friday, with a ledger and a close.
What it is
To practise a complete servitor working on a small, real task.
Build a servitor for one task: surface one useful contact each Friday for eight weeks. Use Mercury and Air. The working is a queue, a weekly draw and a ledger; the close is the eighth Friday.
How to do it
- Write the task and set the lifespan to eight weeks.
- Generate the servitor sheet and sigil; choose the feeding (one minute at the Mercury hour).
- Create a names list and a draw rule (e.g. the first name after a seeded shuffle).
- Each Friday, run the draw, send one message and log the result.
- Each Wednesday, feed the servitor and log it.
- On the eighth Friday, dismiss the servitor, archive the sheet and write the close.
What you need
- A one-sentence task
- A servitor sheet from the Foundry
- A names list (a text file or a table)
- A weekly draw script or a manual draw
- A ledger
- A calendar close
A worked example
The first draw surfaces a former colleague; the message is sent, the reply arrives, and the ledger records the contact. By week four there are two real conversations.
How you know it worked
After four weeks, count the conversations that actually happened. If the task produced none, change the task or close early; do not add a second task.
Variations
- Use Venus and Friday for a social task.
- Use a queue file and a cron job instead of a manual draw.
- Run it with a partner and compare the records.
Code sketch
This is a sketch, not a runnable program. It names the shape of the automation; the definitions are yours.
// Friday draw
const names = readLines('names.txt');
const seed = new Date().toISOString().slice(0, 10);
const pick = names[hash(seed) % names.length];
log({ event: 'draw', construct: 'VEL-ETH-8', pick, seed });Related entries
Instruments
Practices
Constructs
Correspondences
Related
One of 110 entries in the Technomancy workshop. How a working is built Is it wrong somewhere?
Mentioned by 12
Every entry that names The Mercury Inbox Servitor, grouped by section.
❖ Workings 4
- The Saturn Deadline Egregore Related
- The Solar Sigil Card Related
- The Venus Network Charm Related
- The Mercury Hour Daemon Related
⌬ Correspondences 3
- Mercury — message queue Workings
- Water — log Workings
- Wednesday — Mercury Workings
⚙ Instruments 2
- The Servant Foundry Workings
- The Servitor Ledger Workings
✧ Practices 2
- Servitor work Workings
- Feeding a construct Workings
▤ Glossary 1
- Field record Related
More in Workings
The entries either side of this one in the same section.
- The Mercury Hour Daemon A small daemon that announces the planetary hours and prompts the operation that belongs to each.
- The Saturn Deadline Egregore A group construct for a shared deadline, with a charter, a weekly check-in and a public close.
- The Jupiter Archive Blessing A backup and archive ritual with a manifest, a read-back test and a close.
- The Lunar Glitch Oracle A once-a-month reflection: capture one software glitch at the new or full moon, answer three fixed questions, choose one action, and keep a log.
- The Mars Firewall Ward A security banishing: three rules, one test and a close.
- The Solar Sigil Card A daily sigil made at sunrise, published as a card, and closed at sunset.
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.