Job — keep names honest
One convention, stated once, applied to everything
A project sets its file prefix and its versioning mode, and every delivery in that project inherits them. Consistent naming is what makes the rest of the pipeline — and the console — predictable.
- Automatic renaming to the show's convention with prefix enforcement
- Sequential or date-based versioning, chosen per project
- Deliverable identifiers that drive routing and visibility
- Slot ranges, show order and reservations so a slot can be claimed before content arrives
Boundary CueCheck validates and delivers. It does not transcode content into spec on your behalf.
Interface detail from the accepted view — the project's file prefix and versioning mode, with the format of each option written next to it.