Orbtech

This started off as a thought experiment about a technology programmed in the dream world. Once a need for a physical focus came though, I recalled a meme that's currently trending, and… my mind couldn't help but ponder. Don’t take things written here as gospel, it’s just me making up wild ideas as I go. If I ever write again about Orbtech, I could change any of these details.

Yes, this meme inspired the article partially. Cover art of Middle-Earth Quest: A Spy In Isengard, illustrated by Angus Mcbride.

Take some quartz and start polishing it until it's nice and round. Keep going until you can practically see through it. Once that's the case, dip the creation in the dragon blood for 24 hours. It must be the only orb dipped in the dragon blood, if there are multiple this process won’t work. The less blood you use the better, because after using it this way the blood is drained of its magic. If you've done all the steps correctly, you should have a dream orb. Though since any other orbs are way less important, by now it is simply called orb.

Orbs are special devices because at a glance they lack any visible signs of internal logic, and yet they can change their appearance and roll around, even reacting to outside inputs. In actuality, there's a complex code written inside of the orb, accessible through a highly unusual method - dreaming. If one falls asleep while touching the orb, they'll enter the orb's dreamscape. It's a world of dreams, shaped by the person who dreamed in it first after the orb's dragon blood bath. The simplest way to use orbs is for message delivery. Although impractical, since these messages can only be delivered in one’s sleep, the messages require no programming and they can target any of the senses. You can completely overhaul the dreamscape of an orb by dipping it in dragon blood for 24 hours.

Those who dream within the orb and search for the code will find it. It takes the form of a large lattice of strings with vertices that can be knotted at the crossings, or not. One can walk through this lattice only interacting with it when they want to. Depending on these knots, the orb gets its programming, which then manifests outside. I don’t feel like coming up with the exact logic behind these is all that important, so that’s where my specifics of the programming language itself will end.

If you wish to take inputs from the outside world, you must cut one of the strings, create the input within the orb’s dreamscape, and tie the thing to it. Since it’s rather difficult to imagine smells or temperatures, the vast majority of orbs take visual inputs. Maybe in the future, I’ll even figure out a way for the orbs to record and produce sounds. There are two more inputs: the last direction in which it has rolled, and the current direction it would fall in (in one word each, “front” and “down”).

The orbs have two major outputs: Images, and rolling. Through complicated knot schemes, you can project any image that you can code or that the orb can record on its surface. The image is projected onto the orb always the same way front and down. As for rolling, the orb can move on its own, and as it does it changes which way its “front” is. Maybe there could be a way to make the orbs fly, but right now the idea is too raw for me to figure out how exactly.

I don't know where is this from, but it's a lovely animation.

If you search long enough, you’ll find the orb itself within the dreamscape. If you tie a knot around it and attach it to some configuration of knots, it will record its surroundings. It’s a standard to program these orbs to reveal their recordings by waving your hands over them for a couple of seconds, though you could also watch them in the dreamscape.

The more an orb is used, the smaller it gets. When it becomes as small as a marble, it becomes incapable of giving outputs. It can still receive inputs, which is why these orbs can be useful as security camera replacements - tiny enough to be unnoticeable, and useless for most other things. At some point after that, the orb becomes too tiny to even record, or let anyone into its dreamscape. Due to this shrinkage, many people work on maximizing the work time they get out of a single block of quartz. Is it better to create a myriad of small orbs, or one big orb and then sculpt orbs out of the remainders?

If you fall asleep touching multiple orbs at the same time, you’ll enter a random one. However, through doing this you will entangle the orbs - each of these orbs will contain within its dreamscape copies of other orbs, through which they can exchange information. Changes made to one orb will manifest in the copies inside of all other orbs entangled with it.

A cracked orb brings bad luck. It has a harder time rolling, its image is disrupted, maybe even its function goes wrong. Maybe something worse happens if an orb cracks while you’re in its dreamscape. Handling the orbs without cracking them is an art form.

For now, the system is way too simple to be useful for actually evolving a fantasy setting into a true cyberpunk one. But who knows, maybe in time I’ll figure out ways to add more things into it.

David Bowie, from The Dark Crystal