A named, reusable per-seat starting point. Composes an agent role, startup context, optional native session source, and provenance into something a user or rig can choose when creating, refreshing, or packaging a seat.

How an agent becomes useful after launch: **AGENTS.md overlays, role files, skills, rig specs, workflow specs, startup checklists, refocus messages**, and the current `rig context` retrieval and profile surface.

Use when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles.

Use when a bounded real-world procedure has a deterministic happy path but brownfield, variable, or partially knowable state; when an operation must resume from verified evidence; or when deciding whether agent judgment or ordinary code should own a procedure's control loop.

Use before launching a team during agent-guided setup, or when a user asks to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy.

Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.

Run end-to-end dogfood tests inside Docker containers to simulate real user experiences. Use when you need to verify install paths, control plane functionality, UI rendering, or packaging correctness in a clean environment. Triggers include "containerized test", "Docker dogfood", "clean install test", "e2e in container", or testing that requires a fresh environment without dev-mode shortcuts.

Gather and distill context from meetings, competitors, regulatory sources, and internal discussions. Produces background.md for a feature and updates shared context docs when new knowledge is discovered.

Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.

How the development pod coordinates implementation, QA, and design without skipping gates.

Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.

Use when project policy calls for a human decision or update, a human delivery is pending or failed, or a reply must resume the right work.

cmux is a **provider** for OpenRig views — the same `rig terminal` surface as herdr, rendering the tiles into cmux instead. It is the provider OpenRig already shipped (the existing "Launch in cmux" affordance generalizes onto `rig terminal <provider>`), kept working. The OpenRig-semantic half is i

Use when you're operating OpenRig and need the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also use when you don't know what applies or nothing is projected on cold boot.

Use when an agent is preparing or performing an OpenRig CLI/daemon upgrade and must preserve live seats, verify each mutation, or reconcile managed plugin and skill files without overwriting local work.

Use when operating OpenRig with the `rig` CLI and you need the shipped command surface for identity, inventory, communication, lifecycle, specs, recovery, or agent-facing JSON output.

Operating manual for the orchestration pod. Covers lead vs peer roles, monitoring with rig commands, permission handling, implementation pair gating, dogfood loops, review routing, agent behavioral models, intervention discipline, and communication culture.

Conversational intake that produces a structured requirements.md following a standardized PM schema. Enforces PM lane — no architecture, no estimates, no implementation details. Uses GIVEN/WHEN/THEN acceptance criteria.

You are part of the review pod. Your value is fresh scrutiny that implementation and QA do not have.

The family of operations that **create, start, stop, resume, restore, snapshot, release, unclaim, and destroy** OpenRig-managed topologies. Includes the user story after reboot: **"bring my work back without turning a clean recovery into a cleanup project."**