Meeting Notes 2025-07-10

[muscariello]

Attendees:
Jodee Varney (Cisco)
Laszlo Gecse (Cisco)
Luca Muscariello (Cisco)
Catarina Paralta (Cisco)
Sam Betts (Cisco)
Ramiz Polic (Cisco)
Adam Tagscherer (Cisco)
Arpad Csepi (Cisco)
Sujata Tibrewala (Cisco)

The meeting focused on enhancing SDK development, improving user experience, and discussing new team contributions while addressing ongoing projects and integration efforts.

Discussed making the GitHub document public and read-only for easier access to edits.
Reviewed ongoing developments in OSF and agent directory, focusing on synchronization protocols and SDK maintenance.
Highlighted progress on OSF SDK implementation, favoring a server-side solution over client-side for better reusability.
Introduced a new protobuf schema registry to manage SDKs and facilitate code generation effectively.
Emphasized the importance of user experience by integrating various frameworks like VS Code and MCP with the directory.
Welcomed new team member Sujata, who brings experience in open source community building.
Local search and OASF record support are nearing resolution at the API level.
Ongoing work focuses on synchronization APIs and SDK development for JavaScript and Python.
The integration of Spiffy trust schema aims to enhance authentication and secure communication between nodes.
Node management includes plans for attribute-based OASF discovery across the network.
Public records are accessible across nodes, while access control relies on authentication through Spire.

Agenda/Notes:
Status update:
OASF
Release mgmt
https://buf.build/agntcy/oasf → new repo that enables automation like code gen of sdks and clients
Enables use cases for buf.build users
Simplifies code in repo
oasf/README is updated to point to new buf.build distro
New releases
V0.4 - new use cases supported: A2A cards and MCP servers. Need docs to explain that these are captured in extensions
v0.3.2
New features
Schema exposed through grpc object
Expect release this week including grpc models, stdization of oasf schema, new extensions for runtime MCP & A2A etc
App SDK including where should it go?
There is a new app/SDK repo in agntcy and maybe it should go there?
Compared 2 solutions for where should sit - client vs server side
For moment, propose server side, starting with vscode
Propose to use go templating - and generate client side each use case
Alternative: implement in javascript & python
Laszlo is working on this
Diagraming this first, then creating tasks and solving it
Points both directions GitHub_Actions <-> OASF, MS_CoPilotVSCode <-> OASF
Future consideration (TBD): LangGraph <-> OASF
Future consideration: Python SDK, …
dir
API Versioning: Tibor started this and Ramiz will finish it
Sync protocol
SDK maintenance: JS and Python SDKs are being refactored into unified, single SDKs
CLI updates
Local search? Wildcards?
DHT and everything related to node mgmt
Investigating SPIFFE (prot) / SPIRE (impl) trust schema to be added to dir -> Ramiz
Unanswered questions about how to administer sharing of public records on my node only with other trusted nodes
User feedback from Aether
Using app SDK (to integrate a2a and slim) - need to know where agent is to get its agent card, but app sdk uses the agent card to work out how to get the topic → gap
Want to bring dir into the mix to close the gap
As add agents into aether, would use dir to allow agents to announce themselves