feat: sync open-source context and capsule removal
- remove legacy contexts surfaces from the app, MCP bridge, standalone server, and docs - keep getContext and retrieveQueryContext while aligning the simplified graph-only contract - harden dev startup migration behavior and disable the accidental chat surface in open source Generated with Codex
This commit is contained in:
+17
-34
@@ -1,47 +1,22 @@
|
||||
# Open Source Surface
|
||||
|
||||
The open-source RA-H surface should match the main app contract where product behavior is shared:
|
||||
`ra-h_os` should match the main app contract wherever the underlying product behavior is shared.
|
||||
|
||||
That means the open-source docs should reflect:
|
||||
|
||||
- no runtime `dimensions` model,
|
||||
- optional soft `contexts`,
|
||||
- no automatic context assignment on write,
|
||||
- node quality driven by title, description, source, metadata, and edges.
|
||||
|
||||
## What RA-H OS Includes
|
||||
|
||||
- local SQLite graph
|
||||
- local UI
|
||||
- standalone MCP server
|
||||
- shared skills system
|
||||
- BYO API key path
|
||||
|
||||
## What RA-H OS Does Not Promise
|
||||
|
||||
- every private-app surface
|
||||
- private subscription/auth behavior
|
||||
- official support for every local model stack or vector backend someone can wire up
|
||||
- a guarantee that every community setup is first-class supported
|
||||
|
||||
## Support Boundary
|
||||
|
||||
Supported core path:
|
||||
- RA-H OS app
|
||||
- local SQLite
|
||||
- standard standalone MCP server
|
||||
- documented repo install flow
|
||||
|
||||
Reasonable community pattern:
|
||||
- local model or alternate MCP-capable chat surface layered on top of the documented contract
|
||||
|
||||
Experimental / user-owned:
|
||||
- custom vector backends
|
||||
- unsupported deployment targets
|
||||
- aggressive local-model substitutions that degrade tool quality
|
||||
It should also explain the open-source-specific reality clearly:
|
||||
- no private-app-only promises
|
||||
- a practical standalone MCP install path
|
||||
- pinned package versions for external-agent setup
|
||||
- clear verification and troubleshooting steps
|
||||
- honest support boundaries for fully local or community setups
|
||||
|
||||
## Important App Routes
|
||||
|
||||
- `app/api/nodes/`
|
||||
- `app/api/contexts/`
|
||||
- `app/api/edges/`
|
||||
- `app/api/rah/chat/`
|
||||
- extraction routes
|
||||
@@ -52,3 +27,11 @@ Experimental / user-owned:
|
||||
Main `ra-h` ships first.
|
||||
|
||||
`ra-h_os` is a required follow-up port of the same contract, not a place to preserve older taxonomy behavior.
|
||||
|
||||
## Required Docs Surfaces In `ra-h_os`
|
||||
|
||||
- `README.md` for terse install + MCP quickstart
|
||||
- `docs/README.md` for the start-here path
|
||||
- `docs/8_mcp.md` for the full MCP setup, verification, memory-file guidance, and troubleshooting path
|
||||
- `docs/10_full-local.md` for clearly caveated local/community patterns
|
||||
- `apps/mcp-server-standalone/README.md` for package-level install details that match the repo docs
|
||||
|
||||
Reference in New Issue
Block a user