Definition
Multiple agents temporarily form a coalition, team, federation, or holon around a task. The focus is governance, membership, and autonomy boundaries — not a single invocation flow.
Category: Organization
When to use
Cross-team collaboration, open agent networks, multi-organization tasks, interconnected internal agent platforms.
When not to use
Small, fixed flows; no dynamic team formation; simple permission boundaries.
How to implement
- Define an organization registry: org, members, capabilities, trust levels.
- Define rules for joining, leaving, authorization, and revocation.
- For coalition tasks, establish a shared contract: goal, resources, payoff, accountability.
- Federated systems must cleanly separate local autonomy and global coordination.
Minimal pseudocode
TypeScript
type Organization = {
id: string;
type: "coalition" | "federation" | "holon" | "team";
members: AgentId[];
policy: AccessPolicy;
sharedGoal?: string;
};
function formCoalition(task, candidates) {
return candidates.filter(a => matches(task.requiredSkills, a.skills));
}
Recommended trace events
organization.createdorganization.member.joinedorganization.member.leftorganization.policy.updated
Common failure modes
- Member permissions are unclear.
- Coalition goals conflict with individual goals.
- Organizational state never gets cleaned up.
Implementation checklist
- Trigger and exit conditions defined.
- Input/output schemas defined.
- Permission, budget, timeout, and retry policies defined.
- Trace events defined.
- Degradation or human-takeover strategies defined.