the recipe catalog.

Mystical assessment of engineering fate. Recommended for: project kickoffs, retrospective frame-setting, post-incident reflection, mandatory innovation days. Each card draws from the Major Arcana of Engineering — The Reluctant Refactor, Two of YAGNIs, The Hanged Migration, and so on. Compliance posture: spiritual.

Heartfelt confession of accumulated technical debt, addressed to the team. References real files in the current codebase. Suitable for: pre-rotation handoffs, end-of-quarter reflection, performance-review attachments. The maintainer means every word.

Iterative root-cause analysis applied to a single question, performed N times in sequence. Each pass reaches a more existential root than the previous. By pass 21, the root cause is "the human condition." Approved for: incident reviews, planning offsites, performance management.

Sequentially-numbered contrarian claims about modern software practice. The first 20% are mainstream-spicy; the last 20% are defensible only under squint. Recommended for: thought-leadership pipelines, conference CFPs, internal newsletters, the Friday all-hands.

Four-engineer debate panel. Greta (idealist), Marcus (jaded), Priya (pragmatist), Anonymous L8 (dismissive). They never agree. Closing minute provided by a meeting note-taker who has given up. Use for: architecture reviews, vendor evaluations, RFC discussions.

Each level is a review of the previous review. By level 8, the review is critiquing the epistemology of code review itself. Conclusion at all depths: the code is, on balance, fine. Recommended for: change-management workflows, audit preparedness, philosophical engineering practice.

Comprehensive migration plan to a framework the team has never used. Includes Gantt chart, risk matrix (4 risks per phase), budget estimate (six figures minimum), executive summary. Use for: roadmap planning, vendor-evaluation justifications, leadership offsites.

Single-elimination bracket of architectural patterns evaluated against the current codebase. Quarterfinals, semifinals, final, crowning. The winning architecture is celebrated with a Trophy Plate essay demonstrating that the current code already exemplifies it.