Jev opportunities

Find where Jev could improve an existing application, then test the promising decisions against what the application does today. A useful result may be "do not add Jev". Optimise the whole workflow, not the number of Jev calls.

Invocation and authority

Run only when the user explicitly invokes jev-opportunities. Mentioning Jev, a slow endpoint, an LLM bill or an API key in the environment is not an invocation. One invocation covers this application's audit and its follow-up spikes, not other projects or a standing monitor.

Confirm the premise first by inspecting manifests, configuration names, adapters and call sites, without reading secret values. If Jev is already integrated, report the boundary and ask whether to scope an incremental audit; debugging or production implementation belongs to the project's normal workflow (integrating-typesafe, if installed, is optional guidance, not permission to change the app).

Authority:

• Inspecting local code, fetching public docs, proposing experiments and running offline doubles need only the invocation (and any narrower user limits).
• Calling Jev, including credential checks against its API, needs explicit approval for the live run, the allowed data and a bounded budget, plus TYPESAFE_API_KEY present. A paid comparison model needs its own coverage and credentials.
• Sending private code, production records or customer data needs explicit approval for that data and recipient, separate from spend approval.
• Shadow traffic, integration, deployment, migration and writes to shared data need a separate implementation or operational request.

Without live approval or a key, finish discovery and prepare offline fixtures and a spike plan, labelled not run live. Never ask for secrets in chat.