feat(patterns): add trust middleware guardrails recipe#711
Open
sriram7737 wants to merge 5 commits into
Open
Conversation
|
I have not money |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
A recipe demonstrating a guardrails-as-code pattern for Claude agent loops: validating tool calls, enforcing policy deterministically, routing consequential actions to HITL, and emitting an inspectable trace before execution.
Why
Agent loops that call real tools need a deterministic safety layer distinct from the model. This notebook shows the pattern end-to-end, using the open-source Pramagent SDK as the implementation.
Validation
registry.yaml.sriram7737toauthors.yamlin alphabetical order.python -m json.tool..github/scripts/verify_registry.pywithPYTHONIOENCODING=utf-8: the new author, registry author, and notebook path pass; the script then fails on an unrelated existingBillingcategory in the current registry.