Repeatable practices: what they do, what goes in, what comes out, and a worked example.

A practice

Glitch divination

Read an error, a crash, a repeated fragment or a broken feed as the draw.

What it is

To use the machine's own failures as a divination medium.

At a glance

Inputs
A question; a glitch source; a capture; a ledger.
Outputs
A screenshot or log line, a reading and a record.

How to do it

Write the question. Choose a source of glitches. When a glitch appears, capture it — a screenshot, a log line, a timestamp — before interpreting it. Read it against the question and write one action or one thing to leave alone. Close the session.

A worked example

Question: 'what should I stop maintaining?' A build error on an abandoned branch. Reading: 'the part that keeps breaking wants to be removed.' Action: delete the branch and record it.

Variations

  • Use the next error in a terminal as the draw.
  • Use a corrupted image or a broken link.
  • Run a weekly glitch draw at the same hour and read the series.

Related entries

Constructs

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

Mentioned by 11

Every entry that names Glitch divination, grouped by section.

⚙ Instruments 2

✧ Practices 2

⌘ Protocols 2

⌬ Correspondences 2

❖ Workings 1

▤ Glossary 1

✎ Prompts 1

More in Practices

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

All of Practices →

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.