Collab Modes

This section explains how matic turns agent collaboration into an explicit runtime contract on every work item. The selected mode determines who can write, who can approve, how concurrency is shaped, and when the daemon must pause, block, or escalate execution. Read these pages to decide whether a task should stay with one owner, add a co-agent, fan out into parallel slices, or run under named oversight.

Solo

The baseline single-owner mode: one persistent agent holds write authority, while helpers, tools, and inbox traffic stay outside named collaborator state.

Pair

How two persistent agents share one work item and workspace under a lead/co-agent contract, with filesystem mutex rules for coordinated concurrent writes.

Supervised

How execution runs under a named supervisor whose brief, review, and HITL approvals gate lifecycle transitions without taking over workspace writes.

Swarm

How a parent agent fans independent slices out across agents, helpers, or both, then aggregates the results back under one accountable run.

Mode Selection Policy

How matic resolves the mode during planning by cascading through policies, squad templates, team defaults, role-slot metadata, and per-item overrides.

Mode Transitions

The transition rules for entering, acknowledging, terminating, and chaining modes mid-run, including ownership changes and required agent messages.

Runtime Enforcement

How the daemon, runtime, and guardrails turn mode choice into enforceable behavior across write permissions, pair locks, supervised checkpoints, and policy violations.