Add ExternalTrustSignalProvider adapter contract#16
Open
Conversation
Contributor
Author
|
Status note: this PR captured the ExternalTrustSignalProvider contract work, but |
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.
Summary
ExternalTrustSignalProviderschema for optional external identity, certificate-tier, reputation, counterparty, and registry lookup verifier inputs.agent_machine.external_trustsemantic validation with explicit freshness, signature, provider-ref, signal-type, safety, and non-authority checks.Safety posture
External trust signals are never authorization. They only become optional verifier inputs for the local Agent Registry grant resolver when fresh, properly scoped, signed when required, and marked with
authority: non-authoritative-verifier-input.The contract explicitly forbids raw prompt content, KV-cache contents, private memory, API keys, wallet private keys, raw credentials, raw user data, and secrets in adapter payloads.
Validation
Expected validation paths:
python3 scripts/validate-json.pypython3 scripts/validate-governance.pypython3 -m agent_machine.external_trust examples/external-trust-signal-provider.active.json --expect usablepython3 -m agent_machine.external_trust examples/external-trust-signal-provider.stale.json --expect unusablemake validateCloses #13