docs: name brain-mcp and say where its code lives (#94)

Conversation 3 Commits 2 Files Changed 1

+35 -3

2 Commits

Author	SHA1	Message	Date
mathias	ecbef33637	docs: point the README's forge links at git.d-ma.be (#94 ) CI / Lint / Test / Vet (pull_request) Successful in 37s Details CI / Mirror to GitHub (pull_request) Skipped Details The three forge links in README.md used http://gitea.d-ma.be, an alias whose ingress was removed by infra#126. Verified rather than assumed: DNS still resolves the name to the same IP, but a public repo returns 404 there and 200 on git.d-ma.be, with no redirect — so the links are broken, not merely old. Scope is README.md only. The dated files under docs/superpowers/plans and specs are records of what was done in April/May 2026, when that hostname was correct; rewriting them would falsify the record rather than fix a link. Note the agentsquad link still 404s unauthenticated — that repo is private, which is expected and not a URL problem. Refs #94, infra#126.	2026-08-20 17:37:05 +02:00
mathias	25b9b6683e	docs: name brain-mcp and say where its code lives (#94 ) CI / Lint / Test / Vet (pull_request) Successful in 37s Details CI / Mirror to GitHub (pull_request) Skipped Details A forge search for "brain-mcp" returned nothing for this repo: the description mentions neither the brain nor brain-mcp, and the README said "accumulates learnings into a searchable brain" without ever using the string `brain-mcp` or its hostname. Both appeared only in CLAUDE.md and AGENTS.md — generated agent-context files, not the human front door. That is precisely the experience that generated infra#265. Since #91 part 2 decided the code stays in ingestion, discoverability has to be answered by naming. Adds a "Where brain-mcp lives" section: the ingress, the package, a table mapping what-you-are-looking-for to where-it-is (including that the brain content is a different repo), and why it is not standalone, with a pointer to the ADR for the full reasoning and the reversal trigger. Docs only. Repo description and topics are set through the forge API, not in this diff. Refs #94, #91.	2026-08-20 17:32:20 +02:00

Author

SHA1

Message

Date

mathias

ecbef33637

docs: point the README's forge links at git.d-ma.be (#94 )

CI / Lint / Test / Vet (pull_request) Successful in 37s

Details

CI / Mirror to GitHub (pull_request) Skipped

Details

The three forge links in README.md used http://gitea.d-ma.be, an alias
whose ingress was removed by infra#126. Verified rather than assumed: DNS
still resolves the name to the same IP, but a public repo returns 404
there and 200 on git.d-ma.be, with no redirect — so the links are broken,
not merely old.

Scope is README.md only. The dated files under docs/superpowers/plans and
specs are records of what was done in April/May 2026, when that hostname
was correct; rewriting them would falsify the record rather than fix a
link.

Note the agentsquad link still 404s unauthenticated — that repo is
private, which is expected and not a URL problem.

Refs #94, infra#126.

2026-08-20 17:37:05 +02:00

mathias

25b9b6683e

docs: name brain-mcp and say where its code lives (#94 )

CI / Lint / Test / Vet (pull_request) Successful in 37s

Details

CI / Mirror to GitHub (pull_request) Skipped

Details

A forge search for "brain-mcp" returned nothing for this repo: the
description mentions neither the brain nor brain-mcp, and the README said
"accumulates learnings into a searchable brain" without ever using the
string `brain-mcp` or its hostname. Both appeared only in CLAUDE.md and
AGENTS.md — generated agent-context files, not the human front door. That
is precisely the experience that generated infra#265.

Since #91 part 2 decided the code stays in ingestion, discoverability has
to be answered by naming.

Adds a "Where brain-mcp lives" section: the ingress, the package, a table
mapping what-you-are-looking-for to where-it-is (including that the brain
*content* is a different repo), and why it is not standalone, with a
pointer to the ADR for the full reasoning and the reversal trigger.

Docs only. Repo description and topics are set through the forge API, not
in this diff.

Refs #94, #91.

2026-08-20 17:32:20 +02:00

docs: name brain-mcp and say where its code lives (#94) #99