Omarchy spirit
Keyboard first. Thoughtful defaults. A desktop that feels considered — and remains yours to reshape.
Explore OmarchyThere will be blood.
The Omakase/Omacom Ethos. Rednode P2P Runtime Desktop Environment.
An experimental NixOS Distribution
01 / HIROTHE OS BEFORE THE STREET
THE SUBSTRATE
Before the Metaverse,
there was the machine
that could run it.
Hiro Protagonist helped write the Metaverse and lives in a storage unit. Last of the freelance hackers. He owns almost nothing, and what he owns is entirely his — the code, the blades, the last word.
He did not start by building a world. He started by building a machine that would answer to him and to no one else — configuration readable end to end, agents that remained guests, keys that never left the hardware.
The Metaverse was the visible layer. OMAKA was the substrate.
He still carries both. The swords are the reminder that some problems are settled at the edge of a blade. The code is the reminder that the more important battles are settled underneath — in the layer that decides who may act, who holds the identity, and who gets the last word when the agent and the human disagree.
Hiro owns almost nothing.
What he owns, he owns completely.
- In the book
- He built a machine that would answer to him alone.
- In Rednode
- Readable end to end. Agents stay guests. Keys never leave the hardware.
02 / JUANITA · THE IDEA
A machine that
answers to you,
and nobody else.
- In the book
- She wrote the code that made avatars human, then refused to use the room she had furnished.
- In Rednode
- Identity lives on your machine. Nothing about you is lent back to you.
Hiro and Juanita did not begin with the Street. They began with an operating system — explicit, local, and stubbornly under the user’s word. The human was the final authority; the agent was a guest. Only once that foundation existed did the Metaverse become possible.
OMAKA is that earlier layer. The OS before the Street.
Juanita Marquez saw what the Metaverse did to people before anyone would say it out loud, and refused to enter it on those terms. She wrote the code that made avatars human, then would not use the room she had furnished. Her objection was never the technology. It was the arrangement.
Something else is using your computer now. Agents read your files, run your commands, reach the network for you. A fine thing to want, and a dangerous thing to rent.
OMAKA is built for both operators.
The human
Keeps the keys, the identity, and the last word.
The agent
Gets a system it can reason about — every part of it written down.
NixOS is the readable foundation. Rednode is the sovereign, local-first runtime. A considered starting point; nothing welded shut.
03 / Y.T. · THE INGREDIENTSCYPHERPUNKS WANTED
Malleable with
Sensible Defaults
A modern OS for the Humagentic Age
and Sovereign Operator.
Y.T. is a Kourier. She owns none of the roads and moves through all of them, harpooning whatever is going her way — franchise borders are somebody else's problem. She carries a board, good judgement, and no loyalty to any system.
- In the book
- A Kourier owns none of the roads and still moves through all of them.
- In Rednode
- Peer-to-peer transport — no server in the middle deciding who may reach whom.
NixOS foundation
A system described in configuration. Repeatable setups, deliberate changes, a way back when you need one.
Explore NixOSRednode heart
A sovereign, local-first P2P runtime for personal apps, identity, and peer connections on your machine.
Where we are04 / RIFE / ENZO · THE ARRANGEMENTWHOSE WORD HOLDS
Someone always
owns the pipe.
The question was never who owns it.
It is what happens to you when they do.
L. Bob Rife
Control the infrastructure.
Own what passes through it.
Uncle Enzo
A promise has weight.
His word holds because he keeps it.
A rented agent runs on somebody’s silicon, under somebody’s terms. It answers to a party you have never met. That is the arrangement.
The keys stay on the machine.
The machine is yours.
- In the book
- Rife owned the fiber. Enzo's word held because he kept it.
- In Rednode
- Authority is signed and local, not lent by a party you have never met.
05 / RAVENRAW CAPABILITY
NO PERMISSION SURFACE
The sword answers
only to itself.
Raven does not ask the system for permission. He arrives armed, moving, and already outside the polite contract.
He is capability without governance. A private nation on two wheels.
No admin panel. No appeal process. No explanation owed.
There is a lesson in that, and it is not comfort. Sovereignty without memory, restraint, or obligation stops being sovereignty. It becomes weather — impossible to negotiate with, dangerous to ignore.
Hiro has the swords, and someone to answer to.
That is the entire difference.
- In the book
- Armed, moving, and already outside the polite contract.
- In Rednode
- Capability without policy is the thing Rednode refuses. Absent authority fails closed.
06 / NGDESIGNED COMPETENCE
Ng does not waste motion. The body is not the interface. The chair is not a limitation. The machine is not an accessory.
Everything around him has been designed until it obeys.
Sensors. Weapons. Cameras. Movement. Command.
No romance, no mysticism. Architecture made exact enough to become force.
OMAKA wants that competence. A system should not flatter you with possibility while hiding the path; it should make the real controls visible and exact.
Capability is not escaping constraint.
It is knowing it well enough to design with it.
- In the book
- Everything around him has been designed until it obeys.
- In Rednode
- Explicit configuration. Constraints are declared and readable, never hidden in a default.
CONTROL MADE EXACT
The machine
is part of the mind.
07 / NAM-SHUB OF ENKIDEFENSE AS LANGUAGE
THE COUNTERMEASURE SPEAKS
When the virus
is linguistic.
The countermeasure is language. Not a bigger wall. Not a stronger lock. Not a louder command.
A phrase. A structure. A pattern.
Something that changes what the infection is allowed to mean.
The Nam-shub of Enki is defense beneath the level of tools: the grammar of the attack rewritten before it can finish naming you.
That is the system OMAKA wants to be. Readable enough to inspect. Explicit enough to repair. Strange enough to resist the spells other machines cast.
The cure has to be a sentence.
- In the book
- A phrase that changes what the infection is allowed to mean.
- In Rednode
- Policy as data. What a process may do is stated in advance, and checked before it acts.
08 / THE LIBRARIANIT HAS READ EVERYTHING THAT HAPPENED
RECEIPTS, NOT WISHES
It remembers
what actually happened.
In Rednode it takes the form of a ledger, and the ledger is the whole of it.
Ledger — Rednode
- entries
- what was said, signed, done
- writes
- immutable, local-first
- order
- kept
- recall
- complete
- agenda
- none
Handed back on request.
Hiro asks. It retrieves, cites, and stops. A record of what happened, in a world of agents willing to rewrite your files and your memory.
Everything else here is an argument.
This one is a record.
The Librarian is a daemon, not a mind. Stephenson is explicit that it is not an intelligence, and that is the point.
09 / REDCLAWSMALL BOT. BIG CLAW.
Redclaw is the only figure here not on loan from Snow Crash. The others are borrowed to make a point; this one we had to build.
A master of its domain
Nothing inside Rednode is closed to it.
A servant to you
Every capability was handed to you, and can be taken back.
YOUR NATIVE SIDEKICK
Small bot.
Big claw.
Hiro has the swords.
Y.T. has the board.
You get the claws.
Other agents can be written, summoned, or discarded inside Rednode. Redclaw is native — there at first boot, not installed later, not rented from someone else's silicon.
A shell with a mind of its own, running under your word.
Taking shape with OMAKA- In the book
- The only figure on this page we did not borrow.
- In Rednode
- The native agent. Capabilities are granted by the operator, and revocable.
10 / FIDO · TAKING SHAPEIN DEVELOPMENT
Blood, sweat, and configuration
OMAKA is being built as a complete, opinionated NixOS system with Rednode as its native runtime. The first public ISO is not yet linked here.
Shipped
- A working design for how human and agent share the machine, without the agent owning it
- An explicit configuration model, so every part of the system can be read and changed
- Redclaw and the Librarian running under local control
Not yet
- A public download link
- An installer aimed at first-time users
The ISO goes here when it can be judged on its own terms.
Fido is a Rat Thing: a dying pit bull, armoured and isotope-powered, bound to a territory he cannot leave. When Y.T. is in danger he crosses it anyway. Constraints are real. They are not always final.
Don't get redholed.
OMAKA and Rednode by Redstar Systems
LEGAL NOTICE & TRIBUTE DISCLAIMER: This project (omaka.red) is a non-commercial, open-source experimental software platform and a creative tribute to the work of Neal Stephenson. Snow Crash, its characters (including Y.T., Uncle Enzo, and L. Bob Rife), and its associated concepts are the sole intellectual property of Neal Stephenson and his publishers. This project is entirely independent and is not affiliated with, endorsed by, sponsored by, or associated with the author, Darhansoff & Verrill Literary Agents, or any corporate rights holders. No copyright or trademark infringement is intended.