Repository navigation
Extension-point question: external handoff acknowledgments in resumed workflows #10347
Replies: 1 comment
|
For Python Put a serializable snapshot of the artifact version, tool-call ID and arguments, logical workflow/run ID, and session ID in the request payload before pausing. Use the workflow events to deliver the request externally. Keep the request and verified attestation in your own durable store, with an idempotency key such as For the tool arguments, take the snapshot at the tool/adapter boundary you want the participant to attest to. An outer function middleware's input can still be changed or normalized further down the pipeline; the FunctionInvocationContext documentation describes that behavior. AI helped prepare a local check on |
Uh oh!
There was an error while loading. Please reload this page.
I'm preparing MSc thesis work at TU Delft within SLIME, a wider direction of helping humans and capable AI participants cooperate and develop through experience. My public TrustChain engineering explores signed interaction records and delegation: https://github.com/viftode4/trustchain.
For a workflow that pauses and resumes across a human-agent handoff, which supported extension point should associate an external participant's acknowledgment with the relevant artifact version, tool-call arguments and workflow/session identifiers? Would existing middleware and workflow events already provide the right boundary?
I am asking for guidance on an existing extension point before building an integration, rather than reporting a bug or asserting a missing capability. I have no Agent Framework adapter. An acknowledgment would record the participant's attestation; it would not prove execution correctness or authorize another action.
All reactions