Meeting Notes - 11.21.25 #715
KingLeonidas0706
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Attendees:
• Luca Muscariello - Cisco
• Andras Jaky - Cisco
• Arpad Csepi - Cisco
• Jerry Franklin - Independent
• Jodee Varney - Cisco
• Laszlo Gecse - Cisco
• Michael Clifford - Red Hat
• Morgan Foster - Red Hat
• Paul Cayet - Oracle
• Tibor Kircsi - Cisco
• Jason Bonafide - Dell
• Andrew Doellman - Cisco
AGNTCY + Kagenti Alignment
• Both teams are addressing the same lifecycle gaps from opposite ends (build-time vs runtime).
• Kagenti provides a Kubernetes operator handling agent builds, identity, and card routing.
• AGNTCY offers mature build-time pipelines (OCI, SBOM, provenance, distribution).
• Agreement to collaborate instead of duplicating work.
• Kagenti will organize a workshop demo for AGNTCY.
Open Problem: Binding Agent Cards to Workloads
• No standard today for securely binding a signed agent card to a running workload.
• Requires late-binding metadata, replay protection, and workload identity mapping.
• Directory may serve as part of the eventual trust model.
Agent Card Standard
• Cross-project Agent Card spec emerging (Google + Anthropic).
• Intent to unify card formats across A2A and MCP.
• Still early - governance and runtime binding are unresolved.
Agent Spec Update
• Specifies agent structure, skills, and workflows.
• Next version: runtime framework, protocol (A2A/MCP), environment variables in OASF records.
• Enables deployment, behavioral search, multi-agent patterns (manager–worker, swarm).
• Potential Kubernetes alignment.
Distributed / Multi-Agent Patterns
• Need shared context, specialization, and parallelization patterns.
• Collaboration opportunities: identity inheritance, secure forking, workload discovery.
Demonstration
• MCP used to access local Directory node.
• Five OASF records created, validated, pushed.
• Search/pull operations shown.
Testbed
• Internal testbed live (TSC companies only).
• Node deployment/peering docs coming.
• Policies for external nodes and enterprise boundaries in development.
Directory Working Group - 11.21.2025.docx
Beta Was this translation helpful? Give feedback.
All reactions