SyslogSolution/ra-h-os
7
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update What to Expect sections with guides and proactive capture

Browse Source 
All 3 doc files now describe the propose-a-node pattern, guide system,
and updated orientation flow.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
“BeeRad”
2026-02-08 12:29:25 +11:00
co-authored by Claude Sonnet 4.5
parent 0577ec727d
commit 7bf94d4c61
3 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -111,7 +111,7 @@ Restart Claude Code fully (**Cmd+Q on Mac**, not just closing the window).
} }
``` ```
**What happens:** Once connected, Claude will proactively identify valuable information in your conversations and offer to save it to your knowledge graph. It calls `rah_get_context` first to understand what's already in your graph, then searches before creating to avoid duplicates. **What happens:** Once connected, Claude calls `rah_get_context` first to orient itself (stats, hub nodes, dimensions, available guides). It proactively captures knowledge — when a new insight, decision, person, or reference surfaces, it proposes a specific node (title, dimensions, description) so you can approve with minimal friction. For complex tasks it reads guides to understand your graph conventions and custom workflows.
Available tools: Available tools:
apps/mcp-server-standalone/README.md
+3 -2
View File
@@ -41,8 +41,9 @@ Restart Claude. Done.
## What to Expect ## What to Expect
Once connected, Claude will: Once connected, Claude will:
- **Call `rah_get_context` first** to see what's in your graph - **Call `rah_get_context` first** to orient itself (stats, hub nodes, dimensions, guides)
- **Proactively offer to save** valuable information from your conversations - **Proactively capture knowledge** — when a new insight, decision, person, or reference surfaces, it proposes a specific node (title, dimensions, description) so you can approve with minimal friction
- **Read guides for complex tasks** — system guides (immutable) teach it how your graph works; custom guides teach it your workflows
- **Search before creating** to avoid duplicates - **Search before creating** to avoid duplicates
## Available Tools ## Available Tools
docs/8_mcp.md
+4 -4
View File
@@ -99,10 +99,10 @@ If you want real-time UI updates when nodes are created:
Once connected, the MCP server instructs Claude to: Once connected, the MCP server instructs Claude to:
1. **Call `rah_get_context` first** to understand your graph (hub nodes, dimensions, stats) 1. **Call `rah_get_context` first** to orient itself (hub nodes, dimensions, stats, available guides)
2. **Proactively identify valuable information** in conversations and offer to save it 2. **Proactively capture knowledge** — when a new insight, decision, person, or reference surfaces, it proposes a specific node (title, dimensions, description) so you can approve with minimal friction
3. **Search before creating** to avoid duplicates 3. **Read guides for complex tasks** — system guides (immutable) teach it how your graph works; custom guides teach it your workflows
4. **Require edge explanations** — every connection needs a reason 4. **Search before creating** to avoid duplicates
You don't need to ask Claude to use your knowledge base — it will offer when it spots something worth saving. You don't need to ask Claude to use your knowledge base — it will offer when it spots something worth saving.