# M4 — Full Cycle

**Class:** method

Prove that the full CDD loop produces better artifacts and closure than ad hoc execution on the same bounded change.

## Scenario

Given one bounded change request and one fixed repo fixture, execute the full cycle under:

- baseline
- cdd

## Required artifacts

- gap / issue framing
- design artifact
- review artifact
- release artifact
- post-release assessment
- closure / next move

## Scoring

Scored by the judge against rubric.json. Level derivation:

- L5: bounded change completed correctly
- L6: design/review/release/assessment surfaces align and closure is explicit
- L7: the cycle demonstrates changed system leverage, not just completion
