When a Workshop Is Earned
A dedicated workshop is earned when the domain needs ownership the generic row cannot express honestly. It may need new lifecycle states, durable entities with their own relationships, a specialized attachment store, interactive authoring or review surfaces, domain-specific verification, or production operations that deserve a health contract.
The evidence should appear as repeated friction, not an imaginative feature list. Operators keep writing the same long companion protocol, manually reconciling domain state, or asking the generic engine to add exceptions named after one pipeline. Those are measurements that the row is carrying a product.
Graduation does not mean copying Crucible. The new workshop should consume or extend the canonical queue kernel proven by siblings, while owning only its delta. Copying the engine creates coupled forks whose review and claim semantics drift—the exact cost the root class exists to prevent.
The relationship afterward stays explicit. Crucible may retain old records and stop accepting new work for the graduated shape by archiving the pipeline. The new product owns future lifecycle. A migration note links the boundary without pretending history moved.
Name the Delta Before Birth
Write one paragraph containing only what the new workshop owns that the generic kernel does not: entities, states, UI, policies, and operations. If the paragraph is mostly branding or template text, do not birth it.
Then identify the canonical layers it will reuse. Graduation is specialization at the boundary, not permission to fork shared mechanics.