Repository Jev policy: read current instructions and accepted ADR mapping; without adoption, do not consult. In an adopted host scope, use eligible Jev Recommend general/current before substantive work on new tasks or material task/capability changes. Skip unchanged continuations, confirmations, status and consultation itself. Adoption is not activation, processing consent or qualification. Require scoped processing authority, qualified hook/inventory/delivery and existing credentials. Use verified current availability and restrictions, not installed files, missing flags or a complete-inventory assumption. Honor explicit user choices, explicit-only rules, permissions and Plan/read-only limits. Send minimal non-sensitive summary and public capability cards; exclude secrets, customer data, paths, raw prompts/transcripts and tool results. Minimization is not guaranteed redaction. Validate returned IDs; retain host execution control. Follow references/network-access.md: on failure say no Jev recommendation was produced; native continuation is not Jev advice. Only host evidence establishes denial. No new retries, caches, setup, policy edits or alternate routes; no repeat prompts after denial or status for skipped messages.
