RFC: Optional cryptographic identity layer for gitagent manifests#73
Open
aeoess wants to merge 1 commit intoopen-gitagent:mainfrom
Open
RFC: Optional cryptographic identity layer for gitagent manifests#73aeoess wants to merge 1 commit intoopen-gitagent:mainfrom
aeoess wants to merge 1 commit intoopen-gitagent:mainfrom
Conversation
…ifests Closes open-gitagent#70 (proposal). Adds spec/rfcs/identity.md per shreyas-lyzr's review. - Optional identity block in agent.yaml (public_key, key_fingerprint, passport_uri, signatures) - Verification semantics in spec, enforcement in runtime - Two-deep delegation example with parent-signs-child manifest flow - Revocation behavior tight enough to keep two implementations from diverging - Non-goals section bounding scope - Cross-walk to Agent Passport System as one reference impl Backwards compatible: existing agent.yaml files validate unchanged.
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.
Closes #70. Adds
spec/rfcs/identity.mdper @shreyas-lyzr's review on the proposal thread.Three asks from #70 addressed:
passport_urireach the same answer.Plus the structural points from the response:
identityblock insideagent.yaml, not a separate file (Section 3).identity.public_key,identity.key_fingerprint,identity.passport_uri,identity.signatures.<scope>.agent.yaml.identity.*to APS primitives so a thin (~30-line) adapter satisfies Section 5 against any APS endpoint.The
identityblock is additive and optional. Existingagent.yamlfiles validate against the v0.1.x schema unchanged.Open questions deferred to future RFCs (Section 8): multi-signature thresholds, agent-to-tool delegation, cross-repo parent resolution, conformance test vectors.
cc @shreyas-lyzr