Build the Ladder
The full Crucible design is a ladder, not a funnel that demands every task climb. A unique scoped task enters oneoff and may remain there forever. A second comparable occurrence permits a named pipeline. Repeated domain pressure may later earn a dedicated workshop. Each step adds permanent structure only after evidence pays for it.
Moving upward changes ownership. oneoff stores task-specific notes under shared policy. A named row owns reusable template and stage choices. A workshop owns domain lifecycle, state, UI, materials, and operations while reusing the kernel. Skipping a level hides an untested assumption inside expensive software.
Moving sideways is allowed. Two occurrences may produce two different oneoffs. A named pipeline may split when task shapes diverge. A graduated workshop may still send unrelated scoped work back through Crucible. The ladder is a decision model, not an organizational rank.
The final proof is a record of why the current level is sufficient. That record should name occurrences, shared behavior, unresolved differences, current friction, and the next signal that would reopen the decision. Architecture becomes revisable without becoming arbitrary.
Capstone: Oneoff to Product
Choose a real task shape and write three artifacts: its first oneoff brief, a comparison against the second occurrence, and either a named row or a reason not to promote. Then write the exact domain pressure that would be required before a workshop birth.
Do not optimize for reaching the top. The best answer may be oneoff forever. A ladder is useful because it gives restraint a positive, evidence-backed name.