Step-by-step procedures: what you need, when to do them, and what can go wrong.

A procedure

Build an egregore

Charter, name, mark, first ritual and first feeding for a group construct.

What it is

To make a group's shared attention explicit and bounded.

At a glance

When
The day and hour of the chosen planet for the first meeting; the review on the agreed date.

How to do it

  1. Write the charter: purpose, members, boundaries, feeding, review, close.
  2. Choose the aspect and generate the shared sigil.
  3. Hold a first meeting or ritual that uses the sigil.
  4. Agree the feeding schedule and the steward.
  5. Log the first feeding and the review date.
  6. At the review, read the charter and change one thing.

What you need

  • A shared document
  • A shared sigil
  • A calendar
  • A steward

A worked example

The 'Saturn Room' charters a quarterly project, meets on Sundays, pins the sigil, and reviews at the end of the quarter.

What can go wrong

  • The charter has no close or no way to leave.
  • The group has a sigil but no feeding schedule.
  • The steward becomes the only person who can close it.

Background

Keeping a record

The charter, the sigil, the first feeding line and the review.

Related entries

Constructs

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

Mentioned by 8

Every entry that names Build an egregore, grouped by section.

◈ Constructs 2

▤ Glossary 2

⚙ Instruments 1

✧ Practices 1

⌘ Protocols 1

❖ Workings 1

More in Protocols

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

All of Protocols →

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.