Jev project rule selection checks whether a supplied instruction belongs in the current task context. The model reads the task, an optional changed-file path and one rule description. It returns Apply rule, Skip rule or Missing context. The page evaluates applicability; it does not inspect the repository or determine whether an edit follows the rule.
A checkout calculation needs payment instructions even when the request says only 'fix the bug.' A changed path such as src/checkout/discount.ts supplies evidence that the vague request lacks. Conversely, building a production bundle on a laptop does not mean deploying it. A release rule that excludes local builds should stay out of that task.
The source is Elia Alberti's post about jev-rules, a plugin that supplies relevant project context. We built an independent exercise with synthetic tasks and a preview-only consumer. The maintainer's implementation uses its own questions, hooks and delivery policy. This page does not install that plugin, reproduce its measurements or claim that selecting instructions enforces them.