rig expand / rig shrink / rig launch / rig remove / rig discover / rig bind / rig adopt / rig attach. Covers the 4 failure modes (newly created seat lacks queue/startup/role; edges and permissions not updated; adopt/bind succeeds at tmux but not OpenRig identity; shrink/remove leaves stale topology references) and the rule that mutation must work while the rig is active, not just in clean fixtures.\nmetadata:\ncli_surfaces_referenced:\n- adopt\n- attach\n- bind\n- discover\n- expand\n- launch\n- ps\n- release\n- remove\n- shrink\n- unclaim\n- up\n- whoami\nopenrig:\nstage: factory-approved\nsibling_skills:\n- rig-lifecycle\n- seat-scaling-and-specialization\n- cross-host-rig-commands\n- sidecar-operator\n- rig-bundles-and-shareable-artifacts\n- specification-system\n- extension-and-user-workspaceThe ability to change a rig while it is alive: expand, shrink,\nlaunch, remove, discover, bind, adopt, and attach seats or sessions.\nSeat management includes the stable identifiers, edges, roles, and\nstartup context that make those mutations coherent.
\nOpenRig should be easy to reach for. A user should be able to add\ncapacity, retire capacity, adopt an existing session, or attach a\nterminal without rebuilding the whole topology. If mutation is\nrarely tested, users avoid it and the product collapses back into\nstatic launch scripts.
\nrig expand <rig> <pod-fragment-path>)rig shrink / rig remove)rig launch)rig bind)rig adopt)rig attach --self)rig up (lifecycle, not mutation)seat-scaling-and-specialization skillseat-continuity-and-handover skillrig whoami doesn't know about it; downstream consumers see partial state.Proof must cover mutation while a rig is active, not just in a\nclean test fixture. The useful matrix:
\n| Operation | \nWhat to verify | \n
|---|---|
| Add seat | \nNew seat has queue, startup context, role; rig whoami resolves it | \n
| Remove seat | \nStale references cleaned; edges/permissions updated | \n
| Adopt existing session | \ntmux session bound at OpenRig identity layer; rig whoami reports correctly | \n
| Attach observer terminal | \nExternal CLI attachment recorded | \n
| Verify topology projections after each move | \nrig ps --nodes reflects current truth, not pre-mutation cache | \n
A clean-fixture proof is necessary but not sufficient. Live-rig proof\ncatches the failure modes that fixture-mode misses.
\nThe current coordination experiments repeatedly need new queues,\nwatchdogs, humans, and test seats — which makes this family\nstrategically important. Seat continuity work will eventually\nseparate stable seat identity from runtime occupant identity (see\nseat-continuity-and-handover).
Per cli-reference.md v0.2.0:
rig expand <rig-id> <pod-fragment-path> (with optional session_source)rig shrink <rigId> <podRef>rig launch <rigId> <nodeRef>rig remove <rigId> <nodeRef>rig discover [--draft]rig bind <discoveredId> --rig <rigId> (--node <id> | --pod <ns> --member <name>)rig adopt <path> --bind <logicalId=tmuxSessionOrDiscoveryId>rig attach --self --rig <rigId> --node <logicalId>rig unclaim <sessionRef> / rig release <rigId>The 2026-04-30 topology mutation add-seat proof pass is active.\nProduct Lab shaped it; planner authored IMPLEMENTATION.md; driver\nlanded the smallest honest CLI retry-guidance patch for failed\nrig expand recovery. Remaining proof is the Section B disposable-rig\nruntime matrix, blocked on operator posture and owned by\norch-lead@your-rig.
openrig-user skill — CLI surface for rig expand / shrink / launch / remove / bind / adopt / attachseat-scaling-and-specialization skill — when to add specialized capacity vs genericseat-continuity-and-handover skill — replacing an occupant on a stable seat (different shape than topology mutation)cross-host-rig-commands skill — cross-host topology mutation (deferred)