Work / AI infrastructure · flagship
The Sin Fleet
One intelligence spread across seven machines. Each runs its own agent with its own job, and they coordinate over a private network while I get one clean report.
- Role
- Architect, operator, owner
- Status
- Live
- Year
- 2026
- Link
- Private
The problem
Running real businesses on real servers means backups, monitoring, deploys and a hundred small chores. A single chatbot can't hold that. A pile of cron jobs can't explain itself when something breaks.
What I built
Sin (Symbiotic Intelligence Nexus) is a fleet of AI agents, one per machine, each with a defined role: a Raspberry Pi 5 control plane that owns schedules and alarms, a 40-thread workstation for local inference and builds, a hot replica, a restic vault that only verifies, an expendable host that runs restore drills, a read-only sentinel on production, and a laptop cockpit.
The agents talk to each other directly over a private Tailscale network. Only the hub talks to me. A shared working folder syncs to every machine and is versioned in git, and one source of truth for agent configuration renders each machine's rules, so drift gets reported instead of lingering.
The rule the whole fleet is built on: a backup is not a backup until it has been restored. Every drill extracts a real snapshot on a separate host, counts files and bytes, hashes a sample against live production and opens the databases.
Proof, not adjectives
- Production snapshot of 40,282 files (2.365 GiB) restored on a drill host in 10 seconds.
- 25 files hash-checked against live production: 0 mismatches.
- Both Postgres databases opened and queried from the restore, one with 65 tables.
- A second copy of the vault passes restic check on separate hardware.
- 4,177 files and 736 agent skills backed up across nine agent homes.
Read more
The full story of the first production restore drill, and the two traps it caught that a normal backup report would have hidden.