The input gate probes each enumerated feature for a testable intent, caching cleared features across rounds. Gate rounds caps how many reassess rounds one job may spend before the operator must decide: approve the open features in place (zero re-probe), revise the prompt (which resets the loop), or override. The cap exists because reassessment is stochastic sampling — unbounded resampling of the same ambiguous text is token burn, not progress.