Steward Transfer Protocol
The documented process by which an outgoing Steward's undocumented judgment calls, exception history, and informal heuristics are captured and verified before departure — distinct from the Operational Ledger, which captures routine operational history but not necessarily the reasoning behind non-routine calls made from experience rather than a documented rule.
The Steward Transfer Protocol addresses a succession event structurally different from ordinary staff turnover. In a traditional team, a departing employee's knowledge is partially redundant with colleagues who absorb the gap. In the Stewardship Model, there is no team beneath the Steward to absorb anything — there is the Steward, the Agent Council governing routine T2 decisions, and whatever has been formally documented in the Operational Ledger. Anything the outgoing Steward knew that never made it into that formal record leaves with them, in full, on their last day.
The specific gap the protocol closes is the distance between recorded decisions and recorded reasoning. The Operational Ledger is a strong record of what happened; it is a weaker record of why a specific judgment call was made the way it was, particularly for genuinely novel, ambiguous cases resolved through accumulated experience rather than an already-documented rule. If the outgoing Steward is a Bridge Operator specifically, the transfer risk is sharper still, because the integrative judgment that profile carries is precisely the kind of tacit pattern-recognition that resists full encoding.
The protocol's three components — structured exit interview, defined overlap window, and explicit profile assessment — are all more useful specified in advance than assembled during an actual departure under time pressure, and the strongest version runs continuously rather than only at the point of departure, converting a single compressed handoff into an incrementally maintained record.
Application
The protocol has three components: a structured exit interview in which the outgoing Steward narrates the judgment behind the Operational Ledger's most significant non-routine exceptions; a defined overlap window in which the incoming Steward shadows the outgoing one specifically to observe novel-case handling; and an explicit assessment of whether the business's current stage still requires a Bridge Operator profile in the incoming Steward, or whether a strong generalist can now fill the role.
Context
Key-Man Risk's existing architectural remedy — the Stewardship Model and Agentic Core documenting operational knowledge into a reusable system — addresses ongoing dependency correctly but not the specific succession event. The Stewardship Model's efficiency comes from concentrating oversight in one generalist rather than a team, which means there is no redundant layer to absorb a departure the way a traditional company's leadership bench would. Some of what a good Steward knows was never fully encodable — it is judgment, accumulated through handling enough novel cases to develop consistent instinct, which the Operational Ledger records the outcomes of but not necessarily the reasoning behind.
This term is machine-readable
Any MCP-compatible AI assistant can retrieve the canonical definition of Steward Transfer Protocol at inference time — no training approximation.
First used: July 2026
Edition 1 · updated July 2026