❖ Section · Workings
Workings
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, and keep the test.
The test is the important part. A working that has no test is a story about a working.
All workings 8
A backup and archive ritual with a manifest, a read-back test and a close.
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.
A security banishing: three rules, one test and a close.
A small daemon that announces the planetary hours and prompts the operation that belongs to each.
A bounded servitor that surfaces one useful contact each Friday, with a ledger and a close.
A group construct for a shared deadline, with a charter, a weekly check-in and a public close.
A daily sigil made at sunrise, published as a card, and closed at sunset.
A small browser charm that surfaces one saved contact or image each visit, and closes after a week.
Build your own
Take a working that is close to what you want, change one part and keep the test. The Build guide has the shared anatomy; the Workshop will draft a brief from a Grimoire aspect.
Everything in this section
1collection, 8 entries. Every one is in the index, where each entry has its own page and shows what it points at and what points back at it.