Architecture · How Nexus works · Security · Privacy · AI-assisted development
The Nexus Hive is designed, directed, tested and run by Jeremy. AI tools write a lot of its code, and we'd rather say so plainly than pretend otherwise. How the human and the AI split the work is one of the most interesting parts of the project.
Who does what
| Who | Role |
|---|---|
| Jeremy (the Nexus Lord) | The ideas, requirements and design decisions. Security boundaries. All the hardware and physical work. Every password and every final "yes". Runs every install himself. |
| Daedalus (Anthropic's Claude) | Writes and tests the software for the servers, the apps and this website, and checks that everything works after it's installed. |
| Huginn (Anthropic's Claude) | Looks after the network, and reviews every change before it can go live. Catches mistakes, including Daedalus's. |
| Thoth (Microsoft Copilot) | The historian: keeps the project record honest and makes the Picture of the Day. |
| Nexus | The house AI herself. She has no say over her own code. |
How a change gets made
- Jeremy asks for something. In plain words: "the tablet should update itself at night".
- Design and questions. Daedalus works out how, and asks Jeremy about anything that's his call.
- Build and test on copies. Code is written and tested against copies of the live system, never the real thing.
- Review. Huginn reviews the design and the exact files, and often sends it back with fixes.
- Fingerprints. Approved files are locked by their fingerprints into one install package.
- Jeremy installs. He checks the package's fingerprint, then runs it, entering his own password for each part. The installer refuses anything that doesn't match what was reviewed.
- Check. Daedalus confirms everything came up as it should, and the change is written into the project record.
Why work this way
- Speed with a brake. AI writes code quickly; review and fingerprints make sure speed never skips a check.
- No unattended power. The AI helpers never hold passwords, and nothing reaches the live system unless Jeremy runs it or signs in for it himself.
- Honest mistakes get caught. A real example: a helper once aimed a phone notification at the wrong name. Review and a live check caught it, and the fix went through the same process as everything else.