# AIチーム／AI組織論

CURRENT_STATUS: UNKNOWN
OBSERVATION: SPEC_ONLY
FRESHNESS: UNKNOWN
PAGE_TYPE: reference
CANONICAL_URL: /tools/ea-037-ai-ai
CLAIM_IDS: none
EVIDENCE_IDS: EVD-EA-037-URL-A3AFC1E8C7C2, EVD-EA-037-URL-E07B731A310B, EVD-EA-037-URL-F6FF5B444FF6, EVD-EA-037-URL-A92F872E85E1, EVD-EA-037-URL-5128128A6A0D, EVD-EA-037-URL-D00A52DB3BD0, EA-037-R11-RESEARCH, EA-037-R11-WEB-READBACK
UNKNOWN_IDS: EA-037-UNKNOWN-01, EA-037-UNKNOWN-02, EA-037-UNKNOWN-CURRENTNESS
OPS_IDS: none

## Summary
「複数AIを組み合わせれば自動的に性能が上がるわけではない。独立して並列化できる高価値taskではmulti-agentが有効な場合がある一方、共有contextや依存関係が多いtaskではcoordination
costとfailure
surfaceが増える。AIチームは役割・権限・state所有・handoff・成果物・停止条件を明示したcontractとして設計し、single-agentまたはworkflow
baselineと比較して採用する。」

## Current judgment
AIチームは ORCHESTRATION_TOPOLOGY + ROLE_AUTHORITY +
TASK_OWNERSHIP + STATE_OWNERSHIP + MESSAGE/ARTIFACT CONTRACT + HANDOFF +
HUMAN_GATE + STOP/RECOVERY
として定義する。patternごとの依存関係・並列性・control
transfer・共有context量を分離する。Anthropicの+90.2%は特定internal
research
evalであり一般保証ではない。A2A適合だけでも業務責任・権限妥当性・品質は保証されない。人間/組織ownerとagent
execution roleを分離する。

## Scope
Enterprise AI Core / agent architecture / organization
overlay / interoperability / governance / implementation / evaluation。

## Confirmed
- AIチームは ORCHESTRATION_TOPOLOGY + ROLE_AUTHORITY +
TASK_OWNERSHIP + STATE_OWNERSHIP + MESSAGE/ARTIFACT CONTRACT + HANDOFF +
HUMAN_GATE + STOP/RECOVERY
として定義する。patternごとの依存関係・並列性・control
transfer・共有context量を分離する。Anthropicの+90.2%は特定internal
research
evalであり一般保証ではない。A2A適合だけでも業務責任・権限妥当性・品質は保証されない。人間/組織ownerとagent
execution roleを分離する。

## UNKNOWN
- EA-037-UNKNOWN-01: / STOP_CONDITION: provider横断・同条件multi-agent vs
single-agent benchmark、組織横断A2A incident/case study、shared-state
ownership標準schema、法的accountability上のAI
role表現はUNKNOWN。必要な証拠・反証・failure
envelope・availability・評価・safe
wordingが揃ったためEA-037はBOUNDED_CLOSE。
- EA-037-UNKNOWN-02: preserve provider-cross benchmark, cross-organization incident/case study, shared-state ownership standard schema, legal accountability role expression.
- EA-037-UNKNOWN-CURRENTNESS: 外部根拠の再確認日がcanonical body/control-planeで確定していないため、currentnessはUNKNOWNとして保持する。日付を推測補完しない。

## Evidence
- EVD-EA-037-URL-A3AFC1E8C7C2 (RESEARCH): https://www.anthropic.com/engineering/multi-agent-research-system — https://www.anthropic.com/engineering/multi-agent-research-system
- EVD-EA-037-URL-E07B731A310B (RESEARCH): https://learn.microsoft.com/en-us/agent-framework/workflows/orchestrations/ — https://learn.microsoft.com/en-us/agent-framework/workflows/orchestrations/
- EVD-EA-037-URL-F6FF5B444FF6 (RESEARCH): https://devblogs.microsoft.com/agent-framework/agent-frameworks-orchestration-patterns-reach-1-0/ — https://devblogs.microsoft.com/agent-framework/agent-frameworks-orchestration-patterns-reach-1-0/
- EVD-EA-037-URL-A92F872E85E1 (RESEARCH): https://a2a-protocol.org/dev/blog/2026/03/12/a2a-protocol-ships-v10-production-ready-standard-for-agent-to-agent-communication/ — https://a2a-protocol.org/dev/blog/2026/03/12/a2a-protocol-ships-v10-production-ready-standard-for-agent-to-agent-communication/
- EVD-EA-037-URL-5128128A6A0D (RESEARCH): https://a2a-protocol.org/latest/topics/key-concepts/ — https://a2a-protocol.org/latest/topics/key-concepts/
- EVD-EA-037-URL-D00A52DB3BD0 (RESEARCH): https://a2a-protocol.org/latest/roadmap/ — https://a2a-protocol.org/latest/roadmap/
- EA-037-R11-RESEARCH (RESEARCH): EA-037 監査済みresearch / canonical revision binding
- EA-037-R11-WEB-READBACK (IMPL): EA-037 Web body identity / canonical readback

## Failure / limits
single-agent/決定論workflowで十分なtaskではcoordination、latency、token/cost、observability、recoveryが悪化し得る。race/duplicate
side effect、handoff loss、circular delegation、manager
bottleneck、shared-state contamination、authority escalation、partial
completion、version driftをfailure classとする。
## Practice
Microsoft
patternはSDK/version/runtime依存。A2Aはv1.0 current stable
baselineだがendpoint/auth/supportedInterfaces/extensions/tenant/network
policyは実装別確認。Anthropic内部architectureは任意tenant/APIで同一構成を設定できることを意味しない。
## Practice
PROPOSAL AI_TEAM_CONTRACT {team_id, objective,
topology, agent_id, role, allowed_tasks, authority_scope, tools,
data_scope, task_owner, state_owner, input_contract,
output_artifact_contract, handoff_edges, approval_gates,
concurrency_policy, idempotency_policy, stop_conditions,
escalation_owner, retry_budget, cost_budget, trace_ids,
version_manifest}。deterministic workflow→single agent+tools→bounded
specialists/handoff→concurrent/managerの順に必要性が観測された場合だけ複雑化。
## Practice
同一golden taskをbaselineと比較しaccepted
completion、coverage、duplicate-work、handoff loss、wrong-owner
routing、conflicting action、tool calls、tokens/cost、p50/p95
latency、human intervention、recovery successを測る。
## Practice
least
privilegeをagent単位に割当てshared
credentialを既定にしない。外部writeはowner/approval/idempotency/reconciliationを要求。message/artifactへdata
minimization/provenanceを適用しtask/handoff/tool
actionをcorrelation可能にする。fan-out/token/cost上限、circular
delegation検知、kill/escalation経路を持つ。
## Practice
EA-006、EA-020、EA-035、EA-036とcross-reference。AI_TEAM_CONTRACTをEA-029
template packへ接続。publication時にA2A current
versionを再pinし、provider mappingではplan/region/admin/tenant
gateを別採集。
## Practice
Microsoft Agent Framework orchestration patterns are 1.0 across Python/.NET at audit; A2A v1.0 stable baseline; Sep 15 roadmap v1.1 items remain near-term work. Anthropic +90.2% internal research-eval gain and ~15x chat-token cost remain provider-specific SOURCE_REPORT, not a general guarantee.
## Practice
A2A conformance != business responsibility/authorization/quality; Microsoft/Anthropic patterns are not universal taxonomy; human/organization owner distinct from agent execution role.
## WHY_THIS_MATTERS_TO_UPDATE
複数agentを置くだけでは重複、責任境界消失、handoff
context欠落、並列副作用、停止条件不在、cost/token増幅が起こる。将来版ではAIチームを擬人的役職表ではなくtask
decomposition、ownership、message/artifact contract、authority、shared
state、human escalation、evaluationを持つ運用構造として扱う。

## SCOPE_ROUTING
Enterprise AI Core / agent architecture / organization
overlay / interoperability / governance / implementation / evaluation。

## CLAIM_OR_RESEARCH_QUESTION
multi-agentをsingle-agent/workflowより優先する条件は何か。role/authority/state/handoff/artifact/stop-escalationをどう記録するか。

## EVIDENCE TABLE
- Anthropic, "How we built our multi-agent research
system", 2025-06-13, accessed 2026-09-25,
https://www.anthropic.com/engineering/multi-agent-research-system ---
SOURCE_REPORT+PRODUCT_VOLATILE,
support+limit。orchestrator-worker、internal research eval
+90.2%、multi-agent約15x chat tokens、共有context/依存taskの不適合。 -
Microsoft, "Workflow orchestrations in Agent Framework", accessed
2026-09-25,
https://learn.microsoft.com/en-us/agent-framework/workflows/orchestrations/
--- VERIFIED_SPEC+PRODUCT_VOLATILE。Sequential/Concurrent/Handoff/Group
Chat/Magentic、HITL。 - Microsoft Agent Framework, "Agent Framework's
Orchestration Patterns Reach 1.0", 2026-07-08, accessed 2026-09-25,
https://devblogs.microsoft.com/agent-framework/agent-frameworks-orchestration-patterns-reach-1-0/
--- VERIFIED_SPEC+PRODUCT_VOLATILE。Python
agent-framework-orchestrations 1.0.0。 - A2A Protocol, "A2A Protocol
Ships v1.0", 2026-03-12, accessed 2026-09-25,
https://a2a-protocol.org/dev/blog/2026/03/12/a2a-protocol-ships-v10-production-ready-standard-for-agent-to-agent-communication/
--- VERIFIED_SPEC。v1.0、multi-protocol/version
negotiation/multi-tenancy/signed Agent Cards、MCPとA2Aの層分離。 - A2A
Protocol, "Core Concepts", accessed 2026-09-25,
https://a2a-protocol.org/latest/topics/key-concepts/ ---
VERIFIED_SPEC。Agent Card/Task/Message/Part/Artifact/contextId/auth。 -
A2A Protocol, "Roadmap", updated 2026-09-15, accessed 2026-09-25,
https://a2a-protocol.org/latest/roadmap/ ---
VERIFIED_SPEC+PRODUCT_VOLATILE, limit。v1.1 task timeline/event
filtering/working-state messages、BiDi
streaming、elicitation/multi-turnはnear-term initiative。

## FINDINGS
AIチームは ORCHESTRATION_TOPOLOGY + ROLE_AUTHORITY +
TASK_OWNERSHIP + STATE_OWNERSHIP + MESSAGE/ARTIFACT CONTRACT + HANDOFF +
HUMAN_GATE + STOP/RECOVERY
として定義する。patternごとの依存関係・並列性・control
transfer・共有context量を分離する。Anthropicの+90.2%は特定internal
research
evalであり一般保証ではない。A2A適合だけでも業務責任・権限妥当性・品質は保証されない。人間/組織ownerとagent
execution roleを分離する。

## LIMITS / COUNTEREVIDENCE / FAILURE ENVELOPE
single-agent/決定論workflowで十分なtaskではcoordination、latency、token/cost、observability、recoveryが悪化し得る。race/duplicate
side effect、handoff loss、circular delegation、manager
bottleneck、shared-state contamination、authority escalation、partial
completion、version driftをfailure classとする。

## AVAILABILITY_GATES
Microsoft
patternはSDK/version/runtime依存。A2Aはv1.0 current stable
baselineだがendpoint/auth/supportedInterfaces/extensions/tenant/network
policyは実装別確認。Anthropic内部architectureは任意tenant/APIで同一構成を設定できることを意味しない。

## IMPLEMENTATION_STATE
PROPOSAL AI_TEAM_CONTRACT {team_id, objective,
topology, agent_id, role, allowed_tasks, authority_scope, tools,
data_scope, task_owner, state_owner, input_contract,
output_artifact_contract, handoff_edges, approval_gates,
concurrency_policy, idempotency_policy, stop_conditions,
escalation_owner, retry_budget, cost_budget, trace_ids,
version_manifest}。deterministic workflow→single agent+tools→bounded
specialists/handoff→concurrent/managerの順に必要性が観測された場合だけ複雑化。

## BENCHMARK_OR_EVAL
同一golden taskをbaselineと比較しaccepted
completion、coverage、duplicate-work、handoff loss、wrong-owner
routing、conflicting action、tool calls、tokens/cost、p50/p95
latency、human intervention、recovery successを測る。

## SECURITY / PRIVACY / AUDIT / COST / OPERABILITY
least
privilegeをagent単位に割当てshared
credentialを既定にしない。外部writeはowner/approval/idempotency/reconciliationを要求。message/artifactへdata
minimization/provenanceを適用しtask/handoff/tool
actionをcorrelation可能にする。fan-out/token/cost上限、circular
delegation検知、kill/escalation経路を持つ。

## SAFE_WORDING_FOR_FUTURE_BOOK
「複数AIを組み合わせれば自動的に性能が上がるわけではない。独立して並列化できる高価値taskではmulti-agentが有効な場合がある一方、共有contextや依存関係が多いtaskではcoordination
costとfailure
surfaceが増える。AIチームは役割・権限・state所有・handoff・成果物・停止条件を明示したcontractとして設計し、single-agentまたはworkflow
baselineと比較して採用する。」

## UPDATE_WORK_HANDOFF
EA-006、EA-020、EA-035、EA-036とcross-reference。AI_TEAM_CONTRACTをEA-029
template packへ接続。publication時にA2A current
versionを再pinし、provider mappingではplan/region/admin/tenant
gateを別採集。

## OPEN_UNKNOWN
/ STOP_CONDITION: provider横断・同条件multi-agent vs
single-agent benchmark、組織横断A2A incident/case study、shared-state
ownership標準schema、法的accountability上のAI
role表現はUNKNOWN。必要な証拠・反証・failure
envelope・availability・評価・safe
wordingが揃ったためEA-037はBOUNDED_CLOSE。

## CURRENTNESS
Microsoft Agent Framework orchestration patterns are 1.0 across Python/.NET at audit; A2A v1.0 stable baseline; Sep 15 roadmap v1.1 items remain near-term work. Anthropic +90.2% internal research-eval gain and ~15x chat-token cost remain provider-specific SOURCE_REPORT, not a general guarantee.

## BOUNDARY
A2A conformance != business responsibility/authorization/quality; Microsoft/Anthropic patterns are not universal taxonomy; human/organization owner distinct from agent execution role.

## OPEN_UNKNOWN
preserve provider-cross benchmark, cross-organization incident/case study, shared-state ownership standard schema, legal accountability role expression.

NEXT: /agent/start.json
STOP: This is a knowledge projection, not an execution order.