4건 · 관련도순
Choose multi-agent architectures using environment-first analysis, coordination pressure, commitment tuning, and knowledge levels. Use for autonomy design, protocol choice, and coordination failures. NOT for single-agent planning, centralized schedulers, or prompt-only swarms.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Frame multi-agent designs through explicit environment, autonomy, information, coordination, commitment, incentive, and verification assumptions. NOT for endorsing multi-agent architecture without need or claiming runtime correctness from conceptual methods.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Jason multi-agent platform implementing AgentSpeak(L) for practical BDI agent programming and deployment
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design discovery, directories, and guilds for agent swarms at scale. Use when agents need to find each other on a shared surface: capability indices, yellow-pages directories, whois/phonebook routing, reputation-aware discovery, and guild structures that scope trust. Covers the canonical prior art (FIPA Directory Facilitator, Contract Net, Chord/DHT, DNS-SD/Consul, EigenTrust, Greif's merchant guilds) and the failure modes (read-poverty, Sybil reset, Goodhart on rank, directory staleness, cold-start). Triggers: "agents can't find each other", "who owns this file/skill", "route a question to the right agent", "capability registry", "agent reputation", "guild / federation of fleets". NOT for issuing identities, granting authority, or automatically assigning work from a directory entry.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.