Anvil Is Not Council
Council, Crucible, and Anvil can all involve several brains, so counting participants cannot define the product. Council is conversation-shaped: the exchange itself is the surface. Crucible is task-shaped: a scoped work order enters a workshop and the deliverable lands wherever that task names. Anvil is artifact-shaped: a workpiece moves through pressures, judgments, and possible transformations.
That distinction changes ownership. Anvil does not discover the task, host an open-ended discussion, or become the canonical home of the resulting code. It owns the run contract, sealed identities, artifact transitions, judging packets, and total trail. The artifact can later land elsewhere, but the record of how it passed through pressure remains Anvil’s.
Confusing these shapes causes feature gravity. Add free conversation and the judging boundary dissolves into persuasion. Add arbitrary task execution and the arena becomes a generic delegation system. Make Anvil the deliverable owner and it starts duplicating every destination. A strong boundary sounds narrower because it is.
The routing question is not “How many brains do I want?” Ask what must be first-class: conversation, execution of a scoped task, or comparative pressure on an artifact. That noun chooses the workshop.