Bloom is a useful counterweight to tool output. The compiler can say a program is well-formed; a learner still needs to
name the concept, explain it, use it, pull it apart, judge it, and make something new with it. The three Navigator
workshops already use that progression because it makes the participant, not the software, the actor.
Use the same ladder on a proposed change. Can we remember the rule it touches? Understand why the rule exists?
Apply it to one real path? Analyze a failure? Evaluate the trade-off? Create a smaller, clearer version?
If we cannot explain a patch at those levels, we do not yet own it.