Architecture X3: avoid, not reject, search-then-dispatch meta-tools
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m52s
CI / e2e (pull_request) Successful in 4m55s

A special-purpose MCP server that works that way may still be worth it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
This commit is contained in:
dongarandClaude Opus 5.5 committed 2026-10-13 19:11:49 +00:00
1 parent 5ea6e4610f
commit e2d55e1caf
1 file changed
+3 -1
+3 -1
View File
@@ -974,8 +974,10 @@ so every upstream action traces to one agent.
- **One instance per (service, site, privilege),** each with its own credentials, so - **One instance per (service, site, privilege),** each with its own credentials, so
a wrong-site or wrong-privilege action needs a tool that isn't mounted. a wrong-site or wrong-privilege action needs a tool that isn't mounted.
- **Per-task tool profiles** mount only what a work item's scope needs. - **Per-task tool profiles** mount only what a work item's scope needs.
- **Rejected: search-then-dispatch meta-tools** over large catalogues (extra round - **Avoid search-then-dispatch meta-tools** over large catalogues (extra round
trips for a local driver, opaque arguments, a tool list that defeats caching). trips for a local driver, opaque arguments, a tool list that defeats caching).
A special-purpose server that works that way may still be worth it, as a
deliberate exception.
### X4. Images, VMs and restarts ### X4. Images, VMs and restarts