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. The async execution context seals and schedules on exit. instructions() rebuilds one replaceable instruction block. Host-owned activate() scopes attribution; it is not a model-facing permission API.

On this page

Execution, Invocation.

Execution

One pinned filesystem and identity. It is never a process-global router. Source declaration

Constructor

Fields and properties

Methods

Build one replaceable block of filesystem instructions and active memory.
Captures rule changes as a proposal against the pinned base revision and checkpoints the execution. It does not accept or publish the proposed rule.
Host-controlled phase scope. Reflection cannot attribute itself as task.

Invocation

Generic host integration. The host retains its model, tools and agent loop. Source declaration Construct with the fields below as arguments. Defaults apply when omitted.

Fields and properties


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