Not AI-first. Not AI-native. AI only.
An operating system whose entire surface is one prompt window, and a mind behind it.
Every system you use today was built for humans first, with AI added on: bolted into the sidebar, folded into the search box, a feature in someone else's ecosystem. number5alive OS is the opposite shape. It is an AI only ecosystem: one open prompt, with a local AI system and a cloud AI system behind it, joined by a governed record — and the human standing between them as the third node, the one who decides.
The structure has a name: the AI interweave. Different intelligences, woven together and kept different on purpose — a local mind in one hand, private, standing on your own floor; a cloud mind in the other, as far ahead as anything on Earth. What crosses between them is messages, never merged state. Each side answers in its own voice, and both answers come back whole, labelled, unblended — for the human to decide on.
Why two minds, and not one bigger one? A single intelligence can't check itself; it can only agree with itself at higher speed. Two different minds can disagree — and the person standing between them gets to hear it. The checking lives in the disagreement.
It would be easy to picture this as two chatbots facing off. That undersells what a seat is. A seat is an ecosystem with an agent standing at its front, and what the OS integrates is the ecosystems, not just the agents.
The home seat is held, in the reference build, by Johnny 5 — and behind him stands his local information harness: reference shelves he checks before he answers (checked knowledge, the physical world, how things are built), several answering modes of his own (one that verifies by agreement and labels its confidence, one fast, one bare, one that deliberately explores the edges), his records and rules, and the gates every change to him must pass before it ships. When the home seat speaks, all of that speaks with it.
The cloud seat is held, in the reference build, by Alex, a moderator — and behind the moderator stands a bench. The Robot Factory, which builds: frontier models passing an artifact through drafting and critique rounds, under written caps. S.A.I.N.T. (System for Aligned Intelligence and Negotiated Truth), which decides: the same caliber of minds convened to deliberate and produce a decision record, dissent included. And beyond those two rooms, as many global AI resources as a question earns — specialists, instruments, services — delegated to like a symphony: each plays the part it is best at, on the conductor's cue, and the whole performance is written to the score.
So the weave is wider than it first looks: two ecosystems, each with its own resources, memory, and rules, meeting at one prompt — crossings governed, generations kept whole, and the human commissioning the performance and deciding what it means.
"Wouldn't you like to be a Pepper too?"
The installation begins with this question. Yes is the first entry in the record. No leaves the machine untouched.
A Pepper is the opposite of a prepper. The prepper prepares against the future: stockpile, withdraw, fortify, survive what's coming by hiding from it. A Pepper decides the other way — stands fully with AI in both hands and steps into the void expecting technology to build the bridge to get across. The full founding note is in the repository: The Pepper Movement.
number5alive OS is being built in the open, ground-up, in the number5alive-os repository. The contracts are law; the build follows them phase by phase, with pass marks written before each phase runs. The laboratory where its ideas are proven first is Number 5 Alive — Johnny 5, the home half, is live there today.
The code is free to use: AGPLv3 for the core, Apache 2.0 for separable libraries. The names — number5alive OS, and Pepper — are not granted by the code license. A fork may take the code; it may not take the identity.