# workpc herdr TCP bridges

These files are intentionally local and gitignored. The workpc herdr exposes
one local Unix socket; Orchestra reaches it over the LAN through three bound
TCP bridges:

| machine | listen | herdr socket |
|---|---|---|
| workpc | 192.168.1.105:9245 | ~/.config/herdr/herdr.sock |

The bridge is a byte-preserving proxy for the newline-delimited JSON protocol.
It does not interpret or authenticate requests; restrict the ports with the
LAN firewall/WireGuard policy.

## Not a federation worker

`herdr-bridge` deliberately does **not** own a checkout. It cannot write
`TASK.md`, inspect Git `HEAD`/branch/dirty hashes, make a scratch commit, or
publish a canonical continuity handoff. Treat it as Design A compatibility
only, not the cross-machine protocol described by Orchestra's spec.

`cmd/orchestra-worker` is the worker-side client. It registers and
heartbeats as the configured herdr id, consumes only router-issued
`TaskLeased` events for that id, creates/validates the local checkout, drives
the local herdr, and seals/pushes a canonical handoff locally before calling
the federation handoff endpoint. It deliberately has no task-claim operation:
homesrv's router is the only scheduler.

Install `deploy/orchestra-worker.service` on the worker host and configure
the federation variables in `deploy/orchestra.env.example`. Set
`ORCHESTRA_MACHINE_ID` on homesrv; that prevents its coordinator from ever
opening, validating, rotating, or cleaning up a workpc checkout.