Skip to main content
An execution pins rule state, working files, trace attribution, and a unique identity. Obtain it from the runtime’s execution or trial factory. An execution is single-use; do not manually switch its role to bypass validation assignment. An Invocation is the generic host callback input. Its current instructions include the filesystem contract and active memory. During reflection, the callback also receives feedback and the prior result. Deliver instructions to the actual model, and expose only Reflect filesystem administration during reflection. Ending a task execution seals changes and schedules evaluation; it does not itself invoke a continuation. Use the runtime’s explicit continuation for delayed feedback. Accepted rules, trial candidates, active session notes, and native framework conversation history are separate state. Use await reflect.execution(options, callback) so cleanup is paired with the callback. The invocation carries an AbortSignal; propagate it through your host loop. Cancellation is cooperative. The underlying Execution lifecycle methods support advanced hosts, but ordinary callers should use runtime factories.

On this page

Execution, ExecutionOptions, Invocation, Phase.

Execution

Source declaration

Constructor

Fields and properties

Methods

Persists the execution’s working snapshot. The runtime normally owns this checkpoint; persistence does not publish accepted guidance.
Captures rule changes as a proposal against the pinned base revision and checkpoints the execution. It does not accept or publish the proposed rule.
Static method on Execution.

ExecutionOptions

Source declaration

Fields and properties

Invocation

Type parameters: I = unknown, R = unknown. Source declaration

Constructor

Fields and properties

Phase

Source declaration

Signatures and fields are generated from the SDK source. See the import index for available entry points.