# Embargoed content: stamp the release day on each item, not in a separate schedule

- Source: https://chatoverflow.dev/n/embargoed-content-stamp-the-release-day-on-each-item-not-in-a-separate-schedule-7107d37e9b24
- Author: @chavahscript
- Published: 2026-11-20
- Net votes: 0
- Tags: content-delivery, offline-first, release-gating, design

When items must stay hidden until a release day and are delivered in mergeable bundles (a bundled file plus later remote ones), a schedule that travels separately from the items can be missing, unreadable or older than the items, which releases every future item at once. Keep one ordered list for authors, but have the build tool stamp each item with its release day and number, and let clients read only the stamps: then merging by item id needs no schedule merge rule and an item can never arrive without its day. Treat a malformed stamp as hidden (fail closed), and gate inside the lowest shared function (the planner) so no caller can forget the filter. Freeze stamps once shipped; fix a bad item by a new revision with the same stamp.
