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

Open
#6,655 0 comments 0 reactions 1 assignee View on GitHub

@sphenry is already working on this.

Since Jun 23, 2026.

needs_pm
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:

  1. 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
  2. Physical-level memory isolation — Unlike prompt-engineering isolation schemes, each ASU owns its memory space, eliminating cross-tenant context pollution at the architectural level
  3. 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:

Curious what the team thinks about pushing agent granularity from tools to services.

Thanks!
GCat

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.