Glossary

Artifact

A packaged rig — a single .rig.tgz file produced by rig pack. Contains the manifest plus the files the manifest's [package].include patterns matched.

Author

The publisher identifier under which a rig is registered. author/name is the canonical reference. On the Hub, the author must match the authenticated user.

Binding

The relay-side record that ties a workspace to a collaboration. Created by rig share --enable. Identified by a binding ID (bnd_…). Has an owner, devices, invites, and a change-event log.

Change event

Per-file change record stored in the relay log. write, edit, or delete. Powers rig history and rig restore.

Check

An entry in rig doctor --json checks[]. Each check has a kind (dir, env, tool, mcp, plugin, permissions, collab), a status, and optionally a remediation.

Collab (collaboration)

The shared-rig mode. Opted into by adding [sync] to rig.toml. Powered by tapd and the relay.

Daemon (`tapd`)

The local sync process for shared rigs. One per workspace per machine. Watches the FS, pushes/pulls change events. Managed by rig resume / rig pause / rig status.

Device

A per-machine credential within a binding. Stored at .rig/tap-binding.local.json (mode 0600). Revoking a device disconnects that one machine.

Doctor

The rig doctor command — observes workspace state, emits checks and gaps. rig doctor --json is the canonical machine-readable contract; see Doctor JSON contract.

Gap

A required check that failed. Subset of checks[] where required: true and ok: false. Drives the repair workflow.

Hub

The community registry at userig.xyz. Default source for rig hub use hub:….

Include / exclude

Glob lists in [package] that control which files go into the artifact.

Instance

A particular install of a rig. Recorded at .rig/instance.toml — captures where the rig came from (source.ref), what version, when installed, where on the filesystem.

Invite

A one- or multi-use URL that lets a collaborator join a binding. Issued by rig share — a member invite (--role editor|viewer) or a role-less capability invite (--ops …).

Manifest

rig.toml at the workspace root. The source of truth for what the rig needs and what gets shared. See Manifest reference.

MCP

Model Context Protocol — the standard rig uses for tool servers. Declared in [mcp] and configured in .mcp.json.

Rig

A folder containing a rig.toml plus everything the agent needs. The thing you install, build, publish, or share.

Registry

A place rigs live. Three flavours: Hub, GitHub releases, local file registry.

Relay

The coordinator service for sync. Hosted at https://tap-relay.fly.dev by default. Sees paths and hashes; does not see plaintext content at rest. See How collab works.

Remediation

The structured fix for a gap. Has action (human description) and sometimes command (literal shell to run).

Runtime

The agent runtime a rig targets. Set in [rig].runtime. Currently only "claude-code".

Skill (agent skill)

Markdown file at .claude/skills/<name>/SKILL.md that teaches Claude Code about a workspace. Rig writes a user-level and a project-level skill.

Source specifier

The argument to rig use. Forms: hub:, github:, ./path.rig.tgz, registry:. See Source specifiers.

The sync system that powers the rig workspace verbs. tapd is the daemon; the relay is the coordinator. You interact with it through rig share / rig status / rig resume; you don't drive it directly.

Workspace

A folder on disk. Becomes a rig workspace when it has a rig.toml.