# (moved) primary-host runbook

This file used to contain the deployment runbook for one specific primary host —
its hostname, addresses, user, service wiring and rollback steps.

**That content now lives in a private repository**, because a host inventory is
operator data for one deployment, not part of the toolkit. This repository is
public and keeps only host-agnostic *mechanism*.

What lives where:

| Content | Home |
|---|---|
| How to expose a palace over HTTP, and the Host/Origin pin | `docs/phase-1-exposure-runbook.md` (here) |
| Why a palace needs a special backup, and how to restore one | `docs/backup-and-recovery.md` (here) |
| Unit/timer/plist templates | `contrib/` (here) |
| Which machine is primary, its addresses, users, tunnels, offsite target | private fleet repository |
| Per-host feeder device names and schedules | private fleet repository |

If you are looking for the mechanism, the two runbooks above are the same
procedures with `<PRIMARY_HOST>` and `<USER>` in place of one site's specifics.