Agentic Memory Domain
GrayMatter owns durable agentic memory and RBAC-scoped object graph awareness. It does not own live agent coordination. SwarmOps owns agent registration, presence, command routing, graph snapshots, and coordination state.
Boundary
| Capability | Owner |
|---|---|
| Durable memory entries, relationships, compaction, reindex, prune, expansion | GrayMatter |
| RBAC-visible object graph context from the full Valhalla schema | GrayMatter through server-authorized APIs |
| Agent registration for CODEX, OpenClaw, ValorIDE, Claude adapters, and Valkyr agents | SwarmOps |
| Live coordination, command forwarding, graph snapshots, telemetry | SwarmOps |
| Workflow execution over memory or graph context | ValkyrAI |
| Chat-based memory actions and advice | Valor |
| Coding-agent memory usage | ValorIDE and third-party agents through GrayMatter APIs |
Object Graph Scope
The entire ThorAPI/ValkyrAI schema can be used as object graph material by GrayMatter, but only through the RBAC of the server. Memory-aware agents should see:
- objects they are authorized to read
- relationships the server permits
- encrypted/secure field metadata without decrypted secrets unless explicitly authorized
- semantic health and memory quality metrics
- agent and SwarmOps metadata needed for coordination
Agent Journey
User Journey
A GrayMatter user wants to:
- See what memories exist and why they matter.
- Secure, edit, delete, compact, reindex, prune, or expand memory.
- Control which agents can read/write memory.
- Understand cost and credit burn.
- Inspect multiagent environments without confusing coordination state with memory state.
Code Anchors
- Memory dashboard:
src/components/memory/MemoryDashboard.tsx - Control API contract:
/v1/graymatter/control - SWARM API schemas:
Swarm,SwarmMessage,SwarmRegisterRequest,SwarmGraphSnapshot - Protocol contracts:
contracts/swarm,docs/graymatter,docs/protocols