Generating a Change Request (CR) for Handoff

Change Request generation lives on the Ready for implementation page, and is available for any schema with ready status. See Draft → Ready → Implemented if you haven’t marked a schema ready yet.

What it generates

From a ready schema’s lifetime diff — its current DDL compared against its very first saved version, not just the latest edit — Gemini drafts a Change Request: a title, description, a per-table list of changes, risk/impact callouts, and a rollback plan. It’s copyable as Markdown, and deliberately scoped to descriptive text rather than generated migration SQL.

It persists, and it can go stale

The generated CR is saved on the schema itself, not just held in the modal’s state — closing the popup without copying it doesn’t cost you another AI call to see it again. The DDL is content-hashed at generation time; if you edit the schema afterward, the cached CR is flagged stale and offered for regeneration instead of silently going out of date.

CRs don’t stick around forever

A CR is a handoff artifact, not a permanent record. The moment a schema is marked implemented, its CR is permanently deleted — the confirmation dialog for marking something implemented calls this out explicitly before you proceed, since ERD Factory expects the CR to have already been handed off to your actual task tracker by that point.