62
FINAL PRACTICE · COURSE COMPLETION
Capstone — explain, run and diagnose Hansen without prompts
This is not a memory test for node names. The final assessment asks one question: have you developed a transferable way of thinking about ComfyUI that works on the next unfamiliar workflow?
CONFIRMEDFinal pedagogical extension. Completion means the learner is ready to study new models/modules independently without another foundational course.
Explain the architecture without Queue Prompt
- Name the major modules and their responsibilities.
- Show the data plane and control plane.
- Show the active route, a bypassed branch and a selector-controlled alternative.
- Explain one module as INPUT → PROCESS → CHECKPOINT → RETURN.
Perform a controlled production run
- Choose the mode deliberately and record effective controls.
- Lock the seed.
- Save intermediate checkpoints.
- Change exactly one variable and create an A/B comparison.
Create one deliberate failure and find it upstream
- For example: wrong selector, excessive denoise, poor mask edge or bypassed required module.
- Do not search the whole canvas: move from the symptom to the first incorrect checkpoint.
- After fixing it, repeat the same seed and prove the change with comparison.
Explain the workflow in your own words
If you can explain to another person why controls, selectors, latent, mask, ControlNet, PEOPLE module and final refinement exist, you are no longer merely running someone else’s workflow. You understand the system.