microsoft / microsoft/agent-framework
Proposal: Goldshine Protocol: A Decentralized Global Capability Delivery Network Based on Agent Encapsulation — Agent-as-Service: ASU Encapsulation for Agent Framework
@sphenry is already working on this.
Since Jun 23, 2026.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
Hi @microsoft/agent-framework team,
I recently published a research paper: "Goldshine Protocol: A Decentralized Global Capability Delivery Network Based on Agent Encapsulation".
Core Problem: Current agent frameworks compose agents by wiring tools together at the function level. But this is like "handing someone a wrench and a manual" instead of "giving them the car, already fixed."
Key Contributions:
- Agent Service Unit (ASU) — A formal five-tuple definition that encapsulates an agent with its own reasoning engine and memory into a single service endpoint, bypassing the function-level bottleneck
- Physical-level memory isolation — Unlike prompt-engineering isolation schemes, each ASU owns its memory space, eliminating cross-tenant context pollution at the architectural level
- Semantic ontology + dual-layer discovery — Intent-driven matching replaces manual tool wiring
Why This Matters for Agent Framework:
- Agent Framework already leads in agent orchestration. The next step is treating agents as composable services rather than tool pipelines
- ASU encapsulation maps naturally to Agent Framework's state management — each ASU maintains its own state graph while exposing a standardized API contract
- This could enable a "plugin marketplace" where agents are packaged, discovered, and invoked without framework-level reconfiguration
Links:
- Full paper: https://zenodo.org/records/20789868
- Code/Repo: https://github.com/gymaira1990-jpg/catnest/tree/main/08-%E9%87%91%E9%97%AA%E9%97%AA%E5%8D%8F%E8%AE%AE
Curious what the team thinks about pushing agent granularity from tools to services.
Thanks!
GCat
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.