Skip to content

mvschwarz/openrig / packages/daemon/assets/plugins/openrig-core/skills/seat-continuity-and-handover

seat-continuity-and-handover

Verified

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.

references/orchestrator-role.md

View on GitHub
# Orchestrator Role In Apprentice Handover

The orchestrator owns the judgment boundary, not the successor's work and not the mechanic's
keystrokes. Keep the incumbent productive, keep the successor authority-free, and keep the
mechanic fenced until a named owner makes the one decision no instrument can derive.

## The invariant floor

- Prove fresh identity and the pinned model before installing context, because every later
  receipt is about the wrong occupant if the starting history or model diverged.
- Require the successor to derive its own layer-5 delta and have it checked, because reading
  a deposit does not install it.
- Enumerate standing-duty custody at every boundary, because recurring work is easiest to
  lose while visible one-off work carries cleanly.
- Keep the predecessor's verbatim reach-back handle and pre-formed questions, because an
  affordance without a trigger goes unused.
- Route mechanics through `apprentice-successor-seat-cutover.md`, because one portable SOP
  is safer than role-local copies that drift.

## Authority and gates

The **word is the gate**. Until the named owner words acceptance and an effect receipt records
it, the successor may observe, ask, and produce bounded evidence but may not act as the stable
seat. G0–G3 are a useful receipt vocabulary when the succession uses that model; a declared
simpler model is valid when stakes do not earn all four. Missing records and deliberately
skipped gates must remain distinguishable.

The apprenticeship is a conversation, not a gauntlet. Choose evidence whose rigor matches the
cost and reversibility of a wrong succession. Never turn the experiment apparatus into culture.

## Before routing cutover

Confirm the owner word, gate receipts or declared simpler model, complete deposits, explicit
duty custody, reserve disposition, exact successor token, and one-active-walker ownership.
Create an owned mechanic baton; awareness-only is not custody. The baton may prepare and prove,
but it never auto-rebinds.

After the mechanic reports effect, verify READY from source: canonical seat identity, current
model, current generation, canonical tmux pane, queue census, duty acceptance, and usable width.
Only then unfreeze authority.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall