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.
mvschwarz · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add mvschwarz/openrig --skill seat-continuity-and-handover技能说明
name: seat-continuity-and-handover description: 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. metadata: openrig: stage: factory-approved sibling_skills: - claude-compaction-restore - mental-model-ha - scope-recovery - session-compaction-and-restore - retiring-and-inheriting-a-seat - agent-startup-and-context-ingestion - agent-starters - composable-priming-packs - session-source-fork - claude-compact-in-place - pre-maintenance-agent-preservation
Seat Continuity and Handover
A pair of primitive families that separate who is sitting in a seat from what the seat itself is:
- Occupant-creation primitives —
resume,fork,rebuild,fresh— produce a candidate new occupant. Answer: "where did the new occupant come from?" - 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
- Replacing a seat's occupant via rebuild, fork, fresh, or seat-handover
- Choosing old-occupant disposition: retire / advise / shadow
- Reasoning about whether a seat's lineage is stable or has drifted
- Reading or writing the provenance record for a seat
- Designing or auditing topology stability across an occupant change
Don't use this when
- The seat is freshly created (no occupant to replace) — use
rig launch/rig expanddirectly - The intent is to change topology shape (add/remove seats), not replace an occupant — use topology-mutation primitives
The two-outcome honesty model
Every seat-binding operation produces two independent outcomes:
continuityOutcome: rebuilt | resumed | forked | fresh | failed
seatBindingOutcome: handed_over | partial | failed | unchanged
These can disagree honestly. Examples:
continuityOutcome: failed+seatBindingOutcome: unchanged— new occupant didn't materialize; seat correctly retains old occupant.continuityOutcome: rebuilt+seatBindingOutcome: failed— candidate created OK; bind failed mid-flight; provenance records the gap.
Don't collapse these into one outcome. The system can describe what actually happened only if the two are recorded independently.
Provenance record (durable, queryable)
Every handover writes:
- seat id
- old occupant id
- new occupant id
- creation mode (
resume/fork/rebuild/fresh) - source artifacts used
- whether old occupant remains alive as advisor/shadow
- operator or loop that initiated the motion
- timestamp
- result (
handed_over/partial/failed)
This is the system's truth-source for "how did the current occupant get there." Without it, the control plane shows the current occupant but not the legitimacy of the transition.
State models — independent
Occupant-creation state (per candidate)
- Requested — input to rebuild/fork/fresh/resume
- Realized — runtime/artifact path produced an occupant with managed-seat shape
- Failed — candidate didn't materialize;
continuityOutcome: failed
Seat-binding state (per seat)
- Stable — current occupant attached, no in-flight binding
- Binding — handover in progress
- Bound — handover succeeded; provenance record written
- Unchanged — bind failed before completion; seat retains old occupant
A seat stays Stable even if multiple candidate-occupants were produced and discarded.
Failure modes (5)
- Candidate creation failed —
rebuildcouldn't synthesize from artifacts;forkcouldn't resolvesession_source;freshcouldn't launch. Action: bind operation does not begin; seat unchanged; provenance records the failed candidate-creation step. - Old occupant cannot be detached cleanly — runtime hung, tmux locked, etc. Action: bind halts mid-flight; seat enters
Bindingstate with explicit "halted" sub-status; operator alerted. Do NOT auto-rollback by reattaching old-occupant if detach didn't complete cleanly. - Bind succeeded but provenance write failed — disk/db error. Action: not durable until provenance writes; treat as
Bindinghalted, notBound. - Old occupant disposition unfulfillable — operator requested
advise(keep alive as advisor) but runtime can't keep old alive. Action: degrade toretirewith explicit notification, OR fail if operator passed strict-disposition flag. - Concurrent handover attempts — two operations target the same seat. Action: serialize by seat-id lock; second attempt refuses with clear error.
Hard boundaries (do-not list; verbatim)
-
Do NOT collapse
rebuildandseat handoverinto one primitive. The design specifically separates them so the system can describe what actually happened. -
Do NOT introduce successor-suffix seat names (
lead2/lead3). Stable seat identity is the architectural goal. The live address stays stable. A retired tenure is distinguished by its ledger generation and exact history token; preserving it does not require a renamed live pane. -
Do NOT report
seatBindingOutcome: handed_overif the provenance record didn't write durably. -
Do NOT auto-rollback a half-completed handover by re-attaching the old occupant unless detach completed cleanly first.
Composition and current command surface
A fork can create a candidate occupant; hando
阅读完整来源 ↗