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
Constructor
Fields and properties
Methods
instructions
instructions
Build one replaceable block of filesystem instructions and active memory.
seal
seal
Captures rule changes as a proposal against the pinned base revision and checkpoints the execution. It does not accept or publish the proposed rule.
activate
activate
Host-controlled phase scope. Reflection cannot attribute itself as task.
Invocation
Fields and properties
Signatures and fields are generated from the SDK source. See the import index for available entry points.

