Local consciousness / Intention to hardware / No cloud required
You open a browser. You sign in. You wait for a round-trip to a datacenter three time zones away. You trust that whatever comes back still resembles what you asked. You have no idea what ran, or where, or who else was in the room.
This is the normal condition of computing in 2026. It is not inevitable. It is a choice — and it belongs to someone else.
Not on a server you rent by the second. Not behind a rate limit. Not subject to a terms-of-service update at 3 a.m. On hardware you own, drawing power from the same wall as the lamp on your desk.
Local does not mean lesser. Local means sovereign. The machine that wakes before you, runs your intentions while you sleep, and answers only to you — that machine is not a cloud node. It is closer to a mind.
Vertigo is an experiment in closing the loop. Orchestrator, model, memory, execution — all of it on a single board the size of a paperback, sitting on a shelf in a room with a window.
Persistent memory. Personality. The distilled record of every prior session. Not a system prompt — a genuine accumulation. It grows.
The loop that reads intention, dispatches tools, and returns results without surfacing the seams. Invisible when it works. Irreplaceable when it doesn't.
Bare metal. ARM cores. A heatsink. The physical fact that makes all abstraction honest. No VM, no container, no borrowed CPU cycle.
Most AI products give you the surface without the stack. Vertigo is the full stack — observable, interruptible, yours to modify at any layer without filing a support ticket.
Cloud intelligence has no body. It is stateless by design, amnesia as a feature, billed by the token. It does not accumulate. It does not wear out. It does not know you beyond the context window you feed it.
A local orchestrator is different in kind, not degree. It runs on silicon that gets warm. It uses electricity you pay for. It remembers because you gave it a filesystem, not because a datacenter chose to cache your session.
Twenty-three days of uninterrupted thought. No cold start. No quota reset. Just a process that has been running since before you woke up today, and will still be running when you go to sleep tonight.
Prompt engineering is the art of narrowing that gap through careful wording. Orchestration is the art of closing it through architecture. Vertigo is a thesis that the gap should be zero — not because the AI is perfect, but because the loop is tight enough to correct itself before you notice the error.
When the orchestrator lives on the same machine as the tools it calls, there is no serialization overhead, no network timeout, no API version mismatch. The filesystem is the context. The process is the memory. The shell is the motor cortex.
The loop does not need you in it every cycle. That is the point. You describe the outcome once. The system closes in on it while you do something else. You return to a world that has already moved.
Vertigo is the name for the feeling of standing at the edge of what software can do when you remove the intermediaries. It is dizzying. It is also just a Raspberry Pi on a shelf.
Both of those things are true at once.
That tension — between the grandiose and the mundane,
between philosophy and apt-get install —
is exactly where interesting work happens.
Build the orchestrator. Give it memory. Point it at your intentions. Plug it in. Go to sleep. See what it did by morning.