Across machines

You do not need this page for one machine. Run the loop, the supervisor, the serve daemon and the drawer on one host, bind the daemon to 127.0.0.1, and everything on this site reads as written. This page is for the day the pieces are split across two machines: it names the two roles, the private network between them, and the port convention.

Two roles, one private network. The writer host runs the loops, the supervisors and the serve daemons for its targets and holds their stores. The operator seat is where tickets are written and filed, main is pushed from, and the drawer lives. They talk over a private network (a Tailscale tailnet, a VPN, a LAN you trust) and nothing else. The code never references that network; it appears only in the address given to --serve and in the URLs in the drawer's config.

flowchart LR
  subgraph seat[Operator seat]
    DR[drawer]
    OP[ssh · git · --file-ticket]
  end
  subgraph writer[Writer host]
    L[loops] --- ST[(stores)]
    S[supervisors] --- ST
    D[serve daemons\n7710, 7711 …] --- ST
  end
  subgraph internet[Public internet, outbound only]
    LIN[Linear]
    CDX[Codex backend]
    GH[origin]
  end
  DR -- HTTP, private network --> D
  OP -- ssh, private network --> writer
  L -. HTTPS .-> LIN
  L -. from the review container .-> CDX
  OP -. push .-> GH

What listens where

Surface	Bound to	Reachable by	Authentication
serve daemons	the host's private-network address, one port per target from 7710	every member of that network	none; membership is the boundary
ssh	the host	the private network (and whatever else the host allows)	keys
loop, supervisor, stores	local processes and files	the host only	filesystem
Linear, Codex, origin	outbound only	n/a	API key, Codex login, deploy key

The daemon has no authentication on purpose. Bind it to the private network's address and never to the wildcard address (all interfaces); there is no flag that narrows an open bind back. On a personal network that is the whole access control, and it is documented so nobody adds a token in a hurry later.

Standing daemons

deploy/holophyte-serve@.service is a systemd user unit template, one instance per target slug, reading ~/.holophyte/SLUG/serve.env for the target path, the bind address and the port. On the writer host the bind address is its private-network address rather than 127.0.0.1. Enable lingering once per host so the user manager starts at boot; then systemctl --user enable --now holophyte-serve@SLUG. The unit restarts on failure and is restarted by hand after a merge that touches the daemon's code. Details in Serving standing.

The drawer

contrib/swiftbar/holophyte.10s.py runs under SwiftBar on the operator seat, a Mac. Its config, ~/.holophyte/drawer.toml, names one daemon per target; HOST is the writer host's name or address on the private network:

linear = "https://linear.app/your-workspace/project/…"

[[daemon]]
name = "holophyte"
url = "http://HOST:7710"

[[daemon]]
name = "lotuspod"
url = "http://HOST:7711"

SwiftBar runs plugins with a bare PATH, so the plugin folder holds a one-line wrapper that calls a Python 3.11+ explicitly. The glyph is the two-leaf mark as an 18 pt template PDF when idle and a white-on-outline variant with a green, amber or red dot when something is working, needs attention, or is unreachable; the variant is one design for both menu-bar tints, because macOS tints the bar from the wallpaper and no signal says which.

Adding a writer host

Federation is more nodes: install the factory on another machine of the private network, give each target there a [board] table and a serve unit on the next free port, and add a [[daemon]] block per target to the drawer's config. No hub, no relay, no shared store. Two hosts must never write the same store; one target is served by exactly one host.

Where a tailnet could carry more

• MagicDNS names in drawer.toml instead of raw addresses.
• An ACL tag on writer hosts limiting the daemon ports to the operator seat, so a guest node or a phone cannot read run identifiers without a grant.
• tailscale serve in front of a daemon the day it gains a write endpoint: it terminates TLS and adds identity headers, which is per-user auth with no secret in the repository.

None of these are needed today. The board, the reviewer's model and the git remote stay on the public internet by design; pulling them onto the private network would make the factory depend on a network to do work it can do from anywhere with a key.