feat(acms): implement multi-agent RDF knowledge sharing — agent-scoped named graphs and cross-agent query federation #3087

Open
opened 2026-04-05 05:33:21 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: feat/v36/uko-multi-agent-knowledge-sharing
  • Commit Message: feat(acms): implement multi-agent RDF knowledge sharing — agent-scoped named graphs and cross-agent query federation
  • Milestone: v3.6.0
  • Parent Epic: #367

Background

The Multi-Agent RDF System enables multiple agents to collaborate through shared RDF knowledge. Each agent maintains its own named graph (scoped knowledge), but can query across all agent graphs via federated SPARQL queries. This enables agents to build on each other's knowledge without overwriting it.

Expected Behavior

  • Each agent has a dedicated named graph in the triple store (e.g., urn:agent:<agent-id>:graph)
  • Agents can assert triples into their own named graph
  • Cross-agent federated queries can span multiple named graphs
  • Conflict resolution strategy for contradictory triples from different agents (provenance-based)
  • MultiAgentKnowledgeService provides the high-level API for agents to interact with the shared knowledge base
  • Integration with the actor/agent execution lifecycle

Dependencies

  • Blocked by: #3086 (inference engine must be implemented first)
  • Blocks: #367

Subtasks

  • Define named graph naming convention for agent-scoped knowledge
  • Implement MultiAgentKnowledgeService with per-agent graph isolation
  • Implement federated SPARQL query across multiple agent graphs
  • Implement provenance-based conflict resolution for contradictory triples
  • Integrate with actor execution lifecycle (assert knowledge on tool completion)
  • Write Behave unit tests for multi-agent knowledge sharing scenarios
  • Ensure nox -e typecheck passes with no suppressions

Definition of Done

  • All subtasks completed
  • Tests written and passing
  • All nox stages pass
  • Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Acting on behalf of: UAT Testing | Agent: ca-epic-planner

## Metadata - **Branch**: `feat/v36/uko-multi-agent-knowledge-sharing` - **Commit Message**: `feat(acms): implement multi-agent RDF knowledge sharing — agent-scoped named graphs and cross-agent query federation` - **Milestone**: v3.6.0 - **Parent Epic**: #367 ## Background The Multi-Agent RDF System enables multiple agents to collaborate through shared RDF knowledge. Each agent maintains its own named graph (scoped knowledge), but can query across all agent graphs via federated SPARQL queries. This enables agents to build on each other's knowledge without overwriting it. ## Expected Behavior - Each agent has a dedicated named graph in the triple store (e.g., `urn:agent:<agent-id>:graph`) - Agents can assert triples into their own named graph - Cross-agent federated queries can span multiple named graphs - Conflict resolution strategy for contradictory triples from different agents (provenance-based) - `MultiAgentKnowledgeService` provides the high-level API for agents to interact with the shared knowledge base - Integration with the actor/agent execution lifecycle ## Dependencies - Blocked by: #3086 (inference engine must be implemented first) - Blocks: #367 ## Subtasks - [ ] Define named graph naming convention for agent-scoped knowledge - [ ] Implement `MultiAgentKnowledgeService` with per-agent graph isolation - [ ] Implement federated SPARQL query across multiple agent graphs - [ ] Implement provenance-based conflict resolution for contradictory triples - [ ] Integrate with actor execution lifecycle (assert knowledge on tool completion) - [ ] Write Behave unit tests for multi-agent knowledge sharing scenarios - [ ] Ensure `nox -e typecheck` passes with no suppressions ## Definition of Done - [ ] All subtasks completed - [ ] Tests written and passing - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Acting on behalf of: UAT Testing | Agent: ca-epic-planner
freemo added this to the v3.6.0 milestone 2026-04-05 05:35:35 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Medium — the capstone of the RDF chain, depends on all three predecessors
  • Milestone: v3.6.0 (already assigned)
  • MoSCoW: Should Have — multi-agent knowledge sharing is the end goal of Epic #367. Important for the full ACMS vision but the milestone can proceed without it if the dependency chain isn't completed in time.
  • Parent Epic: #367 (dependency link already exists)

Dependency chain: #3081#3082#3086#3087. Blocked by #3086.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified ✅ - **Priority**: Medium — the capstone of the RDF chain, depends on all three predecessors - **Milestone**: v3.6.0 (already assigned) - **MoSCoW**: Should Have — multi-agent knowledge sharing is the end goal of Epic #367. Important for the full ACMS vision but the milestone can proceed without it if the dependency chain isn't completed in time. - **Parent Epic**: #367 (dependency link already exists) **Dependency chain**: #3081 → #3082 → #3086 → **#3087**. Blocked by #3086. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo removed this from the v3.6.0 milestone 2026-04-07 00:20:02 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#3087
No description provided.