Add TypeScript policy adapters - #23
Merged
Merged
Conversation
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
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 changed
Why
Integrations need a small source-neutral normalization layer rather than knowledge of the full Python SDK or external governance runtime objects. Policy adapter failures must not leak raw input content or begin partial delivery because a later source record is malformed.
Impact
Node integrations can normalize OPA, Cedar, and AGT policy facts directly into validated AgentTrust events and feed them through the same evidence, log, span, and metric pipeline.
Validation
python -m pytest -q— 92 passed, 20 subtests passednpm run check— build, 26 tests, package dry run passed