Files

T

“BeeRad”andClaude Sonnet 4.5 be675be4e0 feat: MCP server v1.2.0 — guide system + read/write guide tools

Adds full guide system to MCP standalone server. System guides (schema,
creating-nodes, edges, dimensions, extract) are bundled and immutable.
Users can create up to 10 custom guides via rah_write_guide. Syncs guide
infrastructure from main repo to OS repo app code.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2026-02-08 11:15:13 +11:00

1.5 KiB

Raw Blame History

name, description, immutable

name	description	immutable
Edges	Edge philosophy. Explanations, direction, types. Connection patterns.	true

Edges

Philosophy

Edges are the most valuable part of the knowledge graph. Individual nodes are useful; the web of connections between them is what makes the graph powerful.

Rules

Every edge needs an explanation — why does this connection exist? Be specific.
Direction matters — FROM → TO should read like a sentence
Types are inferred — the system infers category/type from your explanation. Don't set types manually.

Direction Convention

Write the explanation so FROM → TO reads naturally:

Episode → Podcast: "Episode of this podcast"
Book → Author: "Written by this author"
Insight → Source: "Extracted from this source"
Idea → Related idea: "Builds on this concept"

Edge Context JSON

{
  "explanation": "Human-readable reason",
  "category": "inferred (created_by, features, part_of, source_of, related_to)",
  "type": "inferred specific type",
  "confidence": 0.0-1.0,
  "created_via": "chat|mcp|workflow"
}

Hub Traversal

Hub nodes (most-connected) are the user's core themes. To understand context around a topic:

Find the relevant hub node
Use queryEdge or sqliteQuery to get its connections
Traverse outward to related nodes

When to Create Edges

After creating synthesis/idea nodes (connect to sources)
When user mentions a relationship between topics
When running the Connect or Integrate guides
When obvious connections exist that aren't captured

1.5 KiB Raw Blame History