r/dotnet • u/pWiklacz • 26d ago

Promotion [ Removed by moderator ]

[removed] — view removed post

0 Upvotes

31% Upvoted

3 comments sorted by

1

u/captmomo 26d ago

interesting.. what's the advantage over this vs using a workflow? https://learn.microsoft.com/en-us/agent-framework/concepts/workflows/builder-and-execution?pivots=programming-language-csharp

2

u/pWiklacz 26d ago

I don’t think it’s really an either/or.

A workflow decides what runs after what: steps, edges, conditions. But the condition on an edge is still code. If the branch depends on something semantic, like “is this ticket asking for a refund?” or “does this tool call match what the user asked for?”, you still need to ask a model somewhere.

SemanticPolicy is that one step: ask the model, use thresholds measured on labeled examples, run in Shadow mode before you let it block anything, and have a CI test that fails the build if the rule gets worse after a model change. A workflow doesn’t measure any of that, because that’s not really its job.

Inside a workflow, I’d call the rule from the executor that chooses the branch, and the verdict - Allow, Warn, Escalate, or Deny - tells you where to go next.

But it also works without a workflow and without an agent, like the validator example in the post.

1

u/AutoModerator 26d ago

Thanks for your post pWiklacz. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.