Repository navigation
docs(go): clarify Gateway policies and manual verification - #65
Merged
Merged
Conversation
hanakannzashi
approved these changes
Oct 14, 2026
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.
Clarify that Go's DeploymentPolicy applies to model deployments, while GatewayVerification.DeploymentVerifier takes a callback without a model argument. Explain that manual Gateway verification must rebuild the attestation client with the pinned HTTP transport before fetching model evidence and signatures.
Link to the corrected walkthrough in nearai/inference-sdk#101. This follows the merged docs PR #64; merge SDK PR #101 first so its guide links resolve.
Validation: checked the SDK links and heading anchors against the updated SDK checkout, and ran git diff --check. Website changes are prose only; the accompanying SDK examples compile against published v0.1.0, including both callback assignments.