Where should capability-level evaluation evidence attach in a composed workflow? #7478
Unanswered
yuehua1213
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Agent Framework supports agents, tools, middleware, and graph workflows with checkpointing, human-in-the-loop control, and multiple providers. In a production system, that makes a single framework-level label too broad for deciding whether a reusable capability is reliable.
A failed workflow may come from one tool, one agent, routing logic, provider behavior, or environment dependencies. Recording evaluation evidence at the capability/node level—while preserving the full workflow context—could make failures and version changes easier to compare.
Does the framework have a recommended stable identifier and evidence model for attaching evaluation results to individual agents, tools, or workflow nodes across Python and .NET?
All reactions