Draft → Ready → Implemented: The Schema Review Workflow

Every saved schema carries a status: draft, ready, or implemented. New saves default to draft.

Draft ⇄ Ready

Once a schema has been saved at least once, a status pill appears in the top bar letting you toggle between draft and ready at any time — this direction is fully reversible, since it’s just marking a schema as “worth a look” rather than claiming anything actually shipped.

The Ready for implementation queue

Ready schemas across all of your projects show up in two places: a summary section on the Dashboard, and the dedicated Ready for implementation page, both showing a one-line +added -removed ~modified table summary — computed as a lifetime diff against the schema’s very first version, not just its most recent edit. This page is a to-do queue, not an archive: it only ever shows schemas that are currently ready.

Clicking a schema on this page opens a full diff review (table-level summary plus the raw-text diff), alongside controls to generate a Change Request and to mark the schema implemented.

Marking implemented

“Mark as implemented” is a deliberate, one-way “this actually ran” claim — separate from the draft/ready toggle, and only available from the Ready for implementation page. Because it permanently deletes any generated Change Request for that schema, you’ll get an explicit confirmation warning first. Once confirmed, the schema drops off the Ready for implementation queue — there’s no browsing list for implemented schemas on that page, and no in-app control to move it back to ready. The schema itself, its diagram, and its version history are completely untouched; only the generated CR text is removed.