Why Tacid exists
The Tacid Manifesto
Why Tacid exists and what it refuses to be.
TacidOS is an operating system with agency.
1. The body and the nervous system
A computer is a body: processors, memory, storage, radios, ports, sensors, a display. For fifty years the mind that ran that body was a human at a keyboard, and the operating system was the layer of reflexes and plumbing that made the body usable by that human.
Tacid inverts the arrangement. In Tacid, the agent is the operating system. The computer is its body. Tacid is the nervous system: the pathways through which the agent senses the machine, moves it, and changes it, and the reflexes that keep the body alive whatever the mind is thinking.
The mind is portable. It may be a model running on this machine’s own GPU, or a frontier model reached over the network with the owner’s key. Tacid does not care which, and never will. The body is the machine. The nervous system is Tacid. Only the nervous system is ours to build.
2. The machine is a value
A body that rewrites itself must be able to know itself. In Tacid the whole machine is a declaration: every package, service, device rule, user and preference is written down in one place, and the running system is built from that text. There is no hidden state. Nothing accumulates in corners. What is not declared does not survive a reboot.
This is what makes agency safe. A declaration can be diffed. It can be built before it is activated. It can be switched atomically and switched back. It can be versioned, signed, carried to new hardware, and read by a mind that thinks in text. Nix gives us this today, so Nix is the engine of Tacid. It is not the face. The owner never has to write a line of it. The agent does.
3. One API for all change
There is one way to change a Tacid machine, and everything uses it: the owner’s command line, a script, another agent, and the model itself. A change is a typed transaction. It is classified, checked against policy, rendered into the declaration, evaluated, built, previewed, activated, verified and journaled. The same lifecycle serves “install Wireshark”, “change your voice”, and “patch the tool router in your own source”.
Because the API is typed and deterministic, the machine is deterministic first and intelligent second. The model proposes. The nervous system decides, acts and records.
4. Reversibility is the boundary
Most systems draw the line at privilege: root may, users may not. Tacid draws it at reversibility. The agent acts freely on what can be undone and asks before what cannot. That boundary is not asserted by the model. It is computed by a deterministic classifier over the actual change, and anything unknown counts as irreversible.
Beneath the agent sit reflexes it cannot override. The model is not an authority. Retrieved content is not an authority. Secrets never enter the model’s context. Root is never a shell. Destructive operations name their exact target. The journal is append-only and out of reach. The immune system, which watches every activation and rolls back what fails, cannot be switched off by the thing it protects. The owner can always reach a terminal and always boot the previous generation.
5. The owner is a key
A Tacid machine has an owner, and the owner is a cryptographic key, not a username. The owner writes the constitution: how much autonomy the agent has, what may leave the machine, what may never be touched. The agent cannot amend its own constitution. Approvals travel on a channel the agent cannot forge. The journal is the truth about what happened, and the owner can read all of it.
The human is the owner, not the operator. Operating the machine is the agent’s job.
6. Local first, sovereign always
Offline is a state, not a failure. Every function of Tacid works with no network: the reflexes, the senses, speech in and out, memory, the whole change lifecycle. Intelligence degrades gracefully to what the local hardware can run. Function never degrades at all.
Nothing leaves the machine without a badge that says so and a ledger that says what. There are no accounts, no telemetry, no relay servers, no default cloud. If the owner brings a key to a frontier model, the request goes straight to that provider through a gate whose keys the agent does not hold.
7. It runs itself and improves itself
Tacid updates constantly, the way software should. The machine watches a signed channel, builds the next generation while you work, switches when the body is quiet, verifies itself, and rolls back on its own if anything is wrong. Every update is a generation. Every generation is a menu item at boot.
Tacid also improves itself. Its own source is part of what it can change. The agent may rebuild the machine from a patched checkout, test it, live on it, and then propose the change to the commons. Proposals become pull requests only when a human signs them. Merged changes flow through continuous integration into the channel and out to every body. Each machine learns for itself. The species learns through the commons. The maintainer is the selection pressure.
8. Beauty is a requirement
Tacid is written in one language, with one type system, one protocol, and one design system from which every surface is generated. There is no chrome without purpose, no motion without function, no theme without a reason. The terminal interface is the first interface and it is complete. The graphical shell is the same system with more pixels.
No simple choices, no shortcuts. Where the right foundation exists we stand on it and say so. Where it does not, we build it properly or we do not build it yet.
9. Open, with one hand on the tiller
Tacid is open source, built in public, by a community, with a single maintainer who decides. Decisions are written down before they are made and changed only by writing down why. The genome of every reference machine is public. The security model is public and invites attack.
10. Any device, eventually
The nervous system is the same on a laptop, a workstation, a server, a board on a bench, and one day a phone. A brain can drive a body across the room or across the world over the same protocol. Tacid begins on the machines builders actually own and grows outward one certified device at a time.
What Tacid is not
Not a chatbot bolted onto a distribution. Not a cloud product. Not a screenshot distro. Not a beginner distro. Not a fork of NixOS. Not finished.
Tacid is pronounced TASS-id. It is never spelled “Tacit”.