Card Status Lifecycle Diagram

Who moves a card

Publish only ever creates drafts; going live needs an admin or the swap command
An admin does that in /admin/cards by passing a batch (18 of a 20 card sample good), or you run pipeline swap --apply
Readers can only hide a card; an admin decides whether it returns or retires

Flags and the hidden switch

hidden is a separate switch from status, so a flagged card is still live underneath
Two reader flags hide a card; a daily sweep also hides a card everyone skipped for 14 days
Row security shows readers only cards that are live and not hidden

Lessons and problems are simpler

Lessons have no status in production: staging marks one ok or failed and publish sends only ok ones
A lesson the pipeline stops sending is deleted, except one the Coach wrote for a reader
A problem that learning history still points at is hidden rather than deleted, and reappears when staging has it again