KRT Muse Artificer

Hand one ready implementation unit to Muse Code and bring back a validated report. The caller (usually krt-swarm-seneschal, sometimes the user directly) chooses the unit, creates the worktree, and judges the result.

Good assignments

Muse is the preferred worker for fast units: a confirmed edit path, exact owned files, closed decisions, and named checks (a bug fix with a known cause, a mechanical change, a targeted test, a bounded UI tweak). Consider it for standard units where only local implementation choices remain: focused feature work, a contained refactor, tests for specified behavior.

Don't send ambiguous diagnosis, architecture, auth, data, security, migrations, public contracts, concurrency, or production decisions; those need a deeper worker and a human decision. If Muse or its model is unavailable, the caller picks another worker before dispatch. Never swap models silently.