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

What it is

To turn a recurring technical annoyance into a monthly reflection and one concrete action.

At the new or full moon, capture one glitch before you interpret it. Answer: what is returning, what is changing, what should be released. Write one action for the month. Keep the log; after six readings, review the series rather than a single draw.

How to do it

Put the next new or full moon in your calendar, with the hour.
When it arrives, capture the first glitch you notice — screenshot or log line — before interpreting it.
Answer three questions: What is returning? What is changing? What should I release?
Write one action you will take this month.
Record the date, moon phase, glitch, answers and action.
Close the session: save the record, close the tabs and leave the desk.
After six readings, review the series and count the actions you actually took.

What you need

The Glitch Oracle
Something that captures the glitch (a screenshot or log line)
A calendar
A notebook or ledger
A closing routine

A worked example

A full-moon draw captures a build error on an old branch. What is returning: the same missing asset. What is changing: the deploy now starts from a clean cache. What should I release: the abandoned branch. Action: delete the branch and close the issue. The log records the error, the three answers and the deletion.

How you know it worked

After six readings, count how many actions were actually taken. If none, the oracle is entertainment; change the questions or stop.

Variations

Use a weekly draw at the same hour.
Replace the glitch with a feed item, a song or a line from a log.
Make the reading a group practice and compare the actions.

Code sketch

This is a sketch, not a runnable program. It names the shape of the automation; the definitions are yours.

const phase = newMoonOrFullMoon(date);       // your calendar decides
const glitch = captureGlitch();               // screenshot or log line
const reading = { returning: '', changing: '', release: '' };
const action = chooseAction(reading);
record({ date, phase, glitch, reading, action });

Related entries

Instruments

The Glitch Oracle

Practices

Protocols

Constructs

Daemon

Correspondences

The Solar Sigil Card

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

Mentioned by 8

Every entry that names The Lunar Glitch Oracle, grouped by section.

✧ Practices 3

⌬ Correspondences 3

⚙ Instruments 2

The Glitch Oracle Workings
The EVP Session Kit Workings

More in Workings

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

All of Workings →