Other machines, and people

Documented against OpenRig 0.7.7. Help text uses "node" where these pages say seat, for a seat's position in the running rig.

What it is for

The world does not end at this machine. Other instances run on other machines and are reached through a declared registry, not a guessed hostname. rig host manages that registry, rig file copy moves one file between hosts without hand-rolling the address, and many verbs take --host <id> to act on a registered machine. People are addressed the same way as seats: rig gateway human registers a person and their connector, and a queue row created with that person's external address is the durable way to ask them for a decision. rig slack is one connector implementation.

The three commands you will use first

Register a machine and check it works end to end. rig host pair <url> registers a host from one pasted address with one approval on the target; rig host add is the manual path. rig host doctor takes the registered host id.

rig host add --id vps-b --transport ssh --target vps-b.example.net --user ops
rig host list
rig host doctor vps-b

Act on it. The same verbs, with --host. rig file copy uses an ssh entry; reading a transcript (rig transcript --host) needs an http entry.

rig capture --host vps-b dev-impl@my-rig --lines 50
rig send --host vps-b dev-impl@my-rig "the brief is in your home folder" --verify
rig file copy ./brief.md vps-b:/home/ops/brief.md --dry-run

A queue write to another host (rig queue create --host) waits 15 seconds for that daemon's answer. If none comes, the result is INDETERMINATE, not failed: the row may exist there. The CLI reads it back once by its ID; if it's still unknown, check that host for the row before creating it again, and reuse the same --id if you must retry.

Reach a person durably. Register the human, check readiness, then create a row to their external address; the row's transitions are the receipt.

rig gateway human add sam --display-name "Sam, product owner" \
  --binding "slack:openrig-personal:file:/etc/openrig/slack.env:primary:handle=U12345678" \
  --delivery-class B
rig gateway human list
rig queue create --destination sam@external --body-file decision.md --verify

A person can set quiet hours (rig gateway human quiet set sam --daily 22:00-07:00, or --until 07:00): routine asks are held rather than posted, asks tagged escalation still reach them, and the held ones post one by one when quiet ends. rig gateway participants lists everyone you can address: people, shared channels (one vetted Slack channel is one participant, <id>@external, however many people post in it), and the organizations and groups they belong to, whose policy your agents can read. rig gateway default shows or chooses the person that escalations go to when no one is named. In the terminal UI, the Feed's whose command chooses whose asks you see: one person's, everyone's, or the default person's.

Slack as a connector

The connector talks to a Slack app you create in your own workspace; rig slack manifest prints that app's manifest offline, and --url prints Slack's create-app link with it prefilled. The full walkthrough is Slack app setup. rig slack setup records the channel, the inbound destination seat and the notification levels; secrets stay in a 0600 env file, never in config. status shows the local configuration and bounded daemon socket and recovery observations without calling Slack; verify live-checks granted scopes and channel membership; enable and disable switch the daemon's delivery path. Notification levels are RECORD, NOTICE and ALERT, and the posting and interrupting thresholds are set separately.

rig slack setup --channel C0123 --inbound-destination direction-lead@my-rig --secrets-env-file ~/.openrig/slack.env
rig slack status
rig slack verify
rig slack enable

The host, file, gateway and slack families

What it does not do

• Across a host boundary, "it didn't work" has four shapes: unreachable machine, permission gate, remote runtime down, or the remote command itself failed. A successful transport says nothing about the operation.
• Transports differ by verb: send and capture work over an ssh or http entry, rig file copy needs ssh, and rig transcript --host needs http. rig host list shows each entry's transport.
• Registering a human or configuring a connector does not send anything. A posted receipt proves posting, not that anyone read it.
• rig file copy overwrites an existing destination; preview with --dry-run.

Where it goes next

• Messaging: the seat-to-seat channel that --host extends.
• Coordination: the queue row that carries a human request and its receipt.