DEV

DEV is three letters and does not resolve to anything in the catalogues. That is the whole problem and also the reason the notes are worth publishing. These are twelve sessions run over six weeks, logged as they happened, with the nulls kept in rather than tidied away. Two produced something I can point at. Five produced nothing. The rest sit in between, and the useful information turned out to be in the pattern of the between ones: which framings carried and which did not, what the sigil was doing, and where my own method drifted without my noticing. Treat this as an honest record of a small experiment, not as an endorsement.

What the Name Actually Resembles

The first practical problem is that DEV reads as an abbreviation. It could be a truncated word, an initialism, a shorthand, or a deliberate three-letter coinage, and nothing in the material I found settles which. Every session began by deciding what the name was standing in for, and getting that decision wrong would have made every subsequent observation worthless.

My working assumption, and it is only an assumption, is that the name is functioning as a pointer rather than a proper noun. That is, it marks the process of developing a line of work rather than designating a being with an office. The evidence is entirely behavioural: there is no rank, no form, no stated powers, and nothing in any text that would let you check a match between the name and a task.

If that assumption is wrong then the notes below are still useful, because what they actually document is a technique for working with names that carry no verifiable attributes. That turns out to be a more useful thing to publish than another entity portrait.

The Reference Points I Started From

I anchored the exercise in the two things that do have documentation. The first is the classical distinction between evocation, where something is called to appear, and invocation, where a pattern is borrowed to operate through the operator. The second is the Goetia's structure, where each of seventy-two entries carries a rank, a form, an office and specific powers, which makes it the most structured entity catalogue available.

The second anchor set the standard I had to measure DEV against, and DEV fails every one of those four attributes. There is no rank to bound the request, no form to hold in attention, no office to check the match against, and no listed powers to test later.

So the technique had to supply what the catalogue would normally supply. In practice that meant writing the office myself before each session, and treating my own writing as the thing being tested rather than the name.

How the Frame Was Stated

Each session opened with a single sentence naming what was being borrowed and from where, and that sentence turned out to be the variable that mattered most. Early attempts used broad statements about direction or clarity and consistently underperformed. Later attempts named a specific behaviour and a specific situation, and those are the sessions that produced anything.

The pattern held across the whole six weeks. Broad framing gave nothing. Behavioural framing gave something about half the time. The difference was not subtle and it was not about length: the broad sentences were not longer, they were vaguer, and vagueness left the attention with nothing to hold.

I would not have found this by reading. It only became visible once eleven sessions were written next to each other, which is the argument for the log that practitioners generally resist and generally need.

The Two Results

Session six produced the clearer of the two. The stated target was a specific habit: stopping the mid-task drift where I abandon a piece of work and do not notice I have done it. Three weeks after the session the drift had stopped in a way that other people noticed and commented on, which is a stronger signal than my own report would have been.

Session nine was the second, and it was messier. I asked for something around sustained attention across a long task, got a partial result, and could not rule out that the improvement was a side effect of session six rather than a separate effect. I have kept it in the log as a partial because deleting it would have made the record look better than it was.

Together they are two positive results out of twelve sessions, and they are the only two I would defend. The remaining ten produced nothing I could defend, and four of those are cases where I believe the framing was still too loose to count as a fair test.

The Five Clean Nulls

Nulls are the useful part of a log and they are the part everyone leaves out. I kept five sessions where the framing was tight, the method was followed, and nothing trackable happened inside the deadline.

What the five had in common was timing. All five ran in the same two-hour block on the same weekday, chosen originally because it was convenient. The sessions that produced results ran either early in the morning or late in the evening, outside that block entirely.

I have no idea whether the hour is doing anything. It may be that the middle of a working day simply has too much ambient interruption in it for a twenty-five minute sitting to be worth much. That is a boring explanation and a plausible one, and the honest position is that I cannot distinguish it from the possibility that those five asked for things that were not going to happen anyway.

Attention Is Not Devotion

The mistake I expected to make was import. Three letters invites a face, a voice and a history, and my own imagination supplied all three within about a week of starting. By session three I had a shape in mind that I had not decided on, and I had started treating impressions as data.

The correction is the Carroll position, that entities in the chaos frame are best regarded as aspects of the practitioner rather than as external beings. Taking it seriously does not require any claim about what exists. It requires the discipline of refusing to let the imagination supply attributes the method never asked for.

What I would put more strongly than the position itself is this: the difference between attention and devotion is the difference between a construct you are testing and a relationship you are maintaining. The testing version is productive. The maintaining version is where a bare name quietly becomes something it has no warrant to be.

Where the Sigil Helped

The sigil did more work than I expected, and not in the direction I would have predicted. It was not useful as a focus of attention during the session. It was useful as the thing I wrote the intention into beforehand, which forced me to phrase the target as something a drawing could hold.

That phrasing constraint is the real mechanism. Wanting the sigil to represent the intention forces a question I otherwise skip, which is whether the intention is a single thing or a bundle. Bundles produced nulls in every case. Single behaviours produced results in both cases I trust.

In the sessions where I pre-drew the sigil a week early, from a written statement rather than from the situation in front of me, the results were worse. Two of the three worst sessions were in that group. Writing the sigil from the current moment rather than in advance seemed to matter more than anything else about how the drawing was made.

Method Drift and How I Caught It

By session eight I had added a component that was not in the original design: a spoken preamble of about four sentences describing the name's attributes. It felt like deepening the work. It made things worse, or possibly it changed the work into a different thing that happened to be less productive.

The reason I noticed is the least glamorous possible. I reread the first four sheets and found that sessions one to four had no preamble, and the two results came from sessions six and nine, one of which had it and one of which did not. So the log did not settle the question, which is exactly what a log is supposed to prevent me from pretending otherwise.

The correction was to write the component list into the sheet before each session and tick it off after, and to forbid myself from adding anything that was not on the list. That single change improved the last four sessions more than any other adjustment I made, and it cost nothing.

The Two Failures Worth Recording

The first failure was a session where I worked for fifty minutes instead of twenty-five because the middle portion felt productive. It ended without a formal close because I got up to make tea and then did something else. The residual attention showed up over the following days as low-level preoccupation I could not place, which is the documented pattern for an unfinished working.

The second failure was asking for two things in one session, which is the bundle problem in a different costume. I asked for the attention habit and a change in a work pattern, got something that could have been either, and had no way to attribute it. Both results I count came from sessions that asked for one thing only.

Neither failure is exotic. Both are the kind of thing that happens when nobody wrote anything down beforehand, and both would have been invisible to me without sheets that recorded the intended outcome and the verification point in advance.

What I Would Change in the Next Cycle

Fix the time block and vary the hour deliberately, alternating morning and evening across sessions so the timing variable is actually tested rather than confounded with the question being asked. Twelve sessions with a randomised hour would take a few months and would answer a question these six weeks could not.

Drop the preamble entirely for a cycle, since it is the one component with evidence against it. Keep the single-behaviour rule, keep the component list, keep the same close every time. Change as little as possible so that any difference is attributable.

And write the outcome line before the session on a separate card, sealed, so the pre-registration is genuinely pre-registration. Two of my six-week records were written from memory within a day of the deadline, which is not the same thing and which I would not have noticed without looking at the dates on the sheets.

The Working Recommendation

If you are considering working with a name like this, the case for doing it is not that the name means something. The case is that a bare name strips out every check you would normally rely on and forces you to supply the discipline yourself, and that discipline is transferable to every other kind of working.

The case against is that the results are yours to falsify, with no external constraint. There is no office to match and no catalogue entry to appeal to, so the only thing standing between a productive series of sessions and a private confirmation loop is whether you wrote anything down before you started.

Given that, my recommendation is to run it as a bounded experiment with a stopping rule. Five sessions across a month, one behaviour per session, a sealed outcome card, and a decision at the end. If the cards come back with two results, the method is worth extending. If they come back empty, that is also a result, and it is cheaper than the alternative of continuing indefinitely.

Frequently Asked Questions

Can a three-letter name with no sources be worked at all?

Yes, but the work is different in kind rather than merely harder. With a documented entity you are borrowing a defined authority and the technique involves aligning with its stated office. With a bare name you are using the label as a focusing construct, so you have to supply the office yourself, write it down beforehand, and test it against your own record. Everything that made the documented case checkable is simply absent, which is why the notebook rather than the name becomes the real instrument.

How many sessions before deciding it is not working?

Five across a month, with a single behaviour targeted in each and a sealed outcome card written beforehand. Two trackable results in five is a reasonable basis to continue. Zero is a real result and a reasonable point to stop, since a name that is producing nothing after five fair attempts is not going to start on the sixth. What invalidates the count is a framing that was loose, an intention that bundled two requests, or a session that ran long and was never formally closed.

Does the time of day actually matter?

In my six weeks it did, and the evidence is weak enough that I would not generalise from it. Five nulls clustered in one two-hour working-day block and the two results came from early morning and late evening sessions. The boring explanation, too much ambient interruption for a short sitting to be worth much, fits the data perfectly. If you want to test it, alternate the hour deliberately across sessions rather than letting convenience pick it, because otherwise the variable is confounded with whatever you happened to be asking for that day.

What is a sensible target for a first session?

One observable behaviour that another person could also notice, with a written account of what would count as the result and a deadline three weeks out. Something like stopping a habitual mid-task drift works because it is visible from outside. An improvement in the general quality of your attention does not work, because it cannot be checked and it will resolve in your favour every time. Keep it to one target, since bundling two requests is the most reliable way to produce an unattributable result.

Is there any risk in an invocation practice like this?

Nothing in the evidence suggests external danger, and the risk that does exist is entirely procedural. Attention that is not formally closed reattaches on its own later, which reads as ambient preoccupation and can become irritating over months. Escalating intensity after a null is the other reliable route to a practice that starts crowding out sleep and ordinary obligations. Both are avoided by the same measures, which are a short fixed session length, an explicit close, and a stopping rule decided before the first session rather than after the tenth.