docs: give delegation readers a complete verifiable first example - #153
Open
imran-siddique wants to merge 3 commits into
Open
docs: give delegation readers a complete verifiable first example#153imran-siddique wants to merge 3 commits into
imran-siddique wants to merge 3 commits into
Conversation
Member
Author
|
@agentrust-io/maintainers please review this PR and submit an approving review if the changes look correct. All checks are green; maintainer approval is still required to merge. Please check the complete quickstart, its trusted-root and signed scope-escalation examples, and the architecture diagram's ordering against the inbound runtime. The documented example is exercised in CI. |
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.
The first commands referenced repository files without a checkout, omitted a usable trusted root, and promised scope escalation from an edit that fails signature verification first. The quickstart now includes its setup and one complete chain generator, retains the root independently, and demonstrates both an untrusted-root rejection and a correctly signed overbroad grant.
The homepage leads to that local result. The architecture page follows the inbound implementation's ordering and distinguishes chain validation, holder authentication, local policy, appraisal, sealed payload handling, and decision provenance. Software assurance and offline replay limits are explicit. The docs deployment now copies SPONSORS.md, which navigation already referenced.
Validation: the exact Python tutorial block passes; its saved chain verifies through the CLI with the expected two-hop read-only leaf result. Ruff passes for the new test. MkDocs builds successfully. No runtime changes; full CI and deployed visual verification follow.