GitHub user QvxSphere added a comment to the discussion: [Feature] Sub-agent Resource for Flink Agents - Framework part
Thanks—yes, that is the boundary I was trying to isolate, and keeping it inside the reconciler makes sense. Our current implementation is not a Flink production integration, so I do not want to overstate it as one. The adjacent operational scenario is an external provider that may complete an invocation before the caller receives or persists the response. On recovery, the reconciler must determine whether the returned completed artifact belongs to the original invocation rather than merely trusting a matching call identity. The pattern we are testing binds a stable invocation ID and canonical request hash to the original persisted result artifact, then makes that binding independently checkable through a signature and discoverable key reference. A mismatch, missing original artifact, or ambiguous reconciliation fails closed before any resend. I agree this is probably best expressed first as a reusable reconciler component or profile. If useful, I can share a small synthetic example focused specifically on that boundary—without presenting it as a Flink integration or production assurance. GitHub link: https://github.com/apache/flink-agents/discussions/909#discussioncomment-18152248 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
