Follow-through from the #91 part 2 decision: brain-mcp stays inside ingestion, so the discoverability complaint that generated infra#265 has to be answered by naming rather than by moving code.
Repo description is "MCP supervisor for disciplined Claude Code sessions" — no mention of the brain, none of brain-mcp.
README says "accumulates learnings into a searchable brain" but never the string brain-mcp, and never the hostname.
brain-mcp.d-ma.be appears only in CLAUDE.md / AGENTS.md — generated agent-context files, not the human front door.
So a forge search for "brain-mcp" returns nothing, which is exactly the experience infra#265 reported.
Scope
Repo description names brain-mcp and its ingress
README section: brain-mcp is served from ingestion/internal/mcp at brain-mcp.d-ma.be, with a pointer to the ADR for why it is not its own repo
Repo topics include mcp and brain
Nothing structural — no code moves
Acceptance Criteria
Someone searching the forge for "brain-mcp" lands on this repo
The README answers "where does this code live" without needing to read Go imports
Risk: LOW
Follow-through from the #91 part 2 decision: brain-mcp stays inside `ingestion`, so the discoverability complaint that generated infra#265 has to be answered by naming rather than by moving code.
ADR: brain `wiki/hyperguild/decisions/brain-mcp-stays-in-ingestion-fix-discoverability-by-name`.
## The measured gap
- Repo **description** is "MCP supervisor for disciplined Claude Code sessions" — no mention of the brain, none of brain-mcp.
- **README** says "accumulates learnings into a searchable brain" but never the string `brain-mcp`, and never the hostname.
- `brain-mcp.d-ma.be` appears **only** in `CLAUDE.md` / `AGENTS.md` — generated agent-context files, not the human front door.
So a forge search for "brain-mcp" returns nothing, which is exactly the experience infra#265 reported.
## Scope
- [ ] Repo description names brain-mcp and its ingress
- [ ] README section: brain-mcp is served from `ingestion/internal/mcp` at `brain-mcp.d-ma.be`, with a pointer to the ADR for why it is not its own repo
- [ ] Repo topics include `mcp` and `brain`
- [ ] Nothing structural — no code moves
## Acceptance Criteria
- [ ] Someone searching the forge for "brain-mcp" lands on this repo
- [ ] The README answers "where does this code live" without needing to read Go imports
**Risk:** LOW
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-through from the #91 part 2 decision: brain-mcp stays inside
ingestion, so the discoverability complaint that generated infra#265 has to be answered by naming rather than by moving code.ADR: brain
wiki/hyperguild/decisions/brain-mcp-stays-in-ingestion-fix-discoverability-by-name.The measured gap
brain-mcp, and never the hostname.brain-mcp.d-ma.beappears only inCLAUDE.md/AGENTS.md— generated agent-context files, not the human front door.So a forge search for "brain-mcp" returns nothing, which is exactly the experience infra#265 reported.
Scope
ingestion/internal/mcpatbrain-mcp.d-ma.be, with a pointer to the ADR for why it is not its own repomcpandbrainAcceptance Criteria
Risk: LOW