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 Saturn Deadline Egregore
A group construct for a shared deadline, with a charter, a weekly check-in and a public close.
What it is
To give a small group a shared time-shape and a clean end.
Charter a group for one quarter. The task is to finish one shared project by a fixed date. Use Saturn and Earth. The feeding is a Sunday check-in; the close is the last Sunday of the quarter.
How to do it
- Write the charter: purpose, members, boundaries, feeding, review and close.
- Generate the shared sigil and pin it in the shared document.
- Hold the first Sunday check-in and agree the project.
- At each check-in, read the charter's purpose and close one open loop.
- At the final Sunday, review the project, archive the charter and post the close.
- The steward removes the sigil and records the close.
What you need
- A charter from the Egregore Charter
- A shared sigil
- A Sunday check-in
- A shared task board
- A review and close date
- A steward
A worked example
A four-person group charters 'The Saturn Room' to finish a zine by the end of the quarter. The Sunday check-in closes one loop each week; the final Sunday ships the zine and closes the charter.
How you know it worked
At the mid-point, ask each member whether the check-in is useful. If half say no, change the feeding rather than adding another meeting.
Variations
- Use a Moon phase for a one-month group.
- Make the project a single deliverable, not a backlog.
- Run a silent group: a shared document and a weekly line instead of a call.
Code sketch
This is a sketch, not a runnable program. It names the shape of the automation; the definitions are yours.
# {{group}} — charter
**Purpose.** Finish {{project}} by {{date}}.
**Feeding.** Sunday check-in, one loop closed.
**Review.** Mid-point and final Sunday.
**Close.** Steward archives the charter and posts the close.Related entries
Instruments
Practices
Protocols
Constructs
Correspondences
Related
One of 110 entries in the Technomancy workshop. How a working is built Is it wrong somewhere?
Mentioned by 3
Every entry that names The Saturn Deadline Egregore, grouped by section.
✧ Practices 2
- Egregore work Workings
- Digital altar Workings
⚙ Instruments 1
- The Egregore Charter Workings
More in Workings
The entries either side of this one in the same section.
- The Mercury Inbox Servitor A bounded servitor that surfaces one useful contact each Friday, with a ledger 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 Mercury Hour Daemon A small daemon that announces the planetary hours and prompts the operation that belongs to each.
- The Solar Sigil Card A daily sigil made at sunrise, published as a card, and closed at sunset.
- The Jupiter Archive Blessing A backup and archive ritual with a manifest, a read-back test and a close.
- The Venus Network Charm A small browser charm that surfaces one saved contact or image each visit, and closes after a week.
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.