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

A procedure

Cast a glitch oracle

Question, aspect, source, capture, reading and close.

What it is

To make a repeatable divination from a machine fault or random draw.

At a glance

When
Any time; a fixed hour makes a series comparable.

How to do it

  1. Write the question.
  2. Choose an aspect.
  3. Choose the source: a glitch, an error, a random value, a feed.
  4. Set the seed.
  5. Capture the draw before interpreting it.
  6. Write the reading and one action.
  7. Record the question, seed, source and reading.
  8. Close the session.

What you need

  • The Glitch Oracle or a notebook
  • A capture tool
  • A ledger

A worked example

Question: 'what should I stop maintaining?' The Tower, a build error at 14:02, reading: 'the part that keeps breaking wants to be removed.' Action: delete the branch.

What can go wrong

  • The draw is repeated until it says something pleasant.
  • The reading is treated as a fact.
  • The capture is lost and the reading cannot be checked.

Background

Keeping a record

The question, seed, source, reading and action.

Related entries

Constructs

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

Mentioned by 7

Every entry that names Cast a glitch oracle, grouped by section.

✧ Practices 2

⌘ Protocols 2

⚙ Instruments 1

❖ Workings 1

▤ Glossary 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.