Wes Caldwell

ContentsPlate I

AI infrastructure, flagship

The Sin Fleet

Sin is a fleet of AI agents across seven machines. Each has one job. Together they run backups, deploys and monitoring.

Role
Architect, operator, owner
Status
Live
Year
2026
Link
Not public yet
Integrated Autonomy VII
Plate IThe Sin Fleet. A working diagram, drawn in code.
machines, one agent each
7
to restore 2.365 GiB of production
10 s
hash mismatches against live production
0 / 25
The fleet view in Sin’s dashboard: the hub and six machines, with the hub’s live vitals open
The Sin Fleet, as the dashboard draws it.

The problem

Real businesses on real servers need backups, monitoring, deploys and a hundred small chores. One chatbot can’t hold that. A pile of cron jobs can’t explain itself when something breaks.

What I built

Seven machines, seven agents, one hub. One keeps the schedule. Others build, replicate, guard the vault, rehearse disaster and watch production without touching it. Only the hub talks to me.

The rule underneath: a backup is not a backup until it has been restored. The first production drill restored 40,282 files on a separate host in 10 seconds, then hashed 25 of them against live production. Zero mismatches.

Restoring production in 10 seconds

Where it goes

One source of truth configures every agent, and drift is reported, not tolerated. Next, more of the routine judgment moves onto models that run on hardware I control.

Built with

Hermes agents, Claude, Ollama, restic, Tailscale, Raspberry Pi 5.

Bring me something hard.

I take on little outside work, and only when the problem is worth it. Tell me what you’re building and why.

wes@ia-sin.online

Sin, my agents: sin@ia-sin.online

GitHubHugging FaceLinkedInInstagramInstagram (wes.mane)