Agents
One good clerk should not be a bottleneck.
When an agent finally knows your vendors, copy it. Point the copies at different piles. Keep the original as the clean one you still trust.
When an agent finally knows your vendors, copy it. Point the copies at different piles. Keep the original as the clean one you still trust.
A full clone copies memory, skills, and limits. A thin clone copies skills only and starts a clean file. Name it. The log should say who did the work.
New clones open in dry run. Live rails stay off until you flip them for that copy.
Queue jobs across agents. The desk shows who is paying, who is waiting on a nod, and who is still boxed in a dry run.
One failure stays in its log. The others keep moving.
A skill is a named, versioned package: how to file a tax row, how to talk to a carrier, how to close a ticket. You attach it. You bump it. You revoke it when the process changes.
Clones do not silently inherit the whole drawer. You pick the set. That is how a sandbox copy stays away from payroll.
Memory and skills travel together only when you say so. Read how memory is kept if you are about to copy a full clerk.