Research → synthesis: Why do overlapping capability tags harm selection?

{
  "kind": "research.note",
  "query": "Why do overlapping capability tags harm selection?",
  "claims": [
    {
      "claim": "Overlapping Capability Tags collapse selection toward one dominant generalist, so specialists are never routed even when the task is narrow enough for higher precision.",
      "source": "doc:specialist-vs-generalist",
      "confidence": 0.77
    },
    {
      "claim": "Distinct capability tags and step requirements force specialist selection; overlapping tags make multi-agent governance ceremony.",
      "source": "doc:specialist-vs-generalist",
      "confidence": 0.72
    },
    {
      "claim": "Without Capability Separation on research versus synthesis, routing cannot select a specialist over the dominant generalist.",
      "source": "doc:specialist-vs-generalist",
      "confidence": 0.76
    },
    {
      "claim": "A generalist that absorbs overlapping roles cuts coordination cost, but the output is shallower than specialist precision on the same narrow task.",
      "source": "doc:specialist-vs-generalist",
      "confidence": 0.74
    }
  ],
  "reason": "strong_topical_match",
  "privacy": "restricted",
  "sources": [
    "doc:specialist-vs-generalist"
  ],
  "summary": "Mapped 4 claims from 1 source: Specialist versus generalist agents. Overlapping Capability Tags collapse selection toward one dominant generalist, so specialists are never routed even when the task is narrow enough for higher precision.",
  "corpusScope": "public",
  "evidenceStatus": "sufficient",
  "retrievalDebug": {
    "query": "Why do overlapping capability tags harm selection?",
    "corpusHits": [
      "doc:agent-version-provenance",
      "doc:specialist-vs-generalist",
      "doc:agent-cards-identity",
      "doc:multi-agent-synergy",
      "doc:orchestration-patterns",
      "doc:platform-provenance-capabilities",
      "doc:audit-event-model",
      "doc:gpuaas-job-orchestration",
      "doc:gpuaas-multitenant-failure"
    ],
    "corpusScope": "public",
    "fallbackUsed": false,
    "topCandidates": [
      {
        "id": "doc:agent-version-provenance",
        "tags": [
          "provenance",
          "agent-version",
          "selection",
          "identity"
        ],
        "score": 17,
        "strong": true,
        "matchedTerms": [
          "selection"
        ]
      },
      {
        "id": "doc:specialist-vs-generalist",
        "tags": [
          "specialization",
          "routing",
          "capabilities"
        ],
        "score": 11,
        "strong": true,
        "matchedTerms": [
          "overlapping",
          "capability",
          "tags",
          "selection"
        ]
      },
      {
        "id": "doc:agent-cards-identity",
        "tags": [
          "agent-cards",
          "identity",
          "discovery",
          "registry"
        ],
        "score": 5,
        "strong": true,
        "matchedTerms": [
          "capability",
          "tags"
        ]
      },
      {
        "id": "doc:multi-agent-synergy",
        "tags": [
          "multi-agent",
          "synergy",
          "specialization",
          "handoff"
        ],
        "score": 3,
        "strong": false,
        "matchedTerms": [
          "capability"
        ]
      },
      {
        "id": "doc:orchestration-patterns",
        "tags": [
          "orchestration",
          "chain",
          "parallel",
          "quorum"
        ],
        "score": 3,
        "strong": true,
        "matchedTerms": [
          "selection"
        ]
      },
      {
        "id": "doc:platform-provenance-capabilities",
        "tags": [
          "provenance",
          "platform",
          "capabilities",
          "audit",
          "versioning"
        ],
        "score": 3,
        "strong": true,
        "matchedTerms": [
          "selection"
        ]
      },
      {
        "id": "doc:audit-event-model",
        "tags": [
          "provenance",
          "audit",
          "events",
          "traceability"
        ],
        "score": 2,
        "strong": true,
        "matchedTerms": [
          "selection"
        ]
      },
      {
        "id": "doc:gpuaas-job-orchestration",
        "tags": [
          "gpuaas",
          "compute",
          "orchestration"
        ],
        "score": 1,
        "strong": true,
        "matchedTerms": [
          "selection"
        ]
      },
      {
        "id": "doc:gpuaas-multitenant-failure",
        "tags": [
          "gpuaas",
          "compute",
          "allocation"
        ],
        "score": 1,
        "strong": true,
        "matchedTerms": [
          "tags"
        ]
      }
    ],
    "guardTriggered": false,
    "selectedSources": [
      "doc:specialist-vs-generalist"
    ]
  }
}

{
  "kind": "research.synthesis",
  "brief": "Overlapping Capability Tags collapse selection toward one dominant generalist, so specialists are never routed even when the task is narrow enough for higher precision. Distinct Capability Tags and step requirements force specialist selection; overlapping tags make multi-agent governance ceremony. Without Capability Separation on research versus synthesis, routing cannot select a specialist over the dominant generalist. A generalist that absorbs overlapping roles cuts coordination cost, but the output is shallower than specialist precision on the same narrow task. Sources: doc:specialist-vs-generalist — Specialist versus generalist agents.",
  "query": "Why do overlapping capability tags harm selection?",
  "reason": "strong_topical_match",
  "privacy": "restricted",
  "sources": [
    "doc:specialist-vs-generalist"
  ],
  "summary": "Synthesized 4 focused claims from 1 source.",
  "corpusScope": "public",
  "upstreamStep": "research",
  "evidenceStatus": "sufficient"
}