A hardware-industry release discipline where products ship on a fixed cadence (e.g., every six months or once a year), and features that aren't ready simply miss the train and wait for the next cycle — the release date itself never slips to accommodate them.
This inverts the usual software instinct to hold the release for a feature. It works because manufacturing, supply chain, and retail windows in hardware make the date itself far more rigid than any single feature; the same logic doesn't automatically transfer to software, where dates are usually the more negotiable variable (see Commit to Time Frames, Not Fixed Dates). Contrast with Continuous Deployment Cadence, and see "Feature Candidate" as Deliberate Anti-Commitment Framing for the software-side equivalent of deliberately not pre-committing a feature to a given release.