# OpenBrain / Hermes Install Path

This project now has a live memory bridge installed inside the Hermes profile.

## Where it lives

### Hermes profile
- Active profile: `~/.hermes/profiles/5-5/`
- MCP server entry: `openbrain-bridge`
- Hermes config file updated automatically:
  - `~/.hermes/profiles/5-5/config.yaml`

### Local bridge implementation
- Bridge script:
  - `mcp/openbrain_bridge.py`
- Virtualenv:
  - `.venv-openbrain/`
- Backing data:
  - `index/archive.db`
  - `approved-memory/install-batch-proposed.jsonl`
  - `approved-memory/source-only-index.jsonl`

## Why this is the right place

OpenBrain’s own architecture describes the memory layer as an MCP-accessible shared substrate rather than a giant prompt dump. In Hermes terms, that means the live install belongs in the MCP layer attached to the active profile, while the archive and reviewed memory artifacts remain on disk as the source of truth.

## Current status

- Hermes can connect to the server.
- The server exposes 8 tools.
- Search and fetch are working against local archive and reviewed memory artifacts.
- The full hosted Supabase/OpenBrain backend is still a later swap-in path.

## Next possible step

If we later move from the local bridge to the hosted OpenBrain backend, the Hermes MCP entry can be repointed without changing the user-facing workflow.