Synthesize a protocol brief from the research notes

Ranking

Hard filters first (including MCP tool policy), then weighted score. Policy denials are eligibility failures, not score penalties.

Events

21

Policy evaluated

0

Policy denied

0

1. TASK_SUBMITTED2026-09-28T22:58:09.681Zschema 1.0

   Synthesize a protocol brief from the research notes

2. RANKED2026-09-28T22:58:09.695Zschema 1.0

   Selected protocol-synthesis (agent:research.synthesis.v1@1.0.0) score 99.9 using balanced role synthesize. Best match id "synthesis"; outcomeTrust 0.76 n=49 weight 6 base 95.3 effective 99.9; audit passed.

   agent:research.synthesis.v1@1.0.0

3. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.697Zschema 1.0

   No capability, skill, tag, or keyword matched the task requirements

   agent:orchestrator.core.v1@0.9.0

4. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.700Zschema 1.0

   No capability, skill, tag, or keyword matched the task requirements

   agent:pricing.engine.v1@0.8.2

5. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.702Zschema 1.0

   No capability, skill, tag, or keyword matched the task requirements

   agent:contract.escrow.v1@0.7.0

6. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.705Zschema 1.0

   No capability, skill, tag, or keyword matched the task requirements

   agent:robot.bay.arm.v1@1.0.0

7. HARD_FILTER_REJECTEDinactive2026-09-28T22:58:09.707Zschema 1.0

   Status is maintenance — only active agents are eligible

   agent:compute.market.v1@0.6.0

8. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.710Zschema 1.0

   No capability, skill, tag, or keyword matched the task requirements

   agent:devtools.docsreader.v1@1.0.0

9. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.712Zschema 1.0

   No capability, skill, tag, or keyword matched the task requirements

   agent:research.gpuaas.v1@1.0.0

10. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.715Zschema 1.0

    No capability, skill, tag, or keyword matched the task requirements

    agent:devtools.issuewright.v1@1.0.0

11. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.717Zschema 1.0

    No capability, skill, tag, or keyword matched the task requirements

    agent:research.literature.v1@1.1.0

12. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.719Zschema 1.0

    No capability, skill, tag, or keyword matched the task requirements

    agent:memory.vault.v1@1.1.0

13. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.722Zschema 1.0

    No capability, skill, tag, or keyword matched the task requirements

    agent:devtools.mystery.v1@1.0.0

14. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.724Zschema 1.0

    No capability, skill, tag, or keyword matched the task requirements

    agent:privacy.router.v1@0.5.1

15. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.727Zschema 1.0

    No capability, skill, tag, or keyword matched the task requirements

    agent:research.provenance.v1@1.0.0

16. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.729Zschema 1.0

    No capability, skill, tag, or keyword matched the task requirements

    agent:devtools.repoadmin.v1@1.0.0

17. HARD_FILTER_REJECTEDno_capability2026-09-28T22:58:09.731Zschema 1.0

    No capability, skill, tag, or keyword matched the task requirements

    agent:trust.score.v1@0.4.0

18. SELECTED2026-09-28T22:58:09.734Zschema 1.0

    Winner protocol-synthesis (agent:research.synthesis.v1@1.0.0) effective 99.9.

    agent:research.synthesis.v1@1.0.0

19. ROUTED2026-09-28T22:58:09.741Zschema 1.0

    Routed to https://agents.example/protocol-synthesis via a2a.

    agent:research.synthesis.v1

20. RESULT_RECEIVED2026-09-28T22:58:09.756Zschema 1.0

    Result success from agent:research.synthesis.v1.

    agent:research.synthesis.v1

21. TASK_DONEfinal2026-09-28T22:58:09.764Zschema 1.0

    Task success by agent:research.synthesis.v1.

    agent:research.synthesis.v1

Result

Standardized agent result. Stored by taskId; retries keep prior attempts.

{
  "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"
}