| name | session-adapter-governance |
| description | Partial Skill: invoke by name only — the SessionAdapter conformance rule: a mutating op verifies its observable effect landed or fails loud, keyed on the op's effect class. Loaded by CRs and producers touching adapter operations. Not triggered by users directly. |
| user-invocable | false |
Session Adapter Governance
The ratified design rule for every SessionAdapter mutating operation — a call that drives the
multiplexer to change peer/session state (send, submit, focus, the nudge composite, the
clear injection, the mail-delivery doorbell). Ratified from doctrine entry 2 (drafted off the
cr150 nudge boot-race; ADR-0025 records the promotion):
A mutating operation must verify its observable effect actually took hold before reporting
success, and fail loud rather than report false success when it cannot. Never fire-and-forget.
Precedent: the cr150 boot-race — unit nudge was one atomic text+Enter send that reported success
regardless of whether the booting harness consumed the Enter, so the peer sat idle while the caller
believed it started. The fix (submit-then-verify-then-retry, throw on the cap) is the reference
pattern below. A mutating op implemented as a single send with no read-back is non-conformant:
it reports success it never observed.
Scope
- Bound: every op that changes session state, and every composite that reports success to a
caller. The verification duty sits on the composite — a raw primitive (, ) used
a conformant verify loop is not itself required to verify; a raw primitive that alone
backs a success report makes that op non-conformant.
