Struct OperatorInfo 

pub struct OperatorInfo {
    pub kind: OperatorKind,
    pub id: String,
    pub senior_bridge: Option<Arc<dyn SeniorBridge>>,
    pub spawn_hook: Option<Arc<dyn SpawnHook>>,
}

The bundle of Operator faces the engine injects into Ctx at dispatch.

The two Arc<dyn ...> fields — the Operator faces that intercept

Conceptually the Operator is one role, but inside the engine it fans out into interception axes that fire independently. The canonical use is one external Operator (say, a WebSocket client) that implements the traits and answers every axis from a single session (see a WebSocket-backed operator session in the server crate).

field	trait	firing layer	purpose
senior_bridge	SeniorBridge	SeniorEscalationMiddleware	When a worker returns ok = false, query a judgment source and upgrade the outcome to Pass.
spawn_hook	SpawnHook	MainAIMiddleware	Pre- and post-spawn observation and approve/reject gating (kind = MainAi / Composite only).

There used to be a third, operator: Option<Arc<dyn crate::operator::Operator>>, resolved from LaunchEnvelope.operator_backend_id and read by OperatorDelegateMiddleware to bypass the spawn entirely. Both are gone. It is worth being precise about what that does not mean: dispatching through an Operator is alive and well — it simply happens on the AgentSpec axis now, where OperatorSpawner holds the Arc<dyn Operator> for the agent’s declared seat. What went is the second, session-global way of reaching one, which resolved its destination from the launch record instead of the Run’s seat and so could not follow a handover. A dispatch’s operator is no longer something the Ctx carries.

The role of kind

Middleware uses OperatorKind (Automate / MainAi / Composite) as a gating signal: MainAi / Composite enable spawn_hook; Automate lets middleware pass through into a normal spawn. senior_bridge is kind-agnostic and fires whenever ok = false.

Default

OperatorKind::Automate with both Arc<dyn ...> fields set to None. Middleware passes through; execution stays inline as usual.

Persistence boundary

OperatorInfo is transient inside Ctx (#[serde(skip)]). The persisted LaunchEnvelope only holds IDs (bridge_id / hook_id / operator_backend_id). At dispatch time the engine resolves each Arc by looking those IDs up in its senior_bridges / spawn_hooks HashMaps via resolve_operator_info(session) -> OperatorInfo. operator_backend_id no longer resolves to anything here — it survives as the persisted session shape and as the launch-time key Engine::list_operator_ids validates an operator_sid against.

Fields

kind: OperatorKind

Gating signal consumed by middleware; see the “role of kind” section above.

id: String

Identifier of the attached Operator/session (LaunchEnvelope.operator_id).

senior_bridge: Option<Arc<dyn SeniorBridge>>

See the senior_bridge row in the table above.

spawn_hook: Option<Arc<dyn SpawnHook>>

See the spawn_hook row in the table above.

Trait Implementations

impl Clone for OperatorInfo

fn clone(&self) -> OperatorInfo

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for OperatorInfo

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for OperatorInfo

fn default() -> Self

Returns the “default value” for a type.