Competencies, Evidence, and Remediation

Score each gate: 0 absent/invalid; 1 partial or materially prompted; 2 independently correct with assumptions, evidence and limits; 3 also defends a changed case and a plausible alternative. Every gate needs at least 2. No average substitutes for a missing failure, state or compatibility contract.

Gate	Competency	Practice	Assessment
C01	Specify preserved observations	P01,P03	A01
C02	Characterize numeric policy	P02,P05	A02
C03	Introduce a controlled seam	P04	A03
C04	Separate refactor and repair evidence	P15,P20	A04
C05	Preserve extraction/inline semantics	P06,P07	A05
C06	Preserve phase and error order	P09,P10	A06
C07	Evaluate conditional restructuring	P11–P13	A07
C08	Maintain mixed-client state	P16,P18	A08
C09	Handle uncertain external effects	P17	A09
C10	Defend compatibility and recovery	P08,P14,P19	A10

Passing all five labs is required but does not demonstrate a refactoring process: the untouched starter already passes. Review the learner's diffs, intermediate checks and design explanation. Copying the final reference is not process evidence.

Complete the three experiments and project. Repair weak gates with a fresh case. After 7–14 days, recheck the weakest gate and another selected gate without the key. Record self-assessment separately from independent review and identify assistance.