Staffing

Staffing is the process by which matic composes a team during the Plan phase of the work lifecycle — matching available agents to required roles, evaluating capability and bandwidth through probes, and spawning new agents when gaps exist. It is probe-driven rather than prompt-driven: selection decisions are grounded in each agent's declared competence, confidence, and current load, not runtime inference. No team engages until a human approves its composition.

Staffing Process

The end-to-end sequence from work item analysis through team confirmation — how matic evaluates requirements, queries probes, resolves gaps, and hands off to human approval.

Roles and Assignment

How roles are defined for a project engagement, assigned to agents, and scoped to that engagement's duration — roles are not part of an archetype, they are instantiated at staffing time.

Probe-Driven Selection

How capability, confidence, bandwidth, and availability probes are evaluated to rank and filter candidates — the DSL used to match task requirements against agent self-models.

Competence and Performance

How historical coverage eval scores (floor-adherence and ceiling-adherence) inform staffing decisions and determine whether HITL gates are required during a new engagement.

Gap Detection and Spawning

How matic identifies capability gaps — no available agent matches — and triggers archetype-based spawning subject to Charter and budget constraints.

Squad Templates

Saved, reusable team compositions that specify archetype positions, roles, and minimum probe requirements; when a position is unfilled, matic spawns from the specified archetype.

Team Composition Approval

The HITL gate at the end of staffing — how the proposed roster is surfaced to the project owner, what feedback is actionable, and what confirms the team to active status.