Charter: ADR-0012 rule 4 (hide automated mechanism) · smallest/safest of the ADR-0012 cleanup items
Problem
brain_index is exposed as a model-facing MCP verb, but its own description says it is auto-called after brain_write. An auto-called operation surfaced as a caller verb is pure cognitive load with no decision behind it — every model reading the toolset has to read it, determine it's not a thing it should call, and move on. That violates ADR-0012 rule 4.
What to do
Remove brain_index (Map-of-Content / _index.md regeneration) from the model-facing MCP toolset.
Keep the capability itself — it still needs to run (auto after writes, and as an admin/maintenance op). Just not as an LLM-callable verb. Options: keep it as an internal function only; or expose it on an admin/CLI surface (dma-cli) not the MCP tool list.
Confirm nothing in the current SKILLs / agents actually calls brain_index directly (grep the harnesses); if something does, that's a mis-use to fix, not a reason to keep it surfaced.
Acceptance
brain_index no longer appears in the model-facing MCP tool list
Auto-index-after-write still happens (verify with a brain_write → index refreshed)
Manual/admin invocation still possible via a non-LLM surface
**Charter:** ADR-0012 rule 4 (hide automated mechanism) · smallest/safest of the ADR-0012 cleanup items
## Problem
`brain_index` is exposed as a model-facing MCP verb, but its own description says it is **auto-called after `brain_write`**. An auto-called operation surfaced as a caller verb is pure cognitive load with no decision behind it — every model reading the toolset has to read it, determine it's not a thing it should call, and move on. That violates ADR-0012 rule 4.
## What to do
- Remove `brain_index` (Map-of-Content / `_index.md` regeneration) from the **model-facing MCP toolset**.
- Keep the capability itself — it still needs to run (auto after writes, and as an admin/maintenance op). Just not as an LLM-callable verb. Options: keep it as an internal function only; or expose it on an admin/CLI surface (`dma-cli`) not the MCP tool list.
- Confirm nothing in the current SKILLs / agents actually calls `brain_index` directly (grep the harnesses); if something does, that's a mis-use to fix, not a reason to keep it surfaced.
## Acceptance
- [ ] `brain_index` no longer appears in the model-facing MCP tool list
- [ ] Auto-index-after-write still happens (verify with a `brain_write` → index refreshed)
- [ ] Manual/admin invocation still possible via a non-LLM surface
- [ ] No caller (SKILL/agent) left calling it directly
- [ ] `task check` green
## Related
- ADR-0012 (rule 4) · sibling cleanup issues (legacy-param removal; brain consolidations under ADR-0009)
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.
Charter: ADR-0012 rule 4 (hide automated mechanism) · smallest/safest of the ADR-0012 cleanup items
Problem
brain_indexis exposed as a model-facing MCP verb, but its own description says it is auto-called afterbrain_write. An auto-called operation surfaced as a caller verb is pure cognitive load with no decision behind it — every model reading the toolset has to read it, determine it's not a thing it should call, and move on. That violates ADR-0012 rule 4.What to do
brain_index(Map-of-Content /_index.mdregeneration) from the model-facing MCP toolset.dma-cli) not the MCP tool list.brain_indexdirectly (grep the harnesses); if something does, that's a mis-use to fix, not a reason to keep it surfaced.Acceptance
brain_indexno longer appears in the model-facing MCP tool listbrain_write→ index refreshed)task checkgreenRelated