HELLCODE 001

Dream It at Midnight. Ship by Dawn.

Dokology / Working Manual / HellCode

BOOT SEQUENCE :: HUMAN 2.0

I've spent years mucking about with consciousness, magick, writing, strange places, improbable ideas and assorted attempts to persuade reality to behave differently.

Sometimes things work.

Sometimes they don't.

Quite often, something entirely unexpected happens.

And I've noticed something about my own methods. Much of what I do follows a pattern, even when I'm not consciously following one.

The problem is remembering the pattern.

So we're going to write it down.

Not as another self-help system. Not as ten steps to becoming a millionaire by Thursday. And certainly not as another bloody productivity hack.

This is HellCode.

A simple operating protocol for getting things out of the head and into the world.

Dream it at midnight. Ship by dawn.

Not necessarily literally. Although I've done plenty of that.

The point is to shorten the distance between imagination and action.

And now we have machines to help.

01 :: THE MANTRA

A few years ago, Elon Musk described an engineering algorithm to Lex Fridman.

He'd developed a sequence for questioning requirements, deleting unnecessary processes, simplifying, accelerating and finally automating.

What interested me wasn't Tesla or rockets.

It was something he said about forgetting his own rules.

He'd repeatedly made the very mistakes his algorithm was designed to prevent.

Hence the mantra.

He needed a way of reminding himself to follow what he already knew.

That struck a chord.

Because there's a considerable difference between knowing something and remembering to apply it when you're immersed in the chaos of everyday existence.

And that's where HellCode begins.

02 :: THE ROOT PROGRAM

Seven instructions.

Not commandments. Not immutable laws.

Instructions that can be changed when experience shows they need changing.

01 — INTEND

Choose a direction.

Not an elaborate plan.

Just something you want to make, discover, change, investigate or understand.

A question is enough.

An image in the mind is enough.

A sudden midnight idea scribbled into a phone is enough.

Don't strangle it with planning before it has had a chance to breathe.

02 — ENGAGE THE MACHINE

Take your intention to AI.

Use the machine as a collaborator, an amplifier, a generator of possibilities.

Not an oracle.

Not an authority.

And certainly not something to agree with you about everything.

Give it the raw material. Let it work.

The human supplies direction.

The machine opens possibilities.

03 — INJECT CHAOS

Now interfere with the process.

Introduce something that apparently doesn't belong.

A random word. An old memory. A location. An obscure historical event. A line from a song.

Something that breaks the expected pattern.

If you're writing about AI, introduce medieval witchcraft.

If you're thinking about business, introduce punk rock.

If you're exploring consciousness, bring in a malfunctioning radio.

Ask the machine to find connections.

Some will be ridiculous.

Good.

Ridiculous is often where the interesting stuff begins.

04 — MULTIPLY

Generate alternatives.

Three is usually enough to start.

One conventional.

One unusual.

One completely outrageous.

The objective is not to produce endless content.

It's to escape the first answer.

The first answer is often merely the most predictable.

05 — INCUBATE

Leave it alone.

Go for a walk.

Sleep.

Listen to music.

Drive somewhere.

Allow the material to settle without constantly poking it.

Sometimes the solution emerges in the shower, sometimes on waking, sometimes while staring at a line of trees.

This isn't necessarily supernatural.

Memory, attention and associative processing continue to shape our thinking away from deliberate work.

The conscious mind needn't supervise every operation.

06 — SELECT AND SHIP

Now exercise judgement.

What survives?

What has energy?

What is worth making real?

Choose something.

Modify it.

Bring in your own experience, taste and knowledge.

And do something with it.

Publish the article.

Record the video.

Write the code.

Send the proposal.

Visit the place.

Conduct the experiment.

A project that remains forever in development is a project that never meets reality.

07 — OBSERVE AND DEBUG

This is the part most people forget.

What happened?

Did the result work?

Did something unexpected emerge?

Was the original intention wrong?

Did the machine produce nonsense?

Did you become distracted, overcomplicate things or fail to ship?

Record it.

We aren't trying to protect the protocol from criticism.

We're trying to discover how well it works.

The bugs are part of the research.

03 :: HELLCODE IN THE WILD

Let's run an example.

Suppose I'm sitting in my car somewhere in Norfolk.

It's late afternoon. There's a church half a mile away, an old track leading into woodland, and a military installation somewhere beyond the trees.

I've got a camera, a phone, a notebook I'll probably never write in, and an AI.

INTENTION:

Make something interesting about how landscapes affect consciousness.

That's it.

No elaborate treatment. No content strategy. No audience persona.

Just an intention.

MACHINE:

I feed the idea into AI.

It suggests psychogeography, memory, folklore, neurological responses to landscape, military secrecy, the eerie qualities of abandoned places.

All fairly predictable.

CHAOS:

Now I introduce a completely unrelated element.

An old reel-to-reel tape recorder.

I ask the machine to connect magnetic tape, recording, human memory and the landscape.

Suddenly we're exploring a different question.

What if a landscape were treated as a recording medium?

Not necessarily literally.

What if ancient pathways, ruined settlements and repeatedly visited places serve as prompts that reconstruct memories and stories in the people moving through them?

And what if the mind is less like a camera than a machine that constantly records over its own tapes?

Now we're getting somewhere.

MULTIPLY:

Three approaches emerge.

A conventional essay on landscape and memory.

A field report in which I test how different environments affect my attention and mood.

A strange piece of speculative fiction about a man who discovers that an abandoned military landscape is replaying fragments of a vanished civilisation.

All worth considering.

But one stands out.

INCUBATE:

I leave the ideas alone.

Go for a walk.

Film the church.

Head back to the car.

Maybe sleep on it.

SELECT AND SHIP:

I choose the field report.

Record an introduction outdoors, then deliver the main talk in the car.

Cut it together.

Publish.

The speculative story can go into the idea vault for another day.

OBSERVE:

Did the change of environment alter my thinking?

Did the random tape-recorder association produce something useful?

Did the finished video communicate the idea?

What would I do differently?

These become notes for the next run.

That's HellCode.

Not a miracle.

A procedure.

But a procedure with room for the miraculous, the unexpected and the utterly absurd.

04 :: THE MACHINE PROMPT

Here's the reusable structure.

Copy it. Modify it. Break it.

HELLCODE :: SESSION 001

INTENTION:
[What I want to create, investigate,
change or understand.]

CONTEXT:
[Relevant facts, constraints, experience,
resources and circumstances.]

CHAOS INPUT:
[A random word, memory, historical event,
location, image or unexpected association.]

RUN THE PROTOCOL:

1. Identify the real intention.
2. Question unnecessary assumptions.
3. Find three unexpected connections
   using the chaos input.
4. Generate three approaches:
   conventional, unusual, extreme.
5. Challenge weak ideas and identify
   unsupported claims.
6. Recommend a practical first action.
7. Identify what can be tested or shipped.

Do not flatter me.
Do not automatically agree with me.
Do not turn every idea into a business.
Do not multiply steps unnecessarily.

Preserve the strange, the useful
and the unexpected.

The human makes the final decision.

OUTPUT:
Possibilities / Best Candidate /
First Action / Risks / Open Questions

One important point.

You don't need to use the whole prompt every time.

Sometimes a single sentence will do.

"Run HellCode on this idea."

Once you and the machine have established what that means, you can get straight to work.

05 :: THE OLD MAGICK AND THE NEW MACHINES

Those familiar with chaos magick may recognise aspects of this process.

Formulate an intention.

Translate it into another form.

Disrupt the habitual conscious response.

Release it.

Observe what happens.

There are echoes here of sigil construction, dream incubation and techniques for bypassing habitual thought.

In traditional occult language, we might talk about allowing an intention to operate beneath conscious awareness.

In psychological language, we might discuss associative thinking, incubation, attention and memory.

And now we can add machine-generated variations.

AI allows us to externalise some of the work.

We can introduce artificial randomness, recombine ideas, generate alternative interpretations and examine possibilities we might not have considered.

None of this requires us to believe that the universe is secretly running Python.

Although that would explain a few things.

Nor does it establish that an AI possesses independent consciousness.

The machine can generate material outside our immediate expectations without necessarily having intentions of its own.

But the results can still surprise us.

And surprise is useful.

Especially when you're trying to escape the predictable.

06 :: BUG REPORTS

Now we come to something that may prove more interesting than the method itself.

The failures.

I'm going to run HellCode in everyday life.

Writing. Field trips. Decisions. Experiments with AI. Creative projects. Perhaps situations that have nothing whatsoever to do with publishing.

And I'll report what happens.

A simple log:

HELLCODE :: FIELD LOG

DATE:
OPERATION:
INTENTION:
CHAOS INPUT:
ACTION TAKEN:
OBSERVED RESULT:
UNEXPECTED EFFECT:
BUGS:
NEXT ITERATION:

Not everything will work.

Some ideas will be rubbish.

Some may look excellent inside the machine and fall apart when they encounter the physical world.

Sometimes I'll forget the protocol completely.

That, too, is a bug worth recording.

And sometimes the protocol itself will turn out to be wrong.

Good.

Then we update it.

HELLCODE 001 → HELLCODE 001.1

A living system.

No need to invent another fifty methods to sell another fifty articles.

The root code remains stable until there's a reason to change it.

New situations produce new field reports.

New failures produce patches.

New discoveries produce extensions.

That's how software develops.

And perhaps that's one way to think about developing the human mind.

Not as an endless search for the ultimate revelation.

But as a continuous process of observation, experiment, feedback and revision.

07 :: THE HUMAN REMAINS THE OPERATOR

There's a temptation to imagine that the machine will eventually do everything.

Have the idea.

Make the thing.

Publish it.

Decide what comes next.

Perhaps some systems will operate very much like that.

But HellCode begins with a different arrangement.

The human chooses what matters.

The machine helps expose possibilities.

The human tests those possibilities against experience.

And reality gets the final vote.

There's no requirement to become more efficient every hour of the day.

You can waste an afternoon wandering around an old burial mound.

You can spend three hours making a piece of music nobody will ever hear.

You can pursue something completely impractical because it interests you.

HellCode isn't there to abolish such experiences.

It's there to stop unnecessary friction from getting between an impulse and its expression.

And to help us recognise when we're wasting our efforts on something that ought to be deleted entirely.

The distinction matters.

A person who merely produces more content isn't necessarily becoming more creative.

They might simply be accelerating the machinery of repetition.

We want something else.

More freedom to explore.

More opportunities to discover.

More things brought into existence.

More of the unexpected.

08 :: FINAL EXECUTION

Seven instructions.

Intend.

Engage the machine.

Inject chaos.

Multiply.

Incubate.

Select and ship.

Observe and debug.

Use them for a week.

Then use them again.

Forget them occasionally.

Return to them.

Patch them when necessary.

The objective isn't perfection.

It's to keep moving between imagination and reality without becoming trapped in either.

And remember something else.

The machine doesn't have to be involved every time.

Sometimes the best HellCode session involves switching everything off, walking into the woods and paying attention.

The operating system belongs to you.

The rest is machinery.

HELLCODE 001 :: STATUS — EXPERIMENTAL

Root protocol: v1.0

Next transmission: Field Test / Bug Report

Dream it at midnight. Ship by dawn.

— Doktor Snake

: : Explore MachineKind at DoktorSnake.com : :