Memory entry filed at the cross-campaign location
~/.claude/projects/-home-mfritsche-src/memory/feedback_characterize_before_change.md
and registered in that MEMORY.md index.
The lesson: when starting a campaign on a new substrate with a
known-good system, iter1 = characterize-and-baseline ONLY. Don't
bundle blockers into iter1; each blocker spawns its own iteration
(iter2/3/4) so each has its own Phase 1 success metric and outside-
team dependency. ampere-fourier iter1 is the worked example —
zero code change in Phase 6, 3 follow-up issues filed, 3 codecs
baseline-validated, ka#6 umbrella closed.
phase8_close.md is the campaign-level close artifact: phase-by-phase
summary table with file links + 3 iteration hand-offs + reference-
history FPS numbers for iter2/3/4 to anchor against.
The 8-phase loop terminates. iter1 closed.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
