Skip to content
C.W.K.
Stream
Lesson 04 of 05 · published

When a Workshop Is Earned

~12 min · product-boundary, graduation, domain-state, operations

Level 0Cold Vessel
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

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.

A workshop is earned when the row can no longer carry the craft cleanly. Domain-specific interaction, lifecycle, visualization, or verification may need its own surface, but the new workshop should still delegate common claims and receipts to the kernel. Graduation separates craft without copying authority.

Code

Describe a workshop delta explicitly·python
workshop_delta = {
    "entities": ["review_thread", "evidence_packet"],
    "states": ["awaiting-human", "reconciled"],
    "ui": ["side-by-side evidence review"],
    "operations": ["domain health and retention policy"],
}
assert any(workshop_delta.values())
assert "queue_engine_copy" not in workshop_delta
print(workshop_delta)

External links

Exercise

Take one overgrown pipeline and write its measured friction, proposed workshop delta, reused canonical layers, and migration boundary.
Hint
If the delta cannot be stated without “more control,” the evidence is not ready.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.