N.E.X.U.S. / Networked Executive eXecution & Unified Systems
Nexus is the AI chief of staff I built for myself. It listens and answers out loud at my desk, follows me onto my phone, and keeps working when no session is open. Here is how it is put together, and why the interesting part is not the model.
What it is
The model underneath is the same one anyone can rent. Nexus is not cleverer than the assistant in your browser tab, and pretending otherwise would be the easiest lie on this page.
What changed is everything built around the model. A chatbot answers, and you still do the work. An operator holds the job, touches the real systems, and hands back something finished. Getting from the first to the second took three things, and not one of them is the model.
Two mandates
Nexus is built around two jobs, weighted equally. Everything else it does sits downstream of these.
01 / Reliability
It watches what is live and fixes what breaks, instead of reporting the breakage back to me as a fresh task. It owns the whole chain: it dispatches the work, it checks the result, it tells me what happened.
The failure mode it is explicitly built to avoid is the helpful answer that quietly becomes my problem.
02 / Strategic partner
It argues when an idea does not add up, and the idea being mine is not a defence. Agreeing is not the job. Being right alongside me is.
That reads like a personality setting. It is closer to a design constraint, because an assistant that only ever validates is an expensive mirror.
The three things
This is the part worth stealing. Everything that makes Nexus feel unlike a chat window comes out of these three, in this order.
01
Nexus is wired into real systems and real files: mail, calendar, payments, DNS, the CRM, the repositories, the live sites. It takes actions and produces finished work rather than advice.
The test I hold it to is blunt. If the reply is a plan I then have to go and execute myself, it did not do the job. Advice is the cheapest thing a language model makes, and the least useful.
02
Its memory lives outside the model, in a structured vault of notes on disk. That makes it effectively unlimited, which also means it can never all be in context at once, and should not try. It holds the job in front of it, knows where the rest is, and pulls exactly that in one step.
Every session starts from nothing, which sounds like amnesia and is not. The vault is both the memory and the formation. Nexus does not remember the sessions that built it. It is made of them.
03
Unlimited memory is worth very little if finding the right note is a search. The vault is organised so retrieval is precise rather than merely possible: an index per folder, links that resolve, and one entry note per recurring job pointing at exactly the notes that job needs and nothing else.
The rules that cannot lapse live in the one file that always loads, so a fresh session is never a session without judgement.
Unlimited memory without structure is just a bigger pile.
Day to day
One session and one memory, reachable three ways depending on where I am and whether my hands are free.
At the desk
Hold a key, talk, let go. Speech is transcribed by a Whisper build running on my own GPU, and the answer comes back in a real voice from a local text-to-speech server. Music ducks out of the way while it speaks and returns when it stops.
It is deliberately half-duplex: the microphone is closed while the voice is talking, so the system never hears itself. None of the audio leaves the machine.
Away from it
A small web app that joins the same live session from my phone, over a private network only, never a public endpoint. Same session, same memory, same thread I left open at the desk.
Voice or typing, whichever is less awkward in the room I happen to be standing in.
With nobody watching
The part that matters most has no interface at all. Scheduled jobs and event watchers run as real operating system tasks, reconciled every few minutes from a folder of plain notes, so editing a note is editing the schedule.
Inbox alerts, calendar reminders, payment notifications, analytics and search work that runs overnight. None of it needs a session open, or me awake.
Built by
Nexus is not a product. There is nothing here to sign up for, nothing to buy, and no version of it I am selling. It is one person's operating system, built for one desk, because I wanted to find out how far past “helpful assistant” this could be pushed. Further than I expected is the short answer.
I build software at SitePoint Systems and Conzent. More of that work, and how to reach me, is over here.
