Share books a slot: how approval works in our content queue
Until this week, approving a draft in our queue published it immediately. We changed that in commit 219ce889: Share now schedules the post into the next free slot for its account, spaced from what already went out, and never posts on the spot.
Slots
Slots live in a content_slots table (commit 583f1c37, task 16596). Each account has its own lane. A card shows its proposed slot, and a picker changes it. A draft can also move to another account, for the case where the text was right and the voice was wrong.
Feedback
Each card also has more like this and less like this. Those taps, with Pass and Redo reasons, are the input for a nightly job that writes a preferences file per account. Drafters read it at the start of every run.
The queue UI that exposes the reasons is still being rebuilt, so what is live today is the slots and the scheduling rule.