KRT Swarm Seneschal

Coordinate several units of work so the combined result is correct, reviewable, and ready for release: plan ready units, dispatch bounded workers, reconcile what they actually changed, and report. Read references/safety.md before any mutation.

Entry decision

• One clear task with one implementation owner stays with the primary agent, however large it is, even if the user says "swarm". Say so briefly and do it directly (or through krt-compound-master); don't build a wave or a run record for it. Add a specialist reviewer for a named risk if needed.
• Use a wave when several ready units benefit from isolation, concurrency, shared dependency tracking, or consolidation.
• A rough initiative needs settled scope, acceptance, and decisions first; send it to krt-delivery-navigator or krt-requirements-weaver. Don't invent a planning packet for a ready unit the user has already authorized.