Skip to content

Fleet Dispatch, Plain Version

Superseded. This is the original single-file plain doc, kept for existing links. The maintained, more complete version is plain/OVERVIEW.md — see README.md for the full two-track documentation index.

Fleet Dispatch lets one PC ask the other house PCs to do work. It has two paths now: instant LAN send, and slower OneDrive queue.

  1. You enqueue a job.
  2. Fleet Dispatch signs it with a private key.
  3. The job lands in that PC's OneDrive inbox folder.
  4. The target PC's persistent listener drains the queue.
  5. It checks the signature.
  6. It checks the usage governor.
  7. It runs Claude CLI or PowerShell.
  8. It writes the result back to OneDrive.
  9. You collect results from any PC.

For instant work, fleet-dispatch send signs the job and posts it straight to the target PC's /dispatch listener over the LAN. The listener checks a bearer token and the job signature, refuses relays, blocks replay, checks the governor, runs the command, writes the result to outbox, and returns the result immediately.

flowchart LR
  A[enqueue] --> B[OneDrive inbox]
  B --> C[serve queue drain]
  C --> D[verify HMAC]
  D --> E[governor gate]
  E --> F[execute]
  F --> G[outbox result]
  G --> H[results]

  I[send] --> J[peer /dispatch]
  J --> K[verify bearer + HMAC]
  K --> E

The fleet key never goes in OneDrive. Create it with fleet-dispatch init-key, then copy it to every PC through SSH.

The LAN listener binds only to this PC's LAN IPv4 address and 127.0.0.1. The bootstrap firewall rule allows port 47600 only from LocalSubnet. Anyone with the fleet key can run commands, so protect it like admin access.

If the usage governor says RED or BLACKOUT, normal jobs wait in inbox. Critical jobs still run.