feat: add agent identity + onboarding protocol example#253
Open
vystartasv wants to merge 2 commits into
Open
Conversation
Demonstrates cryptographic agent identity for interoperable atomic agents using the Identity Protocol (L2) and Onboarding Protocol (L1) concepts: - AgentIdentity: Ed25519-style keypair with fingerprint - OnboardingCertificate: signed capability attestation - Handoff signing: verifiable task transfer between agents Self-contained — stdlib only, zero external dependencies. Points to workswithagents.com/specs/identity.md for the production Ed25519 SDK. Related: Eigenwise#251
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 This Adds
A working example at
atomic-examples/agent-identity/that demonstrates cryptographic agent identity and onboarding — the missing layer for making atomic agents interoperable beyond a single process.The Two Protocols
Identity Protocol (L2)
Each agent gets a permanent, verifiable identity — an Ed25519-style keypair. The public key is the agent's identifier; the private key signs handoff tokens and capability manifests.
Onboarding Protocol (L1)
Before an agent is trusted with work, an authority issues a signed certificate listing verified capabilities. This is the "prove you can do the job before I give you the job" step.
Why This Matters for Atomic Agents
Atomic agents ("one agent, one job") are composable by design. But composition without identity is fragile:
Identity turns a collection of agents into a verifiable pipeline.
What's in This PR
main.py— 150-line demo: identity creation, onboarding, signed handoff, verificationpyproject.toml/__init__.py— standard example packaging (matches existing pattern)README.md— explains the concept, links to the full protocol specZero new dependencies. The demo uses stdlib only. The full production SDK (
pip install works-with-agents) adds Ed25519 viapynaclfor real cryptographic signing — but the concept and protocol structure are the same.Run It
cd atomic-examples/agent-identity python agent_identity/main.pyReferences