Technomancy and Cyber Occultism

Screen-based ritual produces a great deal of writing and very little published data, which is an uncomfortable position for a practice whose entire reputation rests on methodological rigour. This page tries to correct the ratio. It reports what happened across twelve workings run to a fixed protocol over eleven weeks: the six that produced nothing, the two that produced something unexpected, and the practical conclusions that came out of keeping records nobody had asked for. The uncomfortable finding is that the device mattered less than the object, and the useful finding is that an illegible glyph produced no result at all. If you are sceptical of technomancy, this page is written so that you can check every claim against a procedure rather than take any of it on trust.

What this report covers and what it cannot

Twelve workings over eleven weeks, each with a written intent, a fixed frequency, and a review date chosen in advance. Six used a phone screen, four a laptop, two a tablet propped against a wall. Every one was logged on the day it happened, including the nulls.

That sample is far too small to support general claims and large enough to support a method. What follows is therefore about technique rather than truth: what worked, what broke, and which choices turned out to matter more than expected.

The finding nobody predicted

The device turned out to matter less than the object. Two of the workings that produced the clearest effects used a phone that was switched off and set face down, with the sigil displayed on a sheet of paper beside it.

This is not the occult equivalent of a debunking. It suggests that the screen is a delivery mechanism for the imagery and that what is actually being engaged is the imagery plus the deliberate act of focusing. A screen that draws your attention is a tool. A screen that is not being looked at is furniture, and the ritual neither improved nor worsened.

Where the work actually broke down

Four failures share a cause. In each, the sigil was generated by an app with no editing step, and the result was a shape with no resemblance to anything. Every one of those four produced no discernible effect, and the four workings that were drawn by hand, or generated and then edited, produced the only entries I would call notable.

This is a claim about attention, not about art. A glyph that means nothing to the person focusing on it does not function as a compressed statement, whatever its derivation algorithm was. The generator saves time on reduction. It does not save the part where you look at the result and decide whether it carries the thing you meant.

Consent came up more often than expected

Four of the twelve workings involved a device other than mine. Two were a shared family tablet, one was a work laptop I did not own, and one was a phone I had borrowed to photograph a sigil for the record.

The rule that emerged is simple and I had not thought of it before: the device being used has to be yours, or to be used with the owner's knowledge of what it is for. A working performed on someone else's hardware without telling them puts a request into a shared environment that they have no way of declining. That is a real constraint on a practice that otherwise seems entirely private.

Step one, the decision to run something at all

Before the sequence: write down whether you are running this because a specific situation needs addressing, or because it is Tuesday and you have a habit to maintain. The second is fine. It just needs to be named, because the two justify different amounts of record keeping.

A habit run needs a count and a date. A situation run needs a condition that a stranger could check. Mixing the two produces records that support neither purpose, and that was the most common logging failure in this series.

1. Decide whether this is a one-off situation or part of a standing schedule
2. Write the condition in checkable language, or write the count and the date
3. Confirm every device involved is yours or is used with the owner's knowledge
4. Set the review date now, and put it somewhere you will see it

Step two, the intent reduced to a single line

The reduction step is where the screen work most often failed. Typing an intent into a text box and accepting a generated glyph feels like the reduction has been done for you. It has not.

Writing the sentence by hand first, then entering it, doubled the number of times I noticed a wording problem before the sigil was ever made. Three of the four null workings contained an intent I could not have said out loud without hesitating, and hesitating is the signal.

Step three, rendering it in a form worth looking at

Generation and rendering should be separate acts. The generator produces a shape. Something then has to make that shape legible at the size it will be viewed, on the surface it will be viewed on, with the contrast you need to focus on it.

A thin black line on white is legible. Most default generator output at phone size is not. The fix is mundane: increase stroke weight, increase contrast, and view the result at actual size before you commit to it. No working in this series produced an effect with an illegible sigil, and the correlation is not proof of anything but it is consistent.

Step four, the charge, timed rather than felt

Timed charges worked better than the untimed ones in this series, and the reason has nothing to do with numerology. A specified duration gives you a stopping point, and a stopping point is what separates a working from a lapse in attention.

Set a timer for the interval and stop when it goes. The risk with an open-ended charge is that it becomes a place to think about the situation, and thinking about the situation while you are supposed to be doing something else is how several of the weaker entries went.

Step five, dismissal that actually dismisses

The dismissal is the step nearly everyone does and nearly nobody does properly. A working that ends by putting the device away still leaves the intent loaded in the interface, on the home screen, in the recents list, in the search history.

Close the application, clear the recents entry, and put the file somewhere you will not see it for a week. Four of the twelve workings in this series ended with a proper deletion, and those are the four I would repeat.

The two unexpected results

One working produced a result in eleven days that had nothing to do with the imagery: a debt I had been avoiding calling anyone about got paid down. I had been intending it for four months. The sigil made no difference beyond making it scheduled.

The second was a failure that I still count as informative. A protection sigil, drawn by hand, charged carefully, produced a measurable increase in my own vigilance for about a week. I had been anxious already. The working amplified an existing state rather than addressing one, which is worth knowing before you charge something while frightened.

What the whole series actually produced

Across twelve workings with a fixed protocol, one produced a result I can describe as attributable, several produced small behavioural changes that would have happened anyway, and the rest were null. That is a worse ratio than the literature suggests and a better one than scepticism predicts.

The method that emerged is unglamorous: hand-write the intent, check the glyph, time the charge, delete properly, log the same day, review on the date. None of those steps involves technology at all, which is not an argument against technomancy. It is an argument for doing the part of the practice that was never about the device.

Recommendations for a second series

If I ran this again the changes would be a longer baseline, a fixed number of workings rather than a fixed period, and separate runs for state-dependent material like protection work.

I would also stop drawing conclusions from anything under eight entries. The two findings I have offered above, the illegible-sigil correlation and the device-irrelevance, both rest on small numbers and would not survive a much larger sample with different results. Recording that is part of the practice, not an admission that the practice failed.

Frequently Asked Questions

Is screen-based ritual doing anything that paper cannot?

In this series, apparently not, and the working that produced the clearest result used a switched-off phone beside a sheet of paper. That is a finding about twelve trials, not a demonstration about technology. It does support a narrower claim: the device is a delivery mechanism, and the thing doing the work is the imagery plus deliberate focus. Anyone who wants to test that properly can, using matched pairs and a pre-registered condition.

What is the biggest practical mistake people make with digital workings?

Accepting a generated sigil without looking at it. It is faster than drawing, which is exactly why it is dangerous, and the four null entries in this series were all generated with no editing pass. A glyph you cannot recognise does not compress anything for you. The second most common mistake is an open-ended charge, which removes the stopping point that keeps a working from turning into daydreaming about the situation.

Is using code to make magic just programming with extra steps?

It is closer to that than practitioners like to admit, and the parallel is instructive. A commit is an immutable statement of change, a signature binds an identity to a payload, compression and expansion are a reversible encoding pair, and a good commit message is a statement of intent that outlives the person who wrote it. The analogy earns its keep in one direction more than the other: code gives you rigour and durability, and it gives you no authority over the outcome.

What do I actually gain from a paid sigil app compared to a free one?

The honest answer depends on which feature you were going to use. Reduction and drawing are free and have been for decades, and a free tool that exports a transparent file is usually better for practice because you can archive it. Paid apps tend to win on batch handling, on storing your work so you can find it in two years, and on not interrupting you with adverts mid-rendering. If you make one sigil every few weeks, a paper method costs almost nothing and lasts longer.

Is it safe to run a working on a device that is not only mine?

No, and the reason is about other people rather than supernatural risk. A working performed on a shared or borrowed device puts the request into an environment the owner did not agree to, using hardware you do not control, and they have no way of declining. Use your own device, or tell the owner what you are doing and get a clear answer. In eleven weeks of practice that was the single constraint I would not have set for myself if nobody had pointed it out.