.NET: Memory portability between agents — verified memory bundles with chain of custody (complements A2A)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- ai, distributed-systems
Research direction
Start with the proposal's question about placing the work in samples versus treating it as a component discussion. Review the described sealed bundles, chain of custody, local re-verification, ownership, validity intervals, and four-platform implementation. Done means the framework-specific scope and contribution location are agreed.
Written by the indexing model from the issue text.
Description
Maintainer of cognicore-env here (open-source agent memory layer, MIT, MCP-compatible) — this is a proposal, happy to do the work as an example.
Agent Framework's A2A support moves tasks between agents; MCP moves tools. What nothing moves is verified knowledge. When agent A hands off to agent B today, B starts from zero, or teams bolt on a shared store with no provenance — no way to know which agent learned a fact, what evidence it was based on, or how stale it is. In multi-team setups that produces a specific failure mode we have measured: on conflicting facts, models do not decline — they confidently report the wrong one (a practitioner running six teams on shared memory reported 33 percent accuracy on conflict questions without ownership rules).
Proposal: a memory transfer component that emits and consumes sealed bundles. Each memory carries proof (command, result, exit code, output hash) and a chain of custody; receivers import foreign memories in an observed state that requires local re-verification; trust decays across hops. The design now includes owner-per-concept and validity intervals (a convention verified in March is not evidence about April) from that same multi-team review.
The interesting framework-specific angle: a bundle crossing a .NET agent and a Python agent proves the format is runtime-portable — exactly the cross-runtime story Agent Framework is built around. Our transfer layer is implemented and tested across four platforms.
Happy to contribute a working example. Would this belong in samples, or do you see it as a component discussion first?
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 342
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.
More from microsoft/agent-framework
-
python triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/agent-framework#8523 · 1 comment ·
-
.NET compaction documentation
Difficulty 1/5 Under an hour Newbie friendliness 82/100
microsoft/agent-framework#4629 · 1 comment ·
-
harness python reproduced
microsoft/agent-framework#8567 · 2 comments · 1 assignee ·
-
.NET agents reproduced
microsoft/agent-framework#8566 · 1 comment · 1 assignee ·
-
.NET agents python
microsoft/agent-framework#8562 · 1 assignee ·
All issues in microsoft/agent-framework
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100