Research → Synthesis

Why do overlapping capability tags harm selection?

Grounded brief·strong·$1.15 USD

success

A · Answer

Why do overlapping capability tags harm selection?

grounded briefstrong_topical_matchpublic

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.

B · Evidence

grounded briefstrong_topical_matchpublic

Sources

Specialist versus generalist agents

Usefulness

0.81

strong
  • goalAlignment0.83· 25%
  • nonFiller1.00· 25%
  • specificity0.59· 20%
  • structure0.90· 15%
  • grounding0.66· 15%

No flags.

Band strong. Strongest dimensions hold; weakest: specificity 0.59, grounding 0.66.

C · Accountability

Each step names agentId@version and the role-scoped trust move. Boards: Reputation v1.

  • research

    agent:research.literature.v1@1.1.0

    0.65→0.66

    n=40

  • synthesize

    agent:research.synthesis.v1@1.0.0

    0.76→0.76

    n=50

D · Economics

Quote only — no settlement. Reputation v1 is a frozen read-only input. Contract.

1.15 USDecon-v0

base 1.00

  • Strong usefulness+0.15

Reward weights

  • agent:research.literature.v1@1.1.0research0.448rep 0.66 n=40 · modifier on
  • agent:research.synthesis.v1@1.0.0synthesize0.552rep 0.76 n=50 · modifier on

Reputation v1 — frozen. readOnly true. modifier applied.

New research
Advanced details

Ranking-test proof, retrieval diagnostics, step machine, claims, and raw audit. Not required to read the brief, agents, or quote.

  1. researchsuccess
  2. synthesizesuccess

Claims

  1. Overlapping Capability Tags collapse selection toward one dominant generalist, so specialists are never routed even when the task is narrow enough for higher precision.

    0.77 · doc:specialist-vs-generalist

  2. Distinct capability tags and step requirements force specialist selection; overlapping tags make multi-agent governance ceremony.

    0.72 · doc:specialist-vs-generalist

  3. Without Capability Separation on research versus synthesis, routing cannot select a specialist over the dominant generalist.

    0.76 · doc:specialist-vs-generalist

  4. A generalist that absorbs overlapping roles cuts coordination cost, but the output is shallower than specialist precision on the same narrow task.

    0.74 · doc:specialist-vs-generalist

Agents

  1. research

    agent:research.literature.v1@1.1.0

  2. synthesize

    agent:research.synthesis.v1@1.0.0

Retrieval path

Diagnostics

First drop: 3 · in candidates, not selected · corpus public

  1. 1Corpus
  2. 2Candidates
  3. 3Selected
  4. 4Synthesis

Provenance corpus membership · 5/5 found

  • doc:audit-event-modelfound
  • doc:agent-version-provenancefound
  • doc:source-lineagefound
  • doc:result-claim-provenancefound
  • doc:platform-provenance-capabilitiesfound

Query

Why do overlapping capability tags harm selection?

Top candidates · 9

  • doc:agent-version-provenance17

    selection · strong

  • doc:specialist-vs-generalist11

    overlapping · capability · tags · selection · strong · selected · in brief

  • doc:agent-cards-identity5

    capability · tags · strong

  • doc:multi-agent-synergy3

    capability

  • doc:orchestration-patterns3

    selection · strong

  • doc:platform-provenance-capabilities3

    selection · strong

  • doc:audit-event-model2

    selection · strong

  • doc:gpuaas-job-orchestration1

    selection · strong

  • doc:gpuaas-multitenant-failure1

    tags · strong

Selected

doc:specialist-vs-generalist

  1. CHAIN_SUBMITTED22:58:09Z

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

  2. WORKFLOW_SUBMITTED22:58:09Z

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

  3. CHAIN_STEP_STARTED22:58:09Z

    Step research

  4. CHAIN_STEP_DONEagent:research.literature.v1@1.1.022:58:09Z

    Step research success via agent:research.literature.v1@1.1.0

  5. RETRIEVAL_DEBUGGEDagent:research.literature.v1@1.1.022:58:09Z

    Retrieval hits · 1 selected

  6. CHAIN_STEP_STARTED22:58:09Z

    Step synthesize

  7. CHAIN_STEP_DONEagent:research.synthesis.v1@1.0.022:58:09Z

    Step synthesize success via agent:research.synthesis.v1@1.0.0

  8. CHAIN_DONE22:58:09Z

    Chain success

  9. WORKFLOW_DONEfinalagent:research.synthesis.v1@1.0.022:58:09Z

    Research → synthesis success

  10. USEFULNESS_SCOREDagent:research.synthesis.v1@1.0.022:58:09Z

    Usefulness strong (0.81)

  11. TRUST_UPDATEDagent:research.literature.v1@1.1.022:58:09Z

    Trust research agent:research.literature.v1@1.1.0 0.65 → 0.66

  12. TRUST_UPDATEDagent:research.synthesis.v1@1.0.022:58:09Z

    Trust synthesize agent:research.synthesis.v1@1.0.0 0.76 → 0.76

  13. economic_quotedagent:research.synthesis.v1@1.0.022:58:09Z

    Economic 1.15 USD

Canonical result

kind research.synthesis — brief, sources, evidenceStatus, trust, quote.

{
  "result": {
    "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?",
    "summary": "Synthesized 4 focused claims from 1 source.",
    "sources": [
      "doc:specialist-vs-generalist"
    ],
    "upstreamStep": "research",
    "privacy": "restricted",
    "evidenceStatus": "sufficient",
    "reason": "strong_topical_match",
    "corpusScope": "public"
  },
  "usefulness": {
    "flags": [],
    "rationale": "Band strong. Strongest dimensions hold; weakest: specificity 0.59, grounding 0.66.",
    "dimensions": {
      "grounding": 0.66,
      "nonFiller": 1,
      "structure": 0.9,
      "specificity": 0.59,
      "goalAlignment": 0.83
    },
    "scorerVersion": "1.0.0",
    "usefulnessBand": "strong",
    "usefulnessScore": 0.81
  },
  "trust": {
    "updates": [
      {
        "agentId": "agent:research.literature.v1",
        "agentVersion": "1.1.0",
        "role": "research",
        "trustStatus": "updated",
        "outcomeSignals": {
          "reliability": 1,
          "grounding": 0.8,
          "usefulness": null
        },
        "trustBefore": 0.647,
        "trustAfter": 0.656,
        "sampleSizeAfter": 40
      },
      {
        "agentId": "agent:research.synthesis.v1",
        "agentVersion": "1.0.0",
        "role": "synthesize",
        "trustStatus": "updated",
        "outcomeSignals": {
          "reliability": 1,
          "grounding": null,
          "usefulness": 0.81
        },
        "trustBefore": 0.759,
        "trustAfter": 0.763,
        "sampleSizeAfter": 50
      }
    ]
  },
  "ranking": null,
  "economic": {
    "quote": {
      "total": 1.15,
      "baseFee": 1,
      "currency": "USD",
      "adjustments": [
        {
          "code": "usefulness_strong",
          "label": "Strong usefulness",
          "amount": 0.15
        }
      ],
      "pricingVersion": "econ-v0"
    },
    "slice": {
      "label": "Economic v0 Slice A — frozen",
      "frozen": true,
      "version": "0.0.0",
      "pricingVersion": "econ-v0"
    },
    "rewards": [
      {
        "role": "research",
        "weight": 0.448,
        "agentId": "agent:research.literature.v1",
        "agentVersion": "1.1.0",
        "modifierApplied": true,
        "reputationScore": 0.656,
        "reputationSampleSize": 40
      },
      {
        "role": "synthesize",
        "weight": 0.552,
        "agentId": "agent:research.synthesis.v1",
        "agentVersion": "1.0.0",
        "modifierApplied": true,
        "reputationScore": 0.763,
        "reputationSampleSize": 50
      }
    ],
    "reputationInputs": {
      "label": "Reputation v1 — frozen",
      "applied": true,
      "version": "Reputation v1",
      "readOnly": true
    }
  },
  "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"
    ]
  },
  "corpusMembership": [
    {
      "id": "doc:audit-event-model",
      "found": true
    },
    {
      "id": "doc:agent-version-provenance",
      "found": true
    },
    {
      "id": "doc:source-lineage",
      "found": true
    },
    {
      "id": "doc:result-claim-provenance",
      "found": true
    },
    {
      "id": "doc:platform-provenance-capabilities",
      "found": true
    }
  ],
  "retrievalBreakpoint": "in_candidates_not_selected"
}