@gettymade/roux 0.1.2 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -3,24 +3,22 @@ title: Readme
3
3
  ---
4
4
  # Roux
5
5
 
6
- A **Graph Programming Interface (GPI)** for building and maintaining knowledge graphs. Semantic search, graph traversal, and AI co-authoring through a unified interface—regardless of storage backend.
6
+ A **Graph Programming Interface (GPI)** for markdown knowledge bases. Semantic search, graph traversal, and AI-assisted editing through MCP.
7
7
 
8
8
  ## What It Does
9
9
 
10
- - **Semantic search** — Find nodes by meaning, not just keywords
11
- - **Graph traversal** — Follow links, find paths, identify central nodes
12
- - **CRUD operations** — Create, read, update, delete nodes programmatically
13
- - **AI co-authoring** — Let AI assistants read and write knowledge alongside humans
10
+ - **Semantic search** — Find notes by meaning, not just keywords
11
+ - **Graph traversal** — Follow wiki-links, find paths, identify hub notes
12
+ - **CRUD operations** — Create, read, update, delete notes programmatically
13
+ - **MCP integration** — Works with Claude Code and other MCP clients
14
14
 
15
- The graph is always the target structure. Data that isn't natively a graph gets transformed during ingestion. The query model stays constant regardless of source or storage.
15
+ Point it at a markdown directory. Query it like a graph database. Edit in Obsidian.
16
16
 
17
17
  ## Architecture
18
18
 
19
- Roux is a platform of pluggable modules. GraphCore is the coordination hub—it defines provider interfaces but has zero functionality without them.
20
-
21
19
  ```
22
20
  ┌─────────────────────────────┐
23
- External Interfaces MCP Server, REST API, CLI
21
+ MCP Server Claude Code, other clients
24
22
  └──────────────┬──────────────┘
25
23
 
26
24
  ┌──────────────▼──────────────┐
@@ -28,26 +26,17 @@ Roux is a platform of pluggable modules. GraphCore is the coordination hub—it
28
26
  └──────────────┬──────────────┘
29
27
 
30
28
  ┌──────────────▼──────────────┐
31
- │ Providers │ Store, Embedding, LLM, ...
29
+ │ Providers │
30
+ │ DocStore + Transformers.js │
32
31
  └─────────────────────────────┘
33
32
  ```
34
33
 
35
- **Store backends** span zero infrastructure to enterprise scale:
36
- - File-based: DocStore (markdown directories)
37
- - Embedded: SQLite, LevelGraph
38
- - Standalone: SurrealDB, FalkorDB, Memgraph
39
- - Enterprise: Neo4j, ArangoDB, Amazon Neptune
40
-
41
- **Embedding providers** for semantic search:
42
- - Local: transformers.js (default, zero config)
43
- - Self-hosted: Ollama
44
- - Cloud: OpenAI
45
-
46
- Same queries, same results—regardless of what's plugged in.
34
+ **Current implementation:**
35
+ - **DocStore** — Reads markdown directories, parses frontmatter and wiki-links
36
+ - **Transformers.js** — Local embeddings, no external API required
37
+ - **SQLite cache** Fast queries without re-parsing files
47
38
 
48
- ## Current State (v0.1.x)
49
-
50
- Roux ships today with **DocStore**: point it at a markdown directory, query via MCP, edit in Obsidian.
39
+ ## Quick Start
51
40
 
52
41
  ```bash
53
42
  # Install
@@ -56,15 +45,14 @@ npm install -g @gettymade/roux
56
45
  # Initialize on your markdown directory
57
46
  cd ~/my-notes
58
47
  roux init
59
-
60
- # Start the MCP server
61
- roux serve
62
48
  ```
63
49
 
64
- Then ask your AI things like:
65
- - "Search my notes for distributed systems concepts"
66
- - "What links to my note on consensus algorithms?"
67
- - "Create a new note summarizing what I learned today"
50
+ `roux init` creates config files that Claude Code detects automatically. The MCP server starts when you open the project.
51
+
52
+ Then ask Claude things like:
53
+ - "Search my notes for distributed systems"
54
+ - "What links to my consensus algorithms note?"
55
+ - "Create a new note about today's meeting"
68
56
 
69
57
  ### Requirements
70
58
  - Node.js 20+
@@ -74,7 +62,7 @@ Then ask your AI things like:
74
62
 
75
63
  ```bash
76
64
  roux init [directory] # Initialize (creates roux.yaml, .roux/, .mcp.json)
77
- roux serve [directory] # Start MCP server with file watching
65
+ roux serve [directory] # Start MCP server manually (for debugging or non-Claude clients)
78
66
  roux serve --no-watch # Start without watching for changes
79
67
  roux status [directory] # Show node/edge/embedding counts
80
68
  roux viz [directory] # Generate interactive graph visualization
@@ -111,26 +99,27 @@ providers:
111
99
 
112
100
  Embeddings use local transformers.js by default. No external services required.
113
101
 
114
- ### MCP Client Integration
102
+ ### Non-Claude MCP Clients
115
103
 
116
- `roux init` creates `.mcp.json` in your project directory. MCP clients detect and offer to enable the server automatically.
104
+ `roux init` creates `.mcp.json` which Claude Code reads automatically. Other MCP clients may need manual configuration:
117
105
 
118
- ## Roadmap
106
+ ```bash
107
+ # Option 1: Run the server manually
108
+ roux serve
109
+
110
+ # Option 2: Configure your client to spawn it (check your client's docs)
111
+ ```
119
112
 
120
- **Near term:**
121
- - LLMProvider — Text generation for assisted features
122
- - Structural embeddings — Graph-aware vectors
113
+ ## Future
123
114
 
124
- **Medium term:**
125
- - Neo4jStore — Graph database backend for scale
126
- - IngestionProvider — Entity extraction, edge inference
127
- - REST/GraphQL API
115
+ The architecture supports pluggable backends. Currently only DocStore exists—these are planned:
128
116
 
129
- **Future:**
130
- - Multi-store federation
131
- - Multi-tenancy and access control
117
+ - **Additional stores** — Neo4j, SQLite-native, SurrealDB
118
+ - **Cloud embeddings** — OpenAI, Ollama for higher-quality vectors
119
+ - **LLM provider** Text generation for assisted writing
120
+ - **REST API** — For non-MCP integrations
132
121
 
133
- See [implementation-plan.md](docs/implementation-plan.md) for details.
122
+ See `docs/roadmap/` for details.
134
123
 
135
124
  ## How It Works
136
125
 
@@ -140,7 +129,7 @@ See [implementation-plan.md](docs/implementation-plan.md) for details.
140
129
  4. **Graph** — Builds in-memory graph from link relationships
141
130
  5. **Serving** — Exposes operations via MCP protocol
142
131
 
143
- File changes sync automatically when running `roux serve`.
132
+ File changes sync automatically when the MCP server is running.
144
133
 
145
134
  ## Documentation
146
135