Individual skill
seat-continuity-and-handover
Use when replacing a seat's occupant (rebuild/handover/swap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire/advise/shadow), or recording provenance for an occupant change. Two independent outcomes (continuityOutcome + seatBindingOutcome) and the 5 failure modes that prevent silent dishonesty.
packages/daemon/assets/plugins/openrig-core/skills/seat-continuity-and-handover/SKILL.md
Source commit 344815052870e4b1be2486350ba52a8d1c6afeb2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 8,776
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-harness Repository topic
- agent-orchestration Repository topic
- agent-skills Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- cli Repository topic
- codex-cli Repository topic
- multi-agent Repository topic
- tmux Repository topic
- typescript Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 11,228 bytesSKILL.mdcore · 11,228 bytesSKILL.mdcore · 11,228 bytesSKILL.mdcore · 11,228 bytesSKILL.mdcore · 11,228 bytesreferences/apprentice-evidence-toolkit.mddoc · 1,619 bytesreferences/apprentice-successor-seat-cutover.mddoc · 11,198 bytesreferences/orchestrator-role.mddoc · 2,237 bytes
Read excerpt
# Seat Continuity and Handover
A pair of primitive families that separate *who is sitting in a seat* from
*what the seat itself is*:
1. **Occupant-creation primitives** — `resume`, `fork`, `rebuild`, `fresh` — produce a candidate new occupant. Answer: "where did the new occupant come from?"
2. **Seat-binding operations** — handover binds a candidate occupant into the topology. Answer: "what happened to the stable seat identity?" Inspect the current CLI for executable operations; design vocabulary alone does not establish a command.
Core architectural decision: **stable seat identity, fluid occupant
identity, explicit provenance.** Do not encode successive occupants into live
seat names. Keep the stable address and record lineage separately.
## Use this when